GNOME Bugzilla – Bug 312618
gnome-system-monitor crash
Last modified: 2011-11-11 10:03:55 UTC
Distribution: Debian 3.1 Package: system-monitor Severity: normal Version: GNOME2.8.3 2.8.1 Gnome-Distributor: Debian Synopsis: gnome-system-monitor crash Bugzilla-Product: system-monitor Bugzilla-Component: general Bugzilla-Version: 2.8.1 BugBuddy-GnomeVersion: 2.0 (2.8.1) Description: Description of the crash: Gnome informs me that the application gnome-system-monitor has quit unexpectedly after double-clicking on the monitor. The application does not seems to have crashed and restarting the application gives me another error whereas closing the error solves the 'problem' Steps to reproduce the crash: 1. Double-click on system monitor in Gnome panel 2. 3. Expected Results: Don't know what's supposed to happen when double-clicking on panel How often does this happen? Every time you double-click Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnome-system-monitor' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 3523)] [New Thread 32769 (LWP 3524)] [New Thread 16386 (LWP 3525)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0x40254c0b in waitpid () from /lib/libpthread.so.0
+ Trace 62224
Thread 1 (Thread 16384 (LWP 3523))
------- Bug moved to this database by unknown@gnome.bugs 2005-08-04 22:17 UTC ------- Unknown version 2.8.1 in product system-monitor. Setting version to "2.8.x". The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@gnome.bugs. Previous reporter was edwin@vandrham.kabel.utwente.nl.
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 160560 ***