Bug 161171 – gnome-system-monitor 2.8.1 crashes on start

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 161171 - gnome-system-monitor 2.8.1 crashes on start


Summary:	gnome-system-monitor 2.8.1 crashes on start


Status:	RESOLVED DUPLICATE of bug 160560

Product:	system-monitor
Classification:	Core
Component:	general
Version:	2.8.x
Hardware:	Other other

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2004-12-13 17:04 UTC by Scott Harmon
Modified:	2011-11-11 10:03 UTC

See Also:
GNOME target:	---
GNOME version:	2.7/2.8

Description Scott Harmon 2004-12-13 17:05:05 UTC

Distribution: Slackware Slackware 10.0.0
Package: system-monitor
Severity: normal
Version: GNOME2.8.2 2.8.1
Gnome-Distributor: Dropline Systems
Synopsis: gnome-system-monitor 2.8.1 crashes on start
Bugzilla-Product: system-monitor
Bugzilla-Component: general
Bugzilla-Version: 2.8.1
BugBuddy-GnomeVersion: 2.0 (2.8.0)
Description:
Description of the crash:
scott@amdg:~$ gnome-system-monitor
Bonobo accessibility support initialized
GTK Accessibility Module initialized

(gnome-system-monitor:15577): GLib-GObject-CRITICAL **: file gobject.c:
line 1579 (g_object_unref): assertion `G_IS_OBJECT (object)' failed
Bonobo accessibility support initialized
GTK Accessibility Module initialized

Steps to reproduce the crash:
1.  Start gnome-system-monitor
2. 
3. 

Expected Results:
no crash

How often does this happen?
Every time

Additional Information:



Debugging Information:

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 16384 (LWP 15584)]
[New Thread 32769 (LWP 15585)]
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 15584)]
[New Thread 32769 (LWP 15585)]
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 15584)]
[New Thread 32769 (LWP 15585)]
[New Thread 16386 (LWP 15586)]
0x402bd4da in waitpid () from /lib/libpthread.so.0

+ Trace 53475

Thread 3 (Thread 16386 (LWP 15586))

#0 loser_poll
from /lib/libc.so.6
#1 poll
from /lib/libc.so.6
#2 g_main_loop_get_context
from /usr/lib/libglib-2.0.so.0
#3 ??
#4 ??
#5 ??
#6 g_main_context_query
from /usr/lib/libglib-2.0.so.0
#7 ??
#8 ??
#9 ??
#10 g_idle_remove_by_data
from /usr/lib/libglib-2.0.so.0
#11 ??
#12 ??
#13 ??
#14 ??
#15 ??
#16 g_thread_use_default_impl
from /usr/lib/libglib-2.0.so.0
#17 ??
#18 __JCR_LIST__
from /lib/libpthread.so.0
#19 ??
#20 ??
#21 g_thread_use_default_impl
from /usr/lib/libglib-2.0.so.0
#22 g_ascii_table
from /usr/lib/libglib-2.0.so.0
#23 _g_debug_flags
from /usr/lib/libglib-2.0.so.0
#24 ??
#25 ??
#26 ??
from /usr/lib/libglib-2.0.so.0
#27 ??
#28 ??
#29 ??
#30 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#31 ??
from /usr/lib/libglib-2.0.so.0
#32 ??
from /usr/lib/libORBit-2.so.0
#33 g_thread_use_default_impl
from /usr/lib/libglib-2.0.so.0
#34 ??
#35 ??
#36 _dl_runtime_resolve
from /lib/ld-linux.so.2
#37 ??
#38 ??
#39 link_thread_io_context
from /usr/lib/libORBit-2.so.0
#0 waitpid
from /lib/libpthread.so.0





------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-12-13 12:05 -------


Unknown version 2.8.1 in product system-monitor.  Setting version to "2.8.x".
Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "system-monitor".
   Setting to default milestone for this product, '---'
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was scott@amdg.no-ip.org.
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Elijah Newren 2004-12-13 17:35:32 UTC

Appears to be a unique stack trace, according to the simple-dup-finder.

Comment 2 Benoît Dejean 2004-12-13 18:07:13 UTC

could try to reproduce it with cvs gnome-2-8 ?

Comment 3 Scott Harmon 2004-12-13 18:39:48 UTC

cvs-gnome-2-8? Just gnome-system-monitor, or everything?  BTW,
gnome-system-monitor-2.8.0 seems to work fine.

Comment 4 Benoît Dejean 2004-12-13 18:45:40 UTC

http://developer.gnome.org/tools/cvs.html
cvs co -r gnome-2-8 procman

please, test.
Looks like a duplicate of http://bugzilla.gnome.org/show_bug.cgi?id=160560

Comment 5 Scott Harmon 2004-12-13 19:08:44 UTC

Applied patch from
http://cvs.gnome.org/viewcvs/procman/src/callbacks.c?r1=1.99&r2=1.100

And now it doesn't crash.  Looks like a dup then.

Comment 6 Benoît Dejean 2004-12-20 00:43:43 UTC


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