Bug 356339 - Kleopatra fails to verify signed file (No data. Unknown error)
Summary: Kleopatra fails to verify signed file (No data. Unknown error)
Status: RESOLVED WORKSFORME
Alias: None
Product: kleopatra
Classification: Applications
Component: general (show other bugs)
Version: 2.2.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Andre Heinecke
URL: https://bugzilla.suse.com/show_bug.cg...
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-06 17:27 UTC by tosiara
Modified: 2022-12-10 05:13 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot (40.79 KB, image/jpeg)
2017-11-29 16:48 UTC, Ahad
Details

Note You need to log in before you can comment on or make changes to this bug.
Description tosiara 2015-12-06 17:27:53 UTC
Kleopatra fails to verify signature while gpg does without any issue. The error is "Decryption failed: No data". In the details: "Input error: Unknown error"

Reproducible: Always

Steps to Reproduce:
1. sign a test file using gpg (gpg --sign test.txt), this creates test.txt.gpg file
2. verify signature using gpg (gpg --verify test.txt.gpg, "Good signature"
3. go to Kleopatra, File->Decrypt/Verify, select test.txt.gpg file and press "Decrypt/Verify"
4. Error

Actual Results:  
In gpg log (Tools->GnuPG Log Viewer) there is the same output as gpg - "Good signature". But for some reason Kleopatra fails

Expected Results:  
Kleopatra should verify signature as it is valid
Comment 1 Ahad 2017-11-29 16:48:35 UTC
Created attachment 109121 [details]
Screenshot
Comment 2 Ahad 2017-11-29 16:53:34 UTC
Kleopatra notification window keeps opening and stops user from performing any other task. Have to wait for it to finish and opens 100s of notifications window. Sometimes I have input password several times. Some return error.
If I restart outlook, have to do it all over again
Comment 3 Justin Zobel 2022-11-10 22:32:40 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Bug Janitor Service 2022-11-25 05:16:06 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2022-12-10 05:13:24 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!