Stakanov Schufter changed bug 912059
What Removed Added
Version Leap 42.3 Leap 15.0
OS openSUSE 42.3 Other

Comment # 3 on bug 912059 from
Bringing his to Leap 15. 
In leap 15 the situation changed and is the following:
e.g.
User A Owner of the connection. Set to connect automatically. Connected to SSID
snowwhite

User A NOT connected to SSID sevendwarfs

User B Not owner of the wlan connection to snowwhite nor to any other.

Situation in the networkmanager tray:

In user A: correctly shown after connect as connected to SSID snowwhite. 
In user A: correctly shows that A is NOT connected to sevendwarfs. 
vs.
In user B: shown as NOT connected to ANY of the SSIDs, although shown as
connected in general with signal strengh in tray. And offering the button
"connect" which could induce users to press it. 

When I encountered bug 1117230 (privoxy related), when I suddenly did not
resolve, I checked the connections in networkmanager. 
Now astonishingly, limited to USER B (as of above) it did show:
NOT connected to snowwhite, BUT connected to sevendwarfs? So in the indicator
networkmanager gave now instead the oposite of the real connection, limited to
user B, although in user A the correct SSID was shown to be connected. This
seems to be in relation with trying to set up privoxy (see the bug), but I
thought I would mention it. 

The general valid situation is the one reported as first. 

What I did encounter: networkmanager shows a connection as signal strength in
the tray, but, if the user is not owner of the connection, the list of SSIDs
shows all not connected. Sometimes, limited to that user, it even showed the
wrong SSID connected (but was yet a limited case). 

What the software should have done: 
network manager should show the list with the correct SSID connected. 
Not connected SSIDs should be shown as not connected. 
SSIDs should not be inverted within the list.
I am unsure if there should be a button offered for the connected SSID. IMO, if
ever, there should be a button called disconnect, and then the user should be
asked for the root password, as user B in our example is not owner(!) of the
connection.


You are receiving this mail because: