kscreenlocker nvidia crash

Bug #1726376 reported by NecLimDul
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kscreenlocker (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

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

Revision history for this message
Scarlett Gately Moore (scarlettmoore) wrote :
Changed in kscreenlocker (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.