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 665112 - Wired icon is shown even when wired connection is disabled
Wired icon is shown even when wired connection is disabled
Status: RESOLVED FIXED
Product: gnome-shell
Classification: Core
Component: network-indicator
3.2.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
: 665226 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-11-29 09:34 UTC by Kamil Páral
Modified: 2011-12-01 10:07 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
wired off, but showing wired icon (108.87 KB, image/png)
2011-11-29 09:35 UTC, Kamil Páral
Details
cable unplugged and finally showing wifi icon (109.10 KB, image/png)
2011-11-29 09:35 UTC, Kamil Páral
Details

Description Kamil Páral 2011-11-29 09:34:49 UTC
The gnome-shell top bar shows wired connection icon even when I turn the wired connection off using the toggle (see screen1). The icon switches to wifi connection icon only after I manually unplug the cable (see screen2).

I believe the top bar should should wifi icon when wifi is on and wired is off, even when the cable is still plugged in. Because the system is using only wifi at that moment.

Fedora 16, Gnome 3.2
Comment 1 Kamil Páral 2011-11-29 09:35:19 UTC
Created attachment 202354 [details]
wired off, but showing wired icon
Comment 2 Kamil Páral 2011-11-29 09:35:41 UTC
Created attachment 202355 [details]
cable unplugged and finally showing wifi icon
Comment 3 Giovanni Campagna 2011-11-29 16:45:20 UTC
This is definitely unexpected.
Do you see anything suspicious in .xsession-errors, that could have prevented the icon update?
Comment 4 Kamil Páral 2011-11-30 11:01:41 UTC
Great call. I do. When I turn Wired off, this pops up 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"'


I disabled all extensions and restarted gnome-shell, still the same message.

gnome-shell-3.2.1-2.fc16.x86_64, Fedora 16
Comment 5 Kamil Páral 2011-11-30 11:03:52 UTC
By the way when I turn Wired off, I can't turn it on again, unless I unplug cable, wait 10 seconds (until 'cable disconnected' message appears), plug in back again. It may be related.
Comment 6 Giovanni Campagna 2011-11-30 18:58:24 UTC
(In reply to comment #4)
> Great call. I do. When I turn Wired off, this pops up 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"'

Ow... this is a NetworkManager bug, which was fixed not long ago. You should move this bug downstream and ask for an updated version, including the changes in git commit a7f7e808.
(The first release to include that change is 0.9.2, which you can find packaged for F16 in koji but not yet in updates. This means that this bug could be already resolved in the next update to NetworkManager)
Comment 7 Giovanni Campagna 2011-11-30 18:59:34 UTC
*** Bug 665226 has been marked as a duplicate of this bug. ***
Comment 8 Kamil Páral 2011-12-01 10:07:22 UTC
I can confirm this is fixed with NM 0.9.2. I requested update in F16:
https://bugzilla.redhat.com/show_bug.cgi?id=759039

Thank you.