https://bugs.kde.org/show_bug.cgi?id=493145
Iyán Méndez Veiga <m...@iyanmv.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |REPORTED
--- Comment #3 from Iyán Méndez Veiga <m...@iyanmv.com> ---
Filtering the logs with cat logs.txt | grep kscreenlocker I get these lines:
Sep 23 20:03:38 bespin kscreenlocker_greet[97568]: qt.qpa.wayland: Creating a
fake screen in order for Qt not to crash
Sep 23 20:03:38 bespin kscreenlocker_greet[97568]: qt.gui.imageio: libpng
warning: iCCP: known incorrect sRGB profile
Sep 23 20:03:43 bespin kscreenlocker_greet[97568]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128:
TypeError: Property 'startAuthenticating' of object TypeError: Type error is
not a function
Sep 23 20:03:53 bespin kscreenlocker_greet[97568]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128:
TypeError: Property 'startAuthenticating' of object TypeError: Type error is
not a function
Sep 23 20:04:02 bespin kscreenlocker_greet[97568]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128:
TypeError: Property 'startAuthenticating' of object TypeError: Type error is
not a function
Sep 23 20:04:06 bespin kernel: kscreenlocker_g[97568]: segfault at 79c30c360608
ip 000079c325db4ec0 sp 00007fffd9e56eb8 error 4 in
libQt6Qml.so.6.8.0[1b4ec0,79c325ca7000+3d8000] likely on CPU 6 (core 20, socket
0)
Sep 23 20:04:06 bespin kscreenlocker_greet[98239]: The cached device pixel
ratio value was stale on window update. Please file a QTBUG which explains how
to reproduce.
Sep 23 20:04:06 bespin kscreenlocker_greet[98239]: qt.gui.imageio: libpng
warning: iCCP: known incorrect sRGB profile
Sep 23 20:04:08 bespin kscreenlocker_greet[98239]: pam_systemd_home(kde:auth):
New sd-bus connection (system-bus-pam-systemd-home-98239) opened.
Sep 23 20:04:38 bespin kscreenlocker_greet[98239]: Failed to write to the pipe:
Bad file descriptor.
I don't know if it helps...
--
You are receiving this mail because:
You are watching all bug changes.
