| Summary: | kwallet GPG error was No secret key | ||
|---|---|---|---|
| Product: | [Applications] kwalletmanager | Reporter: | Andres <kdebugs> |
| Component: | general | Assignee: | Valentin Rusu <valir> |
| Status: | REPORTED --- | ||
| Severity: | major | CC: | erik, marc.schlegel, qnnp |
| Priority: | NOR | ||
| Version First Reported In: | 24.05.2 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=475389 | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
picture of the error
Journal from the boot with the error |
||
Created attachment 171846 [details]
Journal from the boot with the error
I can confirm this behaviour. I've seen this a couple of weeks ago, but after a reboot the issue was gone. As of today on Suse Tumbleweed Snapshot 13.09.2024, I cannot open my Wallet. Looking into Kleopatra, there is no key. So I backup the key from my other machine and imported it again and after a successful import Kleopatra still shows NO certificates/keys. There seems to be something completely off with the backend. If I can provide more information, please let me know how. One more observation. When I try to create a new key using Kleopatra I receive the error "SQL library used wrong" during (or after) the curve generation. Running "gpg -k" showed that a lock is held by some process. After killing this one (forgot to check which one it was) KWallet started working again. After a reboot Kleopatra also showed all keys again. Maybe the error-handling should be improved to tell the user that something is blocking access. (In reply to Marc from comment #4) > Running "gpg -k" showed that a lock is held by some process. After killing > this one (forgot to check which one it was) KWallet started working again. > After a reboot Kleopatra also showed all keys again. > > Maybe the error-handling should be improved to tell the user that something > is blocking access. It happened again today. The process blocking is gvfsd-fuse. *** Bug 487712 has been marked as a duplicate of this bug. *** happened to me recently with the process keyboxd |
Created attachment 171845 [details] picture of the error SUMMARY kwallet GPG error was No secret key STEPS TO REPRODUCE 1. setup a wallet password as requested in the first time setup (at least on bazzite) 2. reboot pc 3. Check if asked for a password on next login.(sometimes it does and sometimes it doesn't when it) 4. if it does not ask for a password try to open an app that depends on the wallet 5. See error OBSERVED RESULT no password prompt on some logins followed by kwallet GPG error was No secret key EXPECTED RESULT password prompt shows on all logins and no kwallet GPG error was No secret key SOFTWARE/OS VERSIONS Operating System: Bazzite 40 KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.9.8-204.fsync.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6700 XT ADDITIONAL INFORMATION