| View previous topic :: View next topic |
| Author |
Message |
mkyral
Apprentice
Joined: 06 May 2007
Posts: 186
Location: Czech Republic
|
 Posted: Mon Jun 21, 2021 9:16 am Post subject: kde-plasma/kscreenlocker:5.22 - screen locker broken |
 |
|
In current plasma (5.22.1) I'm not able to lock screen. It shows message that screen locker is broken and I have switch into terminal and unlock session via command.
It seems to be caused by dev-qt/qtvirtualkeyboard. But I have no idea how to fix it. I've recompiled both packages, but nothing helped 
| Code: |
$ /usr/lib64/libexec/kscreenlocker_greet --testing
Locked at 1624266226
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
qrc:/QtQuick/VirtualKeyboard/content/components/Keyboard.qml:807:9: QML QQuickItem: Binding loop detected for property "width"
ASSERT: "!this->inputPanel" in file /var/tmp/portage/dev-qt/qtvirtualkeyboard-5.15.2/work/qtvirtualkeyboard-everywhere-src-5.15.2/src/virtualkeyboard/qvirtualkeyboardinputcontext_p.cpp, line 221
Neúspěšně ukončen (SIGABRT)
|
| Code: |
$ eix screenlock
[I] kde-plasma/kscreenlocker
Available versions: (5) 5.21.5^t (~)5.22.1^t **5.22.49.9999*l^t[1] **9999*l^t[1]
{debug +pam test}
Installed versions: 5.22.1(5)^t(11:00:02 21.6.2021)(pam -debug -test)
Homepage: https://kde.org/plasma-desktop
Description: Library and components for secure lock screen architecture
[1] "kde" /var/lib/layman/kde
$ eix qtvirtualkeyboard
[I] dev-qt/qtvirtualkeyboard
Available versions: (5) 5.15.2(5/5.15)^t
{+X debug handwriting +spell test}
Installed versions: 5.15.2(5/5.15)^t(19:17:46 12.1.2021)(X debug spell -handwriting -test)
Homepage: https://www.qt.io/
Description: Customizable input framework and virtual keyboard for Qt
|
|
|
| Back to top |
|
 |
shaumux
Veteran
Joined: 13 May 2005
Posts: 1013
Location: Hamburg
|
| Posted: Fri Jun 25, 2021 6:25 am Post subject: |
|
|
| Having the same issue as well, only way to unlock is to use loginctl from the terminal |
|
| Back to top |
|
|
malc
n00b
Joined: 24 Mar 2016
Posts: 4
|
| Posted: Sat Jul 17, 2021 9:43 am Post subject: |
|
|
| Same symptom here, slightly different output - but - I was able to fix the issue by re-installing sys-libs/pam (which re-merged with the berkdb flag flipped to off - I guess I didn't do a --newuse in a while...) - I wonder if there is some linkage, or if it helps you. |
|
| Back to top |
|
|
dfaure
n00b
Joined: 20 Jan 2025
Posts: 1
|
|
| Back to top |
|
|
|
Desktop Environments
