Description of problem: Two problems: - the graphical installation comes to a standstill when it tries to start the X server. It seems the text console stays and there is a cursor in the top left corner. It's not blinking. - failing the graphical install, I tried text. It fails during installation with a python error. Some unicode error: cannot convert 128 to ASCII or so Version-Release number of selected component (if applicable): Whatever is in the beta DVD ISO How reproducible: always Steps to Reproduce: 1.try to install on Apple G5 (dual socket, but shouldn't matter) 2. 3. Actual results: see above Expected results: both graphical and text installation succeeds Additional info:
Can you please retest with either the latest weekly snapshot or rawhide? I know there have been X changes since the beta that should fix up the first problem you are seeing (at least, similar issues I was seeing have been fixed since then) and the unicode error is definitely fixed. Thanks.
(In reply to comment #1) > Can you please retest with either the latest weekly snapshot or rawhide? How? Where is the snapshot?
We already talked about this in IRC, but pasting here just for tracking purposes. The weekly snapshots are released as ISOs on bittorrent, while rawhide is really hard to track down ISOs for. Sometimes they're made, sometimes not. Anyway you can work around the unicode problem by deselecting the usb firmware packages under hardware support.
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as INSUFFICIENT_DATA.