The following was filed automatically by anaconda: anaconda 11.5.0.38 exception report Traceback (most recent call first): File "/usr/lib/anaconda/storage/devices.py", line 2687, in eject log.warning("error ejecting cdrom %s: %s" % (device, e)) File "/usr/lib/anaconda/installmethod.py", line 47, in doMethodComplete dev.eject() File "/usr/lib/anaconda/dispatch.py", line 205, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 128, in gotoNext self.moveStep() File "/usr/lib/anaconda/gui.py", line 1317, in nextClicked self.anaconda.dispatch.gotoNext() File "/usr/lib/anaconda/iw/progress_gui.py", line 79, in renderCallback self.intf.icw.nextClicked() File "/usr/lib/anaconda/gui.py", line 1338, in handleRenderCallback self.currentWindow.renderCallback() NameError: global name 'device' is not defined
Created attachment 336886 [details] Attached traceback automatically from anaconda.
After discussion on IRC with representation from devel, release engineering and qa, it was agreed to note this issue on the Beta release notes and defer resolution to post-beta. Changing to F11Blocker and noted in the Beta release notes at https://fedoraproject.org/wiki/Fedora_11_Beta_release_notes#Anaconda_installer_issues
Should be better in new anaconda 11.5.0.39
Created attachment 337195 [details] Attached traceback automatically from anaconda.
Created attachment 337362 [details] Attached traceback automatically from anaconda.
Created attachment 337427 [details] Attached traceback automatically from anaconda.
Created attachment 337443 [details] Attached traceback automatically from anaconda.
Created attachment 337463 [details] Attached traceback automatically from anaconda.
*** Bug 493227 has been marked as a duplicate of this bug. ***
Created attachment 337487 [details] Attached traceback automatically from anaconda.
Created attachment 337526 [details] Attached traceback automatically from anaconda.
*** Bug 493323 has been marked as a duplicate of this bug. ***
*** Bug 493320 has been marked as a duplicate of this bug. ***
Created attachment 337539 [details] Attached traceback automatically from anaconda.
Created attachment 337543 [details] Attached traceback automatically from anaconda.
Created attachment 337578 [details] Attached traceback automatically from anaconda.
*** Bug 493416 has been marked as a duplicate of this bug. ***
Created attachment 337589 [details] Attached traceback automatically from anaconda.
Created attachment 337598 [details] Attached traceback automatically from anaconda.
Created attachment 337614 [details] Attached traceback automatically from anaconda.
Created attachment 337624 [details] Attached traceback automatically from anaconda.
Is it also common that when encountering this bug the system does not install grub and can not be booted until selinux=0 is passed on the grub line (once one does a rescue boot and does grub --rescan /dev/sda)? Once booted, one can do a relabel on the drive and it's fine after that, so this is aborting before something critical happens. I can log a separate bug on it, in fact I should, just wanted to make a comment here on it.
Created attachment 337643 [details] Attached traceback automatically from anaconda.
Created attachment 337656 [details] Attached traceback automatically from anaconda.
FYI -- bugzilla preferences allow one to disable email notification when the CC list changes.
Created attachment 337670 [details] Attached traceback automatically from anaconda.
Created attachment 337697 [details] Attached traceback automatically from anaconda.
Created attachment 337703 [details] Attached traceback automatically from anaconda.
Created attachment 337705 [details] Attached traceback automatically from anaconda.
Comment on attachment 337705 [details] Attached traceback automatically from anaconda. HW is HP Elitebook 6930p
Created attachment 337714 [details] Attached traceback automatically from anaconda.
Created attachment 337715 [details] Attached traceback automatically from anaconda.
Comment on attachment 337714 [details] Attached traceback automatically from anaconda. Actual installation was successful. Rebooted into post install config. Finished that, and logged into desktop.
Created attachment 337724 [details] Attached traceback automatically from anaconda.
Created attachment 337781 [details] Attached traceback automatically from anaconda.
Created attachment 337829 [details] Attached traceback automatically from anaconda.
*** Bug 493683 has been marked as a duplicate of this bug. ***
Created attachment 337885 [details] Attached traceback automatically from anaconda.
Created attachment 337934 [details] Attached traceback automatically from anaconda.
Created attachment 337958 [details] Attached traceback automatically from anaconda.
Created attachment 337959 [details] Attached traceback automatically from anaconda.
Created attachment 337966 [details] Attached traceback automatically from anaconda.
Created attachment 337973 [details] Attached traceback automatically from anaconda.
Created attachment 337976 [details] Attached traceback automatically from anaconda.
Created attachment 338012 [details] Attached traceback automatically from anaconda.
Created attachment 338017 [details] Attached traceback automatically from anaconda.
Created attachment 338037 [details] Attached traceback automatically from anaconda.
Created attachment 338050 [details] Attached traceback automatically from anaconda.
*** Bug 493967 has been marked as a duplicate of this bug. ***
Created attachment 338053 [details] Attached traceback automatically from anaconda.
Created attachment 338131 [details] Attached traceback automatically from anaconda.
Created attachment 338141 [details] Attached traceback automatically from anaconda.
Created attachment 338143 [details] Attached traceback automatically from anaconda.
Created attachment 338144 [details] Attached traceback automatically from anaconda.
Created attachment 338154 [details] Attached traceback automatically from anaconda.
Created attachment 338169 [details] Attached traceback automatically from anaconda.
Created attachment 338171 [details] Attached traceback automatically from anaconda.
Created attachment 338181 [details] Attached traceback automatically from anaconda.
*** Bug 494140 has been marked as a duplicate of this bug. ***
Created attachment 338186 [details] Attached traceback automatically from anaconda.
Created attachment 338193 [details] Attached traceback automatically from anaconda.
Created attachment 338195 [details] Attached traceback automatically from anaconda.
Created attachment 338208 [details] Attached traceback automatically from anaconda.
Created attachment 338217 [details] Attached traceback automatically from anaconda.
Created attachment 338250 [details] Attached traceback automatically from anaconda.
Created attachment 338257 [details] Attached traceback automatically from anaconda.
Created attachment 338262 [details] Attached traceback automatically from anaconda.
*** Bug 494231 has been marked as a duplicate of this bug. ***
Created attachment 338284 [details] Attached traceback automatically from anaconda.
Comment on attachment 338208 [details] Attached traceback automatically from anaconda. It seems that the bug tahe place at the end of installation. grub is created so I could use the installation.
Created attachment 338327 [details] Attached traceback automatically from anaconda.
Created attachment 338331 [details] Attached traceback automatically from anaconda.
Created attachment 338356 [details] Attached traceback automatically from anaconda.
By the way, the DVD *does* eject after the scan of the install media. My guess is that Anaconda needs to use the same command/instruction. My boot after cancellation of F11 install due to this eject bug results in a 'black screen'. I have an ATI FireGL V7500 discrete video card plus another ATI integrated card in a new Lenovo W500 laptop. The F11 LiveCD runs just fine though. Right now I am attempting to install F10...
Created attachment 338364 [details] Attached traceback automatically from anaconda.
Created attachment 338422 [details] Attached traceback automatically from anaconda.
Created attachment 338445 [details] Attached traceback automatically from anaconda.
Created attachment 338447 [details] Attached traceback automatically from anaconda.
Created attachment 338465 [details] Attached traceback automatically from anaconda.
This issue has been fixed for some tome, going to close it so we stop getting all these unnecessary automatic additions to the bug.
*** Bug 494674 has been marked as a duplicate of this bug. ***
Created attachment 338590 [details] Attached traceback automatically from anaconda.
Created attachment 338627 [details] Attached traceback automatically from anaconda.
Created attachment 338690 [details] Attached traceback automatically from anaconda.
Created attachment 338718 [details] Attached traceback automatically from anaconda.
Created attachment 338740 [details] Attached traceback automatically from anaconda.
Created attachment 338759 [details] Attached traceback automatically from anaconda.
Created attachment 338801 [details] Attached traceback automatically from anaconda.
Created attachment 338802 [details] Attached traceback automatically from anaconda.
Created attachment 338814 [details] Attached traceback automatically from anaconda.
Created attachment 338821 [details] Attached traceback automatically from anaconda.
Created attachment 338825 [details] Attached traceback automatically from anaconda.
Created attachment 338831 [details] Attached traceback automatically from anaconda.
Created attachment 338832 [details] Attached traceback automatically from anaconda.
Installing on an AMD64. I had previously installed F10/64 on this system, and was replacing it with the Beta (i.e., there was already a version of grub on the drive). I was using the "basic video driver" install due to problems with the ATI card and video. I had selected the Rawhide repos at the package selection start, and then left all installed packages as default. Interesting enough, the install appears to have actually finished. I believe the installer was just trying to eject the DVD and then choked. I filed the bug report using the installer's UI, after which the installer exited and rebooted the system. When the system came back up, the final installer steps proceeded normally and the system is now running fine.
Created attachment 338946 [details] Attached traceback automatically from anaconda.
Created attachment 338998 [details] Attached traceback automatically from anaconda.
Created attachment 339027 [details] Attached traceback automatically from anaconda.
Created attachment 339046 [details] Attached traceback automatically from anaconda.
Created attachment 339063 [details] Attached traceback automatically from anaconda.
Created attachment 339084 [details] Attached traceback automatically from anaconda.
Created attachment 339125 [details] Attached traceback automatically from anaconda.
Created attachment 339160 [details] Attached traceback automatically from anaconda.
Created attachment 339164 [details] Attached traceback automatically from anaconda.
Created attachment 339204 [details] Attached traceback automatically from anaconda.
*** Bug 495249 has been marked as a duplicate of this bug. ***
Created attachment 339271 [details] Attached traceback automatically from anaconda.
Created attachment 339274 [details] Attached traceback automatically from anaconda.
Created attachment 339318 [details] Attached traceback automatically from anaconda.
Created attachment 339344 [details] Attached traceback automatically from anaconda.
Created attachment 339398 [details] Attached traceback automatically from anaconda.
Created attachment 339450 [details] Attached traceback automatically from anaconda.
Created attachment 339602 [details] Attached traceback automatically from anaconda.
*** Bug 495864 has been marked as a duplicate of this bug. ***
Created attachment 339740 [details] Attached traceback automatically from anaconda.
Created attachment 339783 [details] Attached traceback automatically from anaconda.
Created attachment 339877 [details] Attached traceback automatically from anaconda.
Created attachment 339901 [details] Attached traceback automatically from anaconda.
Created attachment 339914 [details] Attached traceback automatically from anaconda.
*** Bug 496144 has been marked as a duplicate of this bug. ***
Created attachment 339927 [details] Attached traceback automatically from anaconda.
Hey guys! i found the solution!!! if you have installed another distribution of linux on your pc & thats boot grub is your default, you cant install this version of fedora!!! to solve this problem, i installed windows 1st to change my boot grub to windows & after that i installed Fedora with no errors!!! i hope this will help all you guys to fix your problem & have a happy installation :-) regards
(In reply to comment #122) > Hey guys! i found the solution!!! > if you have installed another distribution of linux on your pc & thats boot > grub is your default, you cant install this version of fedora!!! > to solve this problem, i installed windows 1st to change my boot grub to > windows & after that i installed Fedora with no errors!!! > i hope this will help all you guys to fix your problem & have a happy > installation :-) > > regards This is not the issue here. My drive was zeroed-out (at least the first few hundred blocks). It turns out that GRUB was installed after all, so I rebooted in F11.
Created attachment 340022 [details] Attached traceback automatically from anaconda.
My drive also had FC10 installed previously, and the crash occurred at the end of the install when it tries to eject the CD just like Charlie (https://bugzilla.redhat.com/show_bug.cgi?id=492459#c95) reported. After a reboot the OS works fine so far.
Created attachment 340043 [details] Attached traceback automatically from anaconda.
Created attachment 340047 [details] Attached traceback automatically from anaconda.
Created attachment 340052 [details] Attached traceback automatically from anaconda.
Created attachment 340082 [details] Attached traceback automatically from anaconda.
Created attachment 340194 [details] Attached traceback automatically from anaconda.
Created attachment 340237 [details] Attached traceback automatically from anaconda.
Comment on attachment 340194 [details] Attached traceback automatically from anaconda. When I submitted this one F11 beta had just finished installing and had an unhandled exception after the last package finished.
Created attachment 340243 [details] Attached traceback automatically from anaconda.
Created attachment 340307 [details] Attached traceback automatically from anaconda.
Created attachment 340429 [details] Attached traceback automatically from anaconda.
Created attachment 340451 [details] Attached traceback automatically from anaconda.
Created attachment 340591 [details] Attached traceback automatically from anaconda.
Created attachment 340739 [details] Attached traceback automatically from anaconda.
Created attachment 340753 [details] Attached traceback automatically from anaconda.
Created attachment 340803 [details] Attached traceback automatically from anaconda.
Comment on attachment 340803 [details] Attached traceback automatically from anaconda. Installation failed with Parallels 3.0 for Mac. /boot ext3 / ext4
Created attachment 340842 [details] Attached traceback automatically from anaconda.
Created attachment 340843 [details] Attached traceback automatically from anaconda.
Comment on attachment 340843 [details] Attached traceback automatically from anaconda. Installation failed with Parallels 4.0 for Mac. /boot ext3 100 MB / ext4
Created attachment 340857 [details] Attached traceback automatically from anaconda.
Created attachment 340938 [details] Attached traceback automatically from anaconda.
Created attachment 341053 [details] Attached traceback automatically from anaconda.
Created attachment 341281 [details] Attached traceback automatically from anaconda.
Created attachment 341380 [details] Attached traceback automatically from anaconda.
Created attachment 341385 [details] Attached traceback automatically from anaconda.
Created attachment 341464 [details] Attached traceback automatically from anaconda.
Created attachment 341471 [details] Attached traceback automatically from anaconda.
Created attachment 341598 [details] Attached traceback automatically from anaconda.
Created attachment 341857 [details] Attached traceback automatically from anaconda.
Created attachment 342508 [details] Attached traceback automatically from anaconda.
Created attachment 342838 [details] Attached traceback automatically from anaconda.
*** Bug 500555 has been marked as a duplicate of this bug. ***
Created attachment 343736 [details] Attached traceback automatically from anaconda.
Created attachment 344250 [details] Attached traceback automatically from anaconda.
Created attachment 345660 [details] Attached traceback automatically from anaconda.
Created attachment 346741 [details] Attached traceback automatically from anaconda.