You are not logged in.
I wonder if anyone else is having this issue. I am finding it consistent across several arch installations, so it does not seem to be a one-off.
The problem that I am having is that when I set a wallpaper specifically for the lock screen, what ends up happening is: if I lock the screen (e.g. using super + L) the lock screen wallpaper I have selected flashes for a split second before then reverting to the Plasma 6.8 default wallpaper. Nothing seems amiss in the ~/.config/kscreenlockerrc file. Is this an upstream bug, or do I have some odd esoteric misconfiguration?
This was not an issue in the 6.7.x releases, where I was also running a wayland session at that time as well.
Everything's all up to date, I don't have any packages pinned to old versions. I am well and truly stumped.
Edit:
This is apparently an upstream bug, fixed in latest svn, with fix expected to be included in 6.8.2
Last edited by Sicarine (Today 11:45:43)
Offline
This issue occurs because of a distinct separation between the Login Screen (handled by the Display Manager, usually SDDM) and the Lock Screen (handled by KScreenLocker) inside KDE Plasma. When you change the lock screen background, the configuration doesn't automatically propagate across all session states, causing the default wallpaper to temporarily "flash" or overwrite your choices.
To fix this completely, you need to align your preferences across three separate locations
But first Can you Bro Plz tell me
• Are you using a multi-monitor setup?
• Is this behavior happening immediately after a system reboot?
• Are you using any custom third-party SDDM themes
Offline
The display manager is not SDDM, it's PlasmaLogin. The login greeter does not misbehave. The regular desktop wallpaper does not misbehave. I am well aware that there are three separate wallpapers. I do not need them to be the same. It being multimonitor or not is irrelevant: the bug reappears across three completely different arch systems. One of them is a laptop.
Also, the lock screen's been working fine through many upgrades of plasma, all the way from 6.3.2, when I initially swapped. It is only now an issue in 6.8.0. Presumably, this means it's a new bug with the 6.8 series.
I would appreciate some advice from people though, not an AI (based on your other post history).
Offline
I did find the following errors in the journal, if this is of help
kscreenlocker_greet[2362]: Worker not ready yet, cannot authenticate.
kscreenlocker_greet[2362]: Worker not ready yet, cannot authenticate.
kscreenlocker_greet[2362]: Worker not ready yet, cannot authenticate.
kscreenlocker_greet[2362]: Worker not ready yet, cannot authenticate.
kscreenlocker_greet[2362]: Worker not ready yet, cannot authenticate.
kscreenlocker_greet[2362]: Worker not ready yet, cannot authenticate.
kscreenlocker_greet[2362]: Worker did not terminate in time, killing it.
kscreenlocker_greet[2426]: Property enabled for Qt::UserRole at QModelIndex(0,0,0x0,PAMAuthenticatorModel(0x56198f35ba10)) has no notify signal
kscreenlocker_greet[2426]: Property passwordField for Qt::ItemDataRole(259) at QModelIndex(0,0,0x0,PAMAuthenticatorModel(0x56198f35ba10)) has no notify signal
kscreenlocker_greet[2426]: Property expectingPrompt for Qt::ItemDataRole(260) at QModelIndex(0,0,0x0,PAMAuthenticatorModel(0x56198f35ba10)) has no notify signal
kscreenlocker_greet[2426]: Property showPrompt for Qt::ItemDataRole(262) at QModelIndex(0,0,0x0,PAMAuthenticatorModel(0x56198f35ba10)) has no notify signal
kscreenlocker_greet[2426]: Property iconName for Qt::ItemDataRole(258) at QModelIndex(0,0,0x0,PAMAuthenticatorModel(0x56198f35ba10)) has no notify signal
kscreenlocker_greet[2426]: Property type for Qt::ItemDataRole(257) at QModelIndex(0,0,0x0,PAMAuthenticatorModel(0x56198f35ba10)) has no notify signal
kscreenlocker_greet[2426]: Property tooltip for Qt::ItemDataRole(261) at QModelIndex(0,0,0x0,PAMAuthenticatorModel(0x56198f35ba10)) has no notify signal
kscreenlocker_greet[2426]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:286:9: QML Connections: Detected function "onPamTimeoutChanged" in Connections element. This is probably intended to be a signal handler but no signal of the target matches the name.
Offline
SOLVED. It is an upstream bug. See https://bugs.kde.org/show_bug.cgi?id=527150. Expected to be fixed in 6.8.2, which I expect to drop on 27 October, and to make its way to Arch repos a day or two after.
Offline