GNOME Bugzilla – Bug 664171
'Wired' switch in network-indicator appears to be purely decorative
Last modified: 2011-11-16 19:48:19 UTC
NetworkManager-0.9.1.90-5.git20110927.fc16.x86_64 Switching wired to 'off' has no effect, with traffic still being routed over the wired interface. Increasing the debug level for NetworkManager and flicking the switch does not seem to produce any output.
Hi I also have this issue. Before there was also a disconnect feature at least that allowed you to disconnect from networks, now I presume you can only turn off the interface to disconnect. I don't really agree with this as I have stated on the mailing list (because there are valid use cases where you want to disconnect from a network but keep the interface on). Now with this bug (the switch to turn on/off the interface not doing anything) I have no way of disconnecting an active connection. This is particularly annoying when using a broadband connection (either with a dedicated dongle or though my phone using Bluetooth). Think about people who travel overseas and that pay premium prices for broadband roaming, they could think they turned it off and in reality it's still consuming data.
Oh, I forgot to mention that I use Ubuntu 11.10 and it's using network-manager-0.9.1.90-0ubuntu5.
I missed the following traceback in .xsession-errors: 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"'
For some weird reason, nm_device_disconnect @callback is not marked (allow-none) in the gir file shipped by the Fedora package, and probably the Ubuntu one as well. It is correclty marked as such in master and in the latest release of NetworkManager. (This means that calling device.disconnect(null) fails, making the switch useless). You should move this bug downstream and ask for a newer version of libnm-glib.
Okay. There is already a bug for Fedora downstream here, which I have updated with the above info: https://bugzilla.redhat.com/show_bug.cgi?id=739035 Gabriel, you might want to file a similar report on Launchpad. Giovanni, if you're sure this is a downstream issue then feel free to close this bug.
It's fixed in gnome-shell + NetworkManager master, so closing.
Here's the ubuntu bug: https://bugs.launchpad.net/bugs/891299