Your message dated Sun, 25 Nov 2007 04:21:35 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#385169: gnupg-agent: command get_passphrase failed:
Unknown system error
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: gnupg-agent
Version: 1.9.20-2
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have a problem with encrypting mails from kmail.
After looking into this
- gpg-agent is running
- GPG_AGENT_INFO is set and valid
but when I run the following command:
[EMAIL PROTECTED]:~/.gnupg$ echo "test" | gpg -ase | gpg
I got this output:
You need a passphrase to unlock the secret key for
user: "Wolfgang Aigner <[EMAIL PROTECTED]>"
2048-bit RSA key, ID 1C9FF77B, created 2004-08-23
gpg-agent[4345]: handler 0x10057828 for fd 0 started
gpg-agent[4345.0x10057e70] DBG: -> OK Pleased to meet you
gpg-agent[4345.0x10057e70] DBG: <- OPTION display=:0
gpg-agent[4345.0x10057e70] DBG: -> OK
gpg-agent[4345.0x10057e70] DBG: <- OPTION ttyname=/dev/tty
gpg-agent[4345.0x10057e70] DBG: -> OK
gpg-agent[4345.0x10057e70] DBG: <- OPTION ttytype=xterm
gpg-agent[4345.0x10057e70] DBG: -> OK
gpg-agent[4345.0x10057e70] DBG: <- OPTION lc-ctype=C
gpg-agent[4345.0x10057e70] DBG: -> OK
gpg-agent[4345.0x10057e70] DBG: <- OPTION lc-messages=C
gpg-agent[4345.0x10057e70] DBG: -> OK
gpg-agent[4345.0x10057e70] DBG: <- GET_PASSPHRASE
31D576EBA534E16BB073623B0C48BEB41C9FF77B X X
You+need+a+passphrase+to+unlock+the+secret+key+for+user:%0A"Wolfgang+Aigner+<[EMAIL
PROTECTED]>"%0A2048-bit+RSA+key,+ID+1C9FF77B,+created+2004-08-23%0A
gpg-agent[4345]: starting a new PIN Entry
gpg-agent[4345]: DBG: connection to PIN entry established
gpg-agent[4345]: command get_passphrase failed: Unknown system error
gpg-agent[4345.0x10057e70] DBG: -> ERR 101 server fault (ec=255.65535)
gpg: problem with the agent - disabling agent use
Enter passphrase: gpg-agent[4345.0x10057e70] DBG: <- BYE
gpg-agent[4345.0x10057e70] DBG: -> OK closing connection
gpg-agent[4345]: handler 0x10057828 for fd 0 terminated
the gpg-agent.conf is here.
###+++--- GPGConf ---+++###
ignore-cache-for-signing
debug-level basic
#log-file socket:///home/wof/.gnupg/log-socket
###+++--- GPGConf ---+++### Sa 01 Okt 2005 01:27:58 CEST
# GPGConf edited this configuration file.
# It will disable options before this marked block, but it will
I have disabled the log-file entry, because the log-socket does not
exist and get not created.
Any hints for me?
Thanks in advance
wof
- -- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: powerpc (ppc)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14.5
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages gnupg-agent depends on:
ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries
ii libgcrypt11 1.2.2-3 LGPL Crypto library - runtime libr
ii libgpg-error0 1.2-1 library for common error values an
ii libpth2 2.0.7-2 The GNU Portable Threads
ii zlib1g 1:1.2.3-13 compression library - runtime
Versions of packages gnupg-agent recommends:
ii gnupg 1.4.5-1 GNU privacy guard - a free PGP rep
ii gnupg2 1.9.20-2 GNU privacy guard - a free PGP rep
ii gpgsm 1.9.20-2 GNU privacy guard - S/MIME version
ii pinentry-qt [pinentry] 0.7.2-3 Qt-based PIN or pass-phrase entry
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iQEVAwUBRPRQeR/d62jpf6fsAQJzpAf/YIR1MF0u9iQU4flcG5u9ToAA+q3uo2Xs
2ybETaCvqFra1EoqK7vniIkqJI1ihyPtkeRyMYAY/SSM2Dxgr3GHN900yY7F6RAd
XpOCsBLxtwukel2HXsecWPOE9izYXWfvqId4XaWy/LFVW2TWlpnHSYhVyv/+yS3J
0LCjO/Lk+ARSGbWFdJq3N1YTPs6uCqUI6q96FzUXXPQmCC7lUynD3nw3/fzUS8MI
0t8Ypuo1jDxI5EHdxqcAyhMBMwurcwsQMXeqcDNIECVN76BAVgwI5qIEwLTFhcEz
8p4CsTbUjEYzNGPcpFeuRzYfGdH/lMt19ug6iXd8MLag1DaqAquR/A==
=IpD+
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Version: 2.0.6-1
* [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
> > * Wolfgang Aigner ([EMAIL PROTECTED]) wrote:
> > > > Still seeing this with version 2.0.0?
> > >
> > > It has changed a bit, but not much:
> > > - signing cancels now also with an error
> > >
> > > If you've got an idea how I can get into this or how I can help you with
> > this
> > > problem, please mail me.
> >
> > Are you still seeing this? It might be the same bug as #401843.
>
> Sorry, I can't verify it at the moment, because my ibook
> has an hardware defect. Please close this bug at the moment.
> If it is still valid I will reopen it.
>
> Thanks for your work
Alright, since I suspect it's that I'm closing. Please reopen if you
see it again.
--
Eric Dorland <[EMAIL PROTECTED]>
ICQ: #61138586, Jabber: [EMAIL PROTECTED]
signature.asc
Description: Digital signature
--- End Message ---
