Bugzilla – Bug 1211444
[Build 20230516] gpg2.4: agent_genkey failed: no such file
Last modified: 2023-10-16 09:56:02 UTC
## Observation gpg: enabled compatibility flags: gpg: pinentry launched (2464 curses 1.2.1 /dev/tty6 linux - 20620/0/5 0/0 -) gpg: pinentry launched (2466 curses 1.2.1 /dev/tty6 linux - 20620/0/5 0/0 -) gpg: pinentry launched (2468 curses 1.2.1 /dev/tty6 linux - 20620/0/5 0/0 -) gpg: pinentry launched (2470 curses 1.2.1 /dev/tty6 linux - 20620/0/5 0/0 -) gpg: agent_genkey failed: No such file or directory gpg: key generation failed: No such file or directory gpg-finished-2 openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-extra@64bit_virtio-2G fails in [gpg](https://openqa.opensuse.org/tests/3295460/modules/gpg/steps/96) ## Test suite description Same as jeos, plus some more tests. ## Reproducible Fails since (at least) Build [20210824](https://openqa.opensuse.org/tests/1885703) ## Expected result Last good: [20210823](https://openqa.opensuse.org/tests/1884770) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensuse&flavor=JeOS-for-kvm-and-xen&machine=64bit_virtio-2G&test=jeos-extra&version=Tumbleweed)
Same as in bsc#1211456. This is probably fixed in the update to version 2.4.1 [0,1]. I'll submit the next version as soon as possible. [0] https://dev.gnupg.org/T6454 [1] https://dev.gnupg.org/rGd9e7488b17fdc617eec735e2c0485b69285ba511
Update to 2.4.2 submitted here: https://build.opensuse.org/request/show/1089861
Issue not fixed with the 2.4.2 update: https://openqa.opensuse.org/tests/3343750#step/gpg/96
*** Bug 1212117 has been marked as a duplicate of this bug. ***
See https://bugzilla.suse.com/show_bug.cgi?id=1211456#c6
Also the comment here. Before modifying the private files of GnuPG processes (~/.gnupg) please shut down the running daemons with a "gpgconf --kill all" In the past this worked by accident somewhat because gnupg automatically restarts its services when their sockets are deleted. But nowadays we place the sockets into /var/run/user/... (See gpgconf --list-dirs) and no longer in the home directory.
I agree that this is a regression since version 2.4.1 because the keyboxd is now enabled by default if the .gnupg directory does-not-exits/is-removed. The change was introduced here: * https://dev.gnupg.org/rGd9e7488b17fdc617eec735e2c0485b69285ba511 But, I also think the QA test should include a restart as mentioned in comment#6 and not block the 2.4.3 version update. Also, we need to carefully review how the gpg-agent is handled in various scenarios and decouple the start from the DM, see for example bsc#1164872. In the meantime, I have submitted the update to 2.4.0 where keyboxd is not enabled by default yet, here: * https://build.opensuse.org/request/show/1113434
Sune Vuorela made a PR for the two issues: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/17898
(In reply to Christophe Marin from comment #8) > Sune Vuorela made a PR for the two issues: > https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/17898 Thanks! I have submitted the update to the latest version to Factory, here: * https://build.opensuse.org/request/show/1116712
The submission to 2.4.3 https://build.opensuse.org/request/show/1116712 has been accepted and released. I'm closing the bug as fixed. Please, reopen if required.