Bug 135004 – gnome-terminal crashed

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 135004 - gnome-terminal crashed


Summary:	gnome-terminal crashed


Status:	RESOLVED DUPLICATE of bug 94509

Product:	gnome-terminal
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other other

Importance:	Normal normal
Target Milestone:	---
Assigned To:	GNOME Terminal Maintainers
QA Contact:	GNOME Terminal Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2004-02-20 23:27 UTC by clwang
Modified:	2004-12-22 21:47 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description clwang 2004-02-20 23:27:15 UTC

Package: gnome-terminal
Severity: normal
Version: 2.0.1
Synopsis: gnome-terminal crashed
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.0.3)

Description:
Description of Problem:
gnome-terminal crashed, apparently after growing the gnome-terminal
window

Steps to reproduce the problem:
i'm not entirely sure, but...
1.  gunzip -c  largefile.gz | less
2. grow the size of the gnome-terminal window
3. crash

Actual Results:
crash

Expected Results:
not to crash

How often does this happen?
recently, it's happening about once per day.

Additional Information:




Debugging Information:

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

(no debugging symbols found)...[New Thread 16384 (LWP 1722)]
0x408eb7f7 in waitpid ()
   from /lib/i686/libpthread.so.0

+ Trace 44419

Thread 1 (Thread 16384 (LWP 1722))

#0 waitpid
from /lib/i686/libpthread.so.0
#1 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 __pthread_sighandler
from /lib/i686/libpthread.so.0
#3 <signal handler called>
#4 kill
from /lib/i686/libc.so.6
#5 raise
from /lib/i686/libpthread.so.0
#6 raise
from /lib/i686/libc.so.6
#7 abort
from /lib/i686/libc.so.6
#8 g_logv
from /usr/lib/libglib-2.0.so.0
#9 g_log
from /usr/lib/libglib-2.0.so.0
#10 vte_terminal_ensure_cursor
from /usr/lib/libvte.so.2
#11 vte_sequence_handler_ce
from /usr/lib/libvte.so.2
#12 vte_terminal_handle_sequence
from /usr/lib/libvte.so.2
#13 vte_terminal_process_incoming
from /usr/lib/libvte.so.2
#14 g_idle_dispatch
from /usr/lib/libglib-2.0.so.0
#15 g_main_dispatch
from /usr/lib/libglib-2.0.so.0
#16 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#17 g_main_context_iterate
from /usr/lib/libglib-2.0.so.0
#18 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#19 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#20 main
#21 __libc_start_main
from /lib/i686/libc.so.6
#0 waitpid
from /lib/i686/libpthread.so.0





------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-02-20 18:27 -------

The original reporter (clwang@yahoo-inc.com) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, gnome-terminal-maint@bugzilla.gnome.org.

Comment 1 Mariano Suárez-Alvarez 2004-02-20 23:30:11 UTC

This has been fixed a while ago. You need to upgrade your
gnome-terminal/vte...

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