"Can't connect to 'log-socket': Connection refused

[aslamK]

Thanks. Yes, the exit status is 0, so the verification succeeds.

I used to see output like the following, and I found that it goes to the log when I run KWatchGnuPG.
===
$ gpg --verify pdfsam_5.1.2-1_amd64.deb.asc pdfsam_5.1.2-1_amd64.deb=
gpg: enabled debug flags: memstat
gpg: Signature made Wed 26 Apr 2023 05:58:12 AM EDT
gpg:
 using RSA key 9F2499EF7ABB9050D7401BCAA3FC4B4C79E8FD49
gpg: Good signature from "Sober Lemur S.r.l.
[<info at pdfsam.org>](mailto:info at pdfsam.org)
" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:
 There is no indication that the signature belongs to the owner.
Primary key fingerprint: 9F24 99EF 7ABB 9050 D740 1BCA A3FC 4B4C 79E8 FD49
gpg: keydb: handles=3 locks=0 parse=3 get=3
gpg:
 build=0 update=0 insert=0 delete=0
gpg:
 reset=0 found=3 not=0 cache=0 not=0
gpg: kid_not_found_cache: count=0 peak=0 flushes=0
gpg: sig_cache: total=6 cached=6 good=6 bad=0
gpg: random usage: poolsize=600 mixed=0 polls=0/0 added=0/0
outmix=0 getlvl1=0/0 getlvl2=0/0
gpg: rndjent stat: collector=0x0000000000000000 calls=0 bytes=0
gpg: secmem usage: 0/65536 bytes in 0 blocks
===

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
===

My config hasn't changed but I did upgrade my OS
(Ubuntu 20.04.2). How can I get commands to output to the console?

---
aslamK

On 4/19/25 23:15, C.J. Collier wrote:

> I like to do something like:
>
> set -e
> gpg --verify
>
> Or
>
> gpg --verify || {
> echo "onoes ever buddy panik!!!"
> exit 1
> }
>
> Or
>
> gpg --verify && echo "Verified!"
>
> Or
>
> gpg --verify
> if [[ $? == 0 ]] ; then
> echo "yay!"
> else
> echo "nay!"
> fi
>
> On Sat, Apr 19, 2025, 19:16 aslamK <4slam at mythicflow.com> wrote:
>
>> This is what happened when I try to verify a signature (the same message
>> appears when I do `gpg --dearmor`):
>>
>> ```
>> $ gpg --verify syncthingtray-1.7.6-x86_64-pc-linux-gnu.tar.xz.sig
>> can't connect to 'socket:///home/user/.gnupg/log-socket': Connection refused
>> ```
>>
>> There is no other output. I am able to see the log using KWatchGnuPG
>> (via Kleopatra). With the log thus open, the `gpg --verify` command does
>> not report the error but it also does not any other output.
>>
>> I do have the public key used for the signature and it has not expired.
>>
>> Here's what the command shows with the verbose option, while the log is
>> open in KWatchGnuPG. It doesn't report whether the verification succeeded.
>>
>> ```
>> $ gpg -vv --verify syncthingtray-1.7.6-x86_64-pc-linux-gnu.tar.xz.sig
>> syncthingtray-1.7.6-x86_64-pc-linux-gnu.tar.xz
>> # off=0 ctb=89 tag=2 hlen=3 plen=307
>> :signature packet: algo 1, keyid E06FE8F53CDC6A4C
>> version 4, created 1745078192, md5len 0, sigclass 0x00
>> digest algo 8, begin of digest 4c 82
>> hashed subpkt 33 len 21 (issuer fpr v4
>> B9E36A7275FC61B464B67907E06FE8F53CDC6A4C)
>> hashed subpkt 2 len 4 (sig created 2025-04-19)
>> subpkt 16 len 8 (issuer key ID E06FE8F53CDC6A4C)
>> data: [2047 bits]
>> ```
>>
>> Shouldn't the result of `gpg --verify` be an explicit affirmative or
>> negative?
>>
>> --
>> aslamK
>>
>> _______________________________________________
>> Gnupg-users mailing list
>> Gnupg-users at gnupg.org
>> https://lists.gnupg.org/mailman/listinfo/gnupg-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20250420/e7c9ad41/attachment-0001.html>