GNOME Bugzilla – Bug 429633
crash in System Log: Ouverture de Visionneur ...
Last modified: 2007-04-19 15:13:07 UTC
Version: 2.16.1 What were you doing when the application crashed? Ouverture de Visionneur de journaux système Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 35311616 vsize: 0 resident: 35311616 share: 0 rss: 12509184 rss_rlim: 0 CPU usage: start_time: 1176552256 rtime: 0 utime: 52 stime: 0 cutime:50 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225426752 (LWP 6460)] (no debugging symbols found) 0xb7417bfe in __waitpid_nocancel () from /lib/libpthread.so.0
+ Trace 127681
Thread 1 (Thread -1225426752 (LWP 6460))
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!
More information about the bug : Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 35319808 vsize: 0 resident: 35319808 share: 0 rss: 12521472 rss_rlim: 0 CPU usage: start_time: 1176700333 rtime: 0 utime: 57 stime: 0 cutime:51 cstime: 0 timeout: 6 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-system-log' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1225193280 (LWP 5582)] 0xb7450bfe in __waitpid_nocancel () from /lib/libpthread.so.0
+ Trace 128139
Thread 1 (Thread -1225193280 (LWP 5582))
Thanks for the stack trace. 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 364106 ***