You are not logged in.
After yesterday's update, KDE Wallet's startup has become very slow.
I'm not sure exactly how KDE Wallet is architectured, but what I mean is that the dialog asking you for your password is now displayed almost a minute after KDE has started, as opposed to being displayed immediately like it used to be. This is very annoying as launching Chromium before KDE Wallet's password has been provided results in all state data (cookies, local storage, etc) being lost.
I'm using GPG for my main (kdewallet) wallet. Anyone else experiencing this?
Offline
Hi, I'm having the same issue. KDE Wallet slow to launch (to show the little unlock dialog), and also I keep losing Chromium cookies. Quite annoying yeah lol.
Offline
Same problem here. I cannot start Chromium or Spotify in a reasonable time.
Downgrading kwallet to 5.96.0-1 fixes the problem.
Last edited by chmurli (2022-08-18 22:02:45)
Offline
Downgrading kwallet to 5.96.0-1 fixes the problem.
Yeah that works for me too as a temporary workaround, thanks
Offline
Please report it upstream
Offline
Thanks you everyone. I've reported the bug upstream: https://bugs.kde.org/show_bug.cgi?id=458085
Offline
Seems to have been fixed by the latest update. Looks like it was an Arch issue after all. I've self-closed KDE bug 458085.
Offline
Being fixed by the latest update doesn't mean it's an Arch issue. Quite the opposite: the latest update adds an upstream patch which is still pending review.
Offline
I've just tested version 5.97.0-3 (latest as of posting) and the issue is still present: slow startup and cookies missing. Still staying on 5.96.0-1 for now.
Offline
To fix the issue you need to do two things: update to kwallet 5.97.0-3, and disable "Secret Service DBus API" in KDE's System Settings.
From what I understand the fix in kwallet 5.97.0-3 is just a quick workaround, not the final solution to this issue which appears to be a deadlock between kwallet and gpg
Offline
I've tested version 5.97.0-4 and the bug still persists. Where is the "Secret Service DBus API" located in Settings, I can't find it?
Offline
The option is in Settings -> KDE Wallet -> Enable Secret Service DBus API (uncheck the option)
However there seem to be a better workaround: you can leave the option checked, but add "no-allow-external-cache" to your ~/.gnupg/gpg-agent.conf file.
Offline
This has been a very annoying issue ... I'm an opensuse tumbleweed user with a fully up-to-date system ... I've tried all the workarounds that I'm able to without success and only been able to solve this by using Kleopatra to reset my kdewallet password to empty ... temporary solution until all this is resolved ... hope this helps others until there is a fix ... cheers
Offline
This has been a very annoying issue ... I'm an opensuse tumbleweed user with a fully up-to-date system ... I've tried all the workarounds that I'm able to without success and only been able to solve this by using Kleopatra to reset my kdewallet password to empty ... temporary solution until all this is resolved ... hope this helps others until there is a fix ... cheers
I am afraid there won't be a fix. In fact, according to https://bugs.kde.org/show_bug.cgi?id=458085#c36 the recommended solution is the above-mentioned one, i.e., add "no-allow-external-cache" to ~/.gnupg/gpg-agent.conf while keeping Secret Service API support enabled. Works fine here for current openSUSE Tumbleweed (sorry for hijacking this thread).
Offline
Offline
I am afraid there won't be a fix. In fact, according to https://bugs.kde.org/show_bug.cgi?id=458085#c36 the recommended solution is the above-mentioned one, i.e., add "no-allow-external-cache" to ~/.gnupg/gpg-agent.conf while keeping Secret Service API support enabled. Works fine here for current openSUSE Tumbleweed (sorry for hijacking this thread).
I've again tried "no-allow-external-cache" with a passphrase ... unfortunately there is still a 50-sec wait for kdewallet to start ... not sure why this is different to your experience
Offline
DRFK wrote:I am afraid there won't be a fix. In fact, according to https://bugs.kde.org/show_bug.cgi?id=458085#c36 the recommended solution is the above-mentioned one, i.e., add "no-allow-external-cache" to ~/.gnupg/gpg-agent.conf while keeping Secret Service API support enabled. Works fine here for current openSUSE Tumbleweed (sorry for hijacking this thread).
I've again tried "no-allow-external-cache" with a passphrase ... unfortunately there is still a 50-sec wait for kdewallet to start ... not sure why this is different to your experience
Could you please leave a comment at https://bugs.kde.org/show_bug.cgi?id=458085? Thx.
Offline
Today's massive update in Tumbleweed to KDE Plasma 5.24.4 KDE Framework 5.97.0 & QT 5.15.5 seems to have remedied the issue ... I have both the secret-bus and "no-allow-external-cache" in gpg-agent.conf ... many thanks for your interest
Offline
Can we please stop the opensuse hijack.
Offline
The option is in Settings -> KDE Wallet -> Enable Secret Service DBus API (uncheck the option)
However there seem to be a better workaround: you can leave the option checked, but add "no-allow-external-cache" to your ~/.gnupg/gpg-agent.conf file.
Hi, sorry for the very late reply.
I was using kwallet 5.96.0-1 for the longest time (until today) because of the bug, using --ignore kwallet whenever -Syu-ing.
I've -Syu-ed today, including kwallet, now on version 5.99.0-1. Disabling Secret Service DBus API in KDE's settings works for me, no need to edit gpg-agent.conf.
For the record I tested 5.99.0-1 with the SS DBus API enabled and the deadlock still persists / Chromium loses its cookies (I made backups of .{config,cache}/chromium though, all good).
Thanks
Offline