GNOME Bugzilla – Bug 455412
crash in gThumb Image Viewer: looking at my pictures I...
Last modified: 2007-07-10 11:25:18 UTC
What were you doing when the application crashed? looking at my pictures I had just uploaded. 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.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: LargePrint Icon Theme: Clearlooks Memory status: size: 156749824 vsize: 156749824 resident: 54652928 share: 36188160 rss: 54652928 rss_rlim: 4294967295 CPU usage: start_time: 1184040592 rtime: 3961 utime: 3671 stime: 290 cutime:1 cstime: 8 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 -1208133376 (LWP 3121)] [New Thread -1284637808 (LWP 3243)] [New Thread -1284109424 (LWP 3242)] [New Thread -1283581040 (LWP 3241)] [New Thread -1272562800 (LWP 3231)] [New Thread -1272034416 (LWP 3230)] (no debugging symbols found) 0x008e0402 in __kernel_vsyscall ()
+ Trace 146906
Thread 1 (Thread -1208133376 (LWP 3121))
----------- .xsession-errors (138 sec old) --------------------- Window manager warning: Invalid WM_TRANSIENT_FOR window 0x45 specified for 0x3200012 (digiKam). Found dcraw version: 8.60 Exif Orientation: 1 Exif Orientation: 1 Exif Orientation: 1 Exif Orientation: 1 Exif Orientation: 1 Exif Orientation: 1 Exif Orientation: 1 Exif Orientation: 1 Exif Orientation: 1 Exif Orientation: 1 Exif Orientation: 1 Exif Orientation: 1 ICE default IO error handler doing an exit(), pid = 3015, errno = 0 --------------------------------------------------
Probably a duplicate of bug 453986. A fix has been committed to svn. It should appear in gThumb 2.10.6, when it is released. Please re-open this bug if it occurs again in 2.10.6 or later. - Mike *** This bug has been marked as a duplicate of 453986 ***