Bug 443190

Summary:	plasma-nm secrets from kwallet timeout very fast when using GPG KWallet backend
Product:	[Plasma] plasmashell	Reporter:	Till Schäfer <till2.schaefer>
Component:	Networking in general	Assignee:	Jan Grulich <jgrulich>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	nate
Priority:	NOR
Version First Reported In:	5.22.5
Target Milestone:	1.0
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	screenshot of two password dialogs

Description Till Schäfer 2021-10-01 08:53:21 UTC

When I login to plasma, kwallet asks me to open my gpg wallet in order to unlock the secrets for my wifi connection. After entering the password via pinentry-qt5, the connection is established.

However, this only works if I am very fast. After a few seconds (lets say 20 seconds or so), there seems to be a timeout that causes Networkmanager to ask for the secret itself via a separate dialog. Even if I enter the passwort to the kwallet pinentry afterwards, this dialog stays open and Networkmanager does not autoconnect to the wifi. In order to connect to the wifi, there are now two options:
1) Provide the passwort manually via the Networkmanager dialog
2) close the networkmanager dialog, got the the Networkmanager applet and click connect (which seems to re-read the credentials from the now open wallet)
Both options are cumbersome and break the normal workflow.

There are two issues here in my opinion:
A) The timeout is much to short. It is typical to turn on a computer and leave it (e.g. make a cup of tea). Thus, I guess a reasonable timeout is much longer.
B) Pinentry has a timeout itself, which is independent from the networkmanager timeout (at least on wayland here). After pinentry times out there is a dialog that asks to retry / abort the opening of a wallet. In my opinion, Networkmanager should only present its own password dialog when the opening of the wallet is canceled in pinetry. Thus, networkmanager should actually never timeout here.

Operating System: Gentoo Linux
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2
Kernel Version: 5.14.8-gentoo (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-4810MQ CPU @ 2.80GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4600

Comment 1 Till Schäfer 2021-10-01 09:36:56 UTC

Created attachment 142057 [details]
screenshot of two password dialogs

Comment 2 Till Schäfer 2021-10-01 09:40:52 UTC

I was able two reproduce the exact same behavior on x11. Thus, no wayland specific.

Comment 3 Ben Cooksley 2024-12-23 18:23:38 UTC

Bulk transfer as requested in T17796

Comment 4 Nate Graham 2025-06-12 18:21:59 UTC

Thanks for the bug report, and I'm sorry we didn't manage to get to it yet. A lot has changed since the issue was reported, in both Plasma and the networking and authentication stacks in general; can I ask you to see if it's still happening in Plasma 6.3.5 or later with Frameworks 6.14 or later? Thanks a lot!

Comment 5 Till Schäfer 2025-06-17 10:45:51 UTC

This issue seems to be limited to using the gpg backend of kwallet. I have reproduced the issue with Plasma 6.1, but after that release I have switched to the Blowfish backend with PAM kwallet unlocking. Thus, I am not able to say if this is still an issue with Plasma 6.3.

Comment 6 Nate Graham 2025-06-17 13:37:51 UTC

Thanks. It would also be interesting to know if there are any changes when using Frameworks 6.14 or later, as that release contained many many architectural changes to KWallet.

Comment 7 Bug Janitor Service 2025-07-02 03:47:21 UTC

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!

Comment 8 Bug Janitor Service 2025-07-17 03:47:31 UTC

🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.