GNOME Bugzilla – Bug 146490
crash on trying to change desktop background wallpaper as user
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Fedora Core release 2 (Tettnang) Package: bugzilla.gnome.org Severity: normal Version: GNOME2.6. unspecified Gnome-Distributor: Red Hat, Inc Synopsis: crash on trying to change desktop background wallpaper as user Bugzilla-Product: bugzilla.gnome.org Bugzilla-Component: bug-buddy parsing Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: Description of the crash: Desktop style (gnome) of user-account changed between two system boots (now it's all black, and different symbols are shon in the quick-launch bar). When trying to alter desktop wallpaper, application "gnome-background-properties" crashes. Everything is fine under "root" account... Steps to reproduce the crash: 1. right-click on desktop 2. choose "Desktop properties" 3. Expected Results: How often does this happen? Everytime i try to change desktop wallpaper 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)...(no debugging symbols found)...(no debugging symbols found)...(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 -150751744 (LWP 3202)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x00c83402 in ?? ()
+ Trace 47974
Thread 1 (Thread -150751744 (LWP 3202))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-09 01:46 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "bugzilla.gnome.org". 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 ralf@schwefer-online.de. 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. *** This bug has been marked as a duplicate of 146130 ***