GNOME Bugzilla – Bug 427129
crash in System Log: nothing. Just trying to ...
Last modified: 2007-04-07 14:06:13 UTC
Version: 2.16.1 What were you doing when the application crashed? nothing. Just trying to access the log Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 51372032 vsize: 0 resident: 51372032 share: 0 rss: 12070912 rss_rlim: 0 CPU usage: start_time: 1175910267 rtime: 0 utime: 35 stime: 0 cutime:33 cstime: 0 timeout: 2 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-system-log' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1209067328 (LWP 5355)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 125656
Thread 1 (Thread -1209067328 (LWP 5355))
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
No problem, here is the stack trace with dbsyms Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 51367936 vsize: 0 resident: 51367936 share: 0 rss: 11907072 rss_rlim: 0 CPU usage: start_time: 1175951253 rtime: 0 utime: 32 stime: 0 cutime:30 cstime: 0 timeout: 2 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-system-log' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208452928 (LWP 9308)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 125786
Thread 1 (Thread -1208452928 (LWP 9308))
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 364106 ***