https://bugs.kde.org/show_bug.cgi?id=514425
--- Comment #9 from Nik <[email protected]> --- NIX ASIDE -- > Considering this appeared suddenly with the latest NixOS upgrade > (nixpkgs/unstable), and I haven't changed anything related to kwallet/KMail > since 2023, and the wallet/KMail works fine when I boot the previous NixOS > generation, should I open a new bug for my specific case? Any suggestions for > debugging steps I should try? (I've spent hours trying to debug it with no > results.) +1 with filing against nix. in the spirit of helping - if I were you I would try to track down the dependency shift around GPG (or your algo), kwallet, what dependencies they use in general there & how the new nix install changed those. maybe your old encryption algo is no longer default or supported etc? Otherwise you might just try exporting your wallet temporarily and creating a new one / importing in your new distro. Anywho - back to the main show .. RE DELAY -- > if those "various issues" include ~1 minute delays No no 1 minute delays. Behavior was always instant .. I would just generally have issues connecting with the wallet. The "various issues" was a short way of saying that this issue surfaced in a couple unpredictable ways -- all of which have gone away with addition of pinentry-qt. Initially I would get an error (attachment in above comment) opening chromium. It would keep popping up rendering chromium unusable (chromium doesn't seem to initialize it's network stack until the wallet is clarified :/) The other weird issue I ran into was kwallet (& manager?) itself. I *think* I remember it being a little grumpy when I set the wallet up (read: potentially warnings? don't remember for sure but it didn't block wallet creation -- may be conflating with original chromium issue .. i was generally confused at that stage) But the _main issue_ I had with kwallet. It actually had a very similar error as chromium _after full reboot_. It was also having issues opening it's own wallet. Instead of getting a password dialogue (to generally unlock the wallet to the system) on login, I was getting some similar are same error as chromium. This is what sent me on my last debugging spree, getting pinentry-qt installed etc. I didn't really know what normal behavior was at the time, so apologies for the slighty fuzzy, verbose report. I wasn't a perfect observer. My main takeaway though is that after installing pinentry-qt _both_ of these issue have disappeared. I am greeted with a wallet unlock request from kwallet/manager on boot, and no applications have any issue using the wallet. -- You are receiving this mail because: You are watching all bug changes.
