Bug 395391 – crash in System Monitor:

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 395391 - crash in System Monitor:


Summary:	crash in System Monitor:


Status:	RESOLVED DUPLICATE of bug 354559

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-01-11 13:47 UTC by makk753
Modified:	2011-11-11 10:03 UTC

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

Description makk753 2007-01-11 13:47:44 UTC

Version: 2.16.1

What were you doing when the application crashed?



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

Memory status: size: 57397248 vsize: 0 resident: 57397248 share: 0 rss: 15785984 rss_rlim: 0
CPU usage: start_time: 1168523189 rtime: 0 utime: 663 stime: 0 cutime:524 cstime: 0 timeout: 139 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 -1225885184 (LWP 25118)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 101250

Thread 1 (Thread -1225885184 (LWP 25118))

#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 gtk_tree_model_get_valist
from /usr/lib/libgtk-x11-2.0.so.0
#5 gtk_tree_model_get
from /usr/lib/libgtk-x11-2.0.so.0
#6 sexy_tree_view_new
from /usr/lib/libsexy.so.2
#7 g_timeout_dispatch
at gmain.c line 3422
#8 IA__g_main_context_dispatch
at gmain.c line 2045
#9 g_main_context_iterate
at gmain.c line 2677
#10 IA__g_main_loop_run
at gmain.c line 2881
#11 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#12 ??
#13 ??
#14 _IO_stdin_used
#15 ??
#16 ??
#17 ??
#0 __kernel_vsyscall

Comment 1 palfrey 2007-01-11 18:46:08 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

Comment 2 André Klapper 2007-01-18 23:47:02 UTC

benoit, please do not close bug reports without even telling a reason after less than 2 days. this is totally inappropriate. please wait for at least 30 days, and please do use a stock answer whn closing. thanks.

Comment 3 André Klapper 2007-01-18 23:47:50 UTC

NEEDINFO as per comment #1

Comment 4 André Klapper 2007-06-20 13:13:21 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 354559 ***