GNOME Bugzilla – Bug 407664
crash in System Monitor: Ending the process on an...
Last modified: 2011-11-11 10:03:55 UTC
Version: 2.16.1 What were you doing when the application crashed? Ending the process on an unresponsive instance of Serpentine. The program failed to burn the disc, so I ejected it and tried to exit. When it wouldn't exit, I ended the process and System Monitor crashed. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 33071104 vsize: 0 resident: 33071104 share: 0 rss: 14454784 rss_rlim: 0 CPU usage: start_time: 1171407812 rtime: 0 utime: 774 stime: 0 cutime:578 cstime: 0 timeout: 196 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 -1225718096 (LWP 5601)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 110526
Thread 1 (Thread -1225718096 (LWP 5601))
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 354559 ***