Guake / guake

Drop-down terminal for GNOME
https://guake.github.io
GNU General Public License v2.0
4.43k stars 575 forks source link

Scrolling unavailability after upgrading to a new version of Linux #802

Open uniit opened 8 years ago

uniit commented 8 years ago

Hello,

After upgrading to a new version of Linux (Ubuntu 16.04/Arch etc.) the screen stopped scrolling through well in guake terminal.

Here is my .screenrc configs:

startup_message off termcapinfo xterm* ti@:te@ termcapinfo xterm* 'hs:ts=;:fs=:ds=;' hardstatus alwayslastline '%{= M} %H%{= G} %l %= %{= w}%-w%{+b r}%n*%t%{-b r}%{w}%+w %= %{c}%d %D %{B}%c '

As far as I see, this behavior is related to 'hardstatus' line. When it is present and I enter some command I am not able to scroll using the mouse wheel (guake just scrolls my previously entered commands). When I press F11 twice then it starts working, however, status line is duplicated after each scroll iteration.

I am using screen + guake utils for a long time and I want to be able to continue working with them.

JFI: This issue is not reproducible in standard Linux terminal.

Any help will be highly appreciated.

gsemet commented 8 years ago

weird indeed

otharwa commented 8 years ago

Me too, please fix this bug =) i love guake

mouseratti commented 8 years ago

I'll try to reproduce that

mouseratti commented 8 years ago

@OleksandrPalamarchuk what version do you use?

uniit commented 8 years ago

@mouseratti Hi,

Ubuntu 16.04.1 LTS Screen version 4.03.01 (GNU) 28-Jun-15 Guake 0.8.5-1

Just install the latest version of those apps.

uniit commented 8 years ago

@mouseratti I'm attaching the screenshot where 'hardstatus' line is duplicated for your convenience. hardline_duplication

uniit commented 8 years ago

@mouseratti I've found some interesting things. The issue with scrolling commands is present on Ubuntu 14.04 as well after upgrading guake to the latest version.

Default package in the 14.04 repository:

Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Architecture: amd64
Version: 0.4.4-1ubuntu1

The issue is not reproducible.

Upgraded package:

Maintainer: Daniel Echeverry <epsilon77@gmail.com>
Architecture: amd64
Version: 0.8.7-1~webupd8~trusty0

The issue is reproducible.

After that, I've downgraded guake to 0.4.4 on Ubuntu 16.04 however this has not helped.

Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Architecture: amd64
Version: 0.4.4-1ubuntu1

As for the one with duplicated status line it is present on 14.04 and appears after pressing F11 twice.

iwarford commented 7 years ago

Guake began to scroll my recently entered commands as well after upgrading from 14.04 to 16.04 last weekend.

Switching tmux into mouse mode alleviated the scrollback issue, but it caused a host of other issues.

This appears to be annoying a couple of people in the last few years:

https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1688528 https://bugzilla.gnome.org/show_bug.cgi?id=538195

Looks like it's been addressed / made an option in an upstream VTE version: https://bugzilla.gnome.org/show_bug.cgi?id=518405

Bit more history here: https://unix.stackexchange.com/questions/295467/mint-mate-17-3-how-to-enable-mouse-scrolling-in-man-less-vim

I don't know what patches have been applied to stock 16.04 though. It looks like the intent after all is said and done to be able to control this with an escape sequence of DEC 1007 (see man console_codes for info on the DEC codes). That certainly doesn't appear to work in the VTE in 16.04 for me, though.

djonatanb commented 6 years ago

This helps as a workaround in my case with byobu/tmux

https://bugs.launchpad.net/byobu/+bug/434041

Please use screen's scrollback buffer instead. Press F7, and then scroll with your up/down, pageup/pagedown, or mouse wheel.

Also, removing the PPA guake 3.0.5 and compiling it with this instructions http://guake.readthedocs.io/en/latest/user/installing.html#install-from-source gets me guake 3.3.0 in which scroll works properly for everything but git status. So the problem still remains and seems to be specific to git status in my case.