Bug 430630 – crash in System Monitor: Closing down open app wi...

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 430630 - crash in System Monitor: Closing down open app wi...


Summary:	crash in System Monitor: Closing down open app wi...


Status:	RESOLVED DUPLICATE of bug 361008

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:	2007-04-17 12:15 UTC by kpeuramaki
Modified:	2011-11-11 10:03 UTC

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

Description kpeuramaki 2007-04-17 12:15:41 UTC

Version: 2.16.1

What were you doing when the application crashed?
Closing down open app windows, just finished installing some apps.  The System Monitor had been open since the night before, approx 9 hours, and was not shut off.  Ijust closed a terminal window when the bug buddy opened up and said that the monitor had crashed.


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

Memory status: size: 49004544 vsize: 0 resident: 49004544 share: 0 rss: 16195584 rss_rlim: 0
CPU usage: start_time: 1176778655 rtime: 0 utime: 298008 stime: 0 cutime:223649 cstime: 0 timeout: 74359 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 -1224927568 (LWP 6740)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 128491

Thread 1 (Thread -1224927568 (LWP 6740))

#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 strcmp
from /lib/tls/i686/cmov/libc.so.6
#5 _gtk_tree_view_column_autosize
from /usr/lib/libgtk-x11-2.0.so.0
#6 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#7 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#8 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#9 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#12 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_window_propagate_key_event
from /usr/lib/libgtk-x11-2.0.so.0
#14 gtk_window_activate_key
from /usr/lib/libgtk-x11-2.0.so.0
#15 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#16 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#17 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#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 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#22 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#23 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#24 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#25 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#26 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#27 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#28 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#29 ??
#30 ??
#31 _IO_stdin_used
#32 ??
#33 ??
#34 ??
#0 __kernel_vsyscall

Comment 1 Pedro Villavicencio 2007-04-18 02:25:58 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 361008 ***