Bug 112467
Summary: | The default theme schemas could not be found when setting themes | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | James Hsu <jameshhsu> |
Component: | libgnome | Assignee: | Ray Strode [halfline] <rstrode> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | 2lprbe78 |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-09-09 18:58:53 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
James Hsu
2003-12-20 09:02:10 UTC
Do you have metacity installed? How did you install your GNOME packages? From the distro binaries or self compiled? You could try to do 'mv .gconf .gconf.old' after logging out. This will give you a fresh set of settings when logging back out. If that solves it maybe a 'diff -urN .gconf.old .gconf' will give some clues... Reverting from libgnome 2.6.0-3 to 2.6.0-2 seems to eliminate this problem. Prior to that, completely removing the user and recreating it still let the user with a seemingly broken gconf. Users who logged in once before the libgnome 2.6.0-3 update was installed seemed to work alright, but if there was no .gconf dir for them, the one that was created would be busted after that update. Hi, Not a long term solution but if you do this: chmod -R 777 /etc/gconf - the problem is solved. I'm sure there is a nicer way to do this (and more secure), but at least it works! Regards D. Hi, Red Hat Linux 9 is very old and now unsupported. If you can reproduce this problem with a recent version of RHEL or Fedora Core, feel free to reopen this bug. |