GNOME Bugzilla – Bug 705104
new network menu has no way to select a wired connection
Last modified: 2013-10-13 14:50:38 UTC
After restarting gnome shell to test the new network menu from bug 704670 and using it for a few hours I noticed there's no mention of my wired connection, and therefore no possibility to select a different profile, I checked the new system status menu proposal and indeed, it's missing. I had to resort to nmcli.
From: https://bugzilla.gnome.org/show_bug.cgi?id=704670#c51 Note that this does have an interesting side effect of not showing network connectivity status on wired. This is intentional, and error states will still be shown in the top bar when they happen." So...really? Among other things, the wired situation shows up in virtual machine deployments.
If you're entirely disconnected, we should show an error state. The only indicator we don't show is the 'connected to wired' one, which doesn't tell you much. System Settings should allow you connect to alternate Wired configurations. Mind if I ask what you use different profiles for?
On my wired connection I have two "real" profiles, classic DHCP & stuff, and another one I have to use in a specific location as that network doesn't have a DHCP server. Also I have a profile to share my wireless link over the wired connection.
Created attachment 251112 [details] screenshot of how it looks for me (single wired network connection, active)
as of gnome-shell-3.9.5-2.fc20.x86_64 I now have a single item on the menu, "VPN" in white, "Off" in grey, and a white expander. Clicking it opens a drop-down with "Connect" in it. I was able to connect to my VPN, but it still thinks it's not connected (it's behaving as described above even though I'm on my VPN).
wired profiles can now be activated in the network panel, at least
(In reply to comment #5) > as of gnome-shell-3.9.5-2.fc20.x86_64 I now have a single item on the menu, > "VPN" in white, "Off" in grey, and a white expander. Clicking it opens a > drop-down with "Connect" in it. I was able to connect to my VPN, but it still > thinks it's not connected (it's behaving as described above even though I'm on > my VPN). Yeah, the fact that wired is shown as an error state in the menu is going to be fixed. It requires new NM APIs.
*** Bug 708966 has been marked as a duplicate of this bug. ***
Also, network indicator does not reflect Wired network connection/disconnection. If you are disconnected from any networks, and you connect to a wired network, the network status indicator icon remains in a "disconnected" status. Refer to bug 708966 for my own rationale and my personal user-story.
Bug #708966 got reopened and now has many more comments than this bug, so let's use that as the main bug instead. *** This bug has been marked as a duplicate of bug 708966 ***