https://bugs.kde.org/show_bug.cgi?id=374890

Vincent PINON <vpi...@kde.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vpi...@kde.org

--- Comment #29 from Vincent PINON <vpi...@kde.org> ---
Hello,

I have 2 laptops on Debian testing (plasma 5.26.90-1, qt 5.15.8+dfsg-2), that
regularly fail to unlock after sleep (but not always, haven't identified the
exact situation yet).
Here is a journalctl extract that seems relevant (note the "kernel: traps:
kscreenlocker_g"):

21:30:03 plasmashell[1236]: qt.qpa.wayland: Wayland does not support
QWindow::requestActivate()
21:30:03 plasmashell[1236]: qt.qpa.wayland: Wayland does not support
QWindow::requestActivate()
21:30:03 plasmashell[1236]: Checking screens: available:
(QScreen(0x56222c70e3a0, name="HDMI-A-1")) redundant: QHash() fake: QSet() all:
(QScreen(0x56222a3c13e0, name="eDP-1"), QScreen(0x56222c70e3a0, name="HDMI-A->
21:30:03 plasmashell[1236]:
file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:20:
TypeError: Cannot read property 'pluginName' of null
21:30:03 plasmashell[1236]:
file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:75:
TypeError: Cannot read property 'configuration' of null
21:30:03 plasmashell[1236]:
file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:78:
TypeError: Cannot read property 'pluginName' of null
21:30:03 plasmashell[1236]:
file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:80:
TypeError: Cannot read property 'configuration' of null
21:30:03 plasmashell[1236]:
file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:81:
TypeError: Cannot read property 'configuration' of null
21:30:03 plasmashell[1236]:
file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:82:
TypeError: Cannot read property 'configuration' of null
21:30:03 plasmashell[1236]:
file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:83:
TypeError: Cannot read property 'configuration' of null
21:30:03 plasmashell[1236]:
file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:84:
TypeError: Cannot read property 'configuration' of null
21:30:03 plasmashell[1236]:
file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:16:
TypeError: Cannot read property 'configuration' of null
21:30:03 plasmashell[1236]:
file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:17:
TypeError: Cannot read property 'configuration' of null
21:30:03 plasmashell[1236]:
file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:18:
TypeError: Cannot read property 'configuration' of null
21:30:03 bluetoothd[733]: profiles/sap/server.c:sap_server_register() Sap
driver initialization failed.
21:30:03 bluetoothd[733]: sap-server: Operation not permitted (1)
21:30:03 kernel: Bluetooth: MGMT ver 1.22
21:30:03 bluetoothd[733]: Failed to set mode: Failed (0x03)
21:30:03 org_kde_powerdevil[14410]: Initializing 
"/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
21:30:03 kernel: traps: kscreenlocker_g[14218] general protection fault
ip:7fa918e8bff4 sp:7ffd482882b8 error:0 in
libQt5Qml.so.5.15.8[7fa918ca0000+2f1000]
21:30:03 org_kde_powerdevil[14416]: Initializing 
"/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
21:30:03 kded5[14411]: Initializing 
"/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
21:30:03 plasmashell[1236]:
file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/FullRepresentation.qml:133:13:
QML Loader: Possible anchor loop detected on centerIn.
21:30:03 plasmashell[14422]: Initializing 
"/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
21:30:03 kded5[14424]: Initializing 
"/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
21:30:03 plasmashell[14430]: Initializing 
"/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings/kcm_fonts.so"
21:30:03 kwin_wayland_wrapper[1111]: not a valid new object id (2), message
get_registry(n)
21:30:03 kwin_wayland_wrapper[1111]: error in client communication (pid 1111)
21:30:03 kwin_wayland_wrapper[14449]: error: received delete_id for unknown id
(43)
21:30:03 kwin_wayland_wrapper[14449]: error: received delete_id for unknown id
(47)
21:30:03 kwin_wayland_wrapper[14449]: error: received delete_id for unknown id
(44)
21:30:03 kwin_wayland_wrapper[14449]: error: received delete_id for unknown id
(45)
21:30:03 kwin_wayland_wrapper[14449]: error: received delete_id for unknown id
(39)
21:30:03 kwin_wayland_wrapper[14449]: error: received delete_id for unknown id
(53)
21:30:03 kwin_wayland_wrapper[14449]: error: received delete_id for unknown id
(38)
21:30:03 kwin_wayland_wrapper[14449]: error: received delete_id for unknown id
(41)
21:30:03 kwin_wayland_wrapper[14449]: error: received delete_id for unknown id
(19)
21:30:03 kwin_wayland_wrapper[14449]: error: received delete_id for unknown id
(18)
21:30:03 kwin_wayland_wrapper[14449]: wl_display@1: error 1: invalid arguments
for wl_display@1.get_registry
21:30:03 kwin_wayland_wrapper[14449]: The Wayland connection experienced a
fatal error: Argument invalide
21:30:03 kwin_wayland_wrapper[14449]: qt.qpa.wayland: Creating a fake screen in
order for Qt not to crash
21:30:03 kwin_wayland_wrapper[14459]: qt.qpa.wayland: Creating a fake screen in
order for Qt not to crash
21:30:03 kwin_wayland_wrapper[14459]: The Wayland connection broke. Did the
Wayland compositor die?
21:30:03 kwin_wayland_wrapper[14462]: qt.qpa.wayland: Creating a fake screen in
order for Qt not to crash
21:30:03 kwin_wayland_wrapper[14462]: The Wayland connection broke. Did the
Wayland compositor die?
21:30:04 bluetoothd[733]: Failed to set mode: Failed (0x03)
21:30:04 kded5[1197]: kf.bluezqt: PendingCall Error: "Failed"

Please let me know what kind of extra info I can give to help. I'm also waiting
for latest release to hit debian-12...

Good luck!

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to