Kleopatra Insanity | Recompiled GnuPG and Kleopatra from scratch (SOLVED)

All of a sudden:

I can encrypt but I cannot sign.

I cannot delete a fake user I made.

I click the “Change Password” button and the icon outline jumps to “close”.

At first I removed Kleopatra. Then I purged it.

Then I backed up /.gnupg/ and emptied it.

Then I took a copy from one month back and tried using what was a good backup.

In the end I compiled everything and started blank and Kleopatra is still insane.

And GnuPGLogWatcher is missing as well.

Linux host 6.12.73+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.73-1 (2026-02-17) x86_64 GNU/Linux

6.12.73+deb13-amd64

Only terminal functions.

What in the world happened to Kleopatra?

UPDATE

This is getting wild. I have never saved my passphrase in kleopatra - and all of a sudden it can sign and I am missing a few tabs.

I only have four tabs under configuration.

Things I’ve run:

gpg-agent --version
gpg-agent (GnuPG) 2.5.17

gpg --version
gpg (GnuPG) 2.5.17

libgcrypt 1.12.0

gpg -vvv debug verbose

gpg --check-trustdb
gpg --update-trustdb
gpgconf --list-dirs
gpgconf --apply-defaults
gpgconf --list-components
gpgconf --check-programs
keyboxd:1:0:
dirmngr:1:0:
gpgconf --kill dirmngr
gpg-agent.conf	
pinentry-program /usr/bin/pinentry

\________________________\_
COMMENTED SECTION

gpg-connect-agent reloadagent /bye
ls /usr/bin | grep pinentry
pinentry-program /usr/bin/pinentry-tty
sudo update-alternatives --config pinentry
$ export GPG_TTY=$(tty)
$ unset DISPLAY
$ gpg-connect-agent updatestartuptty /bye
$ sudo gpg-connect-agent updatestartuptty /by
$ which pinentry
/usr/local/bin/pinentry
$ ls -al /usr/bin/pinentry\*
pinentry-program /usr/local/bin/pinentry

I got everything to work.

Backend error: gpgconf does not seem to know the entry for dirmngr/ldaptimeout
Backend error: gpgconf does not seem to know the entry for dirmngr/max-replies

removed gnupg-agent
removed scdaemon
removed libpam-poldi
removed dirmngr (which removes everything)

changed to pinentry-program /usr/bin/pinentry-qt

Death to all computers!!!

Fixed.

Hi @encrypted,

good that you’ve got the thing sorted out.

A hint for others in a similar situation:
It usually helps to first see if the operations work on the command line, calling the crypto engine more directly. The gui frontends cannot work, if the command line does not. :slight_smile:

Then adding some more diagnostic output, usually diagnoses the problem quickly.

Best Regards,
Bernhard