Bug 396259 – crash in System Monitor: switching from process t...

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 396259 - crash in System Monitor: switching from process t...


Summary:	crash in System Monitor: switching from process t...


Status:	RESOLVED DUPLICATE of bug 361345

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:

Duplicates:	402735 (view as bug list)
Depends on:
Blocks:

Reported:	2007-01-13 22:47 UTC by haltyb
Modified:	2011-11-11 10:03 UTC

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

Description haltyb 2007-01-13 22:47:50 UTC

Version: 2.16.1

What were you doing when the application crashed?
switching from process tab to resources tab


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

Memory status: size: 51802112 vsize: 0 resident: 51802112 share: 0 rss: 21729280 rss_rlim: 0
CPU usage: start_time: 1168728193 rtime: 0 utime: 1484 stime: 0 cutime:1255 cstime: 0 timeout: 229 it_real_value: 0 frequency: 28

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 -1225275728 (LWP 6936)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 101899

Thread 1 (Thread -1225275728 (LWP 6936))

#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 gtk_tree_store_new
from /usr/lib/libgtk-x11-2.0.so.0
#11 gtk_tree_store_new
from /usr/lib/libgtk-x11-2.0.so.0
#12 gtk_tree_store_set_valist
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_tree_store_set
from /usr/lib/libgtk-x11-2.0.so.0
#14 ??
#15 ??
#16 ??
#17 ??
#18 _IO_stdin_used
#19 ??
#20 ??
#21 ??
#22 ??
#23 ??
#24 ??
#25 ??
#26 ??
#27 ??
#28 ??
#29 ??
#30 ??
#31 ??
#32 ??
#0 __kernel_vsyscall

Comment 1 André Klapper 2007-01-19 00:03:58 UTC

Can you please install libgtk2.0-0-dbg and try to reproduce the crash,
copy the stacktrace ("Details" section in bug-buddy), and paste it here?
Thanks in advance!

Comment 2 Susana 2007-01-31 14:55:44 UTC

*** Bug 402735 has been marked as a duplicate of this bug. ***

Comment 3 palfrey 2007-02-07 23:53:37 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 361345 ***