GNOME Bugzilla – Bug 316140
Desktop background preferences dialog crashes on opening
Last modified: 2006-04-19 11:42:12 UTC
Distribution: Debian testing/unstable Package: control-center Severity: normal Version: GNOME2.10.2 2.8.2 Gnome-Distributor: Debian Synopsis: Desktop background preferences dialog crashes on opening Bugzilla-Product: control-center Bugzilla-Component: background Bugzilla-Version: 2.8.2 BugBuddy-GnomeVersion: 2.0 (2.8.1) Description: Description of the crash: Background preferences dialog crashes upon launch Steps to reproduce the crash: 1. Run background preferences app 2. 3. Expected Results: Crash How often does this happen? Every time 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) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (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 -1222080832 (LWP 7392)] [New Thread -1224836176 (LWP 7393)] (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) 0xb79a9201 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 62970
Thread 1 (Thread -1222080832 (LWP 7392))
------- Bug moved to this database by unknown@gnome.bugs 2005-09-13 03:49 UTC ------- Unknown version 2.8.2 in product control-center. Setting version to "2.8.x". The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@gnome.bugs. Previous reporter was vek02@yahoo.com.
looks like a unique stack trace. Crash happens in gnome-vfs, changing product.
Quite likely a duplicate of #148719. gnome-vfs-daemon needs to be restarted. *** This bug has been marked as a duplicate of 148719 ***
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. *** This bug has been marked as a duplicate of 316880 ***