Bug 348470 – crash on 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 348470 - crash on Terminal


Summary:	crash on Terminal


Status:	RESOLVED INCOMPLETE

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

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

URL:
Whiteboard:

Duplicates:	349987 390644 430623 (view as bug list)
Depends on:
Blocks:

Reported:	2006-07-24 04:13 UTC by havoc50
Modified:	2008-01-01 12:27 UTC

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

Description havoc50 2006-07-24 04:13:34 UTC

What were you doing when the app crashed?:
I was telnetting into a network switch, configuring vlans when it crashed


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.15.4 2006-07-11 (Ubuntu)
BugBuddy Version: 2.15.0

Memmory status: size: 62758912 vsize: 0 resident: 62758912 share: 0 rss: 14938112 rss_rlim: 0
CPU usage: start_time: 1153712783 rtime: 0 utime: 597 stime: 0 cutime:546 cstime: 0 timeout: 51 it_real_value: 0 frequency: 0

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 -1226033488 (LWP 4922)]
[New Thread -1266635872 (LWP 4926)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 69551

Thread 1 (Thread -1226033488 (LWP 4922))

#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 vte_terminal_get_default_emulation
from /usr/lib/libvte.so.9
#5 vte_terminal_feed_child_binary
from /usr/lib/libvte.so.9
#6 vte_terminal_feed_child_binary
from /usr/lib/libvte.so.9
#7 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#8 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#9 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#13 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#14 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#15 gdk_window_is_viewable
from /usr/lib/libgdk-x11-2.0.so.0
#16 gdk_window_process_all_updates
from /usr/lib/libgdk-x11-2.0.so.0
#17 gdk_window_process_all_updates
from /usr/lib/libgdk-x11-2.0.so.0
#18 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#19 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#20 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#21 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#22 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#23 ??
#24 ??
#25 _IO_stdin_used
#26 ??
#27 ??
#0 __kernel_vsyscall

Comment 1 Behdad Esfahbod 2006-07-24 21:20:42 UTC

Do you have input methods activated?

Comment 2 Behdad Esfahbod 2006-08-04 21:32:29 UTC

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

Comment 3 palfrey 2006-12-29 19:22:03 UTC

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

Comment 4 palfrey 2007-04-26 17:40:11 UTC

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

Comment 5 André Klapper 2007-10-29 01:04:52 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 and reopen this bug or report a new one. Thanks in advance!

Comment 6 Teppo Turtiainen 2008-01-01 12:27:36 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!