GNOME Bugzilla – Bug 159740
Crash when adding (drag or "Add Wallpaper") a new image
Last modified: 2004-12-22 21:47:04 UTC
This happens when I drag a new image to the wallpaper dialogue. Before I had a 2880 x 1176 TIFF, with much translucency and a 50% opacity image in the middle, called hej4.tif. I then add an image called hej2.tif, with the same dimensions, only 100% opacity on the image. Here gnome-panel crashes, and gnome-background-properties freezes (have to kill it -- it seems to get stuck in a "race" -- 90% CPU) Before setting these wallpapers I used a horizontal gradient. The relevant wallpaper images are here: http://findus.dhs.org/~odd/gnome-wallpaper-bug/gnome-wallpaper-crash-files.tar.bz2 Steps to reproduce the crash: 1. Use horizontal gradient 2. Add hej4.tif. Use it. 3. Add hej2.tif, try to use it. Expected Results: Wallpaper should be displayed. How often does this happen? Every time. Debugging Information: Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found) Using host libthread_db library "/lib/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 182969622656 (LWP 4363)] (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) 0x0000002a96f789a6 in waitpid () from /lib/libpthread.so.0
+ Trace 52813
Thread 1 (Thread 182969622656 (LWP 4363))
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 159724, which has been marked as a duplicate of 146075. *** This bug has been marked as a duplicate of 146075 ***