Bug 642370 - KeyError: 'wlan0' if you delete a wireless entry in the NetworkManager connection editor
Summary: KeyError: 'wlan0' if you delete a wireless entry in the NetworkManager connec...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 14
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Radek Vykydal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 644062 668158 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-12 17:47 UTC by Brian Lane
Modified: 2012-05-31 06:55 UTC (History)
4 users (show)

Fixed In Version: anaconda-15.2.-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-31 06:55:26 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
wlan0 traceback (383.19 KB, text/plain)
2010-10-12 17:48 UTC, Brian Lane 		no flags Details
the traceback (104.61 KB, text/plain)
2010-10-14 07:50 UTC, Radek Vykydal 		no flags Details
Show Obsolete (1) View All

Description Brian Lane 2010-10-12 17:47:23 UTC 
Description of problem:
If you select a wireless device to use during an install (TC1 netinst.iso in this case) you get multiple entries in the NetworkManager edit dialog. If you delete one of them anaconda will traceback when it fails to bring up the device.

Note, my AP is using WPA and I also did not enter the passphrase. If I do not delete one of the entries and do not enter a passphrase I get an error dialog and am allowed to re-try.
Comment 1 Brian Lane 2010-10-12 17:48:36 UTC 
Created attachment 453002 [details]
wlan0 traceback
Comment 2 Radek Vykydal 2010-10-14 07:50:59 UTC 
Created attachment 453393 [details]
the traceback
Comment 3 Chris Lumens 2010-10-18 20:45:28 UTC 
*** Bug 644062 has been marked as a duplicate of this bug. ***
Comment 4 Radek Vykydal 2010-10-19 06:38:36 UTC 
This should be fixed in anaconda-15.2.-1 (rawhide/F15).
Comment 5 Radek Vykydal 2011-06-09 15:17:41 UTC 
*** Bug 668158 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.