The following was filed automatically by anaconda:
anaconda 13.21.44 exception report
Traceback (most recent call first):
File "/usr/lib/anaconda/gui.py", line 114, in copyScreenshots
for f in os.listdir(screenshotDir):
File "/usr/lib/anaconda/iw/congrats_gui.py", line 59, in getNext
File "/usr/lib/anaconda/gui.py", line 1331, in nextClicked
rc = self.currentWindow.getNext ()
File "/usr/lib/anaconda/gui.py", line 1473, in keyRelease
OSError: [Errno 2] No such file or directory: '/tmp/anaconda-screenshots'
Created attachment 415738 [details]
Attached traceback automatically from anaconda.
This occured on an install when I saved screenshots; it happened when I hit F12 at the 'Congratulations' screen.
It's correct that /tmp/anaconda-screenshots doesn't exist; AFAICT, they're *already* saved in /mnt/sysimage/tmp/anaconda-screenshots.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
Your screenshots are being written to /mnt/sysimage/tmp/anaconda-screenshots instead of /tmp/anaconda-screenshots? Are you positive? Because that's pretty odd, and I can't see how that could be the case unless we are somehow chrooted when calling takeScreenShot().
I'll double check again tomorrow, but I do recall them being in /mnt/sysimage/tmp...
The screenshots were taken during package installation, if that helps.
Verified in 20100524.n.0. Screenshots during package installation are written to /mnt/sysimage/tmp.
Also of note - hitting just printscreen pops up an error message from metacity trying to run gnome-screenshot.
(In reply to comment #7)
> Verified in 20100524.n.0. Screenshots during package installation are written
> to /mnt/sysimage/tmp.
> Also of note - hitting just printscreen pops up an error message from metacity
> trying to run gnome-screenshot.
Oh that's lame. Should we:
ln -s /bin/true /usr/bin/gnome-screenshot
That works. Or you could catch those keys and run the anaconda-specific screenshot code? (That might be more complicated.)
This bug is actually several problems:
1) we do not consider screenshots taken while yum/rpm chroots us into /mnt/sysimage (yes, that really happens)
2) pressing F12 on the last screen doesn't have the same effect as just pressing reboot. pushing the button exits anaconda immediately while pressing f12 does the copying too.
3) the error dialog on printscreen.
I'll try to come up with a fix for all three.
Fixed by 38fc82b2ee568d57b53904800557f980a5640ffb in anaconda-31.21.51-1.el6.
Tested with snapshot #7 and the results are:
(In reply to comment #10)
> This bug is actually several problems:
> 1) we do not consider screenshots taken while yum/rpm chroots us into
> /mnt/sysimage (yes, that really happens)
I took several screenshots during package installation. After install all of them were there.
> 2) pressing F12 on the last screen doesn't have the same effect as just
> pressing reboot. pushing the button exits anaconda immediately while pressing
> f12 does the copying too.
Pressing F12 at the end of the installation didn't lead to traceback. There was a dialog that told me that all screenshots were saved under /root/anaconda-screenshots. This has been fixed.
> 3) the error dialog on printscreen.
When pressing the print screen button during installation there was a message that a new screenshot has been taken. This is fixed.
Moving to VERIFIED.
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.