GNOME Bugzilla – Bug 158378
cannot change desktop background
Last modified: 2005-01-17 03:36:55 UTC
Distribution: Fedora Core release 2 (Tettnang) Package: gnome-desktop Severity: normal Version: GNOME2.6. unspecified Gnome-Distributor: Red Hat, Inc Synopsis: cannot change desktop background Bugzilla-Product: gnome-desktop Bugzilla-Component: general Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: Description of the crash: cannot change desktop background, error is displayed right after clicking "Change Desktop Backround" from the context menu on the desktop. Steps to reproduce the crash: 1. right click on the desktop 2. choose change desktop backround 3. an error appears Expected Results: changing backround or at least choose from image files? How often does this happen? always when I try Additional Information: version 2.5.90.2 of the GNOME Display Manager 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 -151129440 (LWP 2993)] [New Thread 16358320 (LWP 2996)] [Thread debugging using libthread_db enabled] [New Thread -151129440 (LWP 2993)] [New Thread 16358320 (LWP 2996)] [Thread debugging using libthread_db enabled] [New Thread -151129440 (LWP 2993)] [New Thread 16358320 (LWP 2996)] [New Thread 15817648 (LWP 2995)] [New Thread 27167664 (LWP 2994)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x009d4402 in ?? ()
+ Trace 52026
Thread 1 (Thread -151129440 (LWP 2993))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-11-15 11:40 ------- 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 ika@bio.med.pl. 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. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Please make sure that the package was compiled with debugging symbols and see http://bugzilla.gnome.org/getting-traces.cgi for more information about useful stack traces. According to the simple-dup-finder this is a unique stack trace.
There's been no response and I'm fairly sure this is a duplicate of bug 146645, so I'm going to mark it as such. If we can get a more complete stack trace and it says otherwise, we can take a closer look, but I'm pretty sure it's a dupe.
*** This bug has been marked as a duplicate of 146645 ***