`gpg --verify` does not report whether verification succeeded or failed.

[aslamK]

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