https://bugzilla.suse.com/show_bug.cgi?id=1226912 Bug ID: 1226912 Summary: gnupg problem with socket connection Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs@suse.de Reporter: axel.braun@gmx.de QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- I want to verify a tarball using gnupg: docb@X1E:~/buildservice/Application:ERP:GNUHealth:Factory/mygnuhealth> gpg --default-key mygnuhealth.keyring --verify mygnuhealth-2.2.0.tar.gz.sig can't connect to 'socket:///home/docb/.gnupg/log-socket': No such file or directory The error message does not change if I create this file, I can work around it with the option --log-file=~/gnupg.log (even if it does not create a log, but thats probably a different story. I found https://forum.gnupg.org/t/problem-with-socket-connection-refused/4669 dealing with this problem, however it does not offer a solution -- You are receiving this mail because: You are on the CC list for the bug.