Bug#634930: gpa: GPA unusable due to General Assuan error

2014-08-31 Thread Andreas Rönnquist 
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-rc-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

2014-01-27 Thread kardan 
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-rc-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

2014-01-07 Thread Joachim Wiedorn 
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

2012-11-30 Thread Michael Stapelberg 
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-rc-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

2012-11-24 Thread Michael Banck 
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

2012-11-10 Thread Cia Watson 
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-rc-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

2012-10-06 Thread Warren Severin 
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-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processed: Re: Bug#634930: gpa: GPA unusable due to General Assuan error

2012-10-05 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

 severity 634930 grave
Bug #634930 [gpa] gpa: GPA unusable due to General Assuan error
Severity set to 'grave' from 'normal'
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
634930: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634930
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org