Show connection state in all opened sessions
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| network-manager-applet (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
Distro version: Ubuntu 10.10
What happens:
The Network Manager applet is only shown in the first session opened in Ubuntu. I.e.: Hansel and Gretel are two distinct user accounts in one Ubuntu PC.
- If Hansel logs in, NM applet is available in its session. Hansel can manage network connections and see current connections' states.
- Hansel locks his session (he does not disconnect). Gretel opens a new session. NM applet is not available to Gretel. She can use network connections established by Hansel, but she can't see what connections it is nor she can see connections states, and if no connection is established she can't proceed either.
- Gretel locks her session. Hansel unlocks his session, then logs out. Gretel unlocks her session. NM applet is not available to her, even if there is no other user currently using NM applet.
What is expected:
NM appler should be seen in every opened session by every users, so everyone could at least observe current network connections' states, at best also be able to manage themselves network connection. NM applet should always be available to all users.
If Hansel and Gretel both have an opened session on an Ubuntu-powered PC, they both should have the ability to see current connections' states and (better) should be able to connect to/disconnect from a network.
| Changed in network-manager-applet (Ubuntu): | |
| status: | New → Confirmed |
| Mathieu Trudel-Lapierre (cyphermox) wrote | #1 |
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 622175, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.