GNOME Bugzilla – Bug 160971
Change desktop background crashes desktop preferences applet
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Debian 3.1 Package: control-center Severity: normal Version: GNOME2.8.1 2.6.1 Gnome-Distributor: Debian Synopsis: Change desktop background crashes desktop preferences applet Bugzilla-Product: control-center Bugzilla-Component: background Bugzilla-Version: 2.6.1 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: Desktop background changer crashes on startup Steps to reproduce the crash: 1. Right-click desktop 2. Choose "Change Desktop Background" 3. Expected Results: How often does this happen? 100%, at the moment. Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnome-background-properties' (no debugging symbols found)...Using host libthread_db library "/lib/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)...(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)...[Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 17234)] [New Thread 32769 (LWP 17248)] [New Thread 16386 (LWP 17249)] (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)...0x40a04c0b in waitpid () from /lib/libpthread.so.0
+ Trace 53386
Thread 1 (Thread 16384 (LWP 17234))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-12-10 13:22 ------- Unknown version 2.6.1 in product control-center. Setting version to "2.6.x". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "control-center". 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 mcn4@leicester.ac.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.
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. Matches the stack trace in bug 158773, which has been marked as a duplicate of 148719. *** This bug has been marked as a duplicate of 148719 ***