#asahi · 2024-02-04 13:02
j2The issue can be quite annoying, because first I thought that removing the .lock - file would fix the issue. First I tried that and kept getting `gpg: waiting for lock (held by XXXXX).` to output on loop, when calling gpg.#asahi · 2024-02-04 12:57
j2ChatGPT suggested it could be more of my distro (asahi fedora 39 w/ KDE) related, than gnupg - related :D#asahi · 2024-02-04 12:55
j2janneg: It's about gnupg. My gpg may stop working if I change my wifi. There is gnupg_spawn_keyboxd_sentinel.lock - file on my $HOME/.gnupg - folder, that contains some sort of hostname that belongs to my ISP. If the .lock - file exists and I start using my (different) home-wifi, I get `gpg: waiting for lock (held by 13162)`. Changing back to the wifi, that was used when the .lock - file was created, fixes the issue.