+++ This bug was initially created as a clone of Bug #477874 +++ Created attachment 327822 [details] Expected results Description of problem: I have a bash alias that spawns vim in a dedicated gnome-terminal with a particular profile for text editing. Occasionally, it will come up with blank lines where text should be, which will persist until I scroll down several times in vim, use the menu item 'Terminal->Reset', or do '!reset' in vim's command mode. The corruption is sporadic, and will happen several times in a row, then go completely away for a while. Occasionally, I will get the message '(gnome-terminal:16737): Vte-WARNING **: No handler for control sequence `device-control-string' defined.' and the gnome-terminal command will not exit/go into the background, as if I had added --disable-factory to the command line. Version-Release number of selected component (if applicable): The problem has been present since Fedora 8, but I only have versions for F9 and F10. F9: gnome-terminal-2.22.2-1.fc9.x86_64 vim-enhanced-7.2.060-1.fc9.x86_64 F10: gnome-terminal-2.24.2-2.fc10.x86_64 vim-enhanced-7.2.060-1.fc10.x86_64 How reproducible: Frequently, but not perfectly. It seems to only hit files larger than the geometry specified on the command line. I have not been able to reproduce without specifying geometry. I usually use --window-with-profile=Editor, but this is not required. The 'Editor' profile uses a smaller font and hides the scrollbar and menu, but this is reproducible without those changes. I believe a file with more lines than the geometry may be a requirement, but have not investigated that very far. Steps to Reproduce: 1. gnome-terminal --geometry=80x50 -x /usr/bin/vim filename 2. Repeat until corruption occurs; this may be 10s of retries. Actual results: See attachment 'Actual results' Expected results: See attachment 'Expected results' [...] --- Additional comment from mschmidt on 2010-07-12 10:40:16 EDT --- It is reproducible in XFCE's Terminal too, so the bug is probably in the vte library which is shared by both. --- Additional comment from behdad on 2010-07-21 16:31:53 EDT --- This is indeed a vte bug, and I have been seen it for a while. Let me look into it. [...] --- Additional comment from mschmidt on 2011-11-09 03:38:20 EST --- Still seeing this in F16. gnome-terminal-3.2.1-2.fc16.x86_64 vte-0.28.1-1.fc16.x86_64 --- Additional comment from dave on 2011-12-15 18:44:51 EST --- Also getting this with vte3: vte3-0.30.1-3.fc16.x86_64 In fact, the corruption happens when editing almost any file with highlighting, making it quite difficult to use.
The reproducer in https://bugzilla.redhat.com/show_bug.cgi?id=477874#c5 is still effective in F16, Gnome 3, vte3.
This bug is still reproducible with rawhide: vte3-0.32.0-1.fc17.x86_64 Actually I'm using just colorized git diff - and then when just move one line up - quite often couple lines just disappear. Is anyone working on this bug at all ? (since the bug is getting quite old)
Still easily reproducible with: gnome-terminal-3.4.1.1-1.fc17.x86_64 vte3-0.32.1-1.fc17.x86_64 Any progress with this issue ?
Nobody is working on it, no.
Being impressed how long does it take to fix this bug. Over 3 years old and there is an easy reproducer which still applies for: gnome-terminal-3.4.1.1-2.fc18.x86_64 vte3-0.32.2-2.fc18.x86_64
Using F17 I see corruption when I run tmux inside of gnome-terminal or xfce4-terminal. It's easy to reproduce on my 24-inch monitor. The steps below seem to reliably recreate the problem. 1. Launch tmux. 2. Create 4 panes; I divide the screen in quarters to have 4 evenly sized panes. 3. In 3 panes open a vim session and in the 4th leave a bash session. 4. Use the tmux keys (Control+B Arrow) to move between the panes. Garbage appears at the spot the cursor is in the pane I active and in the pane I deactive where the cursor was before deactivation. This seems to take less than 2 minutes to appear. If I try to tolerate this for a while (Control-L/reset) for a while then I will see a problem where the whole screen will scroll up and move the tmux status line up but leave a copy of it at the bottom. FWIW, konsole does not exhibit any corruption.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
Still experiencing with rawhide - vte3-0.34.5-1.fc20.x86_64
Is there a upstream bug report about this?
https://bugzilla.gnome.org/show_bug.cgi?id=415277 This is the best candidate that I could find for an upstream bug. Other candidates: https://bugzilla.gnome.org/show_bug.cgi?id=608163 https://bugzilla.gnome.org/show_bug.cgi?id=553971 There is also the following bug preceded 783212: https://bugzilla.redhat.com/show_bug.cgi?id=477874 I fear this bug will never being fixed so I migrated to konsole.
All of us "upstream developers" are aware of this bug, but it's a tricky one and none of us have the time to track it down and fix it :(.
Could you please try with vte3-0.35? It contains some fixes that might be relevant.
Is this scheduled to show up in updates-testing? I have an up-do-date F20: $ rpm -q vte3 vte3-0.34.9-1.fc20.x86_64
Just for fun, I tried to use gnome-terminal, $ rpm -q gnome-terminal vte3 gnome-terminal-3.10.2-1.fc20.x86_64 vte3-0.34.9-1.fc20.x86_64 and found the same issue pretty much instantly. I reproduce it by using tmux inside gnome-terminal, creating some panes, opening an instance or two of vim, and there it is.
I'm not familiar with Fedora, I'm using another distro. I don't think the new version (vte3-0.35.x or 0.36) will end up in F20, but it's already in Rawhide, maybe you can upgrade this single package from there (and then quit all running instances of gnome-terminal). Alternatively, you could download the vte-0.36 tarball, compile with "./confirue" followed by "make" and start with the command "./src/vte2_90". (This method doesn't mess up your running system, and you don't even have to quit gnome-terminal.) I'd be happy to fix the bug if it's still there but first I'd like to hear confirmation, there were really a lot of work happening between 0.34.9 and 0.35.0 and I see a 90%+ chance that your bug is already fixed. Also please note that the original reporter mentioned a use case where he sees corruption, and you mentioned another one. From a technical point of view, we may or may not face two different bugs, squeezed into one bugreport. If your bug still persist, may I ask you to open a new bug, so we leave this one for the original? Please cc me in that case.
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
I haven't seen this kind of terminal corruption for a long time and my reproducer no longer triggers the issue. This vte3 bug has been fixed at some point.