GNOME Bugzilla – Bug 416395
crash in System Monitor: Trying to run normal upd...
Last modified: 2011-11-11 10:03:55 UTC
Version: 2.16.1 What were you doing when the application crashed? Trying to run normal update. App. froze, so I had to close it through System monitor. Happened few times already. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 35012608 vsize: 0 resident: 35012608 share: 0 rss: 14446592 rss_rlim: 0 CPU usage: start_time: 1173436951 rtime: 0 utime: 462 stime: 0 cutime:368 cstime: 0 timeout: 94 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 -1225881936 (LWP 6153)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 117147
Thread 1 (Thread -1225881936 (LWP 6153))
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 354559 ***