Version-Release number of selected component: anaconda-18.6.5 Additional info: libreport version: 2.0.12 cmdline: nomodeset root=live:LABEL=F18PRETC6 kernel: 3.6.0-0.rc2.git2.1.fc18.i686
Created attachment 610992 [details] File: ifcfg.log
Created attachment 610993 [details] File: anaconda-tb
Created attachment 610994 [details] File: environ
Created attachment 610995 [details] File: type
Created attachment 610996 [details] File: storage.log
Created attachment 610997 [details] File: version
Created attachment 610998 [details] File: program.log
Created attachment 610999 [details] File: product
Created attachment 611000 [details] File: syslog
Created attachment 611001 [details] File: hashmarkername
Created attachment 611002 [details] File: anaconda.log
Created attachment 611003 [details] File: release
Created attachment 611004 [details] File: description
How did you get to this point? What was your process?
My system: One SATA disk 100Gb to install to, one USB disk 100Gb with the Fedora iso on it and one USB SD-card 8Gb with LiveOS, vmlinuz and initrd.img to boot from. I boot from the SD-card and want to use the ISO on the USB disk as OS-source. When I first enter the disc partitioning screen, select the disc to install to and compose a partitioning scheme and after this I enter the source selection screen and select the ISO-image I get this bug. When I do it the other way around, ie. first select the iso and then partition my disc, the bug does not occure.
Does this still happen with the Beta TC1 image? http://dl.fedoraproject.org/pub/alt/stage/18-Beta-TC1/
Closing insufficient data. Please retry with beta TC4 and re-open if the problem still exists (with new log files). http://dl.fedoraproject.org/pub/alt/stage/18-Beta-TC4/
Created attachment 630642 [details] Error logs off TC6 This error is reproduceable with all TC-versions so far. Here is the log with TC6. Remind that it only happens if you first set a new partitioning scheme and after that select the ISO-image. Looks to me the partitioning function somehow blocks the disc that has the ISO-image.
I've tried installation from hd. Step to reproduce: 1. copy iso to ext4 native partition 2. boot system installation only with inst.repo=hd:<device>:<path> as parameters 3. go to INSTALLATION SORCE 4. click on Choose ISO Expected result: no traceback ISO should be selected by default as ISTALLATION SOUCE (now is Clesest mirror) Package: anaconda-18.24 Architecture: x86_64 OS Release: Fedora release 18-Beta-TC7
This is still present in 18-TC1
In 18-TC3 neither described installation strategie does not work anymore. Start installation and as soon as you are in the central screen, try to select an iso. This action makes anaconda crash.
I can't reproduce this with Final TC4. I am able to set up a VM with two disks, one blank, one containing an ext4 partition with a 'DVD.iso' file on it (nothing else), go to the 'Installation Source' spoke, select the disk with the DVD.iso file on it as the Device, select the DVD.iso file from that disk, hit Verify, successfully verify the ISO image, and then proceed with an install, which runs from the ISO image. Haven't tested with the inst.repo=hd parameter yet, but the interactive path works fine, no crash.
er, when I say 'this', I meant the crash A.J. Werkman hit in 21.
inst.repo=hd:vdb1:/DVD.iso works fine too. Maybe there's something specific about A.J.'s config.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.