Bug 385020

Summary:	KMail2 does not wait for unlocking of KWallet
Product:	[Applications] kmail2	Reporter:	schelm
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	CONFIRMED ---
Severity:	normal	CC:	kde-bugzilla, samjnaa, work
Priority:	NOR
Version:	5.5.2
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=339767
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description schelm 2017-09-24 17:30:52 UTC

The used system is an updated openSUSE Leap 42.3 with all the common KDE applications, no additional modifications. I have 4 mail accounts configured, the passwords are stored on the computer.
The KWallet is secured via GPG.

After the startup of the computer the auto login of Plasma 5 is triggered. KMail triggers KWallet and KWallet asks for the password. The password is rather long and it takes a moment to type it.

But after too few seconds four password prompts for the mail accounts appear on the screen. I don't know the passwords for my mail accounts, I use KWallet for that...
When I enter my password for KWallet, I can close the other password prompts. Now I can open KMail. Here I have to "start akonadi" before I can use KMail and then all my mail transports are broken (and red in the GUI). I click on "Check mail" and the mail accounts are online again.

This is what I would expect:
- KMail waits for the unlocked KWallet.
- Maybe it reports the mail transports broken after a while. But I do not want to see all these password prompts now, the KWallet password prompt is still open and it never failed in that moment... After unlocking the wallet, KMail should try to read the password again and it should restart the mail transports if possible.

Comment 1 Shriramana Sharma 2017-11-18 05:32:15 UTC

I came across this when reporting bug #387056. The solution seems to reside in https://bugs.kde.org/show_bug.cgi?id=154131#c6 talking about DBus timeout. Please check whether this is applicable to this product.

Comment 2 Justin Zobel 2022-11-10 22:33:00 UTC

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Comment 3 Bug Janitor Service 2022-11-25 05:17:52 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

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

Comment 4 Bug Janitor Service 2022-12-10 05:14:57 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

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

Comment 5 Ryan McCoskrie 2023-08-22 03:42:46 UTC

This bug is happening on my laptop in 2023, desktop is fine. Both are using Fedora.

Any hints on how I can collect relevant information?

Comment 6 sourcemaker 2023-09-03 16:21:02 UTC

I can confirm this issue with the latest updates on ArchLinux.