GNOME Bugzilla – Bug 449370
crash in gThumb Image Viewer: Crach raise when the USB...
Last modified: 2007-06-20 11:48:15 UTC
What were you doing when the application crashed? Crach raise when the USB flash disc was pluged. Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.18-1.2869.fc6 #1 SMP Wed Dec 20 14:51:19 EST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 939483136 vsize: 0 resident: 939483136 share: 0 rss: 30879744 rss_rlim: 0 CPU usage: start_time: 1182312079 rtime: 0 utime: 1459 stime: 0 cutime:1354 cstime: 0 timeout: 105 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 -1208891696 (LWP 7771)] [New Thread 2048596880 (LWP 9169)] [New Thread 2059086736 (LWP 9168)] [New Thread 2069576592 (LWP 9167)] [New Thread 2080066448 (LWP 9166)] [New Thread -1927128176 (LWP 9155)] [New Thread -1895658608 (LWP 9153)] [New Thread -2120492144 (LWP 8995)] [New Thread -2110002288 (LWP 8994)] [New Thread -2099512432 (LWP 8993)] [New Thread -2089022576 (LWP 8992)] [New Thread -1431913584 (LWP 8981)] [New Thread -1916638320 (LWP 8980)] [New Thread -1885168752 (LWP 8813)] [New Thread -1874678896 (LWP 8812)] [New Thread -1864189040 (LWP 8811)] [New Thread -1853699184 (LWP 8810)] [New Thread -1454711920 (LWP 8799)] [New Thread -1465201776 (LWP 8798)] [New Thread -1811739760 (LWP 7953)] [New Thread -1801249904 (LWP 7952)] [New Thread -1790760048 (LWP 7951)] [New Thread -1780270192 (LWP 7950)] [New Thread -1706841200 (LWP 7939)] [New Thread -1717331056 (LWP 7938)] [New Thread -1643902064 (LWP 7827)] [New Thread -1633412208 (LWP 7826)] [New Thread -1622922352 (LWP 7825)] [New Thread -1612432496 (LWP 7824)] [New Thread -1381282928 (LWP 7813)] [New Thread -1391772784 (LWP 7812)] (no debugging symbols found) 0x00ac5402 in __kernel_vsyscall ()
+ Trace 142338
Thread 1 (Thread -1208891696 (LWP 7771))
----------- .xsession-errors (76338 sec old) --------------------- fixme:imm:ImmReleaseContext (0x30196, 0x7d0fe2c8): stub fixme:imm:ImmGetContext (0x30196): stub fixme:imm:ImmSetCompositionWindow STUB fixme:imm:ImmReleaseContext (0x30196, 0x7d0fe2c8): stub fixme:imm:ImmGetContext (0x30196): stub fixme:imm:ImmSetCompositionWindow STUB fixme:imm:ImmReleaseContext (0x30196, 0x7d0fe2c8): stub fixme:imm:ImmGetContext (0x30196): stub fixme:imm:ImmSetCompositionWindow STUB fixme:imm:ImmReleaseContext (0x30196, 0x7d0fe2c8): stub fixme:imm:ImmGetContext (0x30196): stub fixme:imm:ImmSetCompositionWindow STUB fixme:imm:ImmReleaseContext (0x30196, 0x7d0fe2c8): stub ...Too much output, ignoring rest... --------------------------------------------------
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 ***