GNOME Bugzilla – Bug 361345
crash in System Monitor: I was changing the prior...
Last modified: 2011-11-11 10:03:55 UTC
Version: 2.16.1 What were you doing when the application crashed? I was changing the priority of a process. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 31944704 vsize: 0 resident: 31944704 share: 0 rss: 15544320 rss_rlim: 0 CPU usage: start_time: 1160543658 rtime: 0 utime: 128 stime: 0 cutime:100 cstime: 0 timeout: 28 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1211296080 (LWP 18388)] 0xb7e3bbfe in __waitpid_nocancel () from /lib/libpthread.so.0
+ Trace 75743
Thread 1 (Thread -1211296080 (LWP 18388))
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. (Note that the stack trace looks a lot like the one in bug 350166, which was closed as incomplete for lack of information; I'll leave this one open so that hopefully we get the extra info)
*** Bug 368951 has been marked as a duplicate of this bug. ***
*** Bug 369279 has been marked as a duplicate of this bug. ***
*** Bug 386661 has been marked as a duplicate of this bug. ***
I was not doing much when the system monitor crashed. I had Firefox running, and System monitor was running because I was monitoring progress of my weekly backups, using Simple Backup. I also had a Nautilus window open as root. Nothing else was running. This crash happened twice in quick succession. More than that i cannot say.
*** Bug 388094 has been marked as a duplicate of this bug. ***
*** Bug 389502 has been marked as a duplicate of this bug. ***
*** Bug 391733 has been marked as a duplicate of this bug. ***
Reopening: duplicate.
*** Bug 401960 has been marked as a duplicate of this bug. ***
*** Bug 396259 has been marked as a duplicate of this bug. ***
*** Bug 406253 has been marked as a duplicate of this bug. ***
*** Bug 409348 has been marked as a duplicate of this bug. ***
*** Bug 409529 has been marked as a duplicate of this bug. ***
*** Bug 413369 has been marked as a duplicate of this bug. ***
*** Bug 414376 has been marked as a duplicate of this bug. ***
*** Bug 415386 has been marked as a duplicate of this bug. ***
*** Bug 415745 has been marked as a duplicate of this bug. ***
*** Bug 419099 has been marked as a duplicate of this bug. ***
*** Bug 419106 has been marked as a duplicate of this bug. ***
*** Bug 419109 has been marked as a duplicate of this bug. ***
*** Bug 420639 has been marked as a duplicate of this bug. ***
*** Bug 419759 has been marked as a duplicate of this bug. ***
*** Bug 420453 has been marked as a duplicate of this bug. ***
I was using Firefox and google earth when the crash came!, there was also a lot of hard disk activity at the sametime, that was the reason I wanted to look on the monitor I click on "view active process", and after a few seconds later.., Crash!.
*** Bug 425942 has been marked as a duplicate of this bug. ***
*** Bug 435238 has been marked as a duplicate of this bug. ***
*** Bug 443706 has been marked as a duplicate of this bug. ***
*** Bug 422068 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this bug. This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a description of how to reproduce this bug. You'll also need to add a stack trace; please see http://live.gnome.org/GettingTraces for more information about how to do so. Thanks in advance!
*** Bug 474998 has been marked as a duplicate of this bug. ***