You are not logged in.
Using SDDM, regular Plasma desktop (Wayland), regular password login (no autologin), everything up to date.
Since about 2 weeks ago:
```
$ journalctl -b | grep kwallet
paź 06 04:41:27 berbelek sddm-helper[885]: pam_kwallet5(sddm:auth): pam_kwallet5: pam_sm_authenticate
paź 06 04:41:27 berbelek sddm-helper[885]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
paź 06 04:41:28 berbelek sddm-helper[885]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
paź 06 04:41:28 berbelek sddm-helper[945]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
paź 06 04:41:30 berbelek systemd[891]: Created slice Slice /app/dbus-:1.1-org.freedesktop.impl.portal.desktop.kwallet.
paź 06 04:41:30 berbelek systemd[891]: Started dbus-:1.1-org.freedesktop.impl.portal.desktop.kwallet@0.service.
paź 06 04:41:30 berbelek systemd[891]: Started pam_kwallet_init.
paź 06 04:41:30 berbelek pam_kwallet_init[1227]: 2025/10/06 04:41:30 socat[1227] W address is opened in read-write mode but only supports read-only
paź 06 04:41:32 berbelek systemd[891]: Created slice Slice /app/dbus-:1.1-org.kde.kwalletd6.
paź 06 04:41:32 berbelek systemd[891]: Started dbus-:1.1-org.kde.kwalletd6@0.service.
paź 06 04:41:32 berbelek kwalletd6[1550]: g_dbus_proxy_get_object_path: assertion 'G_IS_DBUS_PROXY (proxy)' failed
paź 06 04:41:33 berbelek ksecretd[1077]: Using kwallet without parent window!
paź 06 04:41:38 berbelek kwalletmanager5[1636]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
paź 06 04:41:38 berbelek kwalletmanager5[1762]: QThreadStorage: entry 7 destroyed before end of thread 0x55cd3f6e86e0
paź 06 04:41:38 berbelek kwalletmanager5[1762]: QThreadStorage: entry 4 destroyed before end of thread 0x55cd3f6e86e0
paź 06 04:41:38 berbelek kwalletmanager5[1762]: QThreadStorage: entry 3 destroyed before end of thread 0x55cd3f6e86e0
```
... and the kwallet password prompt pops up right after logging in. Cancelling it makes many programs like Google Chrome unable to start. Must effectively type my password twice upon each login.
Last edited by Donzv (2025-10-13 14:38:42)
Offline
Offline
Cancelling it makes many programs like Google Chrome unable to start. Must effectively type my password twice upon each login.
Offline
Yes, I've read the Wiki.
`pam-kwallet` has been installed the whole time.
This section refers to "window managers", i.e. standalone managers that aren't natively KWallet-aware. I assume Plasma KWallet integration systemsettings module handles this when enabled (and it WAS!), but nonetheless I added `/usr/lib/pam_kwallet_init` to autostart in systemsettings, and it didn't help.
This is a regression: an "it worked fine, then stopped" situation. Any hypotheses that boil down to me neglecting to follow the Wiki and install/enable required components are inconsistent with the feature ever having worked fine.
EDIT: I added the service file according to Automatic D-Bus activation. Didn't help either, nor was needed previously.
Last edited by Donzv (2025-10-06 15:03:21)
Offline
Have you tried to downgrade either kwallet or kwallet-pam to see which one has introduced the regression?
Does the older kwallet ship both
usr/share/dbus-1/services/org.freedesktop.impl.portal.desktop.kwallet.service
usr/share/dbus-1/services/org.kde.kwalletd6.service
?
Offline
In fact the current kwallet ships both. It also ships org.kde.secretservicecompat.service, and I suspect this is related. How can I tell whether it is in effect?
The immediately previous kwallet 6.17.0-1 does not ship /usr/share/dbus-1/services/org.freedesktop.impl.portal.desktop.kwallet.service, unlike 6.18.
Last edited by Donzv (2025-10-06 15:34:53)
Offline
'key so my best guess (assuming that 6.17 does also not have that problem) would be to update again and remove that file and see whether it's the cause so we know whether we've to take a closer look there.
Offline
'key so my best guess (assuming that 6.17 does also not have that problem) would be to update again and remove that file and see whether it's the cause so we know whether we've to take a closer look there.
Yes, deleting the file makes the immediate prompt upon login go away. However, the wallet remains closed at the beginning of the session, and the prompt appears when it is first accessed, just as before. This is considerably less annoying, but PAM->KWallet password handoff simply never worked.
Offline
The offending file comes back with each update of kwallet. Also I don't think just deleting it is the right solution, and neither is downgrading and locking the package.
Offline
Sorry, missed your last reply.
The offending file comes back with each update of kwallet.
"man pacman.conf", see "NoExtract - but no
I don't think just deleting it is the right solution
you'd rather mask the service, https://wiki.archlinux.org/title/D-Bus# … us_service
Then see https://bugs.kde.org/show_bug.cgi?id=509680 (my locally preferred resolution for anything related to the xdg-portal mess is to not have any of the xdg-portal mess installed itfp…)
Offline
Thanks, that works for me.
Offline