Bug 425942 – crash in System Monitor: installing a Bridge game

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 425942 - crash in System Monitor: installing a Bridge game


Summary:	crash in System Monitor: installing a Bridge game


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:

Depends on:
Blocks:

Reported:	2007-04-03 18:27 UTC by marcelo.zamorano
Modified:	2011-11-11 10:03 UTC

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

Description marcelo.zamorano 2007-04-03 18:27:31 UTC

Version: 2.16.1

What were you doing when the application crashed?
installing a Bridge game


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

Memory status: size: 54870016 vsize: 0 resident: 54870016 share: 0 rss: 16936960 rss_rlim: 0
CPU usage: start_time: 1175623839 rtime: 0 utime: 1344 stime: 0 cutime:1194 cstime: 0 timeout: 150 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 -1225459200 (LWP 10242)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 124691

Thread 1 (Thread -1225459200 (LWP 10242))

#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 ??
#33 ??
#34 ??
#35 ??
#36 ??
#37 ??
#38 ??
#0 __kernel_vsyscall

Comment 1 Damien Durand 2007-04-04 11:38:55 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 ***