Bug#727013: Bug #727013: [gnupg2] gpg2 cannot connect to pinentry, although it is installed

2015-09-25 Thread Mariusz Gronczewski 
Also I've noticed that my password for key doesn't work (tried to enter it
at least 5 times and failed everytime and I'm 100% sure it wasnt a typo),
and downgrading to 2.0.28 helped

-- 
Mariusz Gronczewski (XANi) 
GnuPG: 0xEA8ACE64

Bug#727013: Bug #727013: [gnupg2] gpg2 cannot connect to pinentry, although it is installed

2015-09-25 Thread Mariusz Gronczewski 
I have similiar problem.

Config is simple i3 window manager, so no gnome services running by default
except gnome keyring

when I run gpg-agent either from standard /etc/ xsession or from
.xsessionrc I dont get any pinentry, only immediate failure and it logs
(guru loglevel):

2015-09-25 12:21:12 gpg-agent[23399] starting a new PIN Entry
2015-09-25 12:21:12 gpg-agent[23399] DBG: connection to PIN entry
established
2015-09-25 12:21:12 gpg-agent[23399] DBG: error calling pinentry: Operacja
anulowana 
2015-09-25 12:21:12 gpg-agent[23399] failed to unprotect the secret key:
Operacja anulowana
2015-09-25 12:21:12 gpg-agent[23399] failed to read the secret key
2015-09-25 12:21:12 gpg-agent[23399] ssh sign request failed: Operacja
anulowana 
2015-09-25 12:21:12 gpg-agent[23399] ssh request handler for sign_request
(13) ready

(Operacja anulowana is "operation cancelled" in english)

but when I kill the daemon and run it from X11's terminal and then try to
connect (after setting correct env of couse) I get pinentry correctly




-- 
Mariusz Gronczewski (XANi) 
GnuPG: 0xEA8ACE64

Bug#727013: Bug #727013: [gnupg2] gpg2 cannot connect to pinentry, although it is installed

2015-01-06 Thread Thomas Hackert 
Hello Eric, *,
> Control: tags -1 unreproducible
> 
> * Thomas Hackert (thack...@nexgo.de) wrote:
> > Package: gnupg2
> > Version: 2.0.20-1
> > Severity: normal
> > 
> > --- Please enter the report below this line. ---
> > Hello @ll,
> > when I create a test file via
> > 
> > echo test > test
> > 
> > and then use
> > 
> > gpg2 --sign test
> > 
> > to sign my test file, I get the following message
> > 
> > You need a passphrase to unlock the secret key for
> > user: "Test User"
> > 2048-bit RSA key, ID $secret, created 2013-10-21
> > 
> > gpg: can't connect to the agent - trying fall back
> > gpg-agent[4199]: enabled debug flags: assuan
> > gpg: problem with the agent: No pinentry
> > gpg: no default secret key: Operation cancelled
> > gpg: signing failed: Operation cancelled
> > 
> 
> Odd. Could you try running your agent under strace to try to see where
> it's failing to find pinentry?

I have tried different things:
First on my netbook (an Asus eeepC 1000H with Debian Testing i686):
1. "killall gpg-agent" to kill the agent
2. "strace /usr/bin/gpg-agent --daemon --sh
--write-env-file=~/.gnupg/gpg-agent-info-niobe
/usr/bin/dbus-launch --exit-with-session x-session-manager 2&>
~/gnupg_strace.log" to restart the agent (or did you mean something
different here?)
3. switched to another tab in konsole and typed "gpg2 --sign test" (got
the same message as before)
4. switched back to the tab with the strace command
5. have waited for ca. 20 seconds, before an Xdialog window with "KDE is
already running" (or something like that) popped up
6. stopped strace with +, after I confirmed this dialog
.

This resulted in an log file, which is 7.1 MB large. But as I am not a
dev, I cannot see, if my "gpg2 --sign..." leads to any error message,
sorry ... :(

The second try was done on the PC, which I use for my recreational
training with Debian Testing AMD64:
1. Moved my .gnupg directory to dotgnupg (though I have never used GPG
there ... ;) )
2. tried "gpg2 --gen-key"
3. entered all needed data like name, mail address, etc.
4. confirmed its correctness

There I got the message

You need a Passphrase to protect your secret key.

gpg: problem with the agent: No pinentry
gpg: Key generation canceled.

... :( I have installed – as with my eeePC – pinentry-qt4 as well as
pinentry-curses, where the last one is entered in my gpg-agent.conf.

Third try (back at home):
1. Restarted my netbook
2. Did the "gpg2 --sign test" again

Got the message

gpg: writing to `test.gpg'
gpg: signing failed: No pinentry
gpg: signing failed: No pinentry


Now I am at my wit's end ... :( If you know something easy to help you,
feel free to ask :)
Sorry for the inconvenience and have a nice afternoon
Thomas.

-- 
Everyone who comes in here wants three things:
(1) They want it quick.
(2) They want it good.
(3) They want it cheap.
I tell 'em to pick two and call me back.
-- sign on the back wall of a small printing company


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

Bug#727013: [gnupg2] gpg2 cannot connect to pinentry, although it is installed

2015-01-04 Thread Eric Dorland 
Control: tags -1 unreproducible

* Thomas Hackert (thack...@nexgo.de) wrote:
> Package: gnupg2
> Version: 2.0.20-1
> Severity: normal
> 
> --- Please enter the report below this line. ---
> Hello @ll,
> when I create a test file via
> 
> echo test > test
> 
> and then use
> 
> gpg2 --sign test
> 
> to sign my test file, I get the following message
> 
> You need a passphrase to unlock the secret key for
> user: "Test User"
> 2048-bit RSA key, ID $secret, created 2013-10-21
> 
> gpg: can't connect to the agent - trying fall back
> gpg-agent[4199]: enabled debug flags: assuan
> gpg: problem with the agent: No pinentry
> gpg: no default secret key: Operation cancelled
> gpg: signing failed: Operation cancelled
> 

Odd. Could you try running your agent under strace to try to see where
it's failing to find pinentry?

> ... :( If I try the same with gpg (1.4.15)
> 
> gpg --sign test
> 
> , I get
> 
> You need a passphrase to unlock the secret key for
> user: "Test User"
> 2048-bit RSA key, ID $secret, created 2013-10-21
> 
> can't connect to `/tmp/gpg-rz6R90/S.gpg-agent': No such file or
> directory
> gpg: can't connect to `/tmp/gpg-rz6R90/S.gpg-agent': connect failed
> 
> and - despite of the "No such file..." and "connect failed" messages -
> am able to sign my test file ... ;) I have installed different pinentry
> packages (dpkg -l | grep pinentry says
> 
> ii  pinentry-curses   0.8.1-1
> amd64curses-based PIN or pass-phrase entry dialog for GnuPG
> ii  pinentry-qt4  0.8.1-1
> amd64Qt-4-based PIN or pass-phrase entry dialog for GnuPG) and
> have an entry for it in ~/.gnupg/gpg-agent.conf ("pinentry-program
> /usr/bin/pintentry-curses", but it does not make any differnce, if I
> enter "pinentry-program /usr/bin/pintentry-qt4" here ... :( ), but still
> I am not able to use gpg2 ... :( It would be nice, if this can get fixed
> ... ;)
> Sorry for the inconvenience
> Thomas.

-- 
Eric Dorland 
43CF 1228 F726 FD5B 474C  E962 C256 FBD5 0022 1E93


signature.asc
Description: Digital signature

Bug#727013: [gnupg2] gpg2 cannot connect to pinentry, although it is installed

2013-10-21 Thread Thomas Hackert 
Package: gnupg2
Version: 2.0.20-1
Severity: normal

--- Please enter the report below this line. ---
Hello @ll,
when I create a test file via

echo test > test

and then use

gpg2 --sign test

to sign my test file, I get the following message

You need a passphrase to unlock the secret key for
user: "Test User"
2048-bit RSA key, ID $secret, created 2013-10-21

gpg: can't connect to the agent - trying fall back
gpg-agent[4199]: enabled debug flags: assuan
gpg: problem with the agent: No pinentry
gpg: no default secret key: Operation cancelled
gpg: signing failed: Operation cancelled

... :( If I try the same with gpg (1.4.15)

gpg --sign test

, I get

You need a passphrase to unlock the secret key for
user: "Test User"
2048-bit RSA key, ID $secret, created 2013-10-21

can't connect to `/tmp/gpg-rz6R90/S.gpg-agent': No such file or
directory
gpg: can't connect to `/tmp/gpg-rz6R90/S.gpg-agent': connect failed

and - despite of the "No such file..." and "connect failed" messages -
am able to sign my test file ... ;) I have installed different pinentry
packages (dpkg -l | grep pinentry says

ii  pinentry-curses   0.8.1-1
amd64curses-based PIN or pass-phrase entry dialog for GnuPG
ii  pinentry-qt4  0.8.1-1
amd64Qt-4-based PIN or pass-phrase entry dialog for GnuPG) and
have an entry for it in ~/.gnupg/gpg-agent.conf ("pinentry-program
/usr/bin/pintentry-curses", but it does not make any differnce, if I
enter "pinentry-program /usr/bin/pintentry-qt4" here ... :( ), but still
I am not able to use gpg2 ... :( It would be nice, if this can get fixed
... ;)
Sorry for the inconvenience
Thomas.

--- System information. ---
Architecture: amd64
Kernel:   Linux 3.10-3-amd64

Debian Release: jessie/sid
  500 wheezy-pgdg apt.postgresql.org 
  500 unstablesnapshots.ekiga.net 
  500 unstabledownload.jitsi.org 
  500 testing www.deb-multimedia.org 
  500 testing ftp.de.debian.org 
  500 testing apt.last.fm 
  500 stable  security.debian.org 
  500 stable  dl.google.com 
  500 libreofficebox  LibOx 4.1 Test-ISO 
  500 isv:ownCloud:testing download.opensuse.org 

--- Package information. ---
Depends(Version) | Installed
-+-=
gnupg-agent (= 2.0.20-1) | 2.0.20-1
libassuan0(>= 2.0.1) | 2.1.1-1
libbz2-1.0   | 1.0.6-5
libc6  (>= 2.15) | 2.17-93
libcurl3-gnutls  (>= 7.16.2) | 7.32.0-1
libgcrypt11   (>= 1.4.5) | 1.5.3-2
libgpg-error0  (>= 1.10) | 1.12-0.2
libksba8  (>= 1.2.0) | 1.3.0-2
libreadline6(>= 6.0) | 6.2+dfsg-0.1
zlib1g  (>= 1:1.1.4) | 1:1.2.8.dfsg-1
dpkg(>= 1.15.4)  | 1.16.12
 OR install-info | 5.2.0.dfsg.1-1


Package's Recommends field is empty.

Suggests(Version) | Installed
=-+-===
gnupg-doc | 
xloadimage| 

-- 
"Indecision is the basis of flexibility"
-- button at a Science Fiction convention.


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