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 647042 - shows wireless as unavailable while it's connected
shows wireless as unavailable while it's connected
Status: RESOLVED DUPLICATE of bug 647040
Product: gnome-shell
Classification: Core
Component: network-indicator
3.0.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2011-04-07 14:53 UTC by Bill Nottingham
Modified: 2011-04-07 20:34 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
screenshot (237.05 KB, image/png)
2011-04-07 14:53 UTC, Bill Nottingham 		Details

Description Bill Nottingham 2011-04-07 14:53:19 UTC 
Created attachment 185429 [details]
screenshot

See screenshot.
Comment 1 Bill Nottingham 2011-04-07 14:54:14 UTC 
Comment on attachment 185429 [details]
screenshot

f
Comment 2 Giovanni Campagna 2011-04-07 15:44:40 UTC 
This could either mean:

- for some reason, the NMDevice is really UNAVAILABLE => bug in NetworkManager
- somewhere, JS code is failing => bug in gnome-shell, please check .xsession-errors / stdout
Comment 3 Bill Nottingham 2011-04-07 15:56:51 UTC 
$ nmcli dev
DEVICE     TYPE              STATE        
eth0       802-3-ethernet    connected    
wlan0      802-11-wireless   connected    
00:24:90:C2:F0:A3 bluetooth         disconnected 

Only .xsession-errors errors are the ones from bug 647040.
Comment 4 Giovanni Campagna 2011-04-07 17:12:26 UTC 
(In reply to comment #3)
> $ nmcli dev
> DEVICE     TYPE              STATE        
> eth0       802-3-ethernet    connected    
> wlan0      802-11-wireless   connected    
> 00:24:90:C2:F0:A3 bluetooth         disconnected 
> 
> Only .xsession-errors errors are the ones from bug 647040.

Which explains it: inside _deviceStateChanged, _createSection throws, emit('state-changed') is never called and the section title is not updated.
Comment 5 Bill Nottingham 2011-04-07 19:55:59 UTC 
Should this be a dup of 647040, then? Or should the section title be updated regardless?
Comment 6 Giovanni Campagna 2011-04-07 20:34:17 UTC 
It is a duplicate in the sense that fixing the other fixes this one.
So, yeah, marking.

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