GNOME Bugzilla – Bug 301383
It is impossible to start the background picture! :(
Last modified: 2005-04-21 15:19:14 UTC
Distribution: Debian testing/unstable Package: gnome-desktop Severity: normal Version: GNOME2.8.1 unspecified Gnome-Distributor: Ubuntu Synopsis: It is impossible to start the background picture! :( Bugzilla-Product: gnome-desktop Bugzilla-Component: general Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnome-background-properties' (no debugging symbols found)...Using host libthread_db library "/lib/tls/i686/cmov/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)...[Thread debugging using libthread_db enabled] [New Thread 1087623616 (LWP 19176)] [New Thread 1100463024 (LWP 19179)] [Thread debugging using libthread_db enabled] [New Thread 1087623616 (LWP 19176)] [New Thread 1100463024 (LWP 19179)] [Thread debugging using libthread_db enabled] [New Thread 1087623616 (LWP 19176)] [New Thread 1100463024 (LWP 19179)] [New Thread 1100196784 (LWP 19178)] [New Thread 1099049904 (LWP 19177)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 58464
Thread 4 (Thread 1099049904 (LWP 19177))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-04-20 15:36 ------- 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 kalle-vedin@spray.se. 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 155517, which has been marked as a duplicate of 146645 *** This bug has been marked as a duplicate of 146645 ***