https://bugs.kde.org/show_bug.cgi?id=436271
--- Comment #2 from David Edmundson <k...@davidedmundson.co.uk> --- It wasn't a documented feature exposed in the UI, so it's not a bug per-se. The reason it doesn't work is because ksmserver didn't read this env, the process that spawned ksmserver did - which obviously isn't the same with the systemd boot. With the systemd boot, the simplest fix would be to create a drop-in for ksmserver and override the Exec line to ksmserver --lockscreen I have also changed the ksmserver behaviour so that if you run loginctl-lock session before ksmserver starts it will still be honoured, which is a much tidier fix. -- You are receiving this mail because: You are watching all bug changes.
