Bug 355403 – crash in System Monitor: clicked on the applet's ...

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 355403 - crash in System Monitor: clicked on the applet's ...


Summary:	crash in System Monitor: clicked on the applet's ...


Status:	RESOLVED DUPLICATE of bug 354823

Product:	system-monitor
Classification:	Core
Component:	general
Version:	2.14.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-09-11 08:42 UTC by stefan.kli
Modified:	2011-11-11 10:03 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description stefan.kli 2006-09-11 08:42:13 UTC

Version: 2.14.4

What were you doing when the application crashed?
clicked on the applet's symbol.


Distribution: Gentoo Base System version 1.12.4
Gnome Release: 2.16.0 2006-09-10 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 30728192 vsize: 0 resident: 30728192 share: 0 rss: 12873728 rss_rlim: 0
CPU usage: start_time: 1157963909 rtime: 0 utime: 84 stime: 0 cutime:76 cstime: 0 timeout: 8 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)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1219230032 (LWP 23270)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 72095

Thread 1 (Thread -1219230032 (LWP 23270))

#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 dbus_connection_send_with_reply
from /usr/lib/libdbus-1.so.2
#5 dbus_connection_send_with_reply_and_block
from /usr/lib/libdbus-1.so.2
#6 gnome_vfs_volume_monitor_client_get_type
from /usr/lib/libgnomevfs-2.so.0
#7 gnome_vfs_volume_monitor_client_get_type
from /usr/lib/libgnomevfs-2.so.0
#8 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#9 g_object_new
from /usr/lib/libgobject-2.0.so.0
#10 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#11 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#12 g_object_new
from /usr/lib/libgobject-2.0.so.0
#13 gnome_vfs_volume_monitor_unref
from /usr/lib/libgnomevfs-2.so.0
#14 gnome_vfs_get_volume_monitor
from /usr/lib/libgnomevfs-2.so.0
#15 ??
#16 ??
#17 ??
#18 ??
#19 ??
#20 ??
#0 __kernel_vsyscall

Comment 1 Fabio Bonelli 2006-09-12 08:07:03 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report?


*** This bug has been marked as a duplicate of 354823 ***