You are not logged in.

#1 2020-09-27 11:47:44

hoschi
Member
From: Ulm (Germany)
Registered: 2008-11-03
Posts: 458

Cannot scrollback on terminal

Hello!

When I'm on the terminal (TTYx) I cannot scrollback anymore with Shift + [PGUP|PGDN] hmm
I'm a little puzzled. I heared that something should be removed with the upcoming Linux kernel 5.9 but I'm running Archlinux stable with 'linux 5.8.11.arch1-1' currently. Did I missed something or some kind of backport?

No being able to scroll back some lines is uncomfortable. I'm looking into automatically launching screen now to make things more comfortable smile

Thanks

Last edited by hoschi (2020-09-27 11:48:01)

Offline

#2 2020-09-27 16:56:10

porcelain1
Member
Registered: 2020-01-18
Posts: 97

Re: Cannot scrollback on terminal

Wow! Very funny! I also I can't scrollback.

This might be related: https://lore.kernel.org/lkml/2020092311 … uo.ucw.cz/

It seems they removed scrollback for now because there was an "out-of-bound write in fbcon_redraw_softback" present since version 2.2.3 of the kernel, according to an linked email.


Behemoth, wake up!

Offline

#3 2020-09-27 18:48:37

nl6720
The Evil Wiki Admin
Registered: 2016-07-02
Posts: 595

Re: Cannot scrollback on terminal

The change was backported to 5.8.10 and probably to all LTS kernels too.

Offline

#4 2020-09-28 08:09:34

hoschi
Member
From: Ulm (Germany)
Registered: 2008-11-03
Posts: 458

Re: Cannot scrollback on terminal

Thank you nl6720. Therefore it is really a backport!
This hurts sad


Does anyone remember about a feature removal within a stable kernel yikes

Last edited by hoschi (2020-10-05 15:00:08)

Offline

#5 2020-10-05 15:00:49

hoschi
Member
From: Ulm (Germany)
Registered: 2008-11-03
Posts: 458

Re: Cannot scrollback on terminal

My current solution is launching or attaching screen in every shell i.e. through "~/.bashrc" like described here:

if [[ -z "$STY" ]]; then # I also check here for $TERM, because I want use screen only on the VT and not in GNOME-Terminal
   screen -xRR session_name
fi

I recommend also some settings for "~./screenrc":

startup_message off
msgwait 0
vbell off

I think most people are fine reading the startup message once, msgwait prevents showing "new screen" at the bottom for five seconds if not any key is pressed and finally vbell prevents screen from ringing the bell "visually" which is quit annoying with autocompletion.


The solution with a unit file doesn't work properly - for me. A user can and will likely terminate it screen session deliberately itself, Systemd will rightfully recognize that and complain about it. That approach is  using screen as system daemon with screen as user space application, probably screen is not designed for that usage.

Offline

Board footer

Powered by FluxBB