Description of problem: Installation stalls at "Checking dependencies in packages selected for installtion..." box Version-Release number of selected component (if applicable):FC5 x86_64 How reproducible:Every time Steps to Reproduce: 1.Boot system with CD #1 and follow the prompts 2. 3. Actual results:Graphic, as well as text, installations will halt. However, using the 'vnc' method avoids the problem Expected results:No halting Additional info: During the check, the installation process throws up an error box and complains about not being able to eject the CD. It suggest that the CD device might be accessed via Virtual Console #2.
The FC5 x86_64 CD set was verified during the media check phase.
Is it actually stalled, or just going very slowly? This step can take a while, especially with a complicated set of packages. Are there any messages on tty1 or tty3?
As I think about this bug report, one additional comment: The error occured even during the DVD ISO installation. Did not make a difference whether the CD ISOs were used or the DVD ISO. Thanks!
Per Chris's question in comment #2 -- Is it actually stalled, or just going very slowly? This step can take a while, especially with a complicated set of packages. Are there any messages on tty1 or tty3?
It stalled. No additional messages on any tty. I checked the above ttys. I am using a Pentium D - dual core 2.66 Ghz Intel processor with 2 Gbytes of Ram. When the installation process used the VNC method of installation, the "stalled" action only took 2 minutes to complete. However, using the normal console method, that same "stalled" action would not change after 15 minutes of waiting. It was stalled! (I gave up after 15 minutes). Now, another piece of information: I did the normal method for installing using the 32 bit FC5 iso images. The 32 bit CDrom as well as the DVD installed FC5 without stalling! So, this "stalling" problem is restricted to the 64 bit version of FC5
Can you switch to tty2 when it's stalled and try to run top and see what's running?
Reducing severity due to non-activity.
Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and will not be fixed by Fedora. Therefore we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen thus bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.