GNOME Bugzilla – Bug 157687
Desktop Background Application Crashes
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Novell Linux Desktop 9 (i586) Package: gnome-desktop Severity: normal Version: GNOME2.6. unspecified Gnome-Distributor: Novell, Inc. Synopsis: Desktop Background Application Crashes Bugzilla-Product: gnome-desktop Bugzilla-Component: general Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: Description of the crash: While trying to change the background on my desktop, the application crashes. Steps to reproduce the crash: 1. Goto the system menu. 2. Click on Personal Settings. 3. Double Click on the Desktop Background under Appearance Can be reproduced using other methods of access application as well. Expected Results: The application will not load. I receive an error message that says "The application 'gnome-background-properties' has quit unexpectedly." It has three options: Restart Application, Close, or Inform Developers. How often does this happen? Every time I try to change my desktop background. Additional Information: I have recently updated my system with all the updates in Red-Carpets NLD chanell. (Not those on the QA or Test chanell.) Debugging Information: Backtrace was generated from '/opt/gnome/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)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(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 1088753696 (LWP 6660)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0xffffe410 in ?? ()
+ Trace 51747
Thread 1 (Thread 1088753696 (LWP 6660))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-11-08 14:53 ------- 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 judevries@novell.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.
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 146503, which has been marked as a duplicate of 146130. *** This bug has been marked as a duplicate of 146130 ***