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 407750 - Screen corruption when used with screen
Screen corruption when used with screen
Status: RESOLVED FIXED
Product: vte
Classification: Core
Component: general
0.15.x
Other All
: Normal normal
: ---
Assigned To: VTE Maintainers
VTE Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-02-14 06:26 UTC by Mika Fischer
Modified: 2007-02-14 10:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Mika Fischer 2007-02-14 06:26:02 UTC 
Please describe the problem:
The latest upload (2.17.91-0ubuntu1) broke gnome-terminal heavily for me...

I almost always use screen. The problems only seem to occur when I use it. And only when I use the hardstatus feature.

The problem is that every time I fill the screen and it (screen not gnome-terminal) starts to scroll, the screen gets messed up.



Steps to reproduce:
To trigger the problem, you need to put the following in your .screenrc:
hardstatus alwayslastline "Houston, we have a problem..."

Then start screen and for instance type ls -l until the screen is filled...

Actual results:
The terminal gets messed up. It seems like it's scrolling when it shouldn't.

Expected results:
The terminal should not get messed up...

Does this happen every time?
Yes

Other information:
Comment 1 Mika Fischer 2007-02-14 06:34:30 UTC 
The bug is actually in libvte. Reverting to 0.15.2 fixes the issue.
Comment 2 Mariano Suárez-Alvarez 2007-02-14 06:55:07 UTC 
Yup, I can reproduce this using vte's vteapp from SVN as of a couple of days ago, but not with HEAD: indeed, <http://svn.gnome.org/viewcvs/vte?rev=1680&view=rev> seems to have taken care of this.

I'll close this. Do please try using vte from SVN if you can, and if you have problems please reopen.

Thanks for the report, by the way!
Comment 3 Mika Fischer 2007-02-14 10:12:49 UTC 
I extracted the patch from the link above and patched the Ubuntu package with it. This also fixed it for me. Thanks for the pointer!