Bug 375665 - Kleopatra: assertion "prot != UnknownProtocol" while verifying file
Summary: Kleopatra: assertion "prot != UnknownProtocol" while verifying file
Status: RESOLVED WORKSFORME
Alias: None
Product: kleopatra
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Andre Heinecke
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2017-01-28 15:57 UTC by Germano Massullo
Modified: 2018-09-28 05:15 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Germano Massullo 2017-01-28 15:57:59 UTC 
kleopatra-16.08.3

Download
https://github.com/darktable-org/darktable/releases/download/release-2.2.2/darktable-2.2.2.tar.xz

https://github.com/darktable-org/darktable/releases/download/release-2.2.2/darktable-2.2.2.tar.xz.asc

Then decrypt / verify file and select darktable-2.2.2.tar.xz

You will get error:

====
Kleopatra: assertion "prot != UnknownProtocol" failed in void Kleo::Crypto::VerifyDetachedTask::setProtocol(GpgME::Protocol) (/builddir/build/BUILD/kleopatra-16.08.3/src/crypto/decryptverifytask.cpp:1406): Internal error (218103871)
====
Comment 1 Germano Massullo 2017-01-28 16:00:36 UTC 
Downstream bugreport https://bugzilla.redhat.com/show_bug.cgi?id=1417389
Comment 2 Germano Massullo 2017-02-03 23:15:13 UTC 
it looks like you must pass darktable-2.2.2.tar.xz.asc as input file rather than darktable-2.2.2.tar.xz
Comment 3 Daniel Vrátil 2017-02-04 14:05:03 UTC 
Please provide a full backtrace of the crash.
Comment 4 Andrew Crouthamel 2018-09-28 02:35:07 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 set the bug status 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 Germano Massullo 2018-09-28 05:15:51 UTC 
Cannot reproduce on 18.04.3