Description of problem: i tried to verify an ISO IMAGE (there was no image) Version-Release number of selected component: anaconda-18.14 Additional info: libreport version: 2.0.14 cmdline: /usr/bin/python /sbin/anaconda kernel: 3.6.1-1.fc18.x86_64 description: :The following was filed automatically by anaconda: :anaconda 18.14 exception report :Traceback (most recent call first): : File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/source.py", line 821, in on_verify_iso_clicked : dev = self.storage.devicetree.getDeviceByName(dev) :UnboundLocalError: local variable 'dev' referenced before assignment
Created attachment 626154 [details] File: anaconda-tb
Created attachment 626155 [details] File: product
Created attachment 626156 [details] File: type
Created attachment 626157 [details] File: ifcfg.log
Created attachment 626158 [details] File: storage.log
Created attachment 626159 [details] File: version
Created attachment 626160 [details] File: environ
Created attachment 626161 [details] File: anaconda.log
Created attachment 626162 [details] File: syslog
Created attachment 626163 [details] File: hashmarkername
Created attachment 626164 [details] File: packaging.log
Created attachment 626165 [details] File: cmdline_file
Created attachment 626166 [details] File: release
Created attachment 626167 [details] File: program.log
Does updates=http://clumens.fedorapeople.org/865897.img fix this?
@Chris Lumens how are these .img files used?
Add updates=<url> to the kernel command line arguments at boot time.
Created attachment 626202 [details] update img result seems ok It seems the updated image did the trick. It no longer crashes. I propose that some form of red or yellow coloring or hue should be applied to the shown dialog to add emphasis to the shown message "this media is not good to install from" (which is a correct message).
There is a small side-effect, unrelated, when booting selecting the updated image on comment #15, executing in VT2 the command 'anaconda --version' no longer works. Anaconda emits a trace-back.
anaconda-18.17-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.17-1.fc18
Package anaconda-18.17-1.fc18: * 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.17-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-16295/anaconda-18.17-1.fc18 then log in and leave karma (feedback).
anaconda-18.18-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.18-1.fc18
Package anaconda-18.18-1.fc18: * 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.18-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-16402/anaconda-18.18-1.fc18 then log in and leave karma (feedback).
anaconda-18.19-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.19-1.fc18
This bug looks to have been fixed for many anaconda builds now but missed being closed. If you find you are still experiencing it with Fedora 18 Beta (RC1) or later, please re-open the bug. (ref comment #18)