Bug 216753 - firstboot traceback upon execution
firstboot traceback upon execution
Product: Fedora
Classification: Fedora
Component: redhat-logos (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: John (J5) Palmieri
Brock Organ
Depends On:
Blocks: 216686
  Show dependency treegraph
Reported: 2006-11-21 15:47 EST by Jesse Keating
Modified: 2013-03-13 00:51 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-06 12:54:36 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jesse Keating 2006-11-21 15:47:08 EST
This is a compose of FC6+FC6 released updates + some other graphics.

# cat firstboot.1163839045.44 
Traceback (most recent call last):
  File "/usr/share/firstboot/firstbootWindow.py", line 481, in loadModules
    result = module.launch()
  File "/usr/share/firstboot/modules/welcome.py", line 45, in launch
    pix = functions.ditheredImageFromFile("splash-small.png")
  File "/usr/share/firstboot/functions.py", line 83, in ditheredImageFromFile
    (pixmap, mask) = pixbuf.render_pixmap_and_mask()
UnboundLocalError: local variable 'pixbuf' referenced before assignment

# cat /tmp/firstboot-crash.log 
Traceback (most recent call last):
  File "/usr/share/firstboot/firstbootWindow.py", line 370, in leb_realized
    bgimage.draw_pixbuf(None, self.pixbuf, 0, 0, 0, 0)
TypeError: GdkDrawable.draw_pixbuf() argument 2 must be gtk.gdk.Pixbuf, not None
Comment 1 Chris Lumens 2006-11-21 22:19:07 EST
As discussed in IRC earlier today, this is a result of the scriptlet in the
redhat-logos package not setting up a symlink for
/usr/share/firstboot/pixmaps/splash-small.png correctly.  This symlink is needed
for localization of the welcome screen image.
Comment 2 Bug Zapper 2008-04-04 00:51:45 EDT
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.

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:

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
Comment 3 Bug Zapper 2008-05-06 12:54:34 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.