https://bugs.kde.org/show_bug.cgi?id=502808
--- Comment #23 from michaelk83 <[email protected]> --- (In reply to Eduard from comment #22) > Ok, because my problems with Remmina are still there (Arch Linux), I > investigated some things myself ... > Turns out that Remmina still uses kwalletd5. ... > When I downgrade to kwallet 6.13.0-1 and kwallet-pam 6.3.5-1, my problem > stops. > This is without upgrading or downgrading kwallet5, which sits at version > 5.116.0-1. It's still a dependency of multiple other packages. kwallet 6 provides both a kwalletd5 and kwalletd6 API endpoints from the same binary. But I don't know how that works if you also have a kwallet5 package installed side-by-side. If you actually have a kwalletd5 *binary* running, that's probably from that other package. AFAIK, kwallet-pam can only auto-unlock one or the other, not both. If Arch applied the latest patches, then the latest kwallet-pam should be unlocking the new kwallet. > I have to mention that Remmina does not show up in the list of connected > applications in the Kwallet Manager anyway, while Chromium does By "connected applications", do you mean the stored passwords list, or the Allow/Deny lists? If Remmina doesn't show up in the stored passwords, then that would explain why it's asking you for a password: even if the wallet is unlocked, it can't find its password there. Do also check your deny list just in case. Could it be that you have two different wallets, and Remmina's password is in the other one? When you downgrade to 6.13, do you see it in the passwords list in KWalletManager? -- You are receiving this mail because: You are watching all bug changes.
