On Mon Dec 1, 2025 at 4:17 PM CET, Christian Hesse wrote:
Hey Ariadna,
my first guess would be issues with name resolution. I vaguely remember `gnupg` being picky there, and using a very specific mechanism.
Is is possible that your system is set up to use `systemd-resolved` (with `resolve` in `/etc/nsswitch.conf`), but with some broken configuration in `/etc/resolv.conf`? Or vice versa?
If the former is the case this may be fixed by using the systemd stub file:
ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
I use Network Manager as my DNS resolver, and I use my ISP's DNS server. /etc/resolv.conf is the one generated by Network Manager: # Generated by NetworkManager search home nameserver 192.168.1.1 There is a line in /etc/nsswitch.conf that does refer to 'resolve', but I have never ever touched this file, not even when I used systemd-resolved: hosts: mymachines resolve [!UNAVAIL=return] files myhostname dns I could try using a custom DNS with Network Manager, but before that I'd rather confirm that these files are in order. Ari -- Ariadna Vigo https://ariadnavigo.xyz gpg 0xC948873069856D6D