GNOME Bugzilla – Bug 361008
crash in System Monitor: Trying to access the pro...
Last modified: 2011-11-11 10:03:55 UTC
Version: 2.16.1 What were you doing when the application crashed? Trying to access the properties. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 36663296 vsize: 0 resident: 36663296 share: 0 rss: 14946304 rss_rlim: 0 CPU usage: start_time: 1160428130 rtime: 0 utime: 10223 stime: 0 cutime:6097 cstime: 0 timeout: 4126 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 -1225876992 (LWP 6317)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 75508
Thread 1 (Thread -1225876992 (LWP 6317))
*** Bug 365138 has been marked as a duplicate of this bug. ***
*** Bug 375014 has been marked as a duplicate of this bug. ***
*** Bug 384316 has been marked as a duplicate of this bug. ***
*** Bug 388511 has been marked as a duplicate of this bug. ***
Dear all, if you have any valuable information about the unexpected crash of system-monitor you experienced or if you are able to give detailed instructions about how to reproduce the bug, please reopen your bug. Thanks.
*** Bug 402633 has been marked as a duplicate of this bug. ***
*** Bug 405507 has been marked as a duplicate of this bug. ***
*** Bug 410631 has been marked as a duplicate of this bug. ***
reopening as per duplicates (otherwise, email addresses are not added to the CC list when the bug is closed).
*** Bug 414119 has been marked as a duplicate of this bug. ***
*** Bug 393880 has been marked as a duplicate of this bug. ***
Dear reporters, could you please help fixing this by installing some debugging packages [1], start Nautilus as normal, and try to reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] Please install the following debug packages: Ubuntu 6.10: gnome-system-monitor-dbgsym, libgtop2-7-dbgsym, libglib2.0-0-dbg and libgtk2.0-0-dbg. OpenSuSE 10.2: gnome-system-monitor-debuginfo, libgtop-debuginfo, glib2-debuginfo, and gtk2-debuginfo. Fedora Core 6: gnome-system-monitor-debuginfo, libgtop2-debuginfo, glib2-debuginfo, and gtk2-debuginfo. More details can be found here: http://live.gnome.org/GettingTraces
*** Bug 422430 has been marked as a duplicate of this bug. ***
*** Bug 429689 has been marked as a duplicate of this bug. ***
*** Bug 430143 has been marked as a duplicate of this bug. ***
*** Bug 430630 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!