https://bugs.kde.org/show_bug.cgi?id=490924
Sophie Dexter <sophie.dexte...@yahoo.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |FIXED
--- Comment #5 from Sophie Dexter <sophie.dexte...@yahoo.co.uk> ---
(In reply to Fabian Vogt from comment #4)
> It would be useful if you could run
>
> QT_LOGGING_RULES=kscreenlocker_greet.debug=true
> /usr/libexec/kscreenlocker_greet --testing -platform xcb
>
> and reproduce the issue.
Hmm, running that is proving to be tricky since this only occurs immediately
after waking my system from sleep and I don't know how to do what you ask. I've
tried running from a different TTY but I am greeted with:
>> kscreenlocker_greet: Greeter is starting up.
>> qt.qpa.xcb: could not connect to display
>> qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load
>> the Qt xcb platform plugin.
>> qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though
>> it was found.
>> This application failed to start because no Qt platform plugin could be
>> initialized. Reinstalling the application may fix this problem.
>>
>> Available platform plugins are: wayland-egl, wayland, eglfs, linuxfb,
>> minimal, minimalegl, offscreen, vkkhrdisplay, vnc, xcb.
Exporting DISPLAY=0 beforehand doesn't help. Thinking perhaps this is due to
Fedora 40 being Wayland only I then tried wayland and wayland-egl instead of
xcb. For reference, this is the output from running with --testing -platform
wayland-egl (output is similar with -platform wayland option):
>> kscreenlocker_greet: Greeter is starting up.
>> qt.qpa.wayland: qtvirtualkeyboard currently is not supported at client-side,
>> use QT_IM_MODULE=qtvirtualkeyboard at compositor-side.
>> kscreenlocker_greet: [PAM worker kde-smartcard] start: successfully started
>> kscreenlocker_greet: Greeter is running in testing mode
>> kscreenlocker_greet: Testing mode enabled: true
>> kscreenlocker_greet: [PAM worker kde] start: successfully started
>> kscreenlocker_greet: [PAM worker kde-fingerprint] start: successfully started
>> kf.guiaddons: No modifierkeyinfo backend for platform "wayland-egl"
>> org.kde.plasma.keyboardindicator: Unknown key Qt::Key_CapsLock
>> kf.guiaddons: No modifierkeyinfo backend for platform "wayland-egl"
>> org.kde.plasma.keyboardindicator: Unknown key Qt::Key_CapsLock
>> kf.guiaddons: No modifierkeyinfo backend for platform "wayland-egl"
>> org.kde.plasma.keyboardindicator: Unknown key Qt::Key_CapsLock
>> Locked at 1722345401
>> kscreenlocker_greet: PamAuthenticators: starting authenticators
>> kscreenlocker_greet: PamAuthenticators: state changing from
>> PamAuthenticators::Idle to PamAuthenticators::Authenticating
>> kscreenlocker_greet: [PAM worker kde-smartcard] Authenticate: Starting
>> authentication
>> kscreenlocker_greet: [PAM worker kde] Authenticate: Starting authentication
>> kscreenlocker_greet: [PAM worker kde-smartcard] Message: Info message:
>> auth=authinfo_unavail
>> kscreenlocker_greet: [PAM worker kde-fingerprint] Authenticate: Starting
>> authentication
>> kscreenlocker_greet: [PAM worker kde-smartcard] Authenticate: Authentication
>> done, result code: 9 (Authentication service cannot retrieve authentication
>> info)
>> kscreenlocker_greet: PamAuthenticators: Availability changed for
>> non-interactive authenticator kde-smartcard true
>> kscreenlocker_greet: PamAuthenticators: Availability changed for
>> non-interactive authenticator kde-fingerprint true
>> kscreenlocker_greet: PamAuthenticators: Info message from non-interactive
>> authenticator kde-smartcard
>> kscreenlocker_greet: PamAuthenticators: Availability changed for
>> non-interactive authenticator kde-smartcard false
>> kscreenlocker_greet: PamAuthenticators: Availability changed for
>> non-interactive authenticator kde-smartcard false
>> kscreenlocker_greet: [PAM worker kde] Message: Echo-off prompt: Password:
>> kscreenlocker_greet: [PAM worker kde] Starting nested event loop to await
>> response
>> kscreenlocker_greet: PamAuthenticators: Secret prompt from interactive
>> authenticator kde
>> kscreenlocker_greet: [PAM worker kde-fingerprint] Authenticate:
>> Authentication done, result code: 9 (Authentication service cannot retrieve
>> authentication info)
>> kscreenlocker_greet: PamAuthenticators: Availability changed for
>> non-interactive authenticator kde-fingerprint false
>> kscreenlocker_greet: PamAuthenticators: Availability changed for
>> non-interactive authenticator kde-fingerprint false
>> kscreenlocker_greet: PamAuthenticators: responding to interactive
>> authenticator
>> kscreenlocker_greet: [PAM worker kde] Received response, exiting nested
>> event loop
>> kscreenlocker_greet: PamAuthenticators: Interactive authenticator kde
>> changed business
>> kscreenlocker_greet: [PAM worker kde] Authenticate: Authentication done,
>> result code: 0 (Success)
>> kscreenlocker_greet: PamAuthenticators: Interactive authenticator kde
>> changed business
>> kscreenlocker_greet: PamAuthenticators: Success from interactive
>> authenticator kde
>> Unlocked
>> Unlocked
>> Unlocked
>> Unlocked
>> Unlocked
>> Unlocked
>> Unlocked
>> Unlocked
>> Unlocked
Unfortunately though the 'kscreenlocker_greet --testing...' instance is only
visible after I've unlocked my system and my first password attempt is rejected
when actually unlocking. This is even though I run kscreenlocker --tesiting
from a different, text only, TTY after waking my system. Because of this I
haven't been able to reproduce so far with 'kscreenlocker_greet --testing...'
as I only see the broken conversation reports etc. after waking my system from
sleep, but I cannot run the test until I've unlocked - a chicken and egg
conundrum I am yet to crack...
I suspect I've missed something obvious and there is a way to run this
immediately after waking my system from sleep to test kscreenlocker but I
cannot fathom what, is there a way to simulate system sleeping and/or make the
PAM conversation fail instead?
--
You are receiving this mail because:
You are watching all bug changes.
