Red Hat Bugzilla – Bug 869106
F18 anaconda chokes on wireless network names containing spaces
Last modified: 2013-07-02 23:46:34 EDT
Description of problem:
When trying to connect to a wireless network whose name contains spaces, anaconda is inconsistent about replacing the spaces with underscores. This leads to a crash with the following traceback:
anaconda 18.19 exception report
Traceback (most recent call first):
File "/usr/lib64/python2.7/site-packages/pyanaconda/simpleconfig.py", line 77, in read
with open(filename) as f:
File "/usr/lib64/python2.7/site-packages/pyanaconda/simpleconfig.py", line 187, in read
File "/usr/lib64/python2.7/site-packages/pyanaconda/network.py", line 285, in loadIfcfgFile
File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/network.py", line 1060, in getKSNetworkData
File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/network.py", line 1013, in apply
network_data = getKSNetworkData(dev)
File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/__init__.py", line 72, in _on_continue_clicked
File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/__init__.py", line 77, in <lambda>
self.window.connect("continue-clicked", lambda *args: self._on_continue_clicked(cb))
IOError: [Errno 2] No such file or directory: '/etc/sysconfig/network-scripts/ifcfg-L-K Airport Net'
Local variables in innermost frame:
filename: /etc/sysconfig/network-scripts/ifcfg-L-K Airport Net
Now, "L-K Airport Net" is the actual name of the network I want to connect to. But a look into /etc/sysconfig/network-scripts/ shows that the file that was
created during the network config step is
Version-Release number of selected component (if applicable):
anaconda 18.19 (F18 Beta TC6 compose)
Steps to Reproduce:
1. Configure anaconda to use a wireless net whose name contains spaces (note that as of 18.19 there are various sub-bugs you have to dodge to get this far, see bug #855526)
2. Try to continue to hub screen
I've been using this network name for ten years or so, and it's worked fine with many previous Fedora releases. Something broke recently here.
Proposing as F18 Final Blocker, probably using some criterion like:
The installer must be able to use at least one of the HTTP or FTP remote package source options
(as used in bug 855526)
Patch sent to mailing list, updates image to check the fix:
(you need wired connection to get the updates image)
In theory we could argue this as a Beta blocker. But in an entirely unscientific survey, none of the 30+ APs I can see from my apartment has a space in the SSID. So I'm not _hugely_ worried about it.
Proposing as NTH for Beta.
Discussed at 2012-10-31 NTH review meeting: http://meetbot.fedoraproject.org/fedora-qa/2012-10-31/f18beta-blocker-review-6.2012-10-31-16.00.log.txt . Accepted as NTH as this is obviously pretty inconvenient for those with APs with spaces in the SSID, and could be hard or impossible to work around.
anaconda-18.22-1.fc18 has been submitted as an update for Fedora 18.
The fix in 18.22 is bad, it is causing traceback after visitnig network spoke without selecting any wireless ap.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.22-1.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
anaconda-18.23-1.fc18 has been submitted as an update for Fedora 18.
anaconda-18.24-1.fc18 has been submitted as an update for Fedora 18.
Works for me now in Beta-TC7.
anaconda-18.25-1.fc18 has been submitted as an update for Fedora 18.
anaconda-18.26-1.fc18 has been submitted as an update for Fedora 18.
18.26 went stable. Closing. (Bodhi closing of bugs when updates go stable is currently broken).