GNOME Bugzilla – Bug 488314
crash in gThumb Image Viewer: gThumb first crashed whi...
Last modified: 2007-11-15 16:40:03 UTC
What were you doing when the application crashed? gThumb first crashed while importing images from a Canon PowerShot S60, possibly because I at some time switched the camera off during this procedure. However when the "Bug reporting tool" popped up, I canceled. When I later started gThumb again, the "Bug reporting tool" immediately popped up again. I don't know why. 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: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 61657088 vsize: 61657088 resident: 24219648 share: 19234816 rss: 24219648 rss_rlim: 4294967295 CPU usage: start_time: 1192806694 rtime: 546 utime: 449 stime: 97 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 -1208785184 (LWP 343)] [New Thread -1227687024 (LWP 365)] [New Thread -1227158640 (LWP 364)] [New Thread -1226630256 (LWP 363)] [New Thread -1226101872 (LWP 362)] [New Thread -1225573488 (LWP 361)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 171446
Thread 6 (Thread -1225573488 (LWP 361))
----------- .xsession-errors (96825 sec old) --------------------- Resource id: 0x141e104 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 158 Minor opcode: 6 Resource id: 0x141e104 X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x141dec4 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 158 Minor opcode: 6 Resource id: 0x141dec4 ...Too much output, ignoring rest... --------------------------------------------------
When gThumb starts, it opens the most recently opened catalog. If I rename this catalog, gThumb doesn't crash. However if I open the renamed catalog, gThumb crashes. So this bug seems to have something to do with the contents of this special catalog: tom@splash:~/images/Grilling.tmp$ ls -la total 69900 drwxr-xr-x 2 tom tom 4096 2007-10-20 00:27 . drwxrwxr-x 7 tom tom 4096 2007-10-20 00:21 .. -rw-rw-r-- 1 tom tom 3634238 2007-10-19 03:25 00001.avi -rw-rw-r-- 1 tom tom 5021622 2007-10-19 02:48 00001.crw -rw-rw-r-- 1 tom tom 714401 2007-10-13 03:33 00001.jpg -rw-rw-r-- 1 tom tom 14265784 2007-10-19 03:53 00002.avi -rw-rw-r-- 1 tom tom 5701598 2007-10-19 02:58 00002.crw -rw-rw-r-- 1 tom tom 5657052 2007-10-19 02:58 00003.crw -rw-rw-r-- 1 tom tom 5694814 2007-10-19 02:58 00004.crw -rw-rw-r-- 1 tom tom 5924700 2007-10-19 03:00 00005.crw -rw-rw-r-- 1 tom tom 5869220 2007-10-19 03:01 00006.crw -rw-rw-r-- 1 tom tom 18894592 2007-10-19 03:52 1.00001.avi tom@splash:~/images/Grilling.tmp$ for file in *; do file "${file}"; done 00001.avi: RIFF (little-endian) data, AVI, 320 x 240, ~15 fps, video: Motion JPEG, audio: uncompressed PCM (mono, 11024 Hz) 00001.crw: data 00001.jpg: JPEG image data, EXIF standard 2.2 00002.avi: RIFF (little-endian) data, AVI, 640 x 480, 10.00 fps, video: Motion JPEG, audio: uncompressed PCM (mono, 11024 Hz) 00002.crw: data 00003.crw: data 00004.crw: data 00005.crw: data 00006.crw: data 1.00001.avi: RIFF (little-endian) data, AVI, 640 x 480, 10.00 fps, video: Motion JPEG, audio: uncompressed PCM (mono, 11024 Hz)
Can you install the gthumb-debuginfo and libopenraw-debuginfo RPMs from the F7 debuginfo repo and reproduce the crash? This will give us a better backtrace. - Mike *** This bug has been marked as a duplicate of 463970 ***