From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:126.96.36.199) Gecko/2008071615 Fedora/3.0.1-1.fc9 Firefox/3.0.1
Description of problem:
When multiple users are logged in, the NetworkManager applet will only work for one of them. If one of the other users need to interact with NetworkManager, they are screwed.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot system
2. Log in, nm-applet loads and connects automatically
3. Log in as another user, keeping previous user logged in
4. Look in vain for the applet. Starting nm-applet from the command line won't work.
No NetworkManager applet.
NetworkManager applet in all its glory.
This might be related to bug #449976 concerning the inability to set whether the
NetworkManager applet appears on a per-user basis.
*** Bug 460843 has been marked as a duplicate of this bug. ***
This bug drives me crazy. If I leave my computer going, and the screen locks, then someone else (who logs in with their own username) can't control the wireless network. Dialog boxes pop up in the person who first logged in. Please please fix!
Has this bug been fixed for Fedora 10? Would really really love to see it fixed.
This bug still apply to Fedora 10 unfortunatly.
I also suffer from this bug ...
Thank you very much for your help !
This one's a royal pain, eh?
I want to tell you about how I have worked around this bug. It is a workaround, not a fix.
- Create a script called /usr/local/bin/grab-network
sudo killall -1 nm-applet
nohup nm-applet < /dev/null > /dev/null 2>&1 &
- chmod a+x /usr/local/bin/grab-network
- Run visudo, and add these lines:
Cmnd_Alias GRAB_NETWORK = /usr/bin/killall -1 nm-applet
# Allows people in grab_network group to restart wireless.
%grab_network ALL = NOPASSWD: GRAB_NETWORK
- Create a new group in /etc/group called "grab_network".
- Add users who you want to be able to grab the network, to this group.
- On the desktop for each of these users, create a launcher to /usr/local/bin/grab-network.
As I said, a workaround, not a fix.
thanks for the workaround.
In fact this bug is not very annoying as long as the user who logged first is still logged. But when this user log out other users cannot use the network any more unless they log out and in again.
Still, should a bug zapper or the maintener mark this bug as belonging to F10 so that it is still valid when F9 will be end of life ? Thanks !
This bug may be solved..
I did experience it earlier, but now using:
Fedora 10 on 188.8.131.52-159.fc10.x86_64 #1 SMP
I do not longer get this problem. NetworkManager icon appears whatever user I switch to.
Can someone else verify this?
still persist for x86
[axet@axet-laptop ~]$ rpm -qa|grep Network
Same for me on x86 it still persists with the latest NetworkManager packages
I thought perhaps me running Compiz-Fusion was the thing.. not sure if that was correct..
I turned off Compiz-Fusion (via the Desktop Effects control in the System menu) and the problem did returned.. though, once I turn on Desktop Effects again.. the problem stayed.
So now I again have the same problem. I can not reproduce this, even after reboot. I keep getting the missing NetworkManager icon all the time now.
My "Compiz Fusion" installation includes
When I didn't have the problem I got a notification about connected established to my Wireless network.
*** Bug 453985 has been marked as a duplicate of this bug. ***
*** Bug 372171 has been marked as a duplicate of this bug. ***
*** Bug 490850 has been marked as a duplicate of this bug. ***
same in rawhide with:
try to run nm-applet while another user is logged in result in:
** (nm-applet:5442): WARNING **: <WARN> applet_dbus_manager_start_service(): Could not acquire the NetworkManagerUserSettings service as it is already taken. Return: 3
Fedora Bugzappers volunteer triage team
(In reply to comment #15)
> same in rawhide with:
> try to run nm-applet while another user is logged in result in:
> ** (nm-applet:5442): WARNING **: <WARN> applet_dbus_manager_start_service():
> Could not acquire the NetworkManagerUserSettings service as it is already
> taken. Return: 3
Maybe it's another bug but I too get this error message (only single user, no locked screen etc) whenever I want to start nm-applet.
I'm running f11 (fresh install) and version NM 0.7.1-4.git20090414.fc11. In f10, everything was fine.
A remark regarding authorization:
If a connection has been made and the user chooses to fast-user-switch to another account, this other account should not be able to tamper with already established connections, only if he has the appropriate rights to do so (via policykit).
*** Bug 508294 has been marked as a duplicate of this bug. ***
Bug #508294 was reported against F11, so this bug should have its Version bumped to 11 (certainly before F10 goes EOL).
I see this in F11 too.
f12 - the same
Definitely still in F11. I did something similar to comment #5 some months ago but forgot to check for the existence of the bug. It is absolutely related to fast user switch, specifically the nm-applet can only be executed once, but must be owned by the currently active user.
http://wiki.archlinux.org/index.php/Network_manager#Problems_starting_nm-applet_as_normal_user may perhaps help...
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.
More information and reason for this action is here:
This is still broken in F13 alpha, and has been forever.
Running from the command line for the second user gets:
An instance of nm-applet is already running.
Of course the other instance is for the first user so no help at all.
Is there any plan to address this since it's a gaping hole in fast-user-switching support (which otherwise works excellently these days)?
Still broken in F13 release, any updates?
The feature is not implemented yet.
Nevertheless, the subject is currently being discussed on the networkmanager-list:
This is to be addressed in NM 0.9 I think? Hopefully that will be in F15 but as of F14 this is still broken,
Correct, this is addressed in 0.9 and Fedora 15 and later. It works there, but it won't ever work in NM 0.8 and earlier (f14/f13). Given that, I'm going to mark as fixed since it's been working in F15 for a few months already. A large part of NM 0.9 was rearchitecting to make stuff like FUS possible.
another workaround: http://sourceforge.net/projects/nm-applet-guard/