Bug 423561 - NetworkManager only appears to work as root?
NetworkManager only appears to work as root?
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Dan Williams
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-12-13 10:20 EST by Andrew Cagney
Modified: 2007-12-13 21:51 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-12-13 21:51:38 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
nm-tool output (slightly edited) (3.78 KB, text/plain)
2007-12-13 11:21 EST, Andrew Cagney
no flags Details

  None (edit)
Description Andrew Cagney 2007-12-13 10:20:34 EST
On an f8 laptop with a complete reinstall, except for /home (so there could be
old gnome stuff lying around to cause this).

Logging in as root my networks come up.
Logging in as a normal user, I don't see my network manger thingie, and no networks.

Workaround is to login as root and then switch to a normal user.
Comment 1 Dan Williams 2007-12-13 11:04:33 EST
Do you mean 'nm-applet' only works as root?  Sounds odd; because I've done a
bunch of fresh installs of F-8 and haven't had problems with other users.  When
you log in directly as a non-root user, can you run '/usr/bin/nm-tool' and
provide the output?  Can you also see if there's anything related to nm-applet
in ~/.xsession-errors?  Are you using SELinux in enforcing mode?
Comment 2 Andrew Cagney 2007-12-13 11:21:21 EST
Created attachment 287541 [details]
nm-tool output (slightly edited)
Comment 3 Andrew Cagney 2007-12-13 11:23:24 EST
On my fc5 box, when I logged in, the (I guess it's called) nm-applet
automatically appeared and then proceeded to connect.  With f8, I'm finding that
only works with root.  As a normal user I don't see that applet and my network
connections aren't started.

Output from nm-tool is attached.

I turned off SELinux (another story).
Comment 4 Andrew Cagney 2007-12-13 11:42:50 EST
Here's some more (after a re-boot).  Seems nm-applet is running, just not visible:

$ cat .xsession-errors

** (gnome-session:2421): WARNING **: Host name lookup failure on localhost.
Window manager warning: Failed to read saved session file
/home/cagney/.metacity/sessions/default1.ms: Failed to open file
'/home/cagney/.metacity/sessions/default1.ms': No such file or directory
could not attach to desktop process


$ nm-applet 

** (nm-applet:2977): WARNING **: <WARN>  applet_dbus_manager_start_service():
Could not acquire the NetworkManagerUserSettings service as it is already taken.
 Return: 3

(nm-applet:2977): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table
!= NULL' failed

(nm-applet:2977): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed

(nm-applet:2977): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed


$ ps auxw | grep nm-applet
cagney    2532  0.0  0.7  28184  9940 ?        S    11:26   0:00 nm-applet
Comment 5 Dan Williams 2007-12-13 11:45:27 EST
Ok, so it looks like you're running two applets.  Can you check to see whether
there are two applet running as your user?  Can you also report what their
command lines are?
Comment 6 Andrew Cagney 2007-12-13 12:54:40 EST
$ ps auxwww | grep nm-applet
cagney    2464  0.0  0.0   4044   672 pts/4    S+   12:53   0:00 grep nm-applet
cagney    2532  0.0  0.8  47820 10588 ?        S    11:26   0:01 nm-applet

this is the only running nm-applet (I'm guessing it was started when I logged
in).  Trying to run a second from the command line (as nm-applet) gets above error.
Comment 7 Andrew Cagney 2007-12-13 21:51:38 EST
Found it; I lost my egg tray again :-/

Note You need to log in before you can comment on or make changes to this bug.