Bugzilla – Bug 1212402
Wayland causes sddm to appear not functional (because change inadvertently the tty and also interfereswith shutdown
Last modified: 2023-08-02 16:36:07 UTC
Open on a laptop (in my case) two wayland-Plasma sessions for different users. The issues you encounter when closing one are two but they are intimately connected and linked to an unexpected change in TTY. Expected: TTY7 and TTY8 for userA and userB. Factual: is done correctly by the software. Now close user 8 (end session). Expected: Drop back on SDDM screen on TTY7 for the open user. Factual: you come to an non functional greyed out screen on TTY7 showing however correctly the ongoing session of user A. If you try to login, no luck. But you find out that this session is there, but NOT on tty7 but on TTY2. If you go there with cntrl+alt+Fn2 then you can log in and have a functional session of user A. Same procedure if you try to shutdown. Whether one user or two user open, the screen goes to the black command line saying: the system is now going to shut down...but it doesn't, it hangs there. But surprise, if you go with cntrl+alt+F2 on tty2 ..... the system shuts down normally. Sometimes you need also to go cntrl+alt+F2 and thereafter cntrl+alt+F7. And then it shuts down. So the TTY issue does hinder multi-user wayland-Plasma sessions and influences the shutdown. I can reproduce this every time reliably on a ASUS VIVO notebook with system installed on encrypted LVM. When using X-server, this behavior is absent.
I am prone to closing this, because, for what I have read, it is the new behavior of SDDM after "refactoring". So, the first available tty is used which, on a system with e.g. two users does as follows: opens user 1 = tty2 (as tty1 is taken by default). opens user 2 = tty3, unless(!) some event did cause a logging on tty3, then it jumps and for what every reason directly to tty7 (here probably no change was done, just a guess). With me it wanders in that way every day btw also in X not only wayland, mainly because if plasma crashes silently (while idling), then this happens. I do not think that there is anything "buggy", but I am afraid that this is just the logical normal behavior, after all it would be a minor bug because..after this there are only two places were to search empirically, tty 3 and tty5. And if one chooses to go via the applet to change user it works, whatever tty was magically choosen. For what is the shutdown, I am no sure yet why this happens. I am still looking after it. Is there a log were I could look? I have two special suspects (one is mdadm trying to do scrub in background and the other the nitrokey2 app, especially if a nitrokey is still inserted in the usb hub. But that is just a guess up to now (so the shutdown would be an issue of another problem).