Bug 1024170

Summary: After suspend my PC doesn't connect any wireless network
Product: [Fedora] Fedora Reporter: Brallan Jesús Aguilar Rivera <apcomptec>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 19CC: dcbw
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-11-05 03:37:49 UTC Type: Bug
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
Some portion of file /var/log/messages after resume my pc none

Description Brallan Jesús Aguilar Rivera 2013-10-29 04:26:03 UTC
Created attachment 816960 [details]
Some portion of file /var/log/messages after resume my pc

Description of problem: I'm using Fedora 19 and KDE 4.11.2. Always after suspending my pc, I have problems with wireless networks and it does not detect any. I see that completely disables network detection and this leads me to be restarting the computer. Additionally, when I give reboot, it freezes so I turn it off by force. I attached that recorded the file /var/log/messages after suspending my laptop and just before shutting down.


Version-Release number of selected component (if applicable): NetworkManager-0.9.8.2-9.git20130709.fc19.i686


Steps to Reproduce:
1. Suspend pc
2. Resume pc
3. No wireless detection


Actual results:
Before resume my laptop, it doesn't connect any network. Network detection is unavailable.

Expected results:
Before resume session, connect automatically to saved wireless networks.

Additional info: Just when resume my session, I write my pass and my laptop freezes some time (around 30s) and has a little performance reduction (it remains a little time). Also, I suspect it is linked with the last KDE version (4.11.x) and/or kernel (3.11.x). I'm using KDE 4.11.3 and kernel 3.11.6-200.fc19.i686

Comment 1 Brallan Jesús Aguilar Rivera 2013-11-05 03:37:49 UTC
Right now this bug was solved by kernel 3.11.6-201.fc19.i686