Bug 1024170 - After suspend my PC doesn't connect any wireless network
Summary: After suspend my PC doesn't connect any wireless network
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 19
Hardware: i686
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-29 04:26 UTC by Brallan Jesús Aguilar Rivera
Modified: 2013-11-05 03:37 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-11-05 03:37:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Some portion of file /var/log/messages after resume my pc (12.54 KB, text/plain)
2013-10-29 04:26 UTC, Brallan Jesús Aguilar Rivera
no flags Details

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


Note You need to log in before you can comment on or make changes to this bug.