GNOME Bugzilla – Bug 493144
crash in gThumb Image Viewer: watch fotoś
Last modified: 2007-11-03 20:31:06 UTC
What were you doing when the application crashed? watch fotoś 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.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 186531840 vsize: 186531840 resident: 125329408 share: 22466560 rss: 125329408 rss_rlim: 4294967295 CPU usage: start_time: 1194115845 rtime: 4748 utime: 4298 stime: 450 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 -1208142112 (LWP 4637)] [New Thread -1227936880 (LWP 5154)] [New Thread -1268274288 (LWP 5146)] [New Thread -1252684912 (LWP 5145)] [New Thread -1252156528 (LWP 5144)] [New Thread -1251206256 (LWP 5143)] [New Thread -1267745904 (LWP 4829)] [New Thread -1267217520 (LWP 4828)] [New Thread -1266689136 (LWP 4827)] [New Thread -1266160752 (LWP 4823)] [New Thread -1265632368 (LWP 4822)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 174935
Thread 1 (Thread -1208142112 (LWP 4637))
----------- .xsession-errors (297 sec old) --------------------- localuser:mildo being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2721 Initializing nautilus-image-converter extension ** Message: failed to load session from /home/mildo/.nautilus/saved-session-EDLIZT save exif data save exif data save exif data save exif data save exif data --------------------------------------------------
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 ***