Network Manager Applet Cannot Edit Options/Connections As Normal User

Today I installed Network Manager, and Network Manager Applet in XFCE as a normal user. I followed the instructions on the Arch Network Manager Wiki to the best of my knowlage. The NM-Applet connects to my ethernet, and everything is fine. Untill that is, when I right click the NM Applet.
Once right clicked as a normal user, 'Enable Networking', and 'Enable Wireless' are greyed out and unselectable. Also, when I right click the applet and select 'Edit Connections' 90% of the clickable options are greyed out, including the options to 'Edit' or 'Delete' connections. The only clickable option not greyed out is 'Add' button.
Clicking Add brings up the 'Add New Connection Window', but again everything is greyed out. 'Available To All Users' is checked, but is greyed out also. But, starting XFCE as root, allows me to use the NM Applet with no restrictions, AKA none of the greyed out options. Everything works fine.This is my second day using Arch, so I am not sure where to go now.
It also may be of help ito say I haven't gotten a display manager, such as lightdm or gdm.
My guess is that root is listed under a group the 'jesse' isn't. Or maybe it has something to do with PolicyKit. I'm not sure. If someone could give me a set of clear instructions on how to fix this annoyance, it would be greatly appreciated. Thank You.
My Current Normal User Groups wrote: disk lp wheel uucp games network video audio optical storage scanner power users
My /etc/hosts file wrote:
# /etc/hosts: static lookup table for host names
#<ip-address>   <hostname.domain.org>           <hostname>
127.0.0.1              localhost.localdomain localhost jesse
::1                         localhost.localdomain localhost jesse
# End of file
My /etc/rc.conf wrote:
# /etc/rc.conf - configuration file for initscripts
# Most of rc.conf has been replaced by various other configuration
# files. See archlinux(7) for details.
# For more details on rc.conf see rc.conf(5).
DAEMONS=(alsa dbus syslog-ng crond ifplugd networkmanager bluetooth avahi-daemon acahi-dnsconfd avahi-dnsconfd fa$
# Storage
# USEDMRAID="no"
# USELVM="no"
# Network
# interface=eth0
# address=
# netmask=
# gateway=
My /etc/polkit-1/localauthority/50-local.d/org.freedesktop.NetworkManager.pkla wrote:Identity=unix-group:network
Action=org.freedesktop.NetworkManager.*
ResultAny=yes
ResultInactive=no
ResultActive=yes
Last edited by TriforceLZG (2012-09-02 13:43:23)

I found the solution, I had to install a Display Manager. Now everything is fine.

Similar Messages

  • Network-manager-applet cannot run!!!!!!!!!!

    Installed networkmanager and network-manager-applet, but I found it could not startup at boot time.....
    When I run nm-applet in terminal as normal user, it print:
    [yin@q ~]$ nm-applet
    ** (nm-applet:2168): WARNING **: <WARN> request_name(): Could not acquire the NetworkManagerUserSettings service.
    Error: (9) Connection ":1.39" is not allowed to own the service "org.freedesktop.NetworkManagerUserSettings" due to security policies in the configuration file
    When I run "sudo nm-applet", noting was wrong ,and the icon appeared in the panel right top.
    Another question:
    What's the difference between daemons in rc.conf and startup applications in gnome ?
    I add "networknamager"  in daemons line in rc.conf ,but I found there is a network manager entry in startup applications in gnome with the command : nm-applet --sm-disable.  Does they conflict ??
    Last edited by iamybj (2010-03-27 12:52:56)

    iamybj wrote:
    ngoonee wrote:You did not search the forums. Please do so before asking a question.
    I think if the question was resolved, it should be updated to the wiki....
    I find the wiki updating is very slow right now.
    You misunderstand how this community works.
    Users update the wiki, voluntarily. If you find a solution and feel its a common enough problem to post on the wiki, please do so.
    Also, if you can't even bother to do a forum search or google search before asking questions, this may not be the right distro for you. Please read http://wiki.archlinux.org/index.php/FAQ … se_Arch.3F, especially the 'do-it-yourself' part.

  • [xfce4] network-manager-applet not asking for Wifi password

    I am running XFCE with  the gnome network-manager-applet and kwallet as password storage and I do not want to use the gnome keyring because it is making many problems with my current setup.
    There are multiple ways to store passwords in NetworkManager. To save them plain in the config files is not an option for me. So I can put them in a password store or hack them in every time I want to connect.
    While the gnome network-manager-applet does not work with kwallet I accepted to do all the hackery every time.
    Problem: I even can not hack in the passwords.
    If I try to connect the connection is disconnected immediately. The logs say, that "The name org.freedesktop.secrets was not provided by any .service files".
    Long story short:
    - NetworkManager needs the dbus service "org.freedesktop.secrets" to read passwords (via password store or via prompt)
    - kwallet does not announce "org.freedesktop.secrets" - this is done by the nm-plasma applet (which I can not run without hacking XFCE)
    - gnome-keyring announces itself as a secret agent but does not work with my setup
    Do I need to write my own secret agent which only shows a password prompt and parses the input to NM or is there any option/tool/patch/hack/miracle that I have missed to use kwallet with gnome network-manager-applet or to get a password prompt without installing gnome-keyring?
    Thanks in advance
    Last edited by frederik (2015-04-14 15:30:24)

    add this to your start-up: gnome-keyring-daemon --components=gpg
    Edit: and install gnome-keyring ofc
    Last edited by MakeTheGOD (2015-04-28 05:24:33)

  • [SOLVED] network-manager-applet not found

    Hi, I'm quite noob here, and I'm trying to install network-manager-applet with no luck;
    So far I've done
    # pacman -S network-manager-applet
    and I got
    resolving dependencies...
    looking for inter-conflicts...
    Targets (1): network-manager-applet-0.8-1
    Total Download Size: 1.01 MB
    Total Installed Size: 4.35 MB
    Proceed with installation? [Y/n] y
    :: Retrieving packages from extra...
    error: failed retrieving file 'network-manager-applet-0.8-1-x86_64.pkg.tar.gz' from mi.mirror.garr.it : Not Found
    error: failed retrieving file 'network-manager-applet-0.8-1-x86_64.pkg.tar.gz' from ftp.nluug.nl : Not Found
    error: failed retrieving file 'network-manager-applet-0.8-1-x86_64.pkg.tar.gz' from ftp.hosteurope.de : Not Found
    error: failed retrieving file 'network-manager-applet-0.8-1-x86_64.pkg.tar.gz' from ftp-stud.hs-esslingen.de : Not Found
    error: failed retrieving file 'network-manager-applet-0.8-1-x86_64.pkg.tar.gz' from archlinux.puzzle.ch : Not Found
    error: failed retrieving file 'network-manager-applet-0.8-1-x86_64.pkg.tar.gz' from ftp.surfnet.nl : Not Found
    warning: failed to retrieve some files from extra
    error: failed to commit transaction (Not Found)
    Errors occurred, no packages were upgraded.
    so I tried to download the package itself and install it with
    pacman -U network-manager-applet-0.8-2-x86_64.pkg.tar.xz
    and the answer was
    loading package data...
    checking dependencies...
    error: failed to prepare transaction (could not satisfy dependencies)
    :: network-manager-applet: requires mobile-broadband-provider-info
    what to do?
    i cannot find in the repos the package mobile-broadband-provider-info
    thank you in advance
    Last edited by lsk (2010-03-10 10:15:21)

    Update your system - "pacman -Syu".  The clue is that the file you manually downloaded is different to the one pacman is trying to get.

  • [SOLVED]Network Manager Applet and nmcli failing after GCC upgrade

    Hi All,
    So I went to update my system today and there were only like 8 or 9 updates. Like many other people I had an issue with gcc and pacman. To fix this I ran
    pacman -S gcc
    Then I ran:
    pacman -Su
    which updated pacman itself. On reboot though I noticed network manager applet was unable to find any of my network devices despite the fact that network manager was running and I had an IP address. I killed nm-applet and re-ran it and it spewed errors about not being able to connect to network manager. I tried running nmcli and it did the same thing. However, when I run nmcli as root it works. Looking at the arch wiki they suggest you be a part of the wheel and network group which I made sure I was. Everything was working up until I ran those two updates though. Anyone else have this happen or have any idea what is wrong?
    Thanks,
    Hemmar
    EDIT: Never mind - a patch was released for consolekit which fixes the problem.
    Last edited by hemmar (2012-04-13 00:36:49)

    Hi guz46
    I have already tried removing the ! and the same thing happened ... but I realised today that I was being automatically connected to "Auto eth0" despite there being no cable present. When automatic connection was disabled on "Auto eth0" my 3G connection (ppp0) connected fine.
    Could you clarify that the preferred set-up in the /etc/rc.conf for the interfaces is without the !. The Wiki for networkmanager says to disable them, but then states that some may need to be reenabled with no explanation. The purpose of this confuses me!
    Thanks for you help anyways,
    Scott
    EDIT:
    I appear to have fixed my problem with the auto connection on the various interfaces by updating my /etc/rc.conf file to:
    #Static IP example
    #eth0="dhcp"
    ppp0="dhcp"
    wlan0="dhcp"
    eth0="dhcp"
    INTERFACES=(ppp0 wlan0 eth0)
    Thus ensuring that I can connect in order of preference.
    Last edited by ScottArch (2009-11-03 18:48:47)

  • [SOLVED] Network Manager Applet

    One of the things I got used to from Ubuntu is the network manager applet, which allows managing connections with ease. As instructed in the Wiki, I tried installing it with the following commands:
    pacman -S networkmanager
    pacman -S network-manager-applet
    And then launched it by typing
    nm-applet
    But this comes up in the terminal:
    (nm-applet:1518): Gdk-CRITICAL **: gdk_visual_get_red_pixel_details: assertion `GDK_IS_VISUAL (visual)' failed
    (nm-applet:1518): Gdk-CRITICAL **: gdk_visual_get_green_pixel_details: assertion `GDK_IS_VISUAL (visual)' failed
    (nm-applet:1518): Gdk-CRITICAL **: gdk_visual_get_blue_pixel_details: assertion `GDK_IS_VISUAL (visual)' failed
    ** Message: applet now removed from the notification area
    (nm-applet:1518): libnotify-WARNING **: Failed to connect to proxy
    ** (nm-applet:1518): WARNING **: get_all_cb: couldn't retrieve system settings properties: (25) Launch helper exited with unknown return code 1.
    ** (nm-applet:1518): WARNING **: fetch_connections_done: error fetching connections: (25) Launch helper exited with unknown return code 1.
    ** (nm-applet:1518): WARNING **: Failed to register as an agent: (25) Launch helper exited with unknown return code 1
    ** Message: applet now embedded in the notification area
    ** Message: applet now removed from the notification area
    In the notification area the icon looked like it was going to show up, but it's removed immediately.
    I'm not even sure if I can connect to a wireless connection without this, can I? I wouldn't mind using a different method for connecting to my wireless connection, just as long as it works and it automatically connects when I login. So if anyone has got a better idea, please share it with me. In the mean time, what would I need to do to fix this and have the network manager applet working?
    Last edited by faviouz (2011-09-15 15:52:50)

    faviouz wrote:
    Thanks for the quick reply dodo3773!
    It worked excellently! I also added networkmanager to the daemons array and it loads on boot now, which is great.
    No problem. Glad to help. As karol said the wiki has many tips and tricks for almost anything that you need to get your system up and running. Make sure to read through the rest of the networkmanager one in regards to  gnome-keyring, groups, etc.. Take care and welcome to Arch Linux Forums.

  • Weird Network-manager-applet icon

    I have installed network-manager-applet 0.9.8.8-1 and a weird icon is displayed: a question mark
    What does it mean?

    toni wrote:
    Inxsible wrote:its not connected to any network ?
    I am connected correctly and I have Internet connection without problems but I do not know why is it showing a question mark...
    Ok, but you didn't mention that in your first post and sadly, I cannot read minds.
    In any case, its a bug as has been posted above.

  • Network manager in xfce doesn't connect but wifi-menu does?

    I may be misunderstanding how to use this since I've never done wireless from the command line before, but here is my situation:
    I just installed arch on my Acer Aspire One and used both the wired and wireless from the command line. I had never done wireless from the command line before and just followed the Beginners Guide and used wifi-menu to select the network to connect to. It was very very smooth and connected me in seconds. After installing xfce I decided I wanted a tray icon for selecting wireless stuff and so I installed networkmanager and network-manager-applet. After starting nm-applet it reported my wireless as disconnected (even though it was connected) and when I asked it to connect to my network it was unable to connect. I restarted the computer and still no success. While I can get by with wifi-menu, it would be awfully nice if I could get network manager to work with xfce. Does anyone have any thoughts on this?
    Thanks in advance.

    I switched to using wicd and after a little while of using it it seems to work pretty well. It works significantly better than NetworkManager and doesn't drop connections very often so long as the signal is good.
    My one complaint is that every so often a process called wicd-monitor likes to start using 100% cpu on one of my cores. Since this is a netbook and power is critical, I usually end up killing the process or restarting wicd so that it stops draining my battery.

  • Network Manager applet won't show up on my desktop

    I use wifi-menu to connect to wifi, even if I'd like to use NetworkManager since I used it in debian. Anyways, I have NetworkManager installed, and xfce tells me it's in the systray except it's not. This is a pretty huge problem for me, especially because my wifi drivers tend to disconnect and wifi-menu doesn't help that much when I have an internet that doesn't work. In Debian, if my drivers disconnected all I'd have to do is reconnect from NetworkManager and they'd magically work again.

    waddicto wrote:However, I have a different problem now, I have two network applets in my systray.
    The network-manager-applet package installs the startup file: /etc/xdg/autostart/nm-applet.desktop
    Are you starting up another nm-applet somewhere else?

  • Network-manager-applet/hal upgrade.

    Is anybody else having issues after the latest upgrade from gnome-network-manager to network-manager-applet?
    After the upgrade + reboot, the networkmanager icon doesn't appear at start up, and the hal upgrade appears to have done something as well as my Windows partition no longer is mounted, my external drive isn't recognized, and Shutdown and Reboot do not appear on the Shutdown... menu
    Running x86_64

    proxima_centauri wrote:I already tryed downgrading both hal and back to gnome-network-manger.
    I still have no networkmanger icon at start up, but internet still is functional.
    My NTFS partition now shows after going back to old hal, but my external drive still isn't recognized, can't manually mount because there is no /dev/sdb showing up.
    the network icon problem: have you installed network-manager-applet?
    the hal problem: try modify /etc/PolicyKit/PolicyKit.conf as root
    add the following between <config version="0.1"> and </config>
    <match user="$USER">
    <match action="org.freedesktop.hal.storage.*">
    <return result="yes"/>
    </match>
    <match action="hal-storage-mount-fixed-extra-options">
    <return result="yes" />
    </match>
    <match action="hal-storage-mount-removable-extra-options">
    <return result="yes" />
    </match>
    </match>
    where $USER is your username. restart hal.
    and then modify /usr/share/hal/fdi/policy/10osvendor/20-storage-methods.fdi as root
    find the following and modify it. the two lines with <merge key> is what added.
    <!-- allow these mount options for ntfs -->
    <match key="volume.fstype" string="ntfs">
    <match key="/org/freedesktop/Hal/devices/computer:system.kernel.name" string="Linux">
    <merge key="volume.fstype" type="string">ntfs-3g</merge>
    <merge key="volume.policy.mount_filesystem" type="string">ntfs-3g</merge>
    <append key="volume.mount.valid_options" type="strlist">uid=</append>
    <append key="volume.mount.valid_options" type="strlist">gid=</append>
    <append key="volume.mount.valid_options" type="strlist">umask=</append>
    <append key="volume.mount.valid_options" type="strlist">dmask=</append>
    <append key="volume.mount.valid_options" type="strlist">fmask=</append>
    <append key="volume.mount.valid_options" type="strlist">locale=</append>
    <append key="volume.mount.valid_options" type="strlist">utf8</append>
    </match>
    the original post is at http://www.linuxsir.org/bbs/thread344125.html. it's in chinese.
    hope this works.

  • Network Manager get ip but no connection to the internet

    Hi guys,
    I'm new to Arch, and first of all I must say that I think I'm going to love it :-)
    Never seen a package manager so fast to install a lot of packages! And it's kinda cool to have everything under control.
    But here is a problem I don't have under control : I've installed networkmanager following the wiki on my kde4 desktop and I've got a weird behaviour. Everything seems to work perfectly, nm-applet launch automaticaly and connect to my network. I can see that my wireless card got an ip using ifconfig and iwconfig show me associated. BUT none of my apps (firefox, konqueror, ping...) can see that I'm connected!
    So I've made a little script to connect me by hand using iwconfig and dhcpcd but that's not a real solution since I use a lot of different wireless network...
    So if any of you has an idea that will be nice ;-)
    A little bit more about my configuration :
    rc.conf :
    #eth0="dhcp"
    #wlan0="dhcp"
    INTERFACES=(lo !eth0 !wlan0)
    I've tried with and without the # before the two interface without any change.
    DAEMONS=(syslog-ng !network netfs crond hal kdm networkmanager dbus)
    Tried with both !network and network without any change too.
    Last edited by toflames (2009-07-21 15:46:36)

    Ifpluged is for wired networking...
    In fact this is not a DHCP problem, as I get an IP without any problem. But I've tried this too, without any change.
    The result of NetworkManager --no-daemon is interesting, here with an open network near me, the one that works out of the box with NM :
    NetworkManager: <info> (wlan0): device state change: 1 -> 2
    NetworkManager: <info> (wlan0): bringing up device.
    NetworkManager: <info> (wlan0): preparing device.
    NetworkManager: <info> (wlan0): deactivating device (reason: 2).
    NetworkManager: <info> (wlan0): device state change: 2 -> 3
    NetworkManager: <info> (wlan0): supplicant interface state: starting -> ready
    NetworkManager: <info> Activation (wlan0) starting connection 'Auto bbox2-d719'
    NetworkManager: <info> (wlan0): device state change: 3 -> 4
    NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
    NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
    NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
    NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
    NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
    NetworkManager: <info> (wlan0): device state change: 4 -> 5
    NetworkManager: <info> Activation (wlan0/wireless): connection 'Auto bbox2-d719' requires no security. No secrets needed.
    NetworkManager: <info> Config: added 'ssid' value 'bbox2-d719'
    NetworkManager: <info> Config: added 'scan_ssid' value '1'
    NetworkManager: <info> Config: added 'key_mgmt' value 'NONE'
    NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
    NetworkManager: <info> Config: set interface ap_scan to 1
    NetworkManager: <info> (wlan0): supplicant connection state: scanning -> disconnected
    NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning
    NetworkManager: <info> (wlan0): supplicant connection state: scanning -> associating
    NetworkManager: <info> (wlan0): supplicant connection state: associating -> associated
    NetworkManager: <info> (wlan0): supplicant connection state: associated -> completed
    NetworkManager: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'bbox2-d719'.
    NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
    NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
    NetworkManager: <info> (wlan0): device state change: 5 -> 7
    NetworkManager: <info> Activation (wlan0) Beginning DHCP transaction.
    NetworkManager: <info> dhcpcd started with pid 9392
    dhcpcd: version 5.0.6 starting
    NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
    NetworkManager: <info> DHCP: device wlan0 state changed (null) -> preinit
    dhcpcd: wlan0: rebinding lease of 192.168.1.65
    dhcpcd: wlan0: broadcasting for a lease
    dhcpcd: wlan0: offered 192.168.1.14 from 192.168.1.1
    dhcpcd: wlan0: acknowledged 192.168.1.14 from 192.168.1.1
    dhcpcd: wlan0: checking for 192.168.1.14
    dhcpcd: wlan0: leased 192.168.1.14 for 86400 seconds
    NetworkManager: <info> DHCP: device wlan0 state changed preinit -> bound
    NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) scheduled...
    NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) started...
    NetworkManager: <info> address 192.168.1.14
    NetworkManager: <info> prefix 24 (255.255.255.0)
    NetworkManager: <info> gateway 192.168.1.1
    NetworkManager: <info> hostname 'inflames'
    NetworkManager: <info> nameserver '192.168.1.1'
    NetworkManager: <info> domain name 'home'
    NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
    NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) complete.
    NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
    NetworkManager: <info> (wlan0): device state change: 7 -> 8
    NetworkManager: <info> Policy set 'Auto bbox2-d719' (wlan0) as default for routing and DNS.
    NetworkManager: <info> Activation (wlan0) successful, device activated.
    So dhcpcd is setting up the route as it should. But here is the result with my wep encrypted network :
    NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
    NetworkManager: <WARN> nm_dhcp_manager_handle_event(): Received DHCP event from unexpected PID 9392 (expected 0)
    NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
    NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
    NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
    NetworkManager: <info> (wlan0): supplicant connection state: completed -> disconnected
    NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
    NetworkManager: <info> (wlan0): device state change: 4 -> 5
    NetworkManager: <info> Activation (wlan0/wireless): access point 'Auto SpeedTouchDBBA4B' has security, but secrets are required.
    NetworkManager: <info> (wlan0): device state change: 5 -> 6
    NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
    NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
    NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
    NetworkManager: <info> (wlan0): device state change: 6 -> 4
    NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
    NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
    NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
    NetworkManager: <info> (wlan0): device state change: 4 -> 5
    NetworkManager: <info> Activation (wlan0/wireless): connection 'Auto SpeedTouchDBBA4B' has security, and secrets exist. No new secrets needed.
    NetworkManager: <info> Config: added 'ssid' value 'SpeedTouchDBBA4B'
    NetworkManager: <info> Config: added 'scan_ssid' value '1'
    NetworkManager: <info> Config: added 'key_mgmt' value 'NONE'
    NetworkManager: <info> Config: added 'auth_alg' value 'OPEN'
    NetworkManager: <info> Config: added 'wep_key0' value '<omitted>'
    NetworkManager: <info> Config: added 'wep_tx_keyidx' value '0'
    NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
    NetworkManager: <info> Config: set interface ap_scan to 1
    NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning
    NetworkManager: <info> (wlan0): supplicant connection state: scanning -> associating
    NetworkManager: <info> (wlan0): supplicant connection state: associating -> associated
    NetworkManager: <info> (wlan0): supplicant connection state: associated -> completed
    NetworkManager: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'SpeedTouchDBBA4B'.
    NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
    NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
    NetworkManager: <info> (wlan0): device state change: 5 -> 7
    NetworkManager: <info> Activation (wlan0) Beginning DHCP transaction.
    dhcpcd: version 5.0.6 starting
    dhcpcd: wlan0: rebinding lease of 192.168.1.14
    NetworkManager: <info> dhcpcd started with pid 9844
    NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
    NetworkManager: <info> DHCP: device wlan0 state changed normal exit -> preinit
    dhcpcd: wlan0: NAK: Lease is invalid. from 192.168.1.254
    NetworkManager: <info> DHCP: device wlan0 state changed preinit -> (null)
    dhcpcd: wlan0: broadcasting for a lease
    dhcpcd: wlan0: offered 192.168.1.65 from 192.168.1.254
    dhcpcd: wlan0: acknowledged 192.168.1.65 from 192.168.1.254
    dhcpcd: wlan0: checking for 192.168.1.65
    dhcpcd: wlan0: leased 192.168.1.65 for 86400 seconds
    NetworkManager: <info> DHCP: device wlan0 state changed (null) -> bound
    NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) scheduled...
    NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) started...
    NetworkManager: <info> address 192.168.1.65
    NetworkManager: <info> prefix 24 (255.255.255.0)
    NetworkManager: <info> nameserver '192.168.1.254'
    NetworkManager: <info> domain name 'lan'
    NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
    NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) complete.
    NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
    NetworkManager: <info> (wlan0): device state change: 7 -> 8
    NetworkManager: <info> Activation (wlan0) successful, device activated.
    NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
    It's easy to see that NM does not set up the route as it does with the open network...
    I'm thinking more and more about posting a bug report about this. What do you think?
    Edit : I forgot to mention that I was using NM on various distributions (ubuntu, fedora, opensuse...) without any problem on this network.
    Last edited by toflames (2009-07-23 17:11:42)

  • No Network Manager Applet

    So I just installed Arch on my desktop, I am wireless, but I have made sure my wireless card is properly configured. I have gone into the settings menu and looked at my applets and it says the applet is there but it never works or shows up. For whatever reason, no matter how many desktop environments I try I never have a network manager. I've tried KDE, Gnome, XFCE, and Cinnamon and none of them have it. Ordinarily I wouldn't mind connecting to wifi through the terminal, but when I go back to school, the network there requires a username to log in which according to my experience is not possible through the terminal. If it is please correct me and/or offer me a suggestion. Thanks in advance

    TheNeXus84 wrote:
    I am using an Intel Centrino Advanced N6205 wireless card.
    the output of my systemctl status NetworkManager command is as follows:
    [root@ArchLinux cj]# systemctl status NetworkManager
    NetworkManager.service - Network Manager
       Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled)
       Active: active (running) since Sun 2013-12-22 20:42:57 EST; 23s ago
    Main PID: 645 (NetworkManager)
       CGroup: /system.slice/NetworkManager.service
               └─645 /usr/bin/NetworkManager --no-daemon
    Dec 22 20:43:11 ArchLinux NetworkManager[645]: <info> Config: set interface ...1
    Dec 22 20:43:13 ArchLinux NetworkManager[645]: <info> (wlp5s0): supplicant i...d
    Dec 22 20:43:13 ArchLinux NetworkManager[645]: <info> (wlp5s0): supplicant i...d
    Dec 22 20:43:13 ArchLinux NetworkManager[645]: <warn> Connection disconnecte...)
    Dec 22 20:43:13 ArchLinux NetworkManager[645]: <info> (wlp5s0): supplicant i...d
    Dec 22 20:43:13 ArchLinux NetworkManager[645]: <warn> Connection disconnecte...)
    Dec 22 20:43:13 ArchLinux NetworkManager[645]: <info> (wlp5s0): supplicant i...g
    Dec 22 20:43:13 ArchLinux NetworkManager[645]: <info> (wlp5s0): supplicant i...d
    Dec 22 20:43:14 ArchLinux NetworkManager[645]: <info> (wlp5s0): supplicant i...g
    Dec 22 20:43:17 ArchLinux NetworkManager[645]: <info> (wlp5s0): supplicant i...d
    Hint: Some lines were ellipsized, use -l to show in full.
    UPDATE: I fixed the problem. I had to enable DHCPCD. sorry to be a bother to you all but thanks for the help and support.
    EDIT: upon rebooting my previous problem has occurred again.
    Make sure that you have done
    systemctl enable NetworkManager
    as well as
    systemctl start NetworkManager
    - also when you ran dhcpcd how did you do it?  Your network interface is wlp5s0 so you need to have dhcp running for that interface -
    systemctl start [email protected]
    will start it if it is not started, and
    systemctl enable [email protected]
    will ensure it starts after booting up. However I never needed to start dhcpcd at all when using NetworkManager.
    There are occasions when the relative timing of different services does not allow some services to start properly - and then occasionally you need to add in some items to the NetworkManager service file to tell it to wait until the network is up first, if there are delays in the network starting at boot time but that can be sorted out once the basic services are set to start at boot.
    Last edited by mcloaked (2013-12-23 18:01:46)

  • [Gnome 3] Network Manager can only create system connections

    Hello,
    Coming from ubuntu, I installed Arch with Gnome 3 (didn't like unity). I have a small annoyance with Network manager from [testing]. When I select a wireless network, it asks for my sudo password and creates a system connection under /etc/NetworkManager/system-connections. Even when unchecking "Available for all users" in nm-connection-editor afterwards, the settings are kept in /etc instead of gconf/dconf and gnome-keyring as was the case in ubuntu (don't know if that was also the case in arch with gnome 2).
    Of course, I can instruct PolicyKit to not ask for a password when modifying the connections, but I'd prefer to keep my keys in gnome-keyring instead of unencrypted files. As the single user of the system, I do not need system connections.
    Any ideas?

    Seems like this is an upstream change in nm 0.9, and no workaround that I know existed for it.

  • Cannot edit sudoers file in single user mode.

    I did not back up my sudoers file on my pro.
    I made a change to it, adding my "test" user to be able to use sudo, but upon restarting, it didn't work, and I cannot edit the file via cd in single user mode.
    I mounted the drive, changed permissions, but it seems that I don't have the option to use vi, visudo, vim.
    Thanks for the help.

    I mounted the hdd using the command below.
    I then made sure I could get to the file by cd to it.
    Then once I was there, i would attempt to type vis <tab> to complete, and visudo does not show up. Typed in visudo, nothing. This was on a brand new mb pro. I can wipe it out, but I would rather figure out why its not working.
    The reason for all this is I have to give it to a user at my job. We don't want them to have admin rights to install anything they want, but they need to use sudo in X11 for compiling and such. I read online that I can edit/add their username to the sudoers file, and allow them the right to sudo for compiling, starting apache on their laptops, etc.
    Thanks.

  • SSDD - Network-Manager-Applet never works for me...

    So I've discovered the wonders of E17 and everything works wine, apart from a few minor bugs of course, but nothing to do with networking.
    Just to be sure I've been following the instructions on the wiki, but though it would seen that nm-apples is actually started, it does not show up in the taskbar, which kinda defeats the purpose.
    I should mention of course that to the best of my abilities I've checked and rechecked that there's nothing wrong with my network interfaces. After much meddling about I even succeeded in compiling connman, which seem to work, only my wireless is disable in the process and I can't seem to enable it.
    When I log out and try a: "ip link set wlan0 up" and all I get is this:
    RTNETLINK answers: operation not possible due to RF-kill
    which of course is of no help at all.
    I don't know where else to go from here, apart from one of those Linus distributions where the wireless is more or less the only thing that works.
    I don't really know what I'm asking for, but I'm out of ideas and certainly out of my mind to go trough this every single time and either ending up creating the connection manually every time it's needed, or something else than Arch.
    Mind you I'm not saying that this is anyone's fault but my own, only I can not see how it can be my own. I've tried just about everything, including praying to various gods.!
    Well, enough ranting. If anyone have any suggestion, they are certainly welcome.
    Best regards.
    edit:
    I should be sure to mention that the rf-kill issue is not a hardware switch issue. The issue does not exists using networkmanager.
    Last edited by zacariaz (2012-08-23 16:49:34)

    I've had similar issues in the UK with my ATV. I am able to stream photos and music from any of the other devices around the house, via wi-fi to it, but movies have been hit and miss. We have had 3 that have stopped during playback, telling us it will be another 1 1/2 hrs before it has loaded. We have ended up trying the following:
    Resetting the ATV
    Restoring it to factory settings
    Trying different wi-fi channels
    Using Ethernet (it's about a foot away)
    Downloading movies way in advance of watching them
    Our wi-fi signal is full strength with an average rate of 9.8MB and I don't have issues with drop-outs or impaired performance on any other device as far as I know. I've had to resume movies by renting them again on our Virgin Media service and get refunds from the iTunes store...
    It's been really frustrating, but speaking to experts in my local Apple store and finally, Applecare, it appears that I may have a rogue unit. I'm sending it back for them to check as it is still under warranty.
    Maybe you have similar?

Maybe you are looking for