Wired interface cannot be disconnected using Shell network applet

This is expected behavior: wired is supposed to be taken in priority over wireless and over other wireless systems (3G, bluetooth, etc).

As a workaround, you may wish to edit the connection settings, go under the IPv4 tab then click the Routes button, and check the "Use this connection only for resources on its network" checkbox. This will avoid NM using this connection as a default gateway.

Since it's not a bug, I'm closing this as Invalid.

This is not invalid as I pressed Disconnect in network manager.

This might be a gnome-shell issue as I have not tested it in unity's network manager.

I understand prioritising ethernet over wired when I am connected, but when I set the connection to "off" it should not be used at all.

It seems that disabling the ethernet connection does not actually disconnect it. As I am writing this message without a wireless card and the "Ethernet Controller" connection "off".

If you click "Off" or whatever for the connection, it *is* disconnected. What may happen though is that it re-connects if it's set to connect automatically. What you need to be looking at is likely the icon in Shell or in Unity to tell whether something is connected or not; but in any case if the connection is disconnected, it's not going to be used for the default route (and it shouldn't normally get autoconnected after that, or at least it doesn't with nm-applet).

Regardless, if you have reason to believe there's still an issue, don't hesitate to reopen by setting this bug report to "New". It would help if you could make sure you reproduce the issue, then provide the output of 'ip route list'. Note that any other connections may also be on and taking the default gateway, *all* wired connections will keep priority, in this case it may be eth0 as much as eth1.

http://i.imgur.com/kpu4W.png

That image shows the "off" state

then:

$ ip route list
default via 192.168.0.1 dev eth1 proto static
169.254.0.0/16 dev eth1 scope link metric 1000
192.168.0.0/24 dev eth1 proto kernel scope link src 192.168.0.7 metric 1

Changed it to gnome-shell because the behaviour is as expected in Ubuntu Unity

Well, right there we can clearly see eth1 has the default route.

What does the following command yield?

nmcli -f all dev list iface eth1

Confirming after testing locally: the gnome-shell nm applet responds to the off switch only for wifi, not for wired. Using the Off switch in the control panel works, though.

There's even an error in .xsession-errors.

** (nm-applet:2422): DEBUG: foo_client_state_changed_cb
** (nm-applet:2422): DEBUG: going for offline with icon: notification-network-ethernet-disconnected
** (nm-applet:2422): DEBUG: going for offline with icon: notification-network-ethernet-disconnected
** (nm-applet:2422): DEBUG: foo_client_state_changed_cb
** (nm-applet:2422): DEBUG: foo_client_state_changed_cb
    JS ERROR: !!! Exception was: Error: Error invoking NMClient.disconnect: Invalid callback given for argument callback
    JS ERROR: !!! lineNumber = '0'
    JS ERROR: !!! fileName = '"gjs_throw"'
    JS ERROR: !!! stack = '"("Error invoking NMClient.disconnect: Invalid callback given for argument callback")@gjs_throw:0
()@/usr/share/gnome-shell/js/ui/status/network.js:371
([object _private_Clutter_Event])@/usr/share/gnome-shell/js/ui/status/network.js:232
([object _private_Shell_GenericContainer],[object _private_Clutter_Event])@/usr/share/gnome-shell/js/ui/popupMenu.js:81
"'
    JS ERROR: !!! message = '"Error invoking NMClient.disconnect: Invalid callback given for argument callback"'

$ nmcli -f all dev list iface eth1 #on
GENERAL.DEVICE: eth1
GENERAL.TYPE: 802-3-ethernet
GENERAL.DRIVER: sky2
GENERAL.HWADDR: <redacted>
GENERAL.STATE: connected
CAPABILITIES.CARRIER-DETECT: yes
CAPABILITIES.SPEED: 1000 Mb/s
WIRED-PROPERTIES.CARRIER: on
IP4-SETTINGS.ADDRESS: 192.168.0.7
IP4-SETTINGS.PREFIX: 24 (255.255.255.0)
IP4-SETTINGS.GATEWAY: 192.168.0.1
IP4-DNS1.DNS: 8.8.8.8
IP4-DNS2.DNS: 8.8.4.4
$ nmcli -f all dev list iface eth1 #off
GENERAL.DEVICE: eth1
GENERAL.TYPE: 802-3-ethernet
GENERAL.DRIVER: sky2
GENERAL.HWADDR: <redacted>
GENERAL.STATE: connected
CAPABILITIES.CARRIER-DETECT: yes
CAPABILITIES.SPEED: 1000 Mb/s
WIRED-PROPERTIES.CARRIER: on
IP4-SETTINGS.ADDRESS: 192.168.0.7
IP4-SETTINGS.PREFIX: 24 (255.255.255.0)
IP4-SETTINGS.GATEWAY: 192.168.0.1
IP4-DNS1.DNS: 8.8.8.8
IP4-DNS2.DNS: 8.8.4.4

Got a small patch that works as a workaround, see the attached file.

The real fix is to add a missing annotation to libnm-glib; we can deal with that separately.

The attachment "0001-network-set-callback-as-an-anonymous-function-for-di.patch" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-sponsors please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

@Mathieu: What's the status of this? The RedHat bug report has status Fixed as of February 2012. Is this also fixed in Ubuntu?

Can anyone reproduce this in Ubuntu 12.04?

EOL reached for that serie https://wiki.ubuntu.com/Releases