On Mon 11 May 2026 at 10:58:03 (-0400), Felix Miata wrote: > Felix Miata composed on 2026-05-11 10:49 (UTC-0400): > > > This probably dates back more or less to November, with kernel 5.10.0-37, > > and > > applies whether AMD, Intel or NVidia graphics, on all 20+ Bullseyes I still > > have. > > tty1 behaves normally, but 2-6 only has a blinking underscore on row 3 at > > its > > expected position following an invisible shell prompt. > > > > Is this happening to everyone using old-old?--
https://lists.debian.org/debian-user/2025/12/msg00188.html My experience with -37 was not of /no/ text, but of a "random" character all over the screen. As I described, the VCs could be used even though you couldn't read the output from commands. (Changing font size would change the character.) But when I upgraded to -38 on 2026-02-12, normality was restored. On my systems, -37 is long gone (2026-03-13), and all versions before and since -37 have worked normally. > Actually, tty1 only behaves normally to a point. No shell prompt appears, > after > last boot message, and there's no response to keyboard. Also, same behavior > whether target is graphical or multi-user. That's never been my experience, and you make it sound as if the system is unusable. Is that the case? My keyboard was never affected. I'm writing this on a bullseye, old-old system, up to date with -42. The one oddity that I do see, and this is older than bullseye and still occurs on bookworm/trixie, is something that I think I reported many years ago but haven't been worried about. It happens on different computers too. While not logged in (ie on the initial getty), the login: prompt may be erased by what appears to be a self generated Home ClearLine sequence. This can also happen at the Passphrase: prompt when I unlock /home (logged in as the dedicated "unlock" user, who immediately gets logged out by its ~/.profile script). As I then login as me, and startx, I don't have the opportunity to see whether tty1 would keep behaving like this if I kept logging out/in. Nor have I ever seen this behaviour on the other ttys, but that could be because the number of opportunities is just too low (very occasional usage). Cheers, David.
