Bug 739610
Summary: | NetworkManager shows disconnected status icon after laptop is resumed from sleep. | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dusan Obradovic <dusan> | ||||||||||||
Component: | NetworkManager | Assignee: | Dan Williams <dcbw> | ||||||||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
Severity: | high | Docs Contact: | |||||||||||||
Priority: | unspecified | ||||||||||||||
Version: | 17 | CC: | chmelarz, dcbw, jklimes | ||||||||||||
Target Milestone: | --- | ||||||||||||||
Target Release: | --- | ||||||||||||||
Hardware: | i686 | ||||||||||||||
OS: | Linux | ||||||||||||||
Whiteboard: | |||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||
Clone Of: | Environment: | ||||||||||||||
Last Closed: | 2013-07-18 09:23:44 UTC | Type: | --- | ||||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||||
Documentation: | --- | CRM: | |||||||||||||
Verified Versions: | Category: | --- | |||||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
Embargoed: | |||||||||||||||
Attachments: |
|
Description
Dusan Obradovic
2011-09-19 15:53:23 UTC
Created attachment 523860 [details]
messages log
Created attachment 523861 [details]
nm screenshot
Is this still an issue with latest packages? If so, please run these commands when you see the bad icon: $ nmcli nm $ nmcli dev s $ nmcli con s I have exactly the same problem (right now) - after laptop is resumed from sleep, I connect to wlan (I get a dot in the front of my wlan ESSID 'Home' but the icon shows no signal. After a while, the dot disappears from my wlan ESSID and it is not clear if I'm connected or not (but the connection is still active and internet works) Reconnection does not solve the problem, restart of NetworkManager does not help as well. Actually, it has no negative consequences for work with Firefox and internet access but I'm not able to login to work via VPN because our company tool reports Network connection status as "Out or Range" (cannot detect IP address even if is listed via ifconfig), VPN cannot login to company until the laptop is rebooted when it works all again. outputs from suggested commands above: [zdenek@infinity ~]$ nmcli nm RUNNING STATE WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running connected enabled enabled enabled enabled [zdenek@infinity ~]$ nmcli dev s DEVICE TYPE STATE wlan0 802-11-wireless connected eth0 802-3-ethernet unavailable [zdenek@infinity ~]$ nmcli con s NAME UUID DEVICES DEFAULT VPN MASTER-PATH Auto Home a622b11e-737f-421b-bcd9-ea501616e077 wlan0 yes no not set [zdenek@infinity ~]$ rpm -q NetworkManager NetworkManager-0.9.4.0-9.git20120521.fc17.x86_64 I will attach log from a moment when I attempt to connect to my WLAN and snapshots of NetworkManager behaviour at the beginning and after a while. Created attachment 623719 [details]
Logs from messages from a moment of connection attempt
Created attachment 623720 [details]
My WLAN acts as active at the beginning
Created attachment 623721 [details]
but the "dot" disappears after a while
Just a small update: This behaviour is not regular but random (sometimes it works all out of the box immediately after the sleep wake up ;-) ) I didn't see this behaviour for couple of months now. I consider it as solved. This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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 17'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. Ticket can be closed. I am already on F19 and I do not see this behaviour anymore. |