After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 711132 - Network menu confusing when networking is off
Network menu confusing when networking is off
Status: RESOLVED DUPLICATE of bug 709128
Product: gnome-shell
Classification: Core
Component: system-status
3.10.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2013-10-30 11:08 UTC by Kat
Modified: 2014-01-17 09:58 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Kat 2013-10-30 11:08:05 UTC
When networking is "turned off" from the system menu, "Select Network" is still shown and active. This is confusing because there are no networks available when networking is off. On first glance, this makes it seem like networking is broken, especially if one knows there is a network available.

Either "Select Network" should be insensitive when networking is off or

The "Select Network" dialog should say "Network is disabled" and/or allow one to enable the network from that dialog.
Comment 1 Allan Day 2014-01-17 09:58:58 UTC
(In reply to comment #0)
> When networking is "turned off" from the system menu, "Select Network" is still
> shown and active. This is confusing because there are no networks available
> when networking is off. On first glance, this makes it seem like networking is
> broken, especially if one knows there is a network available.
> 
> Either "Select Network" should be insensitive when networking is off or
>
> The "Select Network" dialog should say "Network is disabled" and/or allow one
> to enable the network from that dialog.

My preference is to go for the second approach - that issue is being tracked in bug 709128 . This way, if wifi is off and you are within range of a known network, you can use "turn on", but if you are not within range of a known network, you can go straight to "select network".

I'll mark this as a dupe of 709128 for now, but feel free to tell me if you think there's a problem with that approach.

*** This bug has been marked as a duplicate of bug 709128 ***