Bug 1181329

Summary:	NetworkManager can not connect to wifi after reboot or wake up from sleep mode (workaround available)
Product:	[Fedora] Fedora	Reporter:	Ronald Verbeek <bugzilla>
Component:	NetworkManager	Assignee:	Dan Williams <dcbw>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	21	CC:	dcbw, jklimes, 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:	2015-01-14 17:36:38 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:

Description Ronald Verbeek 2015-01-12 22:05:07 UTC

Description of problem:
After reboot or wake-up after sleep mode Networkmanagaer tries "forever" to connect to wifi network, but does not succeed. ifconfig shows no ip address for wifi card. Manually running dhclient can get an ip address, but NetworkManager still shows "connecting".

I found a workaround by deleting all files in /var/lib/NetworkManager/ and then running: systemctl restart dbus-org.freedesktop.NetworkManager.service

The wifi connection is working after this.

Version-Release number of selected component (if applicable):
0.9.10.1
1.git20150105.fc21

How reproducible:
Every time after reboot or wakeup from sleep mode.

Steps to Reproduce:
1. Have a working wifi connection
2. Press Alt-Shutdown button from system menu to go to sleep mode.
3. Wake up via Esc and login again.
4. NetworkManager shows "connecting", but does not succeed.
5. rm /var/lib/NetworkManager/*
6. systemctl restart dbus-org.freedesktop.NetworkManager.service
7. NetworkManager connects.

Actual results:
Need workaround everytime after sleep mode

Expected results:
NetworkManager reconnects automatically without workaround.

Additional info:

Comment 1 Jirka Klimes 2015-01-14 17:36:38 UTC


*** This bug has been marked as a duplicate of bug 1181477 ***