FS#75650 - [kwallet] 5.97.0-2: kwallet unlock dialog very slow to appear and loses Chromium cookies

Attached to Project: Arch Linux
Opened by jb2170 (SelfAdjointOperator) - Friday, 19 August 2022, 02:03 GMT
Last edited by Antonio Rojas (arojas) - Wednesday, 31 August 2022, 10:25 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Antonio Rojas (arojas)
Felix Yan (felixonmars)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Normally when logging into a desktop and clicking Chromium for the first time a dialog will appear asking for a password to unlock a wallet. This used to take only a couple of seconds but now it takes a full 30 seconds plus. Chromium also loses its cookies because of this for some reason.

Downgrading to 5.96.0-1 works; it is the latest version that doesn't have this bug.

I've uploaded journalctl logs from version 96 and 97
The main line of interest seems to be the following:

Aug 18 22:47:25 WD plasmashell[1653]: [1653:1653:0818/224725.903536:ERROR:object_proxy.cc(623)] Failed to call method: org.kde.KWallet.open: object_path= /modules/kwalletd5: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Steps to reproduce:
- Log into a desktop session with KDE Plasma
- Open Chromium
- Observe the time taken and cookies lost
   96.txt (2.6 KiB)
   97.txt (3.6 KiB)
This task depends upon

Closed by  Antonio Rojas (arojas)
Wednesday, 31 August 2022, 10:25 GMT
Reason for closing:  Upstream
Additional comments about closing:  See upstream report for workarounds
Comment by Toolybird (Toolybird) - Friday, 19 August 2022, 03:17 GMT
What happens if kwallet is opened before Chromium?

New kwallet secrets api was enabled in  FS#75616 . If it's buggy then someone needs to report it upstream...
Comment by jb2170 (SelfAdjointOperator) - Friday, 19 August 2022, 23:06 GMT
I did not try opening kwallet before Chromium, I just relied on it starting as usual. I'm staying on 5.96.0-1 for the meantime
Comment by jb2170 (SelfAdjointOperator) - Monday, 22 August 2022, 00:51 GMT
A bug report has been filed upstream [here](https://bugs.kde.org/show_bug.cgi?id=458085) by bbs.archlinux.org user matafan
Comment by Antonio Rojas (arojas) - Friday, 26 August 2022, 10:29 GMT
Is this fixed with 5.97.0-3?
Comment by jb2170 (SelfAdjointOperator) - Friday, 26 August 2022, 17:47 GMT
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.
Comment by jb2170 (SelfAdjointOperator) - Friday, 26 August 2022, 17:55 GMT
It's these same two sets of lines in `journalctl --user`:

Aug 26 18:36:47 WD plasmashell[1430]: [1430:1430:0826/183647.761072:ERROR:object_proxy.cc(623)] Failed to call method: org.kde.KWallet.open: object_path= /modules/kwalletd5: org.freedesktop.>
Aug 26 18:36:47 WD plasmashell[1430]: [1430:1430:0826/183647.761117:ERROR:kwallet_dbus.cc(147)] Error contacting kwalletd5 (open)

Aug 26 18:37:12 WD plasmashell[1430]: [1430:1430:0826/183712.786551:ERROR:object_proxy.cc(623)] Failed to call method: org.kde.KWallet.close: object_path= /modules/kwalletd5: org.freedesktop>
Aug 26 18:37:12 WD plasmashell[1430]: [1430:1430:0826/183712.786595:ERROR:kwallet_dbus.cc(418)] Error contacting kwalletd5 (close)
Aug 26 18:37:12 WD gpg-agent[1535]: Failed to lookup password for key n/438CE97C82379FF2D90570307BD4D54B8F32E8B8 with secret service: Timeout was reached
Comment by Nicolas Christin (acut3) - Tuesday, 30 August 2022, 16:52 GMT
The fix for this issue is to add no-allow-external-cache to your ~/.gnupg/gpg-agent.conf file. You can either edit the file manually, or run:

echo no-allow-external-cache:0:1 | gpgconf --change-options gpg-agent

Loading...