GNOME Bugzilla – Bug 493471
crash in gThumb Image Viewer: full screen manual view....
Last modified: 2007-11-05 01:13:04 UTC
What were you doing when the application crashed? full screen manual view. hit delete key to remove blurry photo. no response so hit 'n' for next. bug tool appeared. 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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 335044608 vsize: 335044608 resident: 255410176 share: 21512192 rss: 255410176 rss_rlim: 4294967295 CPU usage: start_time: 1194202276 rtime: 8319 utime: 7668 stime: 651 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 -1208264992 (LWP 2926)] [New Thread -1309025392 (LWP 2974)] [New Thread -1240593520 (LWP 2970)] [New Thread -1240065136 (LWP 2969)] [New Thread -1239536752 (LWP 2968)] [New Thread -1239008368 (LWP 2967)] [New Thread -1237955696 (LWP 2956)] [New Thread -1237427312 (LWP 2955)] [New Thread -1236898928 (LWP 2954)] [New Thread -1236370544 (LWP 2951)] [New Thread -1235842160 (LWP 2950)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 175189
Thread 1 (Thread -1208264992 (LWP 2926))
----------- .xsession-errors (412 sec old) --------------------- localuser:gary being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2652 winscard_clnt.c:3349:SCardCheckDaemonAvailability() PCSC Not Running Initializing nautilus-image-converter extension Initializing nautilus-search-tool extension --------------------------------------------------
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. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 485721 ***