Console screen is not updated, but kmscon is working

[norbusan]

System: Arch up to date
Installed: kmscon-patched-git as of today 9.0.0.r10.g20a2fc4-1, libtsm-patched-git 4.0.2.r17.gd66dd16-1

Symptome: The console is working, but the output is only updated when I switch between consoles or console/X. I can log in and type commands, but the screen is only updated after console switch.

[CaptaiNiveau]

I've got a similar problem, not sure if it's the same.
When I log in in TTY2 and run any command and then switch to TTY1, I see the entire output of TTY2. However, if I start typing, it randomly flashes between the TTY1 login and the TTY2 output. Worst of all, it shows the password I typed in login on TTY1 in the random flashes in TTY2.

Same goes for all other TTYs, they randomly flash with the content of the other consoles.

I'll try some more combinations, like turning off hardware acceleration and some other things, but I'm not sure if that'll fix it.

Should I open a new issue for this?

[elliott-farrall]

I have had observed the exact same symptoms as norbusan on NixOS. I have observed this behaviour with nixpkgs-unstable kmscon+libtsm, the latest versions of kmscon+libtsm and also (interestingly) fbterm.

I found that the kmsconvt service would often give a warning about fbdev not detecting the refresh rate so I tried building with fbdev disabled. This lead to kmscon not displaying any image and just freezing whatever was displayed previously.

I do boot with greetd (in a wayland compositor) on tty1 which may cause issues but have also tried just booting to kmscon only and did not have much success.

I know this issue is a bit old but when I have some time I will do a few more experiments to see if I can make any progress.

[hustlerone]

This still happens

[hustlerone]

In order to trigger, start session in greetd then start a session in a kmscon vt. Enjoy the subsequent lobotomy

[kdj0c]

I can't reproduce that, if you want to help fixing this you can either:

• Rebuild kmscon with -Dextra_debug=true, and start it with kmscon --verbose --debug, and post the log here.
• If it used to work with a previous version of kmscon, you can run a git bisect, and this should tell us which commit introduced this issue.

Thanks,