I just installed a fresh Debian unstable VM, and installing
GPA from the repositories (0.9.4-1) on this fresh system doesn't give
the error.
Fresh machine, and a newly generated key (which took forever to
generate), doesn't give any problems, neither when using --disable-x509
or without it.
-- An
Package: gpa
Version: 0.9.0-4
debian_version: 7.3
The following solution worked for me on wheezy (stable). Thanks, Joachim
Wiedorn, for the hint.
$ gpa # => "General Assuan error" + other messages as said in [1]
$ echo $GPG_AGENT_INFO
/home/user/.cache/keyring-kDmTeC/gpg:0:1
$ unset GPG_AGENT_INF
Hello!
At first: I have Debian Wheezy (amd64) installed. And I have two users:
one user (joo) cannot use gpa, but the other user (adjoo) have no problem!
So I have tried to find the reason for this difference and I have found
this:
Found with "set" command as user "joo":
GPG_AGENT_INFO=/home/jo
On Sat, 24 Nov 2012 18:53:39 +0100
Michael Banck wrote:
> Not sure this is related, but "gpa -d" segfaults in libassuan for me
> on a wheezy system. See the attached backtrace, maybe it helps.
I think this is not related.
The crash you are observing is due to a missing call to
assuan_sock_init()
Hi,
On Fri, Oct 05, 2012 at 12:01:42PM +0200, intrigeri wrote:
> Daniel Leidert wrote (08 Jul 2012 11:38:45 GMT) :
> > Instead of removing this file can you please try the option:
> > --disable-x509 instead?
>
> On my up-to-date Wheezy system:
>
> * gpa 0.9.0-2 from Debian Wheezy:
> same error
Package: gpa
Version: 0.9.3-1
Followup-For: Bug #634930
Dear Maintainer,
I have v0.9.3 of GPA and am getting this error also, so I'm adding myself to
the bug report.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental')
Arch
Just to let you know that I can confirm this bug on a Ubuntu 12.04 amd64
setup. Since gpa is not available in the Ubuntu repositories, I
downloaded the 0.9.3 sources and compiled. The result is this same
error. I removed the home-compiled version and instead installed the
0.9.3 amd64 .deb versi
severity 634930 grave
thanks
Hi,
Daniel Leidert wrote (08 Jul 2012 11:38:45 GMT) :
> Instead of removing this file can you please try the option:
> --disable-x509 instead?
On my up-to-date Wheezy system:
* gpa 0.9.0-2 from Debian Wheezy:
same error messages as reported on Debian bug #634930
*
Package: gpa
Version: 0.9.0-2
Followup-For: Bug #634930
Dear Maintainer,
Some info on the status of this bug on a fresh wheezy.
- Install wheezy with the installer beta2
- Install gpa
- Start gpa
- I get three dialogs. I can't click/close any of them
1. GPA error
The GPGME library returned
Am Freitag, den 13.07.2012, 15:30 +0200 schrieb Werner Koch:
> I tried to replicate the problem with the current stable versions of GPA
> 0.9.2 and GPGME (well, my working copy). I was not able to do that. I
> don't have a clean squeeze installation right now available thus I can't
> check 0.9.0
On Fri, 13 Jul 2012 15:30, w...@gnupg.org said:
> Lionel, would you mind to run another test with GPA 0.9.2, GPGME 1.3.2,
> and GnuPG 2.0.19 (or 2.1-beta).
Sorry, Lionel, it was meant to be sent the other Lionel.
--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
--
To UNSUBSC
Hi,
I tried to replicate the problem with the current stable versions of GPA
0.9.2 and GPGME (well, my working copy). I was not able to do that. I
don't have a clean squeeze installation right now available thus I can't
check 0.9.0 easily.
Lionel, would you mind to run another test with GPA 0.9
Should "--disable-x509" be run only with the version 0.9.2 from
experimental ? I didn't think so.
However, this option works and does solve the problem. Then deleting
~/.gnupg is not necessary.
Regards,
Lionel
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subjec
Trying to run "gpa --disable-x509" issues an error in either 0.7.x or
0.9.0 versions:
v 0.7.x: gpa: unrecognized option '--disable-x509'
v 0.9.0: option parsing failed: Option inconnue --disable-x509
Either version was purged and reinstalled multiple times.
Regards,
Lionel
--
To UNSUBSCRIBE
>> Here is my easy workaround to solve this bug.
>>
>> 1. Remove the file where the X.509 certificates are stored.
>>
>> rm usr/share/gnupg2/com-certs.pem
>
> Instead of removing this file can you please try the option:
> --disable-x509 instead?
Tested and works with 'gpa --disable-x509'
>> 2. Re
CCing gpa-dev
BCCing affected users
Am Sonntag, den 08.07.2012, 02:39 + schrieb mnmnm...@tormail.org:
> I have found that the problem is the expired X.509 certificates.
How did you find out?
> Here is my easy workaround to solve this bug.
>
> 1. Remove the file where the X.509 certificates
The problem was not solved with this experimental version :(
However the hack given above does work: I removed "com-certs.pem",
made a backup of my keys,
deleted my ~/.gnupg, reimported the keys and everything works again
with the current 0.9.0-2.
I then tested with the version from experimental
I have found that the problem is the expired X.509 certificates.
Here is my easy workaround to solve this bug.
1. Remove the file where the X.509 certificates are stored.
rm usr/share/gnupg2/com-certs.pem
2. Remove your gnupg configuration folder.
rm home/benutzer/.gnupg/
That's all. Should w
>The newest version is 0.9.2, which is in experimental. Can you try, if your
>problem still occurs?
Yes. I tried it already, It doesn't help at all. Still the same problem. I even
tried to compile it, same problem. I really tried nearly every version.
There are no problems in other Desktop Envi
Hello Lionel,
Can you please check the package in experimental (gpa 0.9.2.) if your
problem still exists?
TIA and regards, Daniel
Am Montag, den 02.07.2012, 09:27 +0200 schrieb Lionel Gamay:
> I had this error displayed in three existing profiles on this machine,
> even with no gpg key stored i
Am Freitag, den 06.07.2012, 14:36 -0400 schrieb dave...@safe-mail.net:
> I have this bug now for over an year and it is not possible to fix it.
> I tried everything. Even other OS. The only solution which helps is to
> use a very old verssion of GPA but I don't like this solution at all.
> I want t
I have this bug now for over an year and it is not possible to fix it. I tried
everything. Even other OS. The only solution which helps is to use a very old
verssion of GPA but I don't like this solution at all. I want to use the newest
version.
I have found out that this bug happens not only o
Dear gnupg/gpa developers,
There is some strange issue with gpa on a Debian users system. See
http://bugs.debian.org/634930
and the mail below. gpa has no debug switch. What do you suggest to
debug the issue?
Regards, Daniel
Am Montag, den 02.07.2012, 09:27 +0200 schrieb Lionel Gamay:
> I ha
I had this error displayed in three existing profiles on this machine,
even with no gpg key stored in one of these profiles. So I created a
fresh new profile as you suggested. The result are:
- there is not any problem with any of the reimported keys in the new profile
- in the new profile, there
Am Sonntag, den 01.07.2012, 09:18 +0200 schrieb Lionel Gamay:
> I was hoping to really have this bug solved but I upgraded from a working
> 0.7.0-1.1 old version this 0.9.0-2 and still get the "General Assuan Error"
> that was first described here.
>
> Of course, as usual, reverting once again to
Package: gpa
Version: 0.9.0-2
Followup-For: Bug #634930
Dear Maintainer,
I was hoping to really have this bug solved but I upgraded from a working
0.7.0-1.1 old version this 0.9.0-2 and still get the "General Assuan Error"
that was first described here.
Of course, as usual, reverting once again
Package: gpa
Version: 0.9.0-1.1
Followup-For: Bug #634930
What is the status of this bug? gpa is essentially useless how is the
severity only normal?
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64
I was able to compile my own version that works fine. Here is how
Debian -- or anyone else that wants to -- can fix the error. There are
two options:
Option 1:
* Debian / Ubuntu need to reintroduce gpa into the repos again, but
make gpa depend on libassuan-dev (v1 only -- not v2).
* libassuan-dev
For debugging info - I do run into this problem when running GPA on sid,
but for some reason the problem is gone on my Debian installations that
run testing - I believe the real problem is in a library that GPA uses
instead of the GPA package itself.
I hope this might help finding the real cause o
Package: gpa
Version: 0.9.0-1
Severity: normal
When started GPA gives the following sequence of errors:
GnuPG is rebuilding the trust database.
This might take a few seconds.
and
GPA Error
The GPGME library returned an unexpected error. The error was:
Ge
30 matches
Mail list logo
