GNOME Bugzilla – Bug 487537
crash in gThumb Image Viewer: looking at picture
Last modified: 2007-10-17 15:10:56 UTC
What were you doing when the application crashed? looking at picture Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 76759040 vsize: 76759040 resident: 32657408 share: 22265856 rss: 32657408 rss_rlim: 4294967295 CPU usage: start_time: 1192633247 rtime: 176 utime: 154 stime: 22 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 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 -1208178976 (LWP 21897)] [New Thread -1255015536 (LWP 21922)] [New Thread -1254487152 (LWP 21921)] [New Thread -1253958768 (LWP 21920)] [New Thread -1253430384 (LWP 21919)] [New Thread -1235825776 (LWP 21913)] [New Thread -1235297392 (LWP 21912)] [New Thread -1234769008 (LWP 21911)] [New Thread -1234240624 (LWP 21910)] [New Thread -1233712240 (LWP 21905)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 170867
Thread 1 (Thread -1208178976 (LWP 21897))
----------- .xsession-errors --------------------- Major opcode: 155 Minor opcode: 6 Resource id: 0x65 X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x140500c X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 155 Minor opcode: 6 Resource id: 0x140500c X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 155 Minor opcode: 6 Resource id: 0x65 --------------------------------------------------
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 in gthumb 2.10.7. *** This bug has been marked as a duplicate of 485721 ***