pin entry dialog zips in and out of view before anyone can input anything

[Martin-Éric Racine]

pinentry-gtk2 was pulled as a dependency by some package and thus suddenly decided to replace the normal command line input of my GPG key password. Nothing wrong with a GUI input per-se, except that the dialog zips in and out of view before I can input anything, which effectively prevents me from inputing my GPG password.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: pinentry-gtk2 0.7.6-1
ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
Architecture: i386
Date: Mon Jul 26 11:19:26 2010
ProcEnviron:
 LANGUAGE=fi_FI:fi:en_US:en
 PATH=(custom, user)
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
SourcePackage: pinentry

[Tony Houghton (h-realh)]

Are you using UNR, or maximus for some other reason? I had the same problem but fixed it by disabling maximus in Startup Applications.

[Martin-Éric Racine (q-funk)]

Yes, I use Maximus. Disabling it is not an option, however.

[Florian Staudacher (florian-staudacher)]

I have the same problem with pinentry-qt. I try to sign a message in KMail or sign a file with kleopatra and as soon as I am supposed to be prompted for my passphrase, the pinentry window pops up and disappears instantly again a few times. Then I get the message, that signing failed...

kde4-config --version:
Qt: 4.7.0
KDE: 4.5.1 (KDE 4.5.1)
kde4-config: 1.0

[Tony Houghton (h-realh)]

Are you using maximus too? It seems to be a common factor with the other two of us. I mention it, not suggesting that you disable maximus, but in the hope that it will help the developers to quickly identify the cause of the bug and fix it.

I don't have maximus installed on the PC I'm using now, but perhaps there's some way of configuring it to make exceptions for certain windows which could be used as a workaround for now?

[Florian Staudacher (florian-staudacher)]

No, I don't even have maximus installed, nonetheless I'm still getting this weird behaviour...
I'd say this is a very important bug, since no KDE application is able to sign/encrypt anything - so this affects more than just the pinentry package.

[Scott Kitterman (kitterman)]

Florian: If you're using pinentry-qt, you should probably be using pinentry-qt4 instead. Also see Bug #657219 for a similar pinentry-qt4 problem that should have a fix in Maverick shortly.

[Paul Elliott (pelliott-blackpatchpanel)]

I have the same problem but only when I am "ssh -X" ed into another X server! It does not happen when I am not using "ssh -X" on either the x-server or the x-client. I am already using pinentry-qt4!