Public bug reported: Seems there are problems with the latest sandboxing done in the kscreenlocker application. When locking the users only sees a message about using `loginctl unlock-sessions` to unlock their session. They then have to use a terminal to run that command to unlock their session.
Running `/usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet --testing` triggers a segfault. I'm using nvidia-304 for a legacy card but the upstream reports are against the latest driver: https://devtalk.nvidia.com/default/topic/1023193/384-69-broke-kde- screen-locker-possibly-other-qt-based-software-on-linux/ https://bugs.kde.org/show_bug.cgi?id=384005 ** Affects: kscreenlocker (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726376 Title: kscreenlocker nvidia crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kscreenlocker/+bug/1726376/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
