"the screensaver is broken and unlocking is no longer possible"

English Install/Boot/Login
1

This is from updating TW today (Aug 23th). I can’t lock the screen without having to drop to a text terminal to unlock.

Triple screens, 1200x1600 + 2560x1600 + 1600x1200, nVidia 1050Ti

2

Screensavers/Screen locking is generally a function of the Desktop, not the OS.
So, you’ll need to identify the Desktop you’re using.

TSU

3

Desktop is KDE

Looks like this from other post around here, but my /tmp is not full (all of my partitions have plenty of space)

3264×1836 495 KB

> /usr/lib64/libexec/kscreenlocker_greet --testing
org.kde.kcoreaddons: Failed to establish shared memory mapping, will fallback to private memory – memory usage will increase
Locked at 1503546921
org.kde.kcoreaddons: Failed to establish shared memory mapping, will fallback to private memory – memory usage will increase
UdevQt: unable to create udev monitor connection
WARNING: Cannot find style “org.kde.desktop” - fallback: “/usr/lib64/qt5/qml/QtQuick/Controls/Styles/Base”
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
file:///usr/share/plasma/look-and-feel/org.openSUSE.desktop/contents/components/VirtualKeyboard.qml:20:1: module “QtQuick.VirtualKeyboard” is not installed
file:///usr/share/plasma/look-and-feel/org.openSUSE.desktop/contents/lockscreen/LockScreenUi.qml:98:103: Unable to assign int to QEasingCurve
file:///usr/share/plasma/look-and-feel/org.openSUSE.desktop/contents/components/VirtualKeyboard.qml:20:1: module “QtQuick.VirtualKeyboard” is not installed
file:///usr/share/plasma/look-and-feel/org.openSUSE.desktop/contents/lockscreen/LockScreenUi.qml:98:103: Unable to assign int to QEasingCurve
file:///usr/share/plasma/look-and-feel/org.openSUSE.desktop/contents/components/VirtualKeyboard.qml:20:1: module “QtQuick.VirtualKeyboard” is not installed
file:///usr/share/plasma/look-and-feel/org.openSUSE.desktop/contents/lockscreen/LockScreenUi.qml:98:103: Unable to assign int to QEasingCurve
QXcbClipboard::setMimeData: Cannot set X11 selection owner
QXcbClipboard::setMimeData: Cannot set X11 selection owner
KCrash: Application ‘kscreenlocker_greet’ crashing…
Segmentation fault (core dumped)

4

Okay, seems as though latest TW KDE does not get along with nvidia driver 384.69, reverting to 381.22 worked.

The only thing different from the above output is 6 more of the QXcbClipboard::setMimeData lines and no segmentation fault.

5

How to revert: the only version in TW is 384.69?

6

Sorry, I’ve always done the manual hard-way installation. I reboot with “3” on the end of the linuxefi line. Then build the nv kernel module + mkinitrd, then reboot.

7

It’s a bug in the latest nvidia driver, and not at all specific to TW or KDE.

A downgrade is only possible by installing the driver “the hard way” though, there are no previous RPM packages in the repo.

8

Could this nvidia bug cause problems with plymouth?
https://forums.opensuse.org/showthread.php/526739-Splash-screen-on-boot-disappeared
https://bugzilla.opensuse.org/show_bug.cgi?id=1002875

9

Unlikely.
plymouth doesn’t use QtQuick or OpenGL (that crash is in nvidia’s OpenGL code).

10

Something something nVidia Qt for the KDE screenlocker problem:
https://www.reddit.com/r/linux/comments/6wbcon/warning_nvidia_driver_38469_seems_to_be_broken/
https://blog.martin-graesslin.com/blog/2017/08/warning-nvidia-driver-384-69-seems-to-be-broken-with-qtquick/
https://devtalk.nvidia.com/default/topic/1023193/linux/384-69-broke-kde-screen-locker-possibly-other-qt-based-software-on-linux/

11

I also had the same problem with Nvidia 384.69 drivers.
Both from File .run and from Repository on Tumbleweed.

12

FYI, a workaround has been added to the kscreenlocker package that disables some security feature for nvidia users and should fix the problem.
It may still take a few days until it will be in Tumbleweed though:
https://build.opensuse.org/request/show/519866

If you need the fix urgently, it should be possible to install it from KDE:Frameworks5 for now.
https://software.opensuse.org//download.html?project=KDE%3AFrameworks5&package=kscreenlocker
(I would recommend to only download and install that one package)

13

It does not happen to me anymore, after the latest updates

14

Hm, the kscreenlocker update is not in yet.

Maybe nvidia fixed it then meanwhile?

15

I do not know what to say …
After the update last week on Thumbleweed, I did not see that screen anymore

16

TW 20170904 + nvidia 384.69 + kernel 4.12.10-3 is now working here also (wrt screenlocker). rotfl!