Bug 645361

Summary: Devices unmanaged after wakeup from sleep
Product: [Fedora] Fedora Reporter: Dalibor Horinek <dal>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 17CC: dcbw, luya, psimerda
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-11 22:29:00 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 Flags
Wireless unmanaged
none
/var/log/messages
none
/var/log/messages
none
messages sorted by nm none

Description Dalibor Horinek 2010-10-21 11:59:54 UTC
Description of problem:
Sometimes when I wake up my laptop from sleep, network manager shows that devies are not managed. It requires restarting NetworkManager.

Version-Release number of selected component (if applicable):
NetworkManager-0.8.1-8.git20100831.fc14.x86_64

How reproducible:
Sleep and wake up. 

Steps to Reproduce:
1. Make laptop sleep 
2. Wake up
  
Actual results:
Devices not managed by NetworkManager

Expected results:
Devices managed by NetworkManager

Additional info:
As client app I use kde-networkmanager-plasma addon.

Comment 1 Dalibor Horinek 2010-10-21 12:01:34 UTC
I don't know If it's related to that, but In the plasmoid I got two connections and after a few sleeps it's multiplied and these two connections are there more than once.

Comment 2 Luya Tshimbalanga 2012-04-18 01:55:04 UTC
Created attachment 578206 [details]
Wireless unmanaged

That bug is triggered on Fedora 17 Beta after awaking the laptop. Here is the hardware profile:
http://www.smolts.org/client/show/pub_04a89964-665e-4737-be55-42c76fd5c8d1

Comment 3 Dan Williams 2012-04-19 23:05:55 UTC
(In reply to comment #2)
> Created attachment 578206 [details]
> Wireless unmanaged
> 
> That bug is triggered on Fedora 17 Beta after awaking the laptop. Here is the
> hardware profile:
> http://www.smolts.org/client/show/pub_04a89964-665e-4737-be55-42c76fd5c8d1

If you could save your /var/log/messages right after you notice this problem, and then attach it to this bug report, that would help us diagnose the problem.  Also, right after you see this happen, please run 'nmcli nm' and paste the output into this bug.

Comment 4 Luya Tshimbalanga 2012-04-20 08:04:31 UTC
Created attachment 578913 [details]
/var/log/messages

Here is messages file as requested. The bug was triggered on april 16 and 17. I am unable to reproduce the problem at the moment. I hope the message file will help to find the cause.

Comment 5 Luya Tshimbalanga 2012-04-20 16:40:23 UTC
Looking at the messages file, could it be that upgdate of glib-networking fixed that problem somewhat?

Comment 6 Luya Tshimbalanga 2012-04-27 04:18:08 UTC
Created attachment 580625 [details]
/var/log/messages

Here is new messages showing networkmanager issue. After update, the status is now "unavailable" until I restarted it.

Comment 7 Dan Williams 2012-04-28 18:09:53 UTC
The second log from comment 6 shows NM waking up correctly.  Unfortunately the first log doesn't have enough detail to figure out what's going on; did you use grep to filter it?  We're looking for the  messages about NM "waking up" and then the stuff immediately after that where it re-scans interfaces and makes the decision to manage them or not manage them.

Comment 8 Luya Tshimbalanga 2012-04-29 03:28:07 UTC
Created attachment 581012 [details]
messages sorted by nm

I haven't used the grep command on the previous attachment. Here is an update that include the unmanaged text which switched to unavailable.

Comment 9 Luya Tshimbalanga 2012-04-29 03:30:30 UTC
Removing needinfo tag. For some reason, bugzilla will not remove it after checking the "provided requested information".

Comment 10 Luya Tshimbalanga 2012-09-19 19:40:42 UTC
Latest NetworkManager update no longer report unmanaged devices after wakeup. This bug is two years so I think it can be closed.