GNOME Bugzilla – Bug 118856
I reinstalled redhat 9 on different hd, remounted old drive and redefined my home dir (after chowning it to me) logged in and tried to change my theme
Last modified: 2004-12-22 21:47:04 UTC
Package: gnome-themes Severity: normal Version: 2.2.0.1 Synopsis: I reinstalled redhat 9 on different hd, remounted old drive and redefined my home dir (after chowning it to me) logged in and tried to change my theme Bugzilla-Product: gnome-themes Bugzilla-Component: Crux BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: crash bang boom (in my best Bjork impression) Steps to reproduce the problem: 1. Install Redhat9 then Ximian Desktop then go crazy installing fonts and themes 2. When system stability goes down reinstall RH9 from the LTSP Project 3. mount /dev/{olddrive} /old chown it then edit /etc/passwd, login and naively expect it all to just work ;) Actual Results: ran theme changer selected theme and kapow! Expected Results: see above How often does this happen? I'll let you know Additional Information: Do not try this at home Debugging Information: Backtrace was generated from '/usr/bin/gnome-theme-manager' (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)...[New Thread 16384 (LWP 3960)] (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)...0x4093c806 in waitpid () from /lib/libpthread.so.0
+ Trace 39231
Thread 1 (Thread 16384 (LWP 3960))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-08-01 05:10 ------- The original reporter (jason@plug.ca) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, seth@gnome.org.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. Also, feel free to follow the status of this bug in bug 115034 and add any additional information you may find. It may help them track down this bug. *** This bug has been marked as a duplicate of 115034 ***