87075 – gpa unable to sign keys - gpgme error

Bug 87075 - gpa unable to sign keys - gpgme error

Summary: gpa unable to sign keys - gpgme error

Status:	RESOLVED WORKSFORME

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	x86 Linux

Importance:	High normal (vote)
Assignee:	Aron Griffis (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2005-03-29 00:48 UTC by Christian Anthon
Modified:	2006-10-04 01:09 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
error log from trying to sign a key (gpgme.log,51.26 KB, text/plain) 2005-03-29 00:49 UTC, Christian Anthon	Details
View All Add an attachment (proposed patch, testcase, etc.)

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

Description Christian Anthon 2005-03-29 00:48:36 UTC

When I try to sign a key I get gpgme errors:

the gpgme library returned an unexpected error. The error was

general error. Turning on gpgme debuggin gives the attached gpgmelog.



Reproducible: Always
Steps to Reproduce:
1. right click on an unsigned key
2. choose sign key
3.

Actual Results:  
error - then nothing

Expected Results:  
Sign the key

Comment 1 Christian Anthon 2005-03-29 00:49:46 UTC

Created attachment 54744 [details]
error log from trying to sign a key

Comment 2 lotso 2005-04-09 02:45:57 UTC

I have this problem too. Downgrading gpg-me and gpa gave not success. In the end, I tried to downgrade gnupg from 1.4.1 to 1.2.6 and it worked.

What is the dependence?

gpa and gpgme is already at the latest version and there are no other masked versions.

Comment 3 Jonas MG 2005-11-08 11:25:48 UTC

I've the same bug.
I tried with gpgme-1.0.3 and gpgme-1.1.0 but nothing

And this bug is open from March!

Comment 4 Robin Johnson archtester

2006-06-27 21:14:29 UTC

Works for me guys, could you please test again with gnupg-1.4.4 and a more recent gpgme?

Comment 5 Robin Johnson archtester

2006-10-04 01:09:58 UTC

no response from user, assuming that it's solved.