Bug 350166 – crash on Monitor di sistema

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 350166 - crash on Monitor di sistema


Summary:	crash on Monitor di sistema


Status:	RESOLVED INCOMPLETE

Product:	system-monitor
Classification:	Core
Component:	general
Version:	2.15.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-08-06 16:14 UTC by franco santini
Modified:	2011-11-11 10:03 UTC

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

Description franco santini 2006-08-06 16:14:28 UTC

What were you doing when the application crashed?
upgrading tolast packages FC6


Distribution: Fedora Core release 5.91 (FC6 Test2)
Gnome Release: 2.15.90 2006-08-03 (Red Hat, Inc)
BugBuddy Version: 2.15.90

Memory status: size: 48246784 vsize: 0 resident: 48246784 share: 0 rss: 14938112 rss_rlim: 0
CPU usage: start_time: 1154880682 rtime: 0 utime: 134 stime: 0 cutime:83 cstime: 0 timeout: 51 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208568112 (LWP 4699)]
(no debugging symbols found)
0x005676de in __waitpid_nocancel () from /lib/libpthread.so.0

+ Trace 70022

Thread 1 (Thread -1208568112 (LWP 4699))

#0 __waitpid_nocancel
from /lib/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 raise
from /lib/libc.so.6
#4 abort
from /lib/libc.so.6
#5 g_logv
from /lib/libglib-2.0.so.0
#6 g_log
from /lib/libglib-2.0.so.0
#7 g_assert_warning
from /lib/libglib-2.0.so.0
#8 gtk_tree_store_new
from /usr/lib/libgtk-x11-2.0.so.0
#9 gtk_tree_store_new
from /usr/lib/libgtk-x11-2.0.so.0
#10 gtk_tree_store_set_valist
from /usr/lib/libgtk-x11-2.0.so.0
#11 gtk_tree_store_set
from /usr/lib/libgtk-x11-2.0.so.0
#12 ??
#13 ??
#14 ??
#15 g_source_get_current_time
from /lib/libglib-2.0.so.0
#16 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#17 g_main_context_check
from /lib/libglib-2.0.so.0
#18 g_main_loop_run
from /lib/libglib-2.0.so.0
#19 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#20 ??
#21 __libc_start_main
from /lib/libc.so.6
#22 ??
#0 __waitpid_nocancel
from /lib/libpthread.so.0

Comment 1 Benoît Dejean 2006-08-06 17:08:25 UTC

Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

Comment 2 Karsten Bräckelmann 2006-09-30 16:22:49 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!