345283 – Error message. Can't decrypt.

Bug 345283 - Error message. Can't decrypt.

Summary: Error message. Can't decrypt.

Status:	RESOLVED WORKSFORME

Alias:	None

Product:	kleopatra
Classification:	Applications
Component:	general (show other bugs)
Version:	2.2.0
Platform:	Microsoft Windows Microsoft Windows

Importance:	NOR grave
Target Milestone:	---
Assignee:	kdepim bugs

URL:
Keywords:	investigated, triaged

Depends on:
Blocks:

Reported:	2015-03-17 21:00 UTC by wdenny
Modified:	2018-09-19 14:41 UTC (History)
CC List:	3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.

Description wdenny 2015-03-17 21:00:09 UTC

After copying the encrypted text I click decrpyt/verify and the following error message appears:

An error occurred: Kleopatra: No backend support for OpenPGP: Unsupported protocol (218103929)

Reproducible: Always

Steps to Reproduce:
1. Copy encrypted text
2. In Kleopatra click decrypt/verify
3. Error message appears

Actual Results:  
This error msg appears:

An error occurred: Kleopatra: No backend support for OpenPGP: Unsupported protocol (218103929)

Expected Results:  
Launched a window to request decryption key

Comment 1 Andre Heinecke 2015-08-05 13:59:44 UTC

This means there is a setup problem. Kleopatra can't find gpg.exe on your system.

Is your Kleopatra Version installed from gpg4win?
Have you tried reinstalling gpg4win? (Which should fix issues like incorrect PATH environment settings)

Comment 2 Andre Heinecke 2016-04-08 15:52:53 UTC

I'm changing the status to needsinfo worksforme as I can't reproduce this without deliberately breaking my installation.

Btw. one of the causes for this could be that gpgconf.exe is no longer in your PATH environment variable and not installed in a standard location.

Comment 3 Andrew Crouthamel 2018-09-19 14:41:38 UTC

This bug has had its resolution changed, but accidentally has been left in NEEDSINFO status. I am thus closing this bug and setting the status as RESOLVED to reflect the resolution change.