GNOME Bugzilla – Bug 153102
up2date trashed my themes
Last modified: 2005-07-21 18:52:54 UTC
Distribution: Fedora Core release 2 (Tettnang) Package: gnome-desktop Severity: normal Version: GNOME2.6. unspecified Gnome-Distributor: Red Hat, Inc Synopsis: up2date trashed my themes Bugzilla-Product: gnome-desktop Bugzilla-Component: general Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: Description of the crash: After running up2date on a clean FC2 core installation the default themes are trashed. Right-clicking on the desktop and selecting "change background" results in a crash. Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnome-background-properties' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread -151133536 (LWP 7400)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x00a617a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 50271
Thread 1 (Thread -151133536 (LWP 7400))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-09-19 16:22 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-desktop". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was darren@tenjin.co.uk. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Hi, Here is some additional information (I raised the bug). I just installed a new version of FC2 (just downloaded the DVD ISO) and was going well until I ran up2date. When I restarted the machine next I found the X desktop to look like it was running in safe mode: black background, no small icons, default app icons for everything else, keyboard repeat off; lost all my profiles for Mozilla, Evolution etc. When I try to change the theme I get this message: "The default theme schemas could not be found on your system. This means that you probably don't have metacity installed, or that your gconfd is configured incorrectly." I do have metacity installed. All was working fine until I ran up2date, even my nVidia card! BTW, I have this installed: metacity-2.8.1-2 - and I have Kernel 2.6.8-1.521 Any ideas? Thanks D.
Hi, Looking on the Fedora Bugzilla it looks like this bug (112467) might be related: http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=112467 BTW, I have tried renaming the gconf folder but that didn't do any good (different error). Regards D.
*** This bug has been marked as a duplicate of 146130 ***
Hi, I'm not sure I agree with the "duplicate" status. I've done some digging and found that if you give everyone access to the /etc/gconf folder tree (chmod -R 777 /etc/gconf) then all of the UI / theme problems disappear. Not sure of the root cause, but either the permissions are bad on /etc/gconf, or those file should be somewhere else??? HTH D.
The original bug report (the crash in gnome-bakground-properties) is a dup of 146130. The additional problems you reported in comment #1 constitute a different bug. You really should have reported them as another bug. I'm reopening and re-assigning to gconf, since it looks like where the problem lies.
This really sounds like a Fedora packaging problem, if it's solved by chmodding the gconf directory, not an upstream one. For that reason I'm closing it. If it happens on a fresh install or something, though, feel free to reopen.