| Summary: | KMail assumes KDEWallet as Secret Service provider, breaking other alternatives | ||
|---|---|---|---|
| Product: | [Applications] kmail2 | Reporter: | Odin Vex <odin.vex> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | aidalgol+kde, bernardo.marx, kapsh, kde, kos.na.bordel, max, odin.vex, radian.booth-0u, steppecat, tbondvagyok |
| Priority: | NOR | ||
| Version: | 6.2.1 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Odin Vex
2023-02-16 05:13:38 UTC
+1 +1 Same problem in the latest Version. This really breaks the usability of Kmail. As KDEWallet does not work with browsers its not a viable option for most users. Apart from that using the security service should be the right approach. I believe it happens here: https://github.com/KDE/kdepim-runtime/blob/master/resources/imap/settings.cpp Thank you! KMail does store secrets into whatever Secret Service is "listening" when setting up an account or logging in but it will not -read- from anything but KDEWallet it seems. It also doesn't wait for the Secret Service to be unlocked. I think perhaps all of Akonadi software might need updating, too. Tokodon and Neochat work correctly. I recently got an update to 6.2.1 (24.08.1-1) and things are worse. Instead of it prompting for a password every time to maintain an IMAP connection (which also got to count for SMTP) it now won't even prompt me and doesn't allow synchronizing at all. I'm unable to send or receive any mail at all. (In reply to Odin Vex from comment #7) > I recently got an update to 6.2.1 (24.08.1-1) and things are worse. Instead > of it prompting for a password every time to maintain an IMAP connection > (which also got to count for SMTP) it now won't even prompt me and doesn't > allow synchronizing at all. I'm unable to send or receive any mail at all. The specific error message is: ------------------- Resource [REDACTED] is broken. Could not read the password: user rejected wallet access ------------------- I never rejected access and KeePassXC always grants without prompting (but does show a notification to me).
> I never rejected access and KeePassXC always grants without prompting (but
> does show a notification to me).
You seems to have kwallet disabled completely, so kmail cannot access it and shows incorrect error. Keepass, playing secret service part in this case, is never reached.
Starting from 6.1.5 should be possible to enable kwallet and it's secret service support separately (restart akonadi and kmail after doing that). Doing that fixes kmail, remembering networks passwords, etc. I'd still prefer it used secret service though.
(In reply to kapsh from comment #9) > > I never rejected access and KeePassXC always grants without prompting (but > > does show a notification to me). > > You seems to have kwallet disabled completely, so kmail cannot access it and > shows incorrect error. Keepass, playing secret service part in this case, is > never reached. > Starting from 6.1.5 should be possible to enable kwallet and it's secret > service support separately (restart akonadi and kmail after doing that). > Doing that fixes kmail, remembering networks passwords, etc. I'd still > prefer it used secret service though. I did disable kwallet as I had no need for it to be running. Thank you, I've temporarily re-enabled it and can use IMAP/SMTP/POP3 with no issues. It's a tolerable work-around for now. :) (In reply to Odin Vex from comment #10) > (In reply to kapsh from comment #9) > > > I never rejected access and KeePassXC always grants without prompting (but > > > does show a notification to me). > > > > You seems to have kwallet disabled completely, so kmail cannot access it and > > shows incorrect error. Keepass, playing secret service part in this case, is > > never reached. > > Starting from 6.1.5 should be possible to enable kwallet and it's secret > > service support separately (restart akonadi and kmail after doing that). > > Doing that fixes kmail, remembering networks passwords, etc. I'd still > > prefer it used secret service though. > > I did disable kwallet as I had no need for it to be running. Thank you, I've > temporarily re-enabled it and can use IMAP/SMTP/POP3 with no issues. It's a > tolerable work-around for now. :) I've discovered a side-effect. Re-enabling kwallet breaks Vorta (Backup) since it attempts to use KDE Wallet if it's enabled instead of Secret Service. I think the answer is to stop KMail from requiring kwallet. I can maintain patches for my own Vorta repo clone until their developer(s) consider removing special handling for kwallet. |