The reason you aren’t getting a response is probably because nobody who has read this knows the answer.
Most people use SDDM with Plasma. SDDM has historically had limitations around user switching so my guess would be that Plasma is handling it internally because of that. That is just speculation on my part though.
OK. I didn´t mean to heart anybody´s feelings. I´m sorry if I did.
Just looking for some help here.
Having said that and going back to your question:
Do you really want me to make a list of the limitations I´ve found? Here? On this thread?
Wouldn´t that be off topic?
Actually, isn´t the question off topic?
Aren´t moderators supposed to watch for that?
I will be happy to answer, but that won´t help solve the issue for which this thread existis.
The only one in GUI settings (that I know) is the commands for shutdown and reboot.
You may also create a shortcut/icon on a toolbar/panel that would run a command. With this, current Lock settings in various pages (Lock screen, SDDM=>Behavior, Battery) would be better disabled, to not interfere.
After petsam pointed me to using dm-tool, I came to this post:
…where they suggest replacing KDE screenlocker greeter executable binary file ( kscreenlocker_greet ) with an executable shell script that uses dm-tool to handle user switching and screen locking.
I modified the script to make it a smoother kscreenlocker_greet fake.
This is the result:
# kscreenlocker_greet fake
# handles screen locking and user switching by means of dm-tool
if [ $2 = '--switchuser' ]
if [ $retval == 0 ]
echo 'Locked at' $(date +%s) # same thing kscreenlocker_greet would output
# Reference for future mods
# Sample parameters passed to kscreenlocker_greet when called
# for Application Launcher > Leave > Switch user
# --immediateLock --switchuser --ksldfd 38
# for Application Launcher > Leave > Lock
# --immediateLock --ksldfd 36
Please beware I am a complete newbie and, as such, I am not system-level conscious of the repercusions this may have.
Well, I can’t follow, or you are hiding your true identity or Linux knowledge.
If you are really a newbie, I would definitely suggest against replacing system packages files, even if your custom replacements are working.
Nobody can in fact find any problem, while you are the only one who can test it practically (not in theory), unless a DM developer shows up.
I slightly see an invitation towards other users, to test your custom Franken on their own systems.
That’s bold for a newbie (as self introduced). Maybe it’s time to uncover your true identity, Linus.
There are several aspects you should gain some more knowledge on, before you contribute to sddm/lightdm development, like how Xorg server, logind/systemd works, what $DISPLAY is and more.
Keep on reading, and don’t forget to give feedback on your personal endeavour.
BTW, you should mention this topic on the new one you have opened to troubleshoot issues from this topic’s solution, or just keep everything in one place (here).
The problem is this forum complains now that the topic has a solution, which is pretty irritating. In addition, I’m getting a hint to welcome somebody to the community.
@panchuz Bienvenido al foro, es un poco dificil buscar ayuda en algun sitio de Internet algunas veces en la manera que la gente contesta, tienes que tratar de acostumbrarte. Pueden juzgarte de la manera que contestas en este topic solamente. Perdoname pero puedo escribir mejor en ingles que español aunque esto no vino por tradución.
Lightdm runs on tty1 and your users are on tty2 and maybe tty3. When you go to switch instead of dropping to lightdm you’re dropping to the others users tty. Instead of tty1 which is likely some weird interaction with lightdm and plasma.
Something like this happens with plasma Wayland when running sddm in Wayland mode without using git version.