https://bugs.kde.org/show_bug.cgi?id=436271
--- Comment #4 from Damjan Georgievski <gdam...@gmail.com> --- (In reply to David Edmundson from comment #2) > It wasn't a documented feature exposed in the UI, so it's not a bug per-se. sorry. I have no idea where I've read about it. It's somewhat prominent on the internet :D > 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. I think in both cases the variable is inherited from the parent process? I don't understand the difference. > > 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. Both fixes seem fine to me. Thanks. -- You are receiving this mail because: You are watching all bug changes.
