Page 1 of 2 12 LastLast
Results 1 to 10 of 16

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

  1. #1

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

    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. #2
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    13,295
    Blog Entries
    2

    Default Re: "the screensaver is broken and unlocking is no longer possible"

    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
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  3. #3

    Default Re: "the screensaver is broken and unlocking is no longer possible"

    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)
    http://i.imgur.com/ql6RhlU.jpg

    > /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. #4

    Default Re: "the screensaver is broken and unlocking is no longer possible"

    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. #5

    Default Re: "the screensaver is broken and unlocking is no longer possible"

    Quote Originally Posted by xorbe View Post
    Okay, seems as though latest TW KDE does not get along with nvidia driver 384.69, reverting to 381.22 worked.
    How to revert: the only version in TW is 384.69?

  6. #6

    Default Re: "the screensaver is broken and unlocking is no longer possible"

    Quote Originally Posted by akontsevich View Post
    How to revert: the only version in TW is 384.69?
    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. #7

    Default Re: "the screensaver is broken and unlocking is no longer possible"

    Quote Originally Posted by xorbe View Post
    Okay, seems as though latest TW KDE does not get along with nvidia driver 384.69, reverting to 381.22 worked.
    It's a bug in the latest nvidia driver, and not at all specific to TW or KDE.

    https://blog.martin-graesslin.com/bl...-with-qtquick/
    https://devtalk.nvidia.com/default/t...ware-on-linux/

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

  8. #8

    Default Re: "the screensaver is broken and unlocking is no longer possible"

    Quote Originally Posted by wolfi323 View Post
    It's a bug in the latest nvidia driver, and not at all specific to TW or KDE.

    https://blog.martin-graesslin.com/bl...-with-qtquick/
    https://devtalk.nvidia.com/default/t...ware-on-linux/

    A downgrade is only possible by installing the driver "the hard way" though, there are no previous RPM packages in the repo.
    Could this nvidia bug cause problems with plymouth?
    https://forums.opensuse.org/showthre...ot-disappeared
    https://bugzilla.opensuse.org/show_bug.cgi?id=1002875

  9. #9

    Default Re: "the screensaver is broken and unlocking is no longer possible"

    Quote Originally Posted by akontsevich View Post
    Could this nvidia bug cause problems with plymouth?
    Unlikely.
    plymouth doesn't use QtQuick or OpenGL (that crash is in nvidia's OpenGL code).

  10. #10

    Default Re: "the screensaver is broken and unlocking is no longer possible"


Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •