Description of problem: Trying to install F19 Alpha TC5 (also happened with TC4) in an environment where only available network is a password-protected wireless net. Version-Release number of selected component (if applicable): whatever's in TC5 How reproducible: it fails here about four out of five times, but it did work once for unclear reasons Steps to Reproduce: 1. at network config screen, click on wireless card 2. select protected network from drop-down dialog box Actual results: popup with "an unknown error has occurred" Expected results: should be able to configure network addressing & password at this point Additional info: I can't figure out how to copy-and-paste the stack trace, but it looks like it's trying to update the hostname and is unable to cope with the fact that it can't connect yet.
On my sixth try, I got past this by the expedient of manually entering a hostname (in the text box for that) before attempting to configure the wireless. But I'm not sure if this actually prevented the broken lookup attempt, or if it just randomly worked this time. Anyway, that's a possible workaround for others seeing a crash at this point.
You can use the automated bug reporting thing to report bugs, in which case the traceback will be posted for you. Or, you can switch over to a tty and grab /tmp/anaconda-tb-* and attach it to this bug.
Created attachment 731986 [details] anaconda traceback
thanks, I'd forgotten about the /tmp file. Also, after trying it several more times, I'm now pretty confident in stating that entering a hostname manually before configuring the card *does* suppress the problem.
dd USB boot - acer aspire one n450 2 GB Memory: no wired network connected. Tried to configure wireless WEP on initial spoke that appears when no networking detected; and anaconda 19.16-1 in TC5 crashed. Only resort was to quit
Proposing as Alpha freeze exception; probably not blocker-worthy as it's only wireless and there's a workaround, but seems like a good FE candidate.
(In reply to comment #6) > ... probably not blocker-worthy as it's only wireless ... My guess is that it's not just wireless but any case where manual configuration is needed for connectivity, eg wired network without DHCP server. Protected wireless is probably just the most common case.
I am not able to reproduce. It would be great if you could try this updates image with a patch: http://rvykydal.fedorapeople.org/updates.949002.img You can copy it to storage (eg USB disk) and use updates=hd:<DEVICE_NAME>:<PATH_TO_THE_FILE> (eg updates=hd:sdc1:/updates.949002.img) boot option.
Discussed at 2013-04-15 freeze exception review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-04-15/f19alpha-blocker-review-7.2013-04-15-16.00.log.txt . Rejected as an FE for Alpha: it's just too late to be taking an as-yet-untested fix for a not-super-critical issue.
anaconda-19.21-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/anaconda-19.21-1.fc19
Package anaconda-19.21-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-19.21-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-6338/anaconda-19.21-1.fc19 then log in and leave karma (feedback).
Package anaconda-19.21-1.fc19, python-meh-0.23-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-19.21-1.fc19 python-meh-0.23-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-6338/python-meh-0.23-1.fc19,anaconda-19.21-1.fc19 then log in and leave karma (feedback).
anaconda-19.21-1.fc19, python-meh-0.23-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.