[EMAIL PROTECTED] wrote:
Hi all,

I ran into a strange error after the first reboot using the SL 5.0 installation DVD. Since I could not find anything about it in the list archives, I will pass it on here.

After the first reboot the system hung up in the firstboot wizard with the following error:

=================================
Traceback (most recent call last):
  File "/usr/share/firstboot/firstbootWindow.py", line 488, 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
==================================

Some digging revealed the problem was with GTK 2.0, resulting in not displaying png files. The firstboot splash screen was simply the first png file loaded. Re-generating the gdk-pixbuf loader files resolved the problem:

===================
# cd /etc
# cd gtk-2.0/
# gdk-pixbuf-query-loaders-32 > ./i686-redhat-linux-gnu/gdk-pixbuf.loaders
# gdk-pixbuf-query-loaders-64 > ./x86_64-redhat-linux-gnu/gdk-pixbuf.loaders
# reboot
===================

I compared the 64 bit version before and after. The following lines had been added:

===============================================
"/usr/lib64/gtk-2.0/2.10.0/loaders/svg_loader.so"
"svg" 2 "gtk20" "Scalable Vector Graphics"
"image/svg+xml" "image/svg" "image/svg-xml" "image/vnd.adobe.svg+xml" "text/xml-svg" ""
"svg" "svgz" "svg.gz" ""
" <svg" "*    " 100
" <!DOCTYPE svg" "*             " 100

"/usr/lib64/gtk-2.0/2.10.0/loaders/io-wmf.so"
"wmf" 0 "gtk20" "Windows Metafile"
"image/x-wmf" ""
"wmf" "apm" ""
"\327\315\306\232" "" 100

"\001" "" 100

"/usr/lib64/gtk-2.0/2.10.0/loaders/libpixbufloader-png.so"
"png" 5 "gtk20" "The PNG image format"
"image/png" ""
"png" ""
"\211PNG\r\n\032\n" "" 100
==============================================

Maybe this is of use for someone else with the same problem.

Roelof

Hi,
Thank you very much for the information, hopefully it will help those that have this problem. I'm curious as to why it happened, and was wondering if you could send me the following files.

  /root/install.log
  /root/install.log.syslog
  /var/log/anaconda.log
  /var/log/anaconda.syslog

Troy
--
__________________________________________________
Troy Dawson  [EMAIL PROTECTED]  (630)840-6468
Fermilab  ComputingDivision/LCSI/CSI DSS Group
__________________________________________________

Reply via email to