Am Sonntag 20 April 2025 08:51:44 schrieb aslamK: > The issue is therefore not with `gnu --verify`, but with the connection > to `log-socket`: > === > can't connect to ' > socket:///home/user/.gnupg/log-socket > ': Connection refused > ===
Check your configuration, e.g. ~/.gnupg/gpg.conf mine has an inactive #debug-level basic #log-file socket:///home/ber/.gnupg/log-socket so I guess that you do have a `log-file` setting in your configuration somewhere or > My config hasn't changed but I did upgrade my OS > (Ubuntu 20.04.2) Ubuntu has changed the defaults. Try setting log-file to a file to see if this changes the connection problem. (Similiar options exist for gpg-agent.conf and dirmngr, make sure to restart those daemons if you change their settings to see an effect.) Bernhard -- https://intevation.de/~bernhard +49 541 33 508 3-3 Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998 Geschäftsführer: Frank Koormann, Bernhard Reiter
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Gnupg-users mailing list [email protected] https://lists.gnupg.org/mailman/listinfo/gnupg-users
