GNOME Bugzilla – Bug 501767
crash in gThumb Image Viewer: a tentar abrir a imagem
Last modified: 2007-12-05 14:45:11 UTC
What were you doing when the application crashed? a tentar abrir a imagem Distribution: PCLinuxOS release 2007 (PCLinuxOS) for i586 Gnome Release: 2.18.0 2007-09-08 (%vendor) BugBuddy Version: 2.18.1 System: Linux 2.6.18.8.tex5 #1 SMP Thu May 10 11:36:58 WST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 108425216 vsize: 108425216 resident: 52731904 share: 20283392 rss: 52731904 rss_rlim: 4294967295 CPU usage: start_time: 1196865595 rtime: 168 utime: 157 stime: 11 cutime:95 cstime: 14 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/i686/libthread_db.so.1". (no debugging symbols found) `shared object read from target memory' has disappeared; keeping its symbols. (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1228355904 (LWP 6854)] [New Thread -1252168800 (LWP 6912)] [New Thread -1251640416 (LWP 6911)] [New Thread -1251112032 (LWP 6910)] [New Thread -1250583648 (LWP 6909)] [New Thread -1297294432 (LWP 6868)] [New Thread -1296766048 (LWP 6867)] [New Thread -1296237664 (LWP 6866)] [New Thread -1245287520 (LWP 6859)] [New Thread -1244759136 (LWP 6858)] (no debugging symbols found) 0xb7f18410 in __kernel_vsyscall ()
+ Trace 180822
Thread 10 (Thread -1244759136 (LWP 6858)): #-1 0xb7f18410 in __kernel_vsyscall () No symbol table info available. Thread 9 (Thread -1245287520 (LWP 6859)): #-1 0xb7f18410 in __kernel_vsyscall () No symbol table info available. Thread 8 (Thread -1296237664 (LWP 6866)): #-1 0xb7f18410 in __kernel_vsyscall () No symbol table info available. Thread 7 (Thread -1296766048 (LWP 6867)): #-1 0xb7f18410 in __kernel_vsyscall () No symbol table info available. Thread 6 (Thread -1297294432 (LWP 6868)): #-1 0xb7f18410 in __kernel_vsyscall () No symbol table info available. Thread 5 (Thread -1250583648 (LWP 6909)): #-1 0xb7f18410 in __kernel_vsyscall () No symbol table info available. Thread 4 (Thread -1251112032 (LWP 6910)): #-1 0xb7f18410 in __kernel_vsyscall () No symbol table info available. Thread 3 (Thread -1251640416 (LWP 6911)): #-1 0xb7f18410 in __kernel_vsyscall () No symbol table info available. Thread 2 (Thread -1252168800 (LWP 6912)): #-1 0xb7f18410 in __kernel_vsyscall () No symbol table info available. Thread 1 (Thread -1228355904 (LWP 6854)): #-1 0xb7f18410 in __kernel_vsyscall () No symbol table info available. ----------- .xsession-errors --------------------- Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded --------------------------------------------------
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 ***