GNOME Bugzilla – Bug 443032
crash in gThumb Image Viewer: veiwing one jpg image.
Last modified: 2007-06-04 12:21:42 UTC
What were you doing when the application crashed? veiwing one jpg image. Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.20-1.2948.fc6 #1 SMP Fri Apr 27 18:53:15 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 221802496 vsize: 0 resident: 221802496 share: 0 rss: 52797440 rss_rlim: 0 CPU usage: start_time: 1180728321 rtime: 0 utime: 338 stime: 0 cutime:313 cstime: 0 timeout: 25 it_real_value: 0 frequency: 0 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 -1208531248 (LWP 8250)] [New Thread -1330656368 (LWP 8261)] [New Thread -1320166512 (LWP 8260)] [New Thread -1309676656 (LWP 8259)] [New Thread -1299186800 (LWP 8258)] [New Thread -1266525296 (LWP 8254)] [New Thread -1225688176 (LWP 8253)] (no debugging symbols found) 0x006ff402 in __kernel_vsyscall ()
+ Trace 137349
Thread 1 (Thread -1208531248 (LWP 8250))
----------- .xsession-errors --------------------- DCOP: unregister 'anonymous-8866' kdeinit: PID 8866 terminated. DCOP: unregister 'kjobviewer' X Error: BadWindow (invalid Window parameter) 3 Major opcode: 7 Minor opcode: 0 Resource id: 0x4800007 DCOP: unregister 'kpdf-8752' DCOPServer : slotTerminate() -> sending terminateKDE signal. kdeinit: terminate KDE. DCOP: unregister 'klauncher' DCOP: unregister 'kded' DCOPServer : slotSuicide() -> exit. ** (bug-buddy:8895): WARNING **: Couldn't load icon for Open Folder --------------------------------------------------
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 356623 ***