libreport version: 2.0.10 cmdline: /usr/bin/python /usr/sbin/anaconda executable: /usr/sbin/anaconda exnFileName: /tmp/anaconda-tb-lMTuCj hashmarkername: anaconda kernel: 3.3.4-5.fc17.ppc64 other involved packages: product: Fedora release: Cannot get release name. time: sön 2 dec 2012 12:59:00 version: 17 anaconda-tb-lMTuCj: Binary file, 1388788 bytes description: :The following was filed automatically by anaconda: :anaconda 17.29 exception report :Traceback (most recent call first): : File "/usr/lib64/python2.7/site-packages/pyanaconda/iutil.py", line 181, in execWithRedirect : raise RuntimeError, errstr : File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1978, in install : root=ROOT_PATH) : File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1097, in write : self.install() : File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 2392, in writeBootloader : anaconda.bootloader.write() : File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 383, in dispatch : self.dir = self.steps[self.step].target(self.anaconda) : File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 247, in go_forward : self.dispatch() : File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1201, in nextClicked : self.anaconda.dispatch.go_forward() : File "/usr/lib64/python2.7/site-packages/pyanaconda/iw/progress_gui.py", line 79, in renderCallback : self.intf.icw.nextClicked() : File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1221, in handleRenderCallback : self.currentWindow.renderCallback() :RuntimeError: Error running mkofboot: No such file or directory environ: :LANG=sv_SE.UTF-8 :LC_NUMERIC=C :TERM=linux :TZ=Europe/Stockholm :XAUTHORITY=/root/.Xauthority :GLADEPATH=/tmp/updates/:/tmp/updates/data/ui/:ui/:/usr/share/anaconda/ui/:/usr/share/python-meh/ :SHLVL=0 :PYTHONPATH=/tmp/updates :GNOME_DISABLE_CRASH_DIALOG=1 :LIBUSER_CONF=/tmp/libuser.ey0WxV :LVM_SUPPRESS_FD_WARNINGS=1 :PWD=/ :MALLOC_PERTURB_=204 :GCONF_GLOBAL_LOCKS=1 :HOME=/tmp :PIXMAPPATH=/tmp/updates/pixmaps/:/tmp/updates/:/tmp/product/pixmaps/:/tmp/product/:pixmaps/:/usr/share/anaconda/pixmaps/:/usr/share/pixmaps/:/usr/share/anaconda/:/usr/share/python-meh/:/usr/share/icons/Fedora/48x48/apps/ :PATH=/usr/bin:/bin:/sbin:/usr/sbin:/mnt/sysimage/bin:/mnt/sysimage/usr/bin:/mnt/sysimage/usr/sbin:/mnt/sysimage/sbin:/sbin:/usr/sbin :MALLOC_CHECK_=2 :DISPLAY=:1
Created attachment 655933 [details] File: anaconda-tb-lMTuCj
The problem occurred at the very last stages of a Fedora 17 ppc64 installation to a PowerMac G5 Quad. I have two other Linux installations on this PowerMac, on two different hard drives. This one would coexist with Ubuntu ppc on the same drive. I'm basically installing it to try out Fedora 17, but I can't get it to install at this time. It seems that mkofboot is in fact available in /sbin and appears to be executable. It's strange that anaconda cannot find it. The installation image used was Fedora-17-ppc64-netinst.iso with SHA256 sum (verified): 312094252888d2d247c52e329617b0813ecbcdfff1b0662d65c89c91e0c8efb4
(In reply to comment #2) > The problem occurred at the very last stages of a Fedora 17 ppc64 > installation to a PowerMac G5 Quad. > > I have two other Linux installations on this PowerMac, on two different hard > drives. This one would coexist with Ubuntu ppc on the same drive. I'm > basically installing it to try out Fedora 17, but I can't get it to install > at this time. > > It seems that mkofboot is in fact available in /sbin and appears to be > executable. It's strange that anaconda cannot find it. > > The installation image used was Fedora-17-ppc64-netinst.iso with SHA256 sum > (verified): > 312094252888d2d247c52e329617b0813ecbcdfff1b0662d65c89c91e0c8efb4 Note: I also tried Fedora-17-ppc64-DVD.iso with SHA256 sum (verified) dbb2d36c2ba3208db8889c05dd848476c985eb2e75dbce3f5614d560ba68092d burnt to a different DVD. The result was exactly the same.
We're running mkofboot from the installed system, not from the installation environment. This looks like a problem with the installation tree you are using: 12:43:30,891 DEBUG anaconda: no package matching yaboot Any idea what may be up there?
(In reply to comment #4) > We're running mkofboot from the installed system, not from the installation > environment. This looks like a problem with the installation tree you are > using: > > 12:43:30,891 DEBUG anaconda: no package matching yaboot > > Any idea what may be up there? No idea, but all of this yaboot business seems a bit confusing since I've understood that Fedora 17 should use GRUB2 for booting on OpenFirmware/ppc systems now? See: http://fedoraproject.org/wiki/Fedora_17_PPC_release_notes "Fedora 17 for Power now uses the grub2 bootloader to boot the installed system. yaboot is still used on the installation media but should be considered otherwise deprecated." I understand that mkofboot is part of yaboot. Do you want a me to collect a listing of the installed tree as-is when the install process quits with this error?
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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 17'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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.