Hi guys,
after an update i get this message:

Code: Select all

The screen locker is broken and unlocking is not possible anymore.
In order to unlock switch to a virtual terminal (e.g. Ctrl+Alt+F2),
log in and execute the command:
loginctl unlock session c2
Afterwards switch back to the running session


How can i fix this?
I am using
Kernel: 5.13.0-35-generic x86_64 bits: 64 Desktop: KDE Plasma 5.24.3 Distro: KDE neon 20.04 5.24
Graphics: Device-1: NVIDIA driver: nvidia v: 510.47.03
Display: x11 server: X.Org 1.20.13 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa
resolution: 1920x1080~60Hz
OpenGL: renderer: NVIDIA GeForce RTX 3080/PCIe/SSE2 v: 4.6.0 NVIDIA 510.47.03
Greetings

Jonny

Just updated and got the same problem on both desktop and laptop.

Cannot find anthing obvious in journalctl.

Have tried to wipe my KDE configuration using the following (from a text console while sddm is stopped) and then started sddm afterwards: problem persists.

Code: Select all

cd ~
rm -rf .kde
rm -rf .cache/plasmashell*
rm -rf .cache/org.kde.dirmodel-qml.kcache
rm -rf .cache/kioexec/ .cache/krunner/ .cache/ksycoca5*
rm -rf .cache/krunnerbookmarkrunnerfirefoxdbfile.sqlite
rm -rf .config/plasma*
rm -rf .config/kde*
cd .local/
rm -rf kate/ kded5/ klipper/ knewstuff3/ kscreen/ konsole/ kwalletd/ ksysguard/ kmail2/ kcookiejar/ kactivitymanagerd/
cd share/
rm -rf dolphin kate kcookiejar kded5 keyrings klipper kmail2 knewstuff3 konsole kscreen ksysguard kwalletd kxmlgui5 plasma_engine_comic plasma plasma_notes org.kde.gwenview
cd ~/.config/
rm -rf akonadi* KDE kconf_updaterc baloo* dolphinrc drkonqirc gwenviewrc kmail2rc k*rc katemetainfos


I have the same issue after today's update.

I have the same problem

Same here after the update to 5.24.3

Same here after the update to 5.24.3

Same here

And i mentioned after the update xournalpp starting really slow and when the desktop appears i get this message:
"Desktop effects restarted due to reset graphics"
And at last i cant boot from older kernels anymore.

With the last update something went totally wrong

The same happens to my laptop. Not only this but the powe / session commands does'n work anymore.

I've to restore a Timeshift Snapshot.

I can confirm the issue too

Ok seems that this is the typical KDE neon bug again

They ship an update for a library (libwayland-cursor0 and libwayland-client0) but they doesn't care about the 32 bit version. At least on my system that was the reason that the wasn't updated. After updating them manually and loosing a lot of 32 bit libraries the lock screen works again

Same here, someone help? The only input i get after putting in the command is "incorrect login" and nothing else

Same here.
- The screen locker is broken
- Logout, Restart and Shutdown via UI don't work
- Some native QT5 applications (flameshot) are extremely sluggish

Creating a new user didn't help either, so it's not profile-related.

My Laptop at the office seems to work fine after the update

Update 1:
As reported by sstaeglich, "apt list --upgradable" shows three new packages...

Code: Select all

libwayland-client0/focal 1.20.0-1+20.04+focal+release+build1 amd64 [aktualisierbar von: 1.18.0-1]
libwayland-cursor0/focal 1.20.0-1+20.04+focal+release+build1 amd64 [aktualisierbar von: 1.18.0-1]
libwayland-egl1/focal 1.20.0-1+20.04+focal+release+build1 amd64 [aktualisierbar von: 1.18.0-1]


... yet none of them are updated using "pkcon update"

You have to manually install it:
sudo apt install libwayland-client0 libwayland-cursor0 libwayland-egl1
power options returns but still blank screen and no panel in my case

plasmabug wrote:You have to manually install it:
sudo apt install libwayland-client0 libwayland-cursor0 libwayland-egl1
power options returns but still blank screen and no panel in my case

Naw, man. I'd rather have them fix the borked mess and live with a non-functioning screen locker for (hopefully) a few days than spending the next few days in dependency hell or with worse issues.

There are already bug reports in the bug tracker for everything that's listed here, so maybe someone's already on the case.

https://bugs.kde.org/show_bug.cgi?id=451324
https://bugs.kde.org/show_bug.cgi?id=451326
https://bugs.kde.org/show_bug.cgi?id=451312
https://bugs.kde.org/show_bug.cgi?id=451328