GNOME Bugzilla – Bug 156831
system monitor crash
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Debian testing/unstable Package: system-monitor Severity: normal Version: GNOME2.8.1 2.7.0 Gnome-Distributor: Ubuntu Synopsis: system monitor crash Bugzilla-Product: system-monitor Bugzilla-Component: general Bugzilla-Version: 2.7.0 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnome-system-monitor' (no debugging symbols found)...Using host libthread_db library "/lib/tls/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 1087483648 (LWP 4662)] (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)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x4023ff2e in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 51453
Thread 1 (Thread 1087483648 (LWP 4662))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-10-29 12:43 ------- Unknown version 2.7.0 in product system-monitor. Setting version to "0.4". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "system-monitor". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was a@hotmail.com. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Please make sure that the package was compiled with debugging symbols and see http://bugzilla.gnome.org/getting-traces.cgi for more information about useful stack traces.
can you reproduce it with GNOME Accessibility disabled ?
confirmed, happens only with gail (gail 1.8.0)
I'll try to provide a complete backtrace later. BTW one way to get the crash is to select a line and then to swith the "View" between "All Processes" and "My Processes" several times
Apart from a full backtrace, I need a a description of how to reproduce the problem. Also, the location of the source for gnome-system-monitor. When you say it happens only with gail 1.8.0 are you sayingh that it does not happen with rpevious versions of gail?
How to reproduce is described in the comment #4: - select a line - switch the "View" to "All Processes" - switch the "View" ro "MY Processes" - ... usually it crashes after 2-3 switch between the view Sources, since that's a GNOME module on the GNOME CVS or http://ftp.gnome.org/pub/GNOME/sources/gnome-system-monitor/2.8/ No, it happens only when I use gail, and my version is 1.8.0. I've not tested with an another version.
I have attempted to reproduce the crash with te instructions abobe bit have not been able to.
*** Bug 146836 has been marked as a duplicate of this bug. ***
See bug #132551. Is it possible that this bug is a duplciate of that one?
seems to but, the patch in #132551 fixes this bug
*** This bug has been marked as a duplicate of 132551 ***