https://bugs.kde.org/show_bug.cgi?id=459341
--- Comment #1 from Sławek <sla...@kaplonski.pl> --- I just found out that problem is fixed when I downgraded libs: gpgme-1.17.0-4.fc36.x86_64 to gpgme-1.15.1-6.fc36.x86_64 gpgme-devel-1.17.0-4.fc36.x86_64 to gpgme-devel-1.15.1-6.fc36.x86_64 gpgmepp-1.17.0-4.fc36.x86_64 to gpgmepp-1.15.1-6.fc36.x86_64 gpgmepp-devel-1.17.0-4.fc36.x86_64 to qgpgme-devel-1.15.1-6.fc36.x86_64 python3-gpg-1.17.0-4.fc36.x86_64 to python3-gpg-1.15.1-6.fc36.x86_64 qgpgme-1.17.0-4.fc36.x86_64 to qgpgme-1.15.1-6.fc36.x86_64 gpgmepp-devel-1.17.0-4.fc36.x86_64 to gpgmepp-devel-1.15.1-6.fc36.x86_64 So bug is probably in one of those packages in 1.17 version -- You are receiving this mail because: You are watching all bug changes.
