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 694654 - Network indicator stuck to connecting state after suspend
Network indicator stuck to connecting state after suspend
Status: RESOLVED DUPLICATE of bug 676285
Product: gnome-shell
Classification: Core
Component: network-indicator
3.6.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2013-02-25 09:26 UTC by Milan Bouchet-Valat
Modified: 2013-03-03 11:15 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Milan Bouchet-Valat 2013-02-25 09:26:41 UTC
I've seen this for several releases (also see bug 659277), but this precise report is with 3.6.2 on Fedora 18. My logs are full of garbage so it's hard to tell, but maybe this is interesting (I know this was mentioned in another report), and it's repeated many times in several occasions:
      JS LOG: Removing an access point that was never added
      JS LOG: Removing an access point that was never added
      JS LOG: Removing an access point that was never added
      JS LOG: Removing an access point that was never added
      JS LOG: Removing an access point that was never added

(gnome-shell:1809): Clutter-WARNING **: clutter_actor_raise Actor '<unnamed>[<Cl
utterGroup>:0x903a400]' is not in the same container as actor '<unnamed>[<Clutte
rGroup>:0xbffc510]'
      JS LOG: Removing an access point that was never added

The Clutter error does not always appear with the other message, but maybe it appears when things start going wrong, not sure. 


Note that once the bug happens, the connecting icon does not go away, at least
for some time, even when disconnecting/reconnecting, or even using a cable
connection. What's even weirder is that right now I'm on cable, and the icon is
a connecting WiFi; if I turn on the WiFi, the icon becomes a connecting cable;
if I turn it off again, the icon goes back to a connecting WiFi.
Disconnecting/reconnecting the cable has no effect on the icon. The only way to
get the correct icon to be shown is to disable both connections at the same
time. Maybe that's a hint.

This morning, after resuming from suspend, the indicator was still stuck in connecting WiFi state while I was on WiFi; turning off WiFi made the network indicator use the connected cable icon, and then the connected WiFi.
Comment 1 Milan Bouchet-Valat 2013-02-25 09:30:31 UTC
Ah, and if you want to relate this to NetworkManager issues, I'm suffering from this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=893580
Comment 2 Milan Bouchet-Valat 2013-03-03 11:15:23 UTC
NM is 0.9.7.997-2.fc18 here.

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