Bug#634930: gpa: GPA unusable due to General Assuan error
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. -- Andreas Rönnquist gus...@gusnan.se -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634930: gpa: GPA unusable due to General Assuan error
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_INFO $ gpa # = no error According to the gpg manpage it appears safe to unset this value. GPG_AGENT_INFO Used to locate the gpg-agent. This is only honored when --use-agent is set. The value consists of 3 colon delimited fields: The first is the path to the Unix Domain Socket, the second the PID of the gpg-agent and the protocol version which should be set to 1. When starting the gpg-agent as described in its documentation, this variable is set to the correct value. The option --gpg-agent-info can be used to override it. Thanks for your work! [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634930#130 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634930: gpa: GPA unusable due to General Assuan error
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/joo/.cache/keyring-wrhM5J/gpg:0:1 But found with set command as user adjoo: GPG_AGENT_INFO=/tmp/gpg-3z7tmb/S.gpg-agent:19715:1 Then I have tested in the terminal of joo other values with success: GPG_AGENT_INFO=/tmp/gpg-KEKPrV/S.gpg-agent:338:2 GPG_AGENT_INFO=/home/joo/.cache/keyring-wrhM5J/gpg GPG_AGENT_INFO=/home/joo/.cache/keyring-wrhM5J/gpg:0:2 All this values can be used for starting gpa successfully! Why gives the first value an error, but the other values not? Especially the last value seems to be interesting? Perhaps someone know the next step of analysis? --- Have a nice day. Joachim (Germany) signature.asc Description: PGP signature
Bug#634930: gpa: GPA unusable due to General Assuan error
On Sat, 24 Nov 2012 18:53:39 +0100 Michael Banck mba...@debian.org 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() and was fixed upstream in http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpa.git;a=commitdiff;h=de5ed61012cfc76d8ef0ebff81625331d43b8b28#patch1 I think you should open a separate bugreport for that. -- Best regards, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634930: gpa: GPA unusable due to General Assuan error
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 messages as reported on Debian bug #634930
Not sure this is related, but gpa -d segfaults in libassuan for me on
a wheezy system. See the attached backtrace, maybe it helps.
Cheers,
Michael
#0 0x77797a5d in _assuan_socket (ctx=0x0,
namespace=namespace@entry=1, style=style@entry=1,
protocol=protocol@entry=0) at system.c:405
res = optimized out
_assuan_trace_context = 0x0
_assuan_trace_func = 0x7779f4ad _assuan_socket
_assuan_trace_tagname = 0x7779f0e2 ctx
_assuan_trace_tag = 0x0
#1 0x7779e8b5 in _assuan_sock_new (ctx=optimized out,
domain=domain@entry=1, type=type@entry=1, proto=proto@entry=0)
at assuan-socket.c:251
No locals.
#2 0x7779e982 in assuan_sock_new (domain=domain@entry=1,
type=type@entry=1, proto=proto@entry=0) at assuan-socket.c:535
No locals.
#3 0x0043ad8f in gpa_start_server () at server.c:1963
socket_name = 0x755920 /home/mba/.gnupg/S.uiserver
rc = optimized out
fd = optimized out
serv_addr = {sun_family = 21328,
sun_path =
u\000\000\000\000\000\304\373w\366\377\177\000\000\360\032m\000\000\000\000\000\001,
'\000' repeats 15 times, PSu, '\000' repeats 14 times\260, C, '\000'
repeats 29 times,
RXw\366\377\177\000\000\000\000\000\000\000\000\000\000\003\000\000\000\000}
serv_addr_len = 110
channel = optimized out
source_id = optimized out
#4 0x0040f34f in main (argc=1, argv=0x7fffe3f8) at gpa.c:453
err = 0x0
context = optimized out
configname = optimized out
keyservers_configname = optimized out
i = optimized out
#0 0x77797a5d in _assuan_socket (ctx=0x0,
namespace=namespace@entry=1, style=style@entry=1,
protocol=protocol@entry=0) at system.c:405
res = optimized out
_assuan_trace_context = 0x0
_assuan_trace_func = 0x7779f4ad _assuan_socket
_assuan_trace_tagname = 0x7779f0e2 ctx
_assuan_trace_tag = 0x0
#1 0x7779e8b5 in _assuan_sock_new (ctx=optimized out,
domain=domain@entry=1, type=type@entry=1, proto=proto@entry=0)
at assuan-socket.c:251
No locals.
#2 0x7779e982 in assuan_sock_new (domain=domain@entry=1,
type=type@entry=1, proto=proto@entry=0) at assuan-socket.c:535
No locals.
#3 0x0043ad8f in gpa_start_server () at server.c:1963
socket_name = 0x755920 /home/mba/.gnupg/S.uiserver
rc = optimized out
fd = optimized out
serv_addr = {sun_family = 21328,
sun_path =
u\000\000\000\000\000\304\373w\366\377\177\000\000\360\032m\000\000\000\000\000\001,
'\000' repeats 15 times, PSu, '\000' repeats 14 times\260, C, '\000'
repeats 29 times,
RXw\366\377\177\000\000\000\000\000\000\000\000\000\000\003\000\000\000\000}
serv_addr_len = 110
channel = optimized out
source_id = optimized out
#4 0x0040f34f in main (argc=1, argv=0x7fffe3f8) at gpa.c:453
err = 0x0
context = optimized out
configname = optimized out
keyservers_configname = optimized out
i = optimized out
A debugging session is active.
Inferior 1 [process 2452] will be killed.
Quit anyway? (y or n)
Bug#634930: gpa: GPA unusable due to General Assuan 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') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/3 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gpa depends on: ii gnupg2 2.0.19-1 ii gpgsm 2.0.19-1 ii libassuan0 2.0.3-1 ii libc6 2.13-35 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-02.33.12+really2.32.4-3 ii libgpg-error0 1.10-3.1 ii libgpgme11 1.2.0-1.4 ii libgtk2.0-0 2.24.10-2 ii zlib1g 1:1.2.7.dfsg-13 gpa recommends no packages. gpa suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634930: gpa: GPA unusable due to General Assuan error
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 version from the debian website (http://ftp.ca.debian.org/debian/pool/main/g/gpa/gpa_0.9.3-1_amd64.deb), and it fails with the same error. Upon finding this thread I tried launching gpa from command line with the --disable-x509 option, and the error disappears. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634930: gpa: GPA unusable due to General Assuan error
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 * gpa 0.9.3-1 from Debian experimental: same error messages as reported on Debian bug #634930 * gpa 0.9.3-1 from Debian experimental, --disable-x509: works fine I'm bumping the severity to grave, as the version currently in testing/sid looks clearly unusable or mostly so to me. Thank you for maintaining GnuPG tools in Debian! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634930: gpa: GPA unusable due to General Assuan error
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 an unexpected error. The error was: General Assuan error This is probably a bug in GPA. GPA will now try to recover from this error. 2. You do not have a private key yet. Do you want to generate one now (recommanded) or do it later? 3. GnuPG is rebuilding the trust database. This might take a few seconds. - On the terminal, I get the following message: ** Message: switched engine to `/usr/bin/gpg2' - I had to kill gpa from a terminal to close it - I installed 0.9.3-1 from experimental and I got the same behaviour. - I created a public/private key pair using the commandline, then start GPA: I still get the General Assuan error but I can click close, and then use the GPA interface. However, most actions throws General Assuan error and fail Thanks by advance for your work, Kjö -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634930: gpa: GPA unusable due to General Assuan error
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.2, GPGME 1.3.2, and GnuPG 2.0.19 (or 2.1-beta). Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634930: gpa: GPA unusable due to General Assuan error
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 UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634930: gpa: GPA unusable due to General Assuan error
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 easily. 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). NOTE: The following packages are unofficial packaging work. We have an outdated gpgme in Debian. I've built packages for the latest gpgme release. However, if you install them, you probably need to downgrade these packages after you've tested, how gpa behaves! GPGME 1.3.2 packages built for unstable are here: http://debian.wgdd.de/debian/incoming/packages/ Regards, Daniel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634930: gpa: GPA unusable due to General Assuan error
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, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634930: gpa: GPA unusable due to General Assuan error
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 subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634930: gpa: GPA unusable due to General Assuan error
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 (0.9.2-1) but this one crashes when trying to open the embedded file manager. NB: gpa didn't work either for me under Xfce since months ago. So I didn't think it was related only to Gnome 3 but more generally to gtk internal changes introduced since the move from the old 2.x. Regards, Lionel 2012/7/7 Daniel Leidert daniel.leid...@wgdd.de: Hello Lionel, Can you please check the package in experimental (gpa 0.9.2.) if your problem still exists? TIA and regards, Daniel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634930: gpa: GPA unusable due to General Assuan error
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 are stored. rm usr/share/gnupg2/com-certs.pem Instead of removing this file can you please try the option: --disable-x509 instead? 2. Remove your gnupg configuration folder. rm home/benutzer/.gnupg/ Is the second step really necessary? That's all. Should work for every version. Enjoy. It works locally without removing this file. [1] proves this too. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634930#45 Regards, Daniel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634930: gpa: GPA unusable due to General Assuan error
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. Remove your gnupg configuration folder. rm home/benutzer/.gnupg/ Is the second step really necessary? Worked for me with just the option. Greetz Bernd -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634930: gpa: GPA unusable due to General Assuan error
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 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 is no General Assuan error when starting gpa In one of the profiles where the bug is present and gnupg is already configured and working with the old version of gpa, I moved away the .gnupg directory in order to have it recreated when starting again the newer gpa. And the error was however still displayed. So this error message seems to be related to something else stored in the currently existing user profiles that I can't figure for now. If you ever have any clue... All my apologies. Lionel ___ Pkg-gnupg-maint mailing list pkg-gnupg-ma...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-gnupg-maint -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634930: gpa: GPA unusable due to General Assuan error
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 Environments, only in GNOME. I think someone in FreeBSD forums wrorte it has to do something with Seahorse. And some certificates. But I don't know for sure what it was. I'm sure it's a GNOME bug though. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634930: gpa: GPA unusable due to General Assuan error
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 work for every version. Enjoy. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634930: gpa: GPA unusable due to General Assuan error
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 on Debian, The same happens on FreeBSD 9.0-RELEASE. So it is for sure not a Debian bug or gpa bug. I am 100% sure this bug has something to do with GNOME. Because the newest gpa version works on XFCE without any problems. This bug happens with Gnome 2 and Gnome 3, On Debian Testing and Debian Sid and on FreeBSD 9.0-RELEASE. I hope the GNOME developers will do something ... gpa is unusable for over an year now. This is really a shame. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634930: gpa: GPA unusable due to General Assuan error
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 to use the newest version. The newest version is 0.9.2, which is in experimental. Can you try, if your problem still occurs? I have found out that this bug happens not only on Debian, The same happens on FreeBSD 9.0-RELEASE. So it is for sure not a Debian bug or gpa bug. I am 100% sure this bug has something to do with GNOME. Because the newest gpa version works on XFCE without any problems. This bug happens with Gnome 2 and Gnome 3, On Debian Testing and Debian Sid and on FreeBSD 9.0-RELEASE. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634930#35 ff. I've already wrote to the gpa developers (but Werner Koch is absent atm AFAIK). Regards, Daniel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634930: gpa: GPA unusable due to General Assuan error
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 is no General Assuan error when starting gpa In one of the profiles where the bug is present and gnupg is already configured and working with the old version of gpa, I moved away the .gnupg directory in order to have it recreated when starting again the newer gpa. And the error was however still displayed. So this error message seems to be related to something else stored in the currently existing user profiles that I can't figure for now. If you ever have any clue... All my apologies. Lionel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634930: gpa: GPA unusable due to General Assuan error
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 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 is no General Assuan error when starting gpa In one of the profiles where the bug is present and gnupg is already configured and working with the old version of gpa, I moved away the .gnupg directory in order to have it recreated when starting again the newer gpa. And the error was however still displayed. So this error message seems to be related to something else stored in the currently existing user profiles that I can't figure for now. If you ever have any clue... All my apologies. Lionel ___ Pkg-gnupg-maint mailing list pkg-gnupg-ma...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-gnupg-maint -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634930: gpa: GPA unusable due to General Assuan error
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 to the older version solves the problem. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-proposed-updates'), (500, 'stable'), (100, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.4-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gpa depends on: ii gnupg2 2.0.19-1 ii gpgsm 2.0.19-1 ii libassuan0 2.0.3-1 ii libc6 2.13-34 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-02.32.3-1 ii libgpg-error0 1.10-3 ii libgpgme11 1.2.0-1.4 ii libgtk2.0-0 2.24.10-1 ii zlib1g 1:1.2.7.dfsg-13 gpa recommends no packages. gpa suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634930: gpa: GPA unusable due to General Assuan error
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 the older version solves the problem. I don't have any problems running gpa on an amd64 machine on Sid. Can you please try the following (depends on how many keys you have in your keyring). Probably try this only with a newly created user account: Run gpa on this new user and import one key after another from the keyring of your usual user account to check, if one of your keys causes the issue. Regards, Daniel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634930: gpa: GPA unusable due to General Assuan error
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 (x86_64) Kernel: Linux 3.3.0-rc6+ (SMP w/6 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gpa depends on: ii gnupg2 2.0.18-2 ii gpgsm 2.0.18-2 ii libassuan0 2.0.3-1 ii libc6 2.13-27 ii libgdk-pixbuf2.0-0 2.24.1-1 ii libglib2.0-02.30.2-6 ii libgpg-error0 1.10-3 ii libgpgme11 1.2.0-1.4 ii libgtk2.0-0 2.24.10-1 ii zlib1g 1:1.2.6.dfsg-2 gpa recommends no packages. gpa suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634930: gpa: GPA unusable due to General Assuan error
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 was recently upgraded to v2, so this broke gpa. * To build properly, the config script MUST be set to assuan API v1, not v2 (should be already). Option 2: * Allow gpa to depend on libassuan-dev v2. * However, to do this, gpa MUST use the new assuan v2 API and change a few function call stubs which violate the new v2 API (using v1 API call stubs). * Then gpa should build fine using the new assuan v2 API. Cheers, -- Kristian Erik Hermansen https://profiles.google.com/kristian.hermansen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634930: gpa: GPA unusable due to General Assuan error
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 of the problem. best regards -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634930: gpa: GPA unusable due to General Assuan error
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: General Assuan error This is probably a bug in GPA GPA will now try to recover from this error I also was unable to generate keys due to the same error messages appearing every time FYI - I found the following here: http://forums.debian.net/viewtopic.php?f=6t=64515 Problem has been solved by installing older version of GPA (GNU Privacy Assistent) from Ubuntu repository (in Debian). thanks! -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.39-2-486 Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gpa depends on: ii gnupg2 2.0.17-2 GNU privacy guard - a free PGP rep ii gpgsm 2.0.17-2 GNU privacy guard - S/MIME version ii libc6 2.13-7 Embedded GNU C Library: Shared lib ii libglib2.0-02.28.6-1 The GLib library of C routines ii libgpg-error0 1.10-0.3 library for common error values an ii libgpgme11 1.2.0-1.4GPGME - GnuPG Made Easy ii libgtk2.0-0 2.24.4-3 The GTK+ graphical user interface ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime gpa recommends no packages. gpa suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
