Bug 1226912 - gnupg problem with socket connection
Summary: gnupg problem with socket connection
Status: NEW
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Pedro Monreal Gonzalez
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-24 15:15 UTC by Axel Braun
Modified: 2024-07-02 04:56 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Axel Braun 2024-06-24 15:15:00 UTC 
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