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 137689 - Terminal window crashes when looking at a man page and resizing the window.
Terminal window crashes when looking at a man page and resizing the window.
Status: RESOLVED DUPLICATE of bug 94509
Product: gnome-terminal
Classification: Core
Component: general
unspecified
Other Linux
: Normal critical
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-03-19 14:22 UTC by b.g.allan
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.0



Description b.g.allan 2004-03-19 14:22:23 UTC
Terminal window crashes when looking at a man page
and resizing the window. This kills all terminal
windows launched.


Steps to reproduce the problem:
1. Start terminal window 
2. open a man page, (eg. 'man kill')
3. while still viewing man page, ie. man page is
still running in window, resize the window.

Actual Results:  Kills all terminal windows that
are running


Expected Results: Terminal windows stay open.


How often does this happen? every time


Additional Information:
Comment 1 Mariano Suárez-Alvarez 2004-04-06 06:03:41 UTC
Thanks for the bug report. Without a stack trace from the crash it's very hard
to determine what caused the crash. Please see
http://bugzilla.gnome.org/getting-traces.cgi for more information about getting
a useful stack trace.

It'd be very useful to know what version of gnome-terminal you are using, too.
Comment 2 b.g.allan 2004-04-06 12:39:19 UTC
I'm using gnome-terminal 2.0.1 with vte-0.8.19.2 running Redhat 8.0
with linux kernel 2.4.20-28.8smp 

This bug showed up after doing an up2date from Redhat.
Comment 3 Mariano Suárez-Alvarez 2004-04-06 17:28:43 UTC
Since you are using those versions, iI'd say this is a bug that has been fixed
for a while now. It is really impossible to be sure unless you can provide a
stack trace, though.
Comment 4 Mariano Suárez-Alvarez 2004-04-18 01:59:11 UTC
I'll just go ahead and close this, as chances are this is a dup of 94509 via
124591. (Going first thru REOPENED...)
Comment 5 Mariano Suárez-Alvarez 2004-04-18 01:59:27 UTC

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