Bug 119137 – gnome-system-monitor crashed

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 119137 - gnome-system-monitor crashed


Summary:	gnome-system-monitor crashed


Status:	RESOLVED DUPLICATE of bug 132551

Product:	system-monitor
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other other

Importance:	High critical
Target Milestone:	---
Assigned To:	System-monitor maintainers
QA Contact:	System-monitor maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2003-08-04 23:41 UTC by Rodd Clarkson
Modified:	2011-11-11 10:03 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Rodd Clarkson 2003-08-04 23:41:38 UTC

Distribution: Red Hat Linux release 9 (Shrike)
Package: gnome-session
Severity: normal
Version: GNOME2.3.4 unspecified
Gnome-Distributor: GARNOME
Synopsis: gnome-system-monitor crashed
Bugzilla-Product: gnome-session
Bugzilla-Component: general
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.3.3.1)
Description:
Description of the crash:

Not sure what happened.  I clicked on a email header in evolution and
thought that it had crashed (it happens a lot) and then realized that it
was gnome-system-monitor (go figure).

Sorry if this is filed in the wrong place, but I wanted to get the trace
into the system.


Debugging Information:

Backtrace was generated from
'/home/rodd/gnome-2.3.3/bin/gnome-system-monitor'

[New Thread 1086016768 (LWP 16966)]
0xffffe002 in ?? ()

+ Trace 39347

Thread 1 (Thread 1086016768 (LWP 16966))

#0 ??
#1 libgnomeui_segv_handle
at gnome-ui-init.c line 738
#2 <signal handler called>
#3 g_logv
#4 g_log
#5 idle_expand_row
at gailtreeview.c line 2165
#6 g_idle_dispatch
at gmain.c line 3241
#7 g_main_dispatch
at gmain.c line 1720
#8 g_main_context_dispatch
at gmain.c line 2268
#9 g_main_context_iterate
at gmain.c line 2349
#10 g_main_loop_run
at gmain.c line 2569
#11 gtk_main
at gtkmain.c line 1093
#12 main
at procman.c line 547
#13 __libc_start_main
from /lib/tls/libc.so.6
#0 ??





------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-08-04 19:41 -------

Reassigning to the default owner of the component, gnome-session-maint@bugzilla.gnome.org.

Comment 1 Elijah Newren 2003-08-05 16:54:04 UTC

Appears to be a unique stack trace, according to the
simple-dup-finder.  Moving from gnome-session to system-monitor,
setting version->2.3.x, marking priority->high & severity->critical,
adding GNOMEVER2.3 & STACKTRACE (due to the debugging symbols) and
bugsquad keywords, and marking as new.

Comment 2 Vincent Untz 2003-10-07 07:29:55 UTC

I had the same crash, with the same stack trace. I killed two
processes, they seemed to disappear from the treeview and it crashed
just a tenth of second later (when updating the treeview ?)

Comment 3 Benoît Dejean 2004-10-22 09:54:35 UTC

can you reproduce it gsm2.8 and libgtop2.8.x ?

Comment 4 Rodd Clarkson 2004-10-22 21:19:49 UTC

I couldn't reproduce it originally. ;-]

I haven't seen any g-s-m issues for ages, so I'm going to close this.

Comment 5 padraig.obriain 2004-11-25 10:31:43 UTC


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