GNOME Bugzilla – Bug 397402
crash in System Monitor: Killing a non-responsive...
Last modified: 2011-11-11 10:03:55 UTC
Version: 2.16.1 What were you doing when the application crashed? Killing a non-responsive program. (TeamSpeak2 client) Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 32972800 vsize: 0 resident: 32972800 share: 0 rss: 14188544 rss_rlim: 0 CPU usage: start_time: 1168981711 rtime: 0 utime: 213 stime: 0 cutime:170 cstime: 0 timeout: 43 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-system-monitor' (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 -1225393664 (LWP 6351)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 102797
Thread 1 (Thread -1225393664 (LWP 6351))
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 396168 ***