How reproducible: Try running knetworkmanager Actual results: [bkevan@localhost ~]$ knetworkmanager ** (nm-applet:4064): WARNING **: <WARN> applet_dbus_manager_start_service(): Could not acquire the NetworkManagerUserSettings service as it is already taken. Return: 3 (nm-applet:4064): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table != NULL' failed (nm-applet:4064): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:4064): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
knetworkmanager here is simply trying to run nm-applet (NetworkManger-gnome). The error you're seeing implies nm-applet is already running. Is this the case (or not)?
[bkevan@localhost ~]$ ps -ae | grep nm-applet 3042 ? 00:00:00 nm-applet Yes it running.. But I don't see it in the tray.. What's up with that?
is the NetworkManager service running? you wont see the applet until it is
regardless, Reassigning -> NetworkManager
I get the same error with multiple users on a laptop attempting to control the network interface. User A starts the laptop. User A logs in and the nm-applet is loaded User A locks the screen User B switches users and logs in attempting to start nm-applet User B does not see nm-applet in the Notification Area User B cannot acquire the NetworkManagerUserSettings service as it is already taken. User B cannot control the network. User B is expecting User A's nm-applet will yeild control of the network to the user who has access to the Xserver. Both users are logged in at the same time. [nesscg@localhost ~]$ nm-applet --version GNOME nm-applet 0.7.0 This is the closest thing to an existing bug I could find. Cheers, Chris
Closing due to inactivity; info requested in comment #3
I'm not the original reporter, but I can see the same problem. # /etc/init.d/NetworkManager status NetworkManager (pid 2400) is running... Also, as explained in comment #5, there is one nm-applet instance running, but it's the one of user A.
*** This bug has been marked as a duplicate of bug 456046 ***