Bug#954943: Makes virtual console 1 unusable
Laurent Bigonville (2020/03/25 17:58 +0100): > Plymouth should exit once the boot is finished so that shouldn't happen. > > There is a bug (whether it's a bug is debated) in systemd version 245-1 > where plymouth can be restarted. > > Can you please check if you have 245-1 installed or do you have an other > version? dpkg says systemd version 245.2-1. Sébastien.
Bug#954943: Makes virtual console 1 unusable
Le 25/03/20 à 17:10, Sebastien Hinderer a écrit : On my system plymouth had been installed without me noticing. At some point I realised that the first virtual console became unusable: not all keys I was pressing did work in shells and programs, whereas the other virtual consoles did continue to work properly. Further investigation (with lsof) showed that plymouth was reading /dev/tty1 concurrently with the running shell / programs. So it got some of the keypresses and that was why I had to type e.g. letters several times. For arrow keys, the escape sequences were even split, plymouth read parts of them while the other parts were read by the shell or currently running program, leading to very odd behaviours. Uninstalling plymouth solved the problem. Plymouth should exit once the boot is finished so that shouldn't happen. There is a bug (whether it's a bug is debated) in systemd version 245-1 where plymouth can be restarted. Can you please check if you have 245-1 installed or do you have an other version?
Bug#954943: Makes virtual console 1 unusable
Package: plymouth Version: 0.9.4-2 Severity: normal Tags: upstream On my system plymouth had been installed without me noticing. At some point I realised that the first virtual console became unusable: not all keys I was pressing did work in shells and programs, whereas the other virtual consoles did continue to work properly. Further investigation (with lsof) showed that plymouth was reading /dev/tty1 concurrently with the running shell / programs. So it got some of the keypresses and that was why I had to type e.g. letters several times. For arrow keys, the escape sequences were even split, plymouth read parts of them while the other parts were read by the shell or currently running program, leading to very odd behaviours. Uninstalling plymouth solved the problem.
