Bug 433101 – 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 433101 - crash in Terminal:


Summary:	crash in Terminal:


Status:	RESOLVED DUPLICATE of bug 394890

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:	2007-04-24 21:23 UTC by champ
Modified:	2007-04-24 23:46 UTC

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

Description champ 2007-04-24 21:23:52 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: 50434048 vsize: 0 resident: 50434048 share: 0 rss: 15167488 rss_rlim: 0
CPU usage: start_time: 1177437077 rtime: 0 utime: 76 stime: 0 cutime:70 cstime: 0 timeout: 6 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 -1226180944 (LWP 10567)]
[New Thread -1245746272 (LWP 10578)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 130347

Thread 1 (Thread -1226180944 (LWP 10567))

#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_time_val_from_iso8601
from /usr/lib/libglib-2.0.so.0
#5 g_tree_lookup
from /usr/lib/libglib-2.0.so.0
#6 vte_terminal_accessible_new
from /usr/lib/libvte.so.9
#7 vte_terminal_accessible_new
from /usr/lib/libvte.so.9
#8 vte_terminal_accessible_new
from /usr/lib/libvte.so.9
#9 _vte_debug_parse_string
from /usr/lib/libvte.so.9
#10 vte_terminal_feed_child
from /usr/lib/libvte.so.9
#11 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#12 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#13 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#17 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#18 gtk_window_propagate_key_event
from /usr/lib/libgtk-x11-2.0.so.0
#19 gtk_window_activate_key
from /usr/lib/libgtk-x11-2.0.so.0
#20 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#21 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#22 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#23 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#24 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#26 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#27 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#28 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#29 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#30 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#31 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#32 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#33 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#34 ??
#35 ??
#36 _IO_stdin_used
#37 ??
#38 ??
#0 __kernel_vsyscall

Comment 1 wavell 2007-04-24 22:54:46 UTC

I was doing some ruby on rails command line options and I pressed the up arrow repeatedly to cause this error.  this is on a hp nx6310 laptop.

I probably couldn't reproduce this if I tried ...

Comment 2 Diego Escalante Urrelo (not reading bugmail) 2007-04-24 23:46:33 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 394890 ***