Bug 156380 - gnome-terminal scroll slow
gnome-terminal scroll slow
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: gnome-terminal (Show other bugs)
3.0
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Behdad Esfahbod
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-29 11:42 EDT by Denise Hynson
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-10-19 15:03:28 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Denise Hynson 2005-04-29 11:42:51 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322)

Description of problem:
Since upgrading to Red Hat Enterprise 3.0 from Red Hat 7.2 & 7.3, the gnome-terminal is so slow scrolling that is almost unusable.

Version-Release number of selected component (if applicable):
gnome-terminal-2.2.2-1

How reproducible:
Always

Steps to Reproduce:
1.  Open a gnome-terminal
2.  vi a large file
3.  CTL F or CTL B
4.  very slow to update
5.  If I use vim response is normal
 
  

Actual Results:  VERY slow to update

Expected Results:  It should scroll smoothly.

Additional info:
Comment 1 RHEL Product and Program Management 2007-10-19 15:03:28 EDT
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
 
For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/
 
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.

Note You need to log in before you can comment on or make changes to this bug.