Red Hat Bugzilla – Bug 156003
error loading theme Default; can't open Default/Default.xml
Last modified: 2007-11-30 17:11:04 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.2) Gecko/20040308
Description of problem:
Reboot to mulituser (after this morning's up2date) cannot login to X11 console. The graphical error box says "There was an error loading the theme Default. Can't open file /usr/share/gdm/themes/Default/Default.xml".
Indeed, the only files in /usr/share/gdm/themes are: Bluecurve circles happygnome happygnome-list. Creating directory Default as symlink to Bluecurve, and file Default/Default.xml as symlink to Bluecurve.xml still does not work.
The Welcome box shows Username: with pre-entered "...", but it will not accept a click to focus, no username can be entered, and typing is ignored. Mouse is active: choosing Session brings up dialog, choices can be selected and OKd, but they have no effect: cannot login. Console switching via Ctrl-Alt-Fn does not work.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. up2date; reboot; attempt to login to graphical console
Actual Results: Error box with complaint about loading theme Default, and file /usr/share/gdm/themes/Default/Default.xml missing. No response to typing on console.
Expected Results: Normal login capability on graphical console.
Same problem but creating actual /Defaults directory and copying contents of
bluecurve to the /Default directory then copying bluecurve.xml to Defaults.xml
*** Bug 156034 has been marked as a duplicate of this bug. ***
I am courious as to how this was resolved? I know I can create the directory/mod
the config file, but why did it happen in the first place and more inportantly
what is being done to fix whatever caused it in the first place? IOW why was it
closed? Did I miss something?
We removed the "Default" symlink from the redhat-artwork package, since it shows
up as a duplicate Bluecurve entry in the gdm config tool. This broke gdm, since
we overlooked that the gdm.conf file still referred to the Default theme. The
fix was to make the gdm.conf file refer to Bluecurve directly