Bug 389454 – crash in System Monitor: I had try close the appl...

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 389454 - crash in System Monitor: I had try close the appl...


Summary:	crash in System Monitor: I had try close the appl...


Status:	RESOLVED DUPLICATE of bug 389327

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:	2006-12-25 13:43 UTC by alex-wolf
Modified:	2011-11-11 10:03 UTC

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

Description alex-wolf 2006-12-25 13:43:56 UTC

Version: 2.17.4.2

What were you doing when the application crashed?
I had try close the application by press button close


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.18-1.2849.fc6xen #1 SMP Fri Nov 10 13:56:52 EST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Enabled

Memory status: size: 51118080 vsize: 0 resident: 51118080 share: 0 rss: 15183872 rss_rlim: 0
CPU usage: start_time: 1167053926 rtime: 0 utime: 58 stime: 0 cutime:36 cstime: 0 timeout: 22 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/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208301856 (LWP 27855)]
(no debugging symbols found)
0x00240402 in __kernel_vsyscall ()

+ Trace 96869

Thread 1 (Thread -1208301856 (LWP 27855))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/i686/nosegneg/libpthread.so.0
#2 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 strlen
from /lib/i686/nosegneg/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/i686/nosegneg/libc.so.6
#19 __libc_start_main
from /lib/i686/nosegneg/libc.so.6
#20 __cxa_pure_virtual
#0 __kernel_vsyscall



----------- .xsession-errors (6 sec old) ---------------------
(process:27782): GLib-GObject-CRITICAL **: gtype.c:2242: initialization assertion failed, use IA__g_type_init() prior to this function
(process:27782): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
GTK Accessibility Module initialized
GTK Accessibility Module initialized
GTK Accessibility Module initialized
GTK Accessibility Module initialized
GTK Accessibility Module initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
--------------------------------------------------

Comment 1 Claudio Saavedra 2006-12-25 22:36:46 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 389327 ***