Hide Forgot
Description of problem: NetworkManager applet offers two options on eth0 (system eth0 + a statically configured network), and a lot of WiFi networks. But selecting either has absolutely no effect. This is under XFCE (Gnome is completely hosed right now) Version-Release number of selected component (if applicable): NetworkManager-0.8.2-6.git20101117.fc15.x86_64 NetworkManager-gnome-0.8.2-6.git20101117.fc15.x86_64 How reproducible: Always Steps to Reproduce: 1. Click on nm-applet 2. 3. Actual results: Right click: Almost everything greyed out Left click: All networks are "disconnected", no way to bring them up Expected results: Additional info: I'm using Realtek's driver for the rtl8192se WiFi card. This did work before with Fedora rwahide.
I just tried to "ifup eth0", and got: ]# ifup eth0 Active connection state: activating Active connection path: /org/freedesktop/NetworkManager/ActiveConnection/0 ** (process:1597): WARNING **: _nm_object_get_property: Error getting 'State' for /org/freedesktop/NetworkManager/ActiveConnection/0: (19) Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist state: unknown Error: Connection activation failed.
Strangely, on this other machine (Samsung N210 under legacy Gnome, not XFCE) NM works just fine.
(In reply to comment #2) > Strangely, on this other machine (Samsung N210 under legacy Gnome, not XFCE) NM > works just fine. A difference is that the non-working one (Toshiba notebook, all up to date) shows in /var/log/messages on boot: Feb 15 13:24:06 laptop15 NetworkManager[901]: <error> [1297787046.157902] [nm-manager.c:1368] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name Feb 15 13:24:06 laptop15 NetworkManager[901]: <error> [1297787046.160440] [nm-manager.c:1368] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name It would be nice to know where those strange settings/names come from/are stored...
Digging around, the haldaemon service hadn't started. Starting it didn't help, anyway.
@Horst hal has been deprecated wrt NM. Hitting this on my rawhide system, deleting profile ( gconf setting ) helped on one system. from var/log/messages Feb 24 17:28:10 localhost NetworkManager[3993]: <error> [1298548690.772040] [nm-manager.c:1368] user_proxy_init(): could not init us er settings proxy: (3) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name Feb 24 17:28:10 localhost NetworkManager[3993]: <error> [1298548690.774347] [nm-manager.c:1368] user_proxy_init(): could not init us er settings proxy: (3) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name from xsession-erros ** (nm-applet:20173): WARNING **: <WARN> activate_connection_cb(): Connection activation failed: No user settings service available
from ./src/nm-manager.c /* Ensure the request to activate the user connection came from the * same session as the user settings service. FIXME: use ConsoleKit * too. */ if (!priv->user_proxy) { g_set_error (error, NM_MANAGER_ERROR, NM_MANAGER_ERROR_INVALID_SERVICE, "%s", "No user settings service available"); goto out; } seems like an issue with ConsoleKit
In NM 0.8 there are two settings services, or dbus services that save/store network configuration and passwords. One is NM itself; the other (the "user" service) is nm-applet or knetworkmanager or whatever. If that's not running, you don't have user settings and you might get that message. If you're trying to fast-user-switch, NM 0.8 and earlier don't support fast user switching, an issue that's been remedied in NM 0.9. Also, is this session that has the problem a root desktop UI session?
(In reply to comment #5) > @Horst > > hal has been deprecated wrt NM. > > Hitting this on my rawhide system, deleting profile ( gconf setting ) helped > on one system. Moving ~/.gconf out of the way doesn't help. (In reply to comment #7) > In NM 0.8 there are two settings services, or dbus services that save/store > network configuration and passwords. One is NM itself; the other (the "user" > service) is nm-applet or knetworkmanager or whatever. If that's not running, > you don't have user settings and you might get that message. If you're trying > to fast-user-switch, NM 0.8 and earlier don't support fast user switching, an > issue that's been remedied in NM 0.9. nm-applet is running, and I'm not trying to switch users or anything. For some strange reason, ConsoleKit thinks I'm not local: $ ck-list-sessions Session2: unix-user = '501' realname = 'Horst H. von Brand' seat = 'Seat3' session-type = '' active = FALSE x11-display = ':0' x11-display-device = '/dev/tty8' display-device = '' remote-host-name = '' is-local = FALSE on-since = '2011-02-26T00:52:10.940252Z' login-session-id = '2' Presumably because X thinks it is already running, first line of .xsession-errors: /usr/bin/startxfce4: X server already running on display :0 > Also, is this session that has the problem a root desktop UI session? Myself, logged into XFCE via XDM (GDM is busted, Gnome is broken).
Presumably this is the same mess being discussed in 679393.
Logged into LXDE. Network Manager's previous configuration ran as expected, but the Enable Networking and Enable Wireless were greyed out. The other tabs work ok. This may be a rare problem. I'll try logout/login and restart.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.