Bug 683191

Summary:	Wireless stopped working after networkmanager update
Product:	[Fedora] Fedora	Reporter:	Joseph Tate <jtate>
Component:	NetworkManager	Assignee:	Dan Williams <dcbw>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	14	CC:	dcbw, mhlavink, sly.midnight
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:	2012-04-30 20:53:49 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Joseph Tate 2011-03-08 19:44:22 UTC

Description of problem:
I updated this morning (some packages snipped for brevity):

Mar 08 12:06:25 Installed: lcms2-2.1-1.fc14.i686
Mar 08 12:06:26 Updated: 1:NetworkManager-glib-0.8.3.997-1.fc14.i686
Mar 08 12:06:28 Updated: 1:NetworkManager-0.8.3.997-1.fc14.i686
Mar 08 12:06:30 Updated: 1:kde-plasma-networkmanagement-0.9-0.35.20110221.fc14.i686
Mar 08 12:06:31 Installed: 1:kde-plasma-networkmanagement-libs-0.9-0.35.20110221.fc14.i686
Mar 08 12:06:32 Updated: sssd-client-1.5.1-9.fc14.i686
Mar 08 12:06:35 Updated: sssd-1.5.1-9.fc14.i686
Mar 08 12:07:51 Erased: knetworkmanager-libs

If I attempt to activate the wireless interface to connect to my home network, I get the following in /var/log/messages:

Mar  8 14:20:06 laputa NetworkManager[13017]: <info> Activation (wlan0) starting connection 'TateFamily'
Mar  8 14:20:06 laputa NetworkManager[13017]: <info> (wlan0): device state change: 3 -> 4 (reason 0)
Mar  8 14:20:06 laputa NetworkManager[13017]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Mar  8 14:20:06 laputa NetworkManager[13017]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Mar  8 14:20:06 laputa NetworkManager[13017]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Mar  8 14:20:06 laputa NetworkManager[13017]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Mar  8 14:20:06 laputa NetworkManager[13017]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Mar  8 14:20:06 laputa NetworkManager[13017]: <info> (wlan0): device state change: 4 -> 5 (reason 0)
Mar  8 14:20:06 laputa NetworkManager[13017]: <info> Activation (wlan0/wireless): access point 'TateFamily' has security, but secrets are required.
Mar  8 14:20:06 laputa NetworkManager[13017]: <info> (wlan0): device state change: 5 -> 6 (reason 0)
Mar  8 14:20:06 laputa NetworkManager[13017]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.

It also pops up the "secrets" dialog, even though the WEP password is stored.

I tried running yum downgrade NetworkManager, but haven't been able to get it working yet.

Version-Release number of selected component (if applicable):
0.8.3.997

How reproducible:
Every time


Steps to Reproduce:
Don't know really.
  
Actual results:
Cannot connect to wireless, networkmanager icon changes to a wifi signal with a white square on the lower left and a key on the lower right.

Expected results:
Wireless should work

Additional info:
Running KDE.  KDE is set to store network secrets unencrypted in a file.

Comment 1 Reilly Hall 2011-03-08 22:01:43 UTC

I am suffering the same problem with F14 i386. Started experiencing it yesterday myself. Attempted regressing to the older version of NetworkManager and then the older version of knetworkmanager\* and that didn't seem to work. Going to try again later tonight see what I can find out.

Comment 2 Joseph Tate 2011-03-09 01:46:13 UTC

I can stop NetworkManager and run iwconfig commands and get the wireless system up and running.  I tried installing nm-applet, but it doesn't show up in the system tray on KDE, so I don't know if it's NM or NM-kde that has the problem.

Comment 3 Joseph Tate 2011-03-11 06:54:54 UTC

I was able to get my wireless to work again after I removed .kde/share/apps/networkmanagement and .kde/share/config/networkmanagementrc.  When I reconfigured, the network manager pieces went back to using the kwallet to store secrets.

Comment 4 Reilly Hall 2011-03-11 14:45:18 UTC

Thanks Joseph, I've been so busy lately.  I also thought that maybe starting the knetworkmanager config over from scratch might help.  I just hadn't been able to dedicate time to hunting down the specific files for that.  So thanks for beating me to it and finding them.  I too am successfully connected once again.  Thank you very much.

Comment 5 Dan Williams 2012-04-30 20:53:49 UTC

I'll close then; it's odd that removing the kde stuff fixes it, but I suppose that's more of a kde bug.  Probably something with the secrets got screwed up and the KDE networkmanagement layer started failing to provide them back to NM when it requested them?