Bug 1217853 - kscreenlocker is broken on wayland with nvidia drivers
Summary: kscreenlocker is broken on wayland with nvidia drivers
Status: NEW
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: KDE Workspace (Plasma) (show other bugs)
Version: Current
Hardware: x86-64 openSUSE Tumbleweed
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: E-Mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-12-06 13:39 UTC by Yan Horobtsov
Modified: 2024-03-19 08:42 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yan Horobtsov 2023-12-06 13:39:13 UTC
I use openSUSE Tumbleweed, the problem I'm having is that every time my PC wakes up from sleep or hibernation it shows me a broken screen locked.
"The screen locker is broken and unlocking is not possible anymore..."

If I press Super + L being in the KDE wayland session, it does show me kscreenlock without breaking. Only occurs after waking up.

I use proprietary nvidia drivers and wayland.

Reproducible: Always
Steps to Reproduce:
1. Launch a wayland session
2. Go into suspend state
3. Wake it up.

Here's the journalctl output of the kscreenlocker:
Dec 04 20:01:29 localhost.localdomain kscreenlocker_greet[7134]: kscreenlocker_greet: Lockscreen QML outdated, falling back to default
Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: kf.kirigami: Failed to find a Kirigami platform plugin
Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: pam_kwallet5(kde:auth): pam_kwallet5: pam_sm_authenticate
Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: pam_kwallet5(kde:auth): pam_kwallet5: we were already executed
Dec 04 20:01:33 localhost.localdomain kscreenlocker_greet[7134]: pam_kwallet5(kde:setcred): pam_kwallet5: pam_sm_setcred

Is there anything I can do to fix or debug it?
Thanks before.
Comment 1 Sebastian Turzański 2024-03-19 08:36:02 UTC
I have the same problem but I don't think it is realated to nvidia.
I got it with plasma6 update
Comment 2 ivo grimaldi 2024-03-19 08:42:53 UTC
I'm using Plasma 6 X11, and I have little less problems.
I think the problem will be resolved in the next snapshot upgrade.