I have a variant on what seems to be a recurring issue. I use two KDE sessions, with one user on F7 and a different user on F8. For user 1 I have set numlock on. However then the session for user two on F8 always starts with numlock off, despite setting the KDE setting to on, and the keyboard setting in YAST to on. Does anyone know how I can start multiple graphical sessions with all the numlocks stating “on”?
AFAIK, this is a SSDM issue.
BTW, some of us are experiencing a “usually Num-Lock indicated as being off” issue when we login to a KDE Plasma 5 session.
Can’t remember if there are KDE KF5 and/or SDDM Bug reports raised against these issues.
Looking at the process tree on this system, the parent process of “sddm” is “systemd” and there’re 2 child processes of “sddm”: “X” and “sddm-helper”.
My “startkde” process is a child of “sddm-helper”.
My “kdeinit5” process is a child of “systemd” and my “ksmserver” process is a child of “kdeinit5”.
If I start a new, parallel, user session, the “sddm” process starts 2 new child processes: “X” and “sddm-helper” – both user “root”.
The new “sddm-helper” process has a new child “startkde” process for the “new” parallel (Test) user session.
There’s also a new “kdeinit5” process for the “new” parallel (Test) user session with a new “ksmserver” process for that user.
And, I’m noticing that, since the parallel session has been started, the “Num-Lock” lamp on the keyboard repeatedly “turns off” – after I’ve turned it on again …
So, the 64-dollar question: who, or what, is managing the switching between the two KDE Session Managers?