Arch Linux

0ryX

Member

Registered: 2024-08-10

Posts: 2

gnupg cannot connect to SQL

I have a fresh install of Arch and when I try to generate a keypair I get the following errors

Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? O
    We need to generate a lot of random bytes. It is a good idea to perform
    some other action (type on the keyboard, move the mouse, utilize the
    disks) during the prime generation; this gives the random number
    generator a better chance to gain enough entropy.
    gpg: Note: database_open 134217901 waiting for lock (held by 12266) ...
    gpg: Note: database_open 134217901 waiting for lock (held by 12266) ...
    gpg: Note: database_open 134217901 waiting for lock (held by 12266) ...
    gpg: Note: database_open 134217901 waiting for lock (held by 12266) ...
    gpg: Note: database_open 134217901 waiting for lock (held by 12266) ...
    gpg: keydb_search failed: Connection timed out
    We need to generate a lot of random bytes. It is a good idea to perform
    some other action (type on the keyboard, move the mouse, utilize the
    disks) during the prime generation; this gives the random number
    generator a better chance to gain enough entropy.
    gpg: Note: database_open 134217901 waiting for lock (held by 12266) ...
    gpg: Note: database_open 134217901 waiting for lock (held by 12266) ...
    gpg: Note: database_open 134217901 waiting for lock (held by 12266) ...
    gpg: Note: database_open 134217901 waiting for lock (held by 12266) ...
    gpg: Note: database_open 134217901 waiting for lock (held by 12266) ...
    gpg: keydb_search failed: Connection timed out
    gpg: error writing public keyring '[keyboxd]': SQL library used incorrectly
    Key generation failed: SQL library used incorrectly

I realized I hadn't installed any sql yet on my system so I went ahead and installed sqlite but I am still getting the same errors.
I've never set this up before and was wondering if the gpg keys that came from installing packages will be gone as well.

EDIT: Solved, I don't really know what happened but since the system was brand new I just uninstalled and reinstalled
and that fixed it. Only thing I may be missing is some gpg keys from packages I've installed but maybe they'll update when I update.
If anyone wants to explain this I would still like to know how this works and maybe what could have been the reason

Last edited by 0ryX (2024-09-25 15:32:32)

0xMetaCrypt

Member

Registered: 2021-08-29

Posts: 1

Re: gnupg cannot connect to SQL

I am having this very same issue but with keydb_search.

error: gpg failed to sign the data:
gpg: Note: database_open 134217901 waiting for lock (held by 139880) ...
gpg: Note: database_open 134217901 waiting for lock (held by 139880) ...
gpg: Note: database_open 134217901 waiting for lock (held by 139880) ...
gpg: Note: database_open 134217901 waiting for lock (held by 139880) ...
gpg: Note: database_open 134217901 waiting for lock (held by 139880) ...
gpg: keydb_search failed: Connection timed out
gpg: skipped "ABXXXXXXBA": Connection timed out

So it seems to me that this might be a fresh issue related to gnupg.

EDIT:

When trying to full-generate-key it returns this, so seemingly also an SQL issue which is peculiar.

We need to generate a lot of random bytes. It is a good idea to perform
some other action (type on the keyboard, move the mouse, utilize the
disks) during the prime generation; this gives the random number
generator a better chance to gain enough entropy.
gpg: Note: database_open 134217901 waiting for lock (held by 139880) ...
gpg: Note: database_open 134217901 waiting for lock (held by 139880) ...
gpg: Note: database_open 134217901 waiting for lock (held by 139880) ...
gpg: Note: database_open 134217901 waiting for lock (held by 139880) ...
gpg: Note: database_open 134217901 waiting for lock (held by 139880) ...
gpg: keydb_search failed: Connection timed out
gpg: error writing public keyring '[keyboxd]': SQL library used incorrectly
Key generation failed: SQL library used incorrectly

Last edited by 0xMetaCrypt (2025-02-17 21:01:04)