Bug 96561 – crash when resizing in pine

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 96561 - crash when resizing in pine


Summary:	crash when resizing in pine


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:	Havoc Pennington
QA Contact:	GNOME Terminal Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2002-10-23 01:24 UTC by btonkes
Modified:	2004-12-22 21:47 UTC

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

Description btonkes 2002-10-23 01:21:38 UTC

Package: gnome-terminal
Severity: major
Version: 2.0.1
Synopsis: crash when resizing in pine
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.0.3)

Description:
Description of Problem:

gnome-terminal crashes when I attempt to resize it while reading a
message in pine.

Steps to reproduce the problem:
1.  Start a gnome-terminal window
2.  Run pine
3.  Open a message that is longer than the length of the screen
4. Maximise the window vertically
5. (Death)

How often does this happen?

Every time.




Debugging Information:

Backtrace was generated from '/home/btonkes/bin/gnome-terminal'

(no debugging symbols found)...[New Thread 8192 (LWP 28589)]
0x420ae169 in wait4 () from /lib/i686/libc.so.6

+ Trace 29256

Thread 1 (Thread 8192 (LWP 28589))

#0 wait4
from /lib/i686/libc.so.6
#1 __DTOR_END__
from /lib/i686/libc.so.6
#2 waitpid
from /lib/i686/libpthread.so.0
#3 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#4 __pthread_sighandler
from /lib/i686/libpthread.so.0
#5 <signal handler called>
#6 kill
from /lib/i686/libc.so.6
#7 raise
from /lib/i686/libpthread.so.0
#8 abort
from /lib/i686/libc.so.6
#9 g_logv
from /usr/lib/libglib-2.0.so.0
#10 g_log
from /usr/lib/libglib-2.0.so.0
#11 vte_terminal_ensure_cursor
from /usr/lib/libvte.so.2
#12 vte_terminal_insert_char
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 wait4
from /lib/i686/libc.so.6





------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-10-22 21:21 -------

The original reporter (btonkes@itee.uq.edu.au) 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, hp@redhat.com.

Comment 1 Brad Tonkes 2002-10-23 01:38:10 UTC

Hmm, on closer inspection it doesn't seem to occur as reliably as I
claimed.  It seems to occur only when I use "gnome-terminal -x pine",
and then only for certain messages.  I do have 1 message for which it
reliably crashes - this message has 7 attachments, about 25 people in
the To: field and about 150 lines of text.

Comment 2 John Fleck 2002-10-23 03:25:35 UTC

This looks as though it was fixed in cvs within the last week. Thanks
for the report.

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