Bug 392005 – crash in System Monitor:

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 392005 - crash in System Monitor:


Summary:	crash in System Monitor:


Status:	RESOLVED DUPLICATE of bug 364839

Product:	system-monitor
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	System-monitor maintainers
QA Contact:	System-monitor maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-01-02 18:59 UTC by oleg
Modified:	2011-11-11 10:03 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description oleg 2007-01-02 18:59:41 UTC

Version: 2.17.4.2

What were you doing when the application crashed?



Distribution: Fedora Core release 6 (Rawhide)
Gnome Release: 2.17.2 2006-11-07 (Red Hat, Inc)
BugBuddy Version: 2.17.3

System: Linux 2.6.19-1.2891.fc7 #1 SMP Thu Dec 21 10:59:07 EST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Permissive
Accessibility: Enabled

Memory status: size: 39624704 vsize: 0 resident: 39624704 share: 0 rss: 16670720 rss_rlim: 0
CPU usage: start_time: 1167764118 rtime: 0 utime: 205 stime: 0 cutime:154 cstime: 0 timeout: 51 it_real_value: 0 frequency: 1

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 -1208449312 (LWP 27225)]
(no debugging symbols found)
0x00ff2402 in __kernel_vsyscall ()

+ Trace 98799

Thread 1 (Thread -1208449312 (LWP 27225))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 strlen
from /lib/libc.so.6
#5 giop_send_buffer_append_string
from /usr/lib/libORBit-2.so.0
#6 ORBit_marshal_value
from /usr/lib/libORBit-2.so.0
#7 ORBit_marshal_value
from /usr/lib/libORBit-2.so.0
#8 ORBit_marshal_any
from /usr/lib/libORBit-2.so.0
#9 ORBit_marshal_value
from /usr/lib/libORBit-2.so.0
#10 ORBit_marshal_value
from /usr/lib/libORBit-2.so.0
#11 ORBit_small_allocbuf
from /usr/lib/libORBit-2.so.0
#12 ORBit_small_invoke_stub
from /usr/lib/libORBit-2.so.0
#13 ORBit_small_invoke_stub_n
from /usr/lib/libORBit-2.so.0
#14 ORBit_c_stub_invoke
from /usr/lib/libORBit-2.so.0
#15 Accessibility_EventListener_notifyEvent
from /usr/lib/libspi.so.0
#16 ??
from /usr/lib/gtk-2.0/modules/libatk-bridge.so
#17 ??
from /usr/lib/gtk-2.0/modules/libatk-bridge.so
#18 exit
from /lib/libc.so.6
#19 __libc_start_main
from /lib/libc.so.6
#20 __cxa_pure_virtual
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
** (gnome-system-monitor:27225): WARNING **: Cannot get volume for mount point '/files'
** (gnome-system-monitor:27225): WARNING **: Cannot get volume for mount point '/files'
** (gnome-system-monitor:27225): WARNING **: Cannot get volume for mount point '/files'
** (gnome-system-monitor:27225): WARNING **: Cannot get volume for mount point '/files'
** (gnome-system-monitor:27225): WARNING **: Cannot get volume for mount point '/files'
** (gnome-system-monitor:27225): WARNING **: Cannot get volume for mount point '/files'
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
--------------------------------------------------

Comment 1 Jonathon Jongsma 2007-01-02 20:51:52 UTC

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 364839 ***