Kleopatra not working any more after update on Gnome / Wayland ?!?

EISENFELD · 2024-05-27 16:28:15

After the update today, Kleopatra won't start anymore. How to fix it ?
I am on Gnome / Wayland. Never had any problems with Kleopatra with Qt6 on Wayland before.

This is what I get when I want to start Kleopatra:

lennart@LENNARTz:~$ kleopatra
qt.core.qobject.connect: QObject::connect: No such signal QPlatformNativeInterface::systemTrayWindowChanged(QScreen*)
gpg.qgpgme: found no group for entry verbose of component "tpm2daemon"
gpg.qgpgme: found no group for entry quiet of component "tpm2daemon"
gpg.qgpgme: found no group for entry debug-level of component "tpm2daemon"
gpg.qgpgme: found no group for entry log-file of component "tpm2daemon"
The Wayland connection experienced a fatal error: Protokollfehler

I also installed gpgp frontent Flatpak - it doesn't start and the Appimage too.
Before the update: No Problemo ;-)

I hope someone can help me with this problem, I use Kleopatra very often.

Thanks

gattino · 2024-05-29 02:13:59

I had the exact same problem today.

[gattino@cryptux ~]$ kleopatra
qt.core.qobject.connect: QObject::connect: No such signal QPlatformNativeInterface::systemTrayWindowChanged(QScreen*)
gpg.qgpgme: found no group for entry verbose of component "tpm2daemon"
gpg.qgpgme: found no group for entry quiet of component "tpm2daemon"
gpg.qgpgme: found no group for entry debug-level of component "tpm2daemon"
gpg.qgpgme: found no group for entry log-file of component "tpm2daemon"
The Wayland connection experienced a fatal error: Errore di protocollo

I tried looking for a solution on other sites but couldn't find anything. I think the only solution is to uninstall Kleopatra and reinstall Kleopatra from Flatpak... I also tried to see if anyone in other Arch based distribution forums was talking about it or had had our problem: I couldn't find anything!

EISENFELD · 2024-05-29 06:21:54

- I tried the Flatpak versions of Kleopatra and Gpgp Frontend but they both didn't start.
- I fixed some problems with TPM and looked at all gpgp and Kleopatra config files but couldn't found any errors.
- I also "talked" with GPT4o and Claude, had long conversations with them to find a solution and the final result and advice from them was: "Ask the community..." ;-)

And the community now says what ?

EISENFELD · 2024-05-29 07:47:54

I now found out:

export QT_QPA_PLATFORM=XCB && kleopatra

works fine, but prints out the following errors on the console:

gpg.qgpgme: found no group for entry verbose of component "tpm2daemon"
gpg.qgpgme: found no group for entry quiet of component "tpm2daemon"
gpg.qgpgme: found no group for entry debug-level of component "tpm2daemon"
gpg.qgpgme: found no group for entry log-file of component "tpm2daemon"

And I have to press ctrl+c after quit kleopatra to return to the terminal prompt.

Last edited by EISENFELD (2024-05-29 07:48:58)

gattino · 2024-05-30 06:37:52

EISENFELD wrote:

works fine, but prints out the following errors on the console:

I installed kleopatra on a laptop with kde wayland to take a look at what is happening. It launches fine with the same tpm stuff in the terminal, so I don’t think that is important.

EISENFELD wrote:

And I have to press ctrl+c after quit kleopatra to return to the terminal prompt.

Kleopatra closes to the system tray. Gnome doesn’t support a system tray. I have the same "problem" with Vorta
We will need an extension for it, so all apps that utilize a system tray are broken by default on gnome...
However, I saw that when I close the application both Vorta and Kleopatra ask me if I want to close definitively or if I want to let them work in the background. If I close them definitively it does not give me the problem of the ctrl+c
And even if I close the application using the CTRL+q combination they do not give me that problem (probably because with that combination of keys the application closes definitively).

EISENFELD wrote:

export QT_QPA_PLATFORM=XCB && kleopatra

I also works with this command.
Thank you for sharing it.
I don't understand why he stopped working with Wayland and we need to running it on x11.... I hope they solve the problem maybe in a next upgrade

pavlosdec · 2024-06-07 16:27:15

I encountered the same problem with Kleopatra 24.05 not running in wayland in both ArchLinux and a fully updated Fedora system (both of them with Gnome desktop).
The same bug exists in gentoo; https://bugs.gentoo.org/933441
A bug is submitted in KDE's Bugtracking System at the 5th of June... https://bugs.kde.org/show_bug.cgi?id=488090
Let's hope it'll be fixed with an update.

Arch Linux

#1 2024-05-27 16:28:15

Kleopatra not working any more after update on Gnome / Wayland ?!?

#2 2024-05-29 02:13:59

Re: Kleopatra not working any more after update on Gnome / Wayland ?!?

#3 2024-05-29 06:21:54

Re: Kleopatra not working any more after update on Gnome / Wayland ?!?

#4 2024-05-29 07:47:54

Re: Kleopatra not working any more after update on Gnome / Wayland ?!?

#5 2024-05-30 06:37:52

Re: Kleopatra not working any more after update on Gnome / Wayland ?!?

#6 2024-06-07 16:27:15

Re: Kleopatra not working any more after update on Gnome / Wayland ?!?

Board footer