GNOME Bugzilla – Bug 449796
crash in gThumb Image Viewer:
Last modified: 2007-06-21 15:06:28 UTC
What were you doing when the application crashed? Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.20-1.2952.fc6 #1 SMP Wed May 16 18:59:18 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 239566848 vsize: 0 resident: 239566848 share: 0 rss: 80240640 rss_rlim: 0 CPU usage: start_time: 1182430925 rtime: 0 utime: 2904 stime: 0 cutime:2683 cstime: 0 timeout: 221 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gthumb' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208297776 (LWP 6989)] [New Thread -1352676464 (LWP 7001)] [New Thread -1342186608 (LWP 7000)] [New Thread -1331696752 (LWP 6999)] [New Thread -1321206896 (LWP 6998)] [New Thread -1287828592 (LWP 6995)] [New Thread -1232430192 (LWP 6994)] (no debugging symbols found) 0x00bfb402 in __kernel_vsyscall ()
+ Trace 142679
Thread 1 (Thread -1208297776 (LWP 6989))
----------- .xsession-errors --------------------- Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". closing closing Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". ** (bug-buddy:14103): WARNING **: Couldn't load icon for Open Folder Xlib: extension "SHAPE" missing on display ":0.0". --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 356623 ***