Bug 361117 – crash in Terminal:

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 361117 - crash in Terminal:


Summary:	crash in Terminal:


Status:	RESOLVED INCOMPLETE

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:

Duplicates:	362237 364273 365418 370078 373704 379171 379514 382799 388244 391222 391610 397648 401752 401814 403759 405123 406355 412106 415633 425025 454114 (view as bug list)
Depends on:
Blocks:

Reported:	2006-10-10 11:35 UTC by ma.cro
Modified:	2008-01-01 13:19 UTC

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

Description ma.cro 2006-10-10 11:35:43 UTC

Version: 2.16.1

What were you doing when the application crashed?



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

Memory status: size: 52510720 vsize: 0 resident: 52510720 share: 0 rss: 16826368 rss_rlim: 0
CPU usage: start_time: 1160478072 rtime: 0 utime: 131 stime: 0 cutime:109 cstime: 0 timeout: 22 it_real_value: 0 frequency: 8665

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

(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 -1226434896 (LWP 15426)]
[New Thread -1246532704 (LWP 15430)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 75594

Thread 1 (Thread -1226434896 (LWP 15426))

#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 g_type_check_instance_is_a
from /usr/lib/libgobject-2.0.so.0
#5 g_object_unref
from /usr/lib/libgobject-2.0.so.0
#6 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#7 _gtk_container_dequeue_resize_handler
from /usr/lib/libgtk-x11-2.0.so.0
#8 gtk_window_new
from /usr/lib/libgtk-x11-2.0.so.0
#9 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#10 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#11 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#15 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#16 gtk_widget_hide
from /usr/lib/libgtk-x11-2.0.so.0
#17 _gtk_window_unset_focus_and_default
from /usr/lib/libgtk-x11-2.0.so.0
#18 g_object_run_dispose
from /usr/lib/libgobject-2.0.so.0
#19 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#20 gtk_widget_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#22 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#23 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#24 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#25 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#26 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#27 ??
#28 ??
#29 _IO_stdin_used
#30 ??
#31 ??
#0 __kernel_vsyscall

Comment 1 Baptiste Mille-Mathias 2006-10-15 17:06:15 UTC

*** Bug 362237 has been marked as a duplicate of this bug. ***

Comment 2 Baptiste Mille-Mathias 2006-10-22 21:06:34 UTC

*** Bug 364273 has been marked as a duplicate of this bug. ***

Comment 3 Baptiste Mille-Mathias 2006-10-22 21:07:20 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

Comment 4 Mariano Suárez-Alvarez 2006-10-26 20:10:00 UTC

*** Bug 365418 has been marked as a duplicate of this bug. ***

Comment 5 André Klapper 2006-11-05 13:54:46 UTC

*** Bug 370078 has been marked as a duplicate of this bug. ***

Comment 6 Damien Durand 2006-11-11 12:37:34 UTC

*** Bug 373704 has been marked as a duplicate of this bug. ***

Comment 7 Don Scorgie 2006-11-25 18:57:14 UTC

*** Bug 379171 has been marked as a duplicate of this bug. ***

Comment 8 Mariano Suárez-Alvarez 2006-11-26 21:04:13 UTC

*** Bug 379514 has been marked as a duplicate of this bug. ***

Comment 9 Christian Kirbach 2006-12-05 22:38:00 UTC

*** Bug 382799 has been marked as a duplicate of this bug. ***

Comment 10 Bruno Boaventura 2006-12-21 15:22:18 UTC

*** Bug 388244 has been marked as a duplicate of this bug. ***

Comment 11 Susana 2006-12-31 11:41:01 UTC

*** Bug 391222 has been marked as a duplicate of this bug. ***

Comment 12 palfrey 2007-01-02 19:01:13 UTC

*** Bug 391610 has been marked as a duplicate of this bug. ***

Comment 13 Bruno Boaventura 2007-01-18 03:06:55 UTC

*** Bug 397648 has been marked as a duplicate of this bug. ***

Comment 14 Christian Kirbach 2007-01-27 22:48:50 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks in advance!

Comment 15 Mariano Suárez-Alvarez 2007-01-29 07:59:20 UTC

*** Bug 401752 has been marked as a duplicate of this bug. ***

Comment 16 Mariano Suárez-Alvarez 2007-01-29 08:23:35 UTC

*** Bug 401814 has been marked as a duplicate of this bug. ***

Comment 17 Bruno Boaventura 2007-02-03 03:13:50 UTC

*** Bug 403759 has been marked as a duplicate of this bug. ***

Comment 18 Mariano Suárez-Alvarez 2007-02-06 20:59:07 UTC

*** Bug 405123 has been marked as a duplicate of this bug. ***

Comment 19 Mariano Suárez-Alvarez 2007-02-10 19:32:24 UTC

*** Bug 406355 has been marked as a duplicate of this bug. ***

Comment 20 Jonathon Jongsma 2007-02-26 19:13:04 UTC

*** Bug 412106 has been marked as a duplicate of this bug. ***

Comment 21 Susana 2007-03-07 12:43:42 UTC

*** Bug 415633 has been marked as a duplicate of this bug. ***

Comment 22 palfrey 2007-04-26 17:24:30 UTC

*** Bug 425025 has been marked as a duplicate of this bug. ***

Comment 23 palfrey 2007-07-06 14:53:05 UTC

*** Bug 454114 has been marked as a duplicate of this bug. ***

Comment 24 Teppo Turtiainen 2008-01-01 13:19:31 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!