No such process. I followed Adam Mizerski's idea but, since this is a new system, just deleted ~/.gnupg . Everything works fine now! On Thu, Jul 25, 2024 at 10:34 AM Carl Hartung <opensuse@cehartung.com> wrote:
On Thu, 25 Jul 2024 09:59:58 +0100 lst7cqtfws--- via openSUSE Users wrote:
My GPG is throwing errors. Any idea what's going on? "SQL library used incorrectly"
Shall I open a bug report against gpg?
$ gpg --import contact%40zerotier.com.gpg gpg: Note: database_open 134217901 waiting for lock (held by 3126) ... gpg: Note: database_open 134217901 waiting for lock (held by 3126) ... gpg: Note: database_open 134217901 waiting for lock (held by 3126) ... gpg: Note: database_open 134217901 waiting for lock (held by 3126) ... gpg: Note: database_open 134217901 waiting for lock (held by 3126) ... gpg: keydb_get_keyblock failed: Value not found gpg: error writing keyring '[keyboxd]': SQL library used incorrectly gpg: error reading 'contact%40zerotier.com.gpg': SQL library used incorrectly gpg: import from 'contact%40zerotier.com.gpg' failed: SQL library used incorrectly gpg: Total number processed: 0
Thanks!
PID 3126 belongs to what running program? (Or did the running program crash and the lock is simply stale?) First identify the program which is blocking access to the database:
ps ax | grep 3126