GNOME Bugzilla – Bug 487387
crash in gThumb Image Viewer: viewing image
Last modified: 2007-10-17 11:43:38 UTC
What were you doing when the application crashed? viewing image 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 20:47:39 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 355467264 vsize: 355467264 resident: 40796160 share: 20447232 rss: 40796160 rss_rlim: 18446744073709551615 CPU usage: start_time: 1192600448 rtime: 97 utime: 83 stime: 14 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496505328 (LWP 25697)] [New Thread 1088985424 (LWP 25719)] [New Thread 1088457040 (LWP 25718)] [New Thread 1087928656 (LWP 25717)] [New Thread 1087400272 (LWP 25716)] [New Thread 1076382032 (LWP 25709)] [New Thread 1075853648 (LWP 25708)] [New Thread 1075325264 (LWP 25707)] [New Thread 1074796880 (LWP 25704)] [New Thread 1074268496 (LWP 25699)] (no debugging symbols found) 0x000000309ba0d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 170753
Thread 1 (Thread 46912496505328 (LWP 25697))
----------- .xsession-errors --------------------- Major opcode: 159 Minor opcode: 6 Resource id: 0xc0 X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x141e32f X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 159 Minor opcode: 6 Resource id: 0x141e32f X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 159 Minor opcode: 6 Resource id: 0xc0 --------------------------------------------------
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 ***