GNOME Bugzilla – Bug 491182
crash in gThumb Image Viewer:
Last modified: 2007-10-28 22:57:04 UTC
What were you doing when the application crashed? 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.20-2936.fc7xen #1 SMP Fri Sep 21 12:07:35 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 313462784 vsize: 313462784 resident: 214716416 share: 34934784 rss: 214716416 rss_rlim: 4294967295 CPU usage: start_time: 1193605992 rtime: 1660 utime: 1537 stime: 123 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/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208387872 (LWP 5336)] [New Thread -1281889392 (LWP 5364)] [New Thread -1306031216 (LWP 5360)] [New Thread -1305502832 (LWP 5359)] [New Thread -1304974448 (LWP 5358)] [New Thread -1304446064 (LWP 5357)] [New Thread -1377354864 (LWP 5354)] [New Thread -1376826480 (LWP 5353)] [New Thread -1376298096 (LWP 5352)] [New Thread -1270871152 (LWP 5340)] [New Thread -1270342768 (LWP 5339)] (no debugging symbols found) 0x007f1402 in __kernel_vsyscall ()
+ Trace 173516
Thread 1 (Thread -1208387872 (LWP 5336))
----------- .xsession-errors (33 sec old) --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 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 in 2.10.7, which is available in the F7 testing repo. *** This bug has been marked as a duplicate of 485721 ***