GNOME Bugzilla – Bug 156884
change desktop background crashes
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Fedora Core release 2 (Tettnang) Package: gnome-panel Severity: normal Version: GNOME2.6. 2.6.1 Gnome-Distributor: Red Hat, Inc Synopsis: change desktop background crashes Bugzilla-Product: gnome-panel Bugzilla-Component: clock applet Bugzilla-Version: 2.6.1 BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: Description of the crash: Try to change the background. It starts at crashes. Steps to reproduce the crash: 1. 2. 3. Expected Results: Should be able to do it. I installed Fedora-core2 and it worked fine then. After after installing the updates, things are no more stable. How often does this happen? everytime. Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnome-background-properties' (no debugging symbols found)...Using host libthread_db library "/lib64/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 182935093600 (LWP 3548)] (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)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x00000038bad0be25 in waitpid () from /lib64/tls/libpthread.so.0
+ Trace 51467
Thread 1 (Thread 182935093600 (LWP 3548))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-10-30 06:07 ------- Unknown version 2.6.1 in product gnome-panel. Setting version to "1.5.x". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-panel". 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 linuxram@us.ibm.com. 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.
This appears to be a unique stack trace according to a quick query. Reporter: Could you install the debuginfo packages from http://download.fedora.redhat.com/pub/fedora/linux/core/2/i386/debug/, get the crash to occur again, and then paste the new stack trace here?
(Looks somewhat like the traces in bug 158979 and bug 160914).
*** This bug has been marked as a duplicate of 146130 ***