Bug 745262

Summary: [network] gnome network icon never changes to "connected" even though connection works
Product: [Fedora] Fedora Reporter: Charles R. Anderson <cra>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: clancy.kieran+redhat, dcbw, drago01, jklimes, lepennec, maxamillion, mishu, nonamedotc, otaylor, ricardo.arguello, samkraju, samuel-rhbugs, sanjay.ankur, walters
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 11:50:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
/var/log/messages
none
.xsession-errors
none
.xsession errors
none
Screenshot showing yum downloading and nm applet still showing "...." none

Description Charles R. Anderson 2011-10-11 20:03:16 UTC
Created attachment 527536 [details]
/var/log/messages

Description of problem:

When connecting to an open wireless network (at least) the gnome shell network manager status icon stays at "..." even after the network connection completes.  It never changes to a completed/connected status which would show the wireless signal strength.

Version-Release number of selected component (if applicable):
NetworkManager-0.9.1.90-3.git20110927.fc16.x86_64
gnome-shell-3.2.0-2.fc16.x86_64

How reproducible:
sometimes

Steps to Reproduce:
1. select an open wireless network from the applet icon
2.
3.
  
Actual results:

Connects, gets an IPv4 & IPv6 address (including default routes on v4 and v6), but icon doesn't change to "connected".

Expected results:

Icon should change to connected state with the wireless signal strength indicator.

Additional info:

After connection is working:

[cra@t 15:57:43 /home/cra]>ip -4 addr show dev wlan0
2: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    inet 199.187.220.73/22 brd 199.187.223.255 scope global wlan0
[cra@t 15:57:47 /home/cra]>ip -6 addr show dev wlan0
2: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
    inet6 2620:0:ce0:101:224:d7ff:fedf:1f08/64 scope global dynamic 
       valid_lft 2591993sec preferred_lft 604793sec
    inet6 fe80::224:d7ff:fedf:1f08/64 scope link 
       valid_lft forever preferred_lft forever

[cra@t 15:57:47 /home/cra]>ip -4 route show dev wlan0
default via 199.187.220.1  proto static 
199.187.220.0/22  proto kernel  scope link  src 199.187.220.73  metric 2 
[cra@t 15:58:21 /home/cra]>ip -6 route show dev wlan0
2620:0:ce0:101::/64  proto kernel  metric 256  expires 2147157sec
fe80::/64  proto kernel  metric 256 
default via fe80::218:74ff:fe56:181a  proto kernel  metric 1024

Comment 1 Charles R. Anderson 2011-10-11 20:05:08 UTC
Created attachment 527537 [details]
.xsession-errors

Comment 2 Erwan LE PENNEC 2011-11-16 21:33:15 UTC
Same issue for me.

Comment 3 Kieran Clancy 2012-01-29 18:41:58 UTC
I've also seen this bug intermittently.

Comment 4 Jirka Klimes 2012-01-30 08:30:14 UTC
(In reply to comment #3)
> I've also seen this bug intermittently.
Probably Gnome Shell network indicator issue. Would you report these, when
the problem occurs:
$ rpm -q gnome-shell
$ rpm -q NetworkManager
$ nmcli dev
attach .xsession-errors

Comment 5 Samuel Sieb 2012-02-08 18:38:13 UTC
I used to see this occasionally, but I haven't seen it for quite a while now.  Maybe it has been fixed.

Comment 6 Ankur Sinha (FranciscoD) 2012-08-10 00:59:35 UTC
I see this when my system wakes from hibernates (using pm-hibernate, since suspend doesn't work on my system currently)

[ankur@ankur ~]$ rpm -q gnome-shell
gnome-shell-3.4.1-5.fc17.x86_64
[ankur@ankur ~]$ rpm -q NetworkManager
NetworkManager-0.9.4.0-9.git20120521.fc17.x86_64
[ankur@ankur ~]$ nmcli dev
DEVICE     TYPE              STATE
7C:61:93:B8:F6:4E bluetooth         disconnected
p1p1       802-3-ethernet    unavailable
wlan0      802-11-wireless   connected
[ankur@ankur ~]$

Comment 7 Ankur Sinha (FranciscoD) 2012-08-10 01:00:14 UTC
Created attachment 603374 [details]
.xsession errors

Comment 8 Ankur Sinha (FranciscoD) 2012-08-10 01:01:23 UTC
Created attachment 603375 [details]
Screenshot showing yum downloading and nm applet still showing "...."

Comment 9 Mukundan Ragavan 2012-10-05 18:44:15 UTC
I am seeing this even in a Virtualbox Virtual Machine. Network works fine but the NM applet shows still connecting.

Comment 11 Fedora End Of Life 2013-01-16 16:22:08 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 12 Ankur Sinha (FranciscoD) 2013-01-17 00:14:20 UTC
Hi,

I saw this on my F18 the other day. I see the upstream bug has a patch in it. Would you know if the patch has been merged to sources yet?

Thanks again,
Warm regards,
Ankur

Comment 13 Fedora End Of Life 2013-12-21 08:29:32 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 14 Fedora End Of Life 2014-02-05 11:50:51 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.