GNOME Bugzilla – Bug 171880
While running two monitor heads, changing the desktop wallpaper caused gnome-panel to crash
Last modified: 2005-03-28 17:06:38 UTC
Distribution: Fedora Core release 2 (Tettnang) Package: gnome-panel Severity: critical Version: GNOME2.6. 2.6.x Gnome-Distributor: Red Hat, Inc Synopsis: While running two monitor heads, changing the desktop wallpaper caused gnome-panel to crash Bugzilla-Product: gnome-panel Bugzilla-Component: clock applet Bugzilla-Version: 2.6.x BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: Description of the crash: While running two monitors, the laptop, and a second larger monitor, I changed the wallpaper on the large monitor and gnome-panel crashed. Steps to reproduce the crash: 1. Run two monitors 2. Change desktop background on second monitor Expected Results: gnome-panel crashes How often does this happen? Haven't tried it more than once. Additional Information: None Debugging Information: Backtrace was generated from '/usr/bin/gnome-panel' (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)...[Thread debugging using libthread_db enabled] [New Thread -151132000 (LWP 3451)] (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)...0x006d07a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 57417
Thread 1 (Thread -151132000 (LWP 3451))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-03-28 11:59 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-panel". 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 sline@steveline.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.
*** Bug 171881 has been marked as a duplicate of this bug. ***
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 146929, which has been marked as a duplicate of 146075. *** This bug has been marked as a duplicate of 146075 ***