Bug 377894 – crash in System Monitor: I was doing absolutely n...

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 377894 - crash in System Monitor: I was doing absolutely n...


Summary:	crash in System Monitor: I was doing absolutely n...


Status:	RESOLVED DUPLICATE of bug 352444

Product:	system-monitor
Classification:	Core
Component:	general
Version:	2.16.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-11-21 20:01 UTC by E.M.vanDoorn
Modified:	2011-11-11 10:03 UTC

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

Description E.M.vanDoorn 2006-11-21 20:01:02 UTC

Version: 2.16.1

What were you doing when the application crashed?
I was doing absolutely nothing! I was at work and when I got home and turned on the monitor I was confronted with "Bug Buddy".

The evening before I was using: emacs, java/javac, firefox, reading mail and listening to music with the standard Ubuntu 
"Rhytmbox Music Player". The computer has been active for two or three days. 

The Apache webserver is since two or three  days reachable from the internet. 
Before the router blocked the connection with Apache.

I hope you have sufficient information.

With regards,

E.M. van Doorn



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 151863296 vsize: 0 resident: 151863296 share: 0 rss: 83275776 rss_rlim: 0
CPU usage: start_time: 1163968606 rtime: 0 utime: 1530597 stime: 0 cutime:1263676 cstime: 0 timeout: 266921 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 -1225804112 (LWP 12059)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 88333

Thread 1 (Thread -1225804112 (LWP 12059))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 ORBit_RootObject_duplicate_T
from /usr/lib/libORBit-2.so.0
#11 CORBA_free
from /usr/lib/libORBit-2.so.0
#12 CORBA_free
from /usr/lib/libORBit-2.so.0
#13 ORBit_free_T
from /usr/lib/libORBit-2.so.0
#14 ORBit_free
from /usr/lib/libORBit-2.so.0
#15 CORBA_free
from /usr/lib/libORBit-2.so.0
#16 gnome_accessibility_module_shutdown
from /usr/lib/gtk-2.0/modules/libatk-bridge.so
#17 gnome_accessibility_module_shutdown
from /usr/lib/gtk-2.0/modules/libatk-bridge.so
#18 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#21 atk_object_notify_state_change
from /usr/lib/libatk-1.0.so.0
#22 gail_window_new
from /usr/lib/gtk-2.0/modules/libgail.so
#23 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#24 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#26 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#27 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#28 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#29 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#30 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#31 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#32 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#33 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#34 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#35 ??
#36 ??
#37 _IO_stdin_used
#38 ??
#39 ??
#40 ??
#0 __kernel_vsyscall

Comment 1 Susana 2006-11-21 23:33:13 UTC

Thanks for taking the time to report this bug.
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 in order to help the developers?


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

Comment 2 E.M.vanDoorn 2006-11-22 08:54:47 UTC

"Could you please answer
the questions in the other report in order to help the developers?"

To which "other report" do you refer??

E.M. van Doorn

Comment 3 Li Yuan 2006-12-06 07:35:55 UTC

I find you have run gnome-system-monitor. How do use it? Just on the panel? Or open the application's window?
If you can install atk-dev and at-spi-dev and gail-dev package to give us a trace with symbol, I would be very appreciate.

Comment 4 E.M.vanDoorn 2006-12-11 11:05:37 UTC

Sorry for waiting.

I rarely use the gnome-system-monitor. I can't remember if I was using
the gnome-system-monitor at the time of the crash.

I will install atk-dev and at-spi-dev and gail-dev.

The problem did not occur for a second time.

The Intel-PC has the following characterics:
-1 Ghz
-256 Mb internal memory
-a few (6?) Gb partion for Linux.