Bug 505333 - kwatchgnupg doesn't remove log socket from gpg.conf when exiting
Summary: kwatchgnupg doesn't remove log socket from gpg.conf when exiting
Status: REPORTED
Alias: None
Product: kleopatra
Classification: Applications
Component: general (other bugs)
Version First Reported In: 4.0.0.241203
Platform: Debian unstable Linux
: NOR minor
Target Milestone: ---
Assignee: Ingo Klöcker
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-06-08 08:19 UTC by Marco
Modified: 2025-06-08 08:19 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Marco 2025-06-08 08:19:20 UTC 
SUMMARY

Kwatchgnupg adds 2 lines to ~/.gnupg/gpg.conf when starting up:

debug-level basic
log-file socket:///home/m/.gnupg/log-socket

It doesn't remove them when exiting.
This results in error messages by gpg if the socket doesn't exist (after the exist of Kleopatra/kwatchgpg).

OBSERVED RESULT

m@ryz:~$ gpg --decrypt
can't connect to 'socket:///home/m/.gnupg/log-socket': Verbindungsaufbau abgelehnt




EXPECTED RESULT

Kleopatra/kwatchgnupg should remove those lines after exiting if it initially added them.

SOFTWARE/OS VERSIONS

Kleopatra: 4.0.0.241203 (24.12.3)
KDE Frameworks: 6.13.0
Qt: 6.8.2 wird verwendet und gebaut wurde mit 6.8.2
Debian GNU/Linux 13 (trixie) (Xcb)
Build ABI: x86_64-little_endian-lp64
Kernel: linux 6.12.30-amd64