Bug 366518 – crash in Terminal: playing supertux

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 366518 - crash in Terminal: playing supertux


Summary:	crash in Terminal: playing supertux


Status:	RESOLVED DUPLICATE of bug 348979

Product:	gnome-terminal
Classification:	Core
Component:	general
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	GNOME Terminal Maintainers
QA Contact:	GNOME Terminal Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-10-28 21:38 UTC by contact
Modified:	2006-11-01 23:31 UTC

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

Description contact 2006-10-28 21:38:49 UTC

Version: 2.16.0

What were you doing when the application crashed?
playing supertux


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 393687040 vsize: 393687040 resident: 23949312 share: 9986048 rss: 23949312 rss_rlim: -1
CPU usage: start_time: 1162047951 rtime: 2357 utime: 2122 stime: 235 cutime:17 cstime: 13 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-terminal'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496370144 (LWP 3106)]
[New Thread 1084229952 (LWP 3114)]
(no debugging symbols found)
0x0000003bd5c0d96f in waitpid () from /lib64/libpthread.so.0

+ Trace 79465

Thread 1 (Thread 46912496370144 (LWP 3106))

#0 waitpid
from /lib64/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 g_type_check_is_value_type
from /lib64/libgobject-2.0.so.0
#4 g_value_type_compatible
from /lib64/libgobject-2.0.so.0
#5 g_object_class_override_property
from /lib64/libgobject-2.0.so.0
#6 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#7 g_signal_emit
from /lib64/libgobject-2.0.so.0
#8 gtk_widget_set_usize
from /usr/lib64/libgtk-x11-2.0.so.0
#9 gtk_widget_set_usize
from /usr/lib64/libgtk-x11-2.0.so.0
#10 gtk_box_pack_start_defaults
from /usr/lib64/libgtk-x11-2.0.so.0
#11 gtk_rc_get_module_dir
from /usr/lib64/libgtk-x11-2.0.so.0
#12 gtk_icon_info_get_type
from /usr/lib64/libgtk-x11-2.0.so.0
#13 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#14 g_main_context_check
from /lib64/libglib-2.0.so.0
#15 g_main_loop_run
from /lib64/libglib-2.0.so.0
#16 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#17 g_cclosure_marshal_VOID__OBJECT
#18 __libc_start_main
from /lib64/libc.so.6
#19 g_cclosure_marshal_VOID__OBJECT
#20 ??
#21 ??
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 Karsten Bräckelmann 2006-10-28 22:09:09 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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

Comment 2 Mariano Suárez-Alvarez 2006-10-29 02:25:39 UTC

This does not really look like a dup of 348814...

Comment 3 Christian Kirbach 2006-10-29 18:46:46 UTC

at least the trace matches exactly. I guess somehow a new tab got opened...

Comment 4 Karsten Bräckelmann 2006-10-30 11:57:11 UTC


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

Comment 5 Karsten Bräckelmann 2006-10-30 11:58:33 UTC

(In reply to comment #2)
> This does not really look like a dup of 348814...

Yeah, see the discussion on bug 348979... :/

Comment 6 Behdad Esfahbod 2006-11-01 23:31:27 UTC

Duping to correct bug.  Seems like 348979 was not a dupe of 348814 afterall.

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