Description of Problem: When calling up2date, a traceback appears with a RuntimeError: couldn't load the font. up2date exits without connecting to redhat. How Reproducible: Always Steps to Reproduce: 1. log in as root 2. call up2date from an xterm Actual Results: A window flashes open briefly and then closes. The following message appears in the xterm. Traceback (innermost last): File "/usr/sbin/up2date", line 831, in ? main() File "/usr/sbin/up2date", line 817, in main gui.main() File "/usr/share/rhn/up2date/gui.py", line 701, in main gui = Gui() File "/usr/share/rhn/up2date/gui.py", line 69, in __init__ style.font = gtk.load_font("-*-helvetica-bold-r-normal--12-*-*-*-p-*-iso8859-1") File "/usr/lib/python1.5/site-packages/gtk.py", line 2610, in load_font return _gtk.gdk_font_load(font) RuntimeError: couldn't load the font Expected Results: up2date should connect to redhat and check for upgrades. Additional Information: This problem appeared after an upgrade from RH7.0 -> 7.1 rpm -q up2date kdebase kdelibs kernel python pygtk XFree86 up2date-2.5.4-1 kdebase-2.1.1-8 kdelibs-2.1.2-1 kernel-2.4.2-2 python-1.5.2-30 pygtk-0.6.6-7 XFree86-4.0.3-5
Gotten some reports that this bug goes away after a restart of xfs and X. Can you verify that is the case? Will attempt to change the up2date code to handle not being able to find this font, but the root of the issue seems to be some sort of Xfree/xfs bug...
Not for me, I'm afraid. I get exactly the same error (did I do it right? I killed the xfs pid and then restarted xfs with the same options, tried up2date, hit ctrl-alt-backspace, logged back in, tried up2date again). I think you're right though about it being down to an X bug, I'm having severe problems with kde (I did all the above in gnome) and the folks at bugs.kde.org think it has to do with xft. Thanks, John
Upgrading to XFree86-4.1.0 seems to resolve this problem. Recommend closing.