Red Hat Bugzilla – Full Text Bug Listing
|Summary:||black display after clicking "Exit installer" in "Unknown Device" dialog|
|Product:||[Fedora] Fedora||Reporter:||Steve Tyler <stephent98>|
|Component:||anaconda||Assignee:||Ales Kozumplik <akozumpl>|
|Status:||CLOSED WONTFIX||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||13||CC:||jonathan, jzeleny, vanmeeuwen+fedora|
|Fixed In Version:||anaconda-13.38||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2011-06-27 11:19:00 EDT||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:|
Description Steve Tyler 2010-03-26 16:05:18 EDT
Created attachment 402933 [details] screenshot of "Unknown Device" dialog Description of problem: After clicking "Exit installer" in the "Unknown Device" dialog, the display goes black. The pointer is visible and functional. The consoles operate as expected. Version-Release number of selected component (if applicable): 19:33:18,804 INFO loader: anaconda version 13.37 on x86_64 starting F13-Beta-RC1 Fedora-13-Beta-x86_64-netinst.iso How reproducible: Always. Steps to Reproduce: 1. Install netinst image on USB stick. sudo livecd-iso-to-disk --reset-mbr --format Fedora-13-Beta-x86_64-netinst.iso /dev/sdc1 2. Proceed to the filter dialog shown in the screenshot. 3. Check a hard drive, do not check the USB stick. 4. Click Next. 5. Click "Exit installer". Actual results: Display goes black. Expected results: System reboots. Additional info: Black display in a different case is reported here: Bug 571861 - exception reporting terminates with black display The "Unknown Device" error is reported here: Bug 568343 - 13-Alpha.RC3 install from USB drive fails with unknown device
Comment 4 Ales Kozumplik 2010-03-29 08:18:51 EDT
Proposing as F13Target. I have a simple fix ready for this.
Comment 5 Ales Kozumplik 2010-04-12 03:29:46 EDT
Fixed by a5641ea8efc9e8405ae2de02847dbd916916cee4, will be in anaconda-13.38.
Comment 6 Ales Kozumplik 2010-04-12 03:35:01 EDT
Fixed on rawhide by 88729013d2d3bc0979bef580a7bc8660e47d155d, will be in anaconda-14.4.
Comment 7 Steve Tyler 2010-04-12 14:05:03 EDT
(In reply to comment #5) > Fixed by a5641ea8efc9e8405ae2de02847dbd916916cee4, will be in anaconda-13.38. Thanks, Ales. http://git.fedoraproject.org/git/anaconda.git?p=anaconda.git;a=commit;h=a5641ea8efc9e8405ae2de02847dbd916916cee4
Comment 8 Bug Zapper 2011-06-02 11:53:10 EDT
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 9 Bug Zapper 2011-06-27 11:19:00 EDT
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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. Thank you for reporting this bug and we are sorry it could not be fixed.