GNOME Bugzilla – Bug 491132
crash in gThumb Image Viewer:
Last modified: 2007-10-28 22:57:37 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: 315174912 vsize: 315174912 resident: 216465408 share: 36110336 rss: 216465408 rss_rlim: 4294967295 CPU usage: start_time: 1193594808 rtime: 1799 utime: 1684 stime: 115 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 -1209194784 (LWP 6183)] [New Thread -1366615152 (LWP 6212)] [New Thread -1299960944 (LWP 6208)] [New Thread -1299432560 (LWP 6207)] [New Thread -1298904176 (LWP 6206)] [New Thread -1298375792 (LWP 6205)] [New Thread -1378161776 (LWP 6201)] [New Thread -1377633392 (LWP 6200)] [New Thread -1377105008 (LWP 6199)] [New Thread -1271678064 (LWP 6187)] [New Thread -1271149680 (LWP 6186)] (no debugging symbols found) 0x00276402 in __kernel_vsyscall ()
+ Trace 173478
Thread 1 (Thread -1209194784 (LWP 6183))
----------- .xsession-errors (121 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 ***