Ägypten : Problem with pinentry-qt

[Bernhard Reiter]

--xkXJwpr35CY/Lc3I
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Ingo,
thanks for the bugreport.
I've opened a ticked and assigned it to Steffen.

	https://intevation.de/rt/webrt?serial_num=3D1489&display=3DHistory


On Sat, Dec 14, 2002 at 09:46:43PM +0100, Ingo Kl=F6cker wrote:
> after updating to the latest versions of the relevant libraries and=20
> programs (from cvs as described on the Aegypten page) pinentry-qt=20
> doesn't work anymore.

> gpg-agent[18407]: can't connect server: ec=3D-1
> gpg-agent[18407]: can't connect to the PIN entry module: ec=3D-1
> gpg-agent[18407]: command get_passphrase failed: no pin entry
> gpg-agent[0x80629ec] -> ERR 101 server fault
> gpg: problem with the agent - disabling agent use
> Enter passphrase: gpg-agent[0x80629ec] <- [EOF]
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
>=20
> pinentry-qt can be started manually. But I get
> ingo@erwin:~> pinentry-qt
> Warning: using insecure memory!
> OK Your orders please
>=20
> I don't get this warning when I start pinentry-gtk manually. Could this=
=20
> be the problem?

I don't think so, the warning is truely just a warning.

> BTW, pinentry-gtk still doesn't show the DESC when it asks for my=20
> passphrase. So the problem with non-ASCII characters in DESC is still=20
> not fixed (cf. my message from Oct 3, 2002).

Known, non-trivial, ticket is
	  https://intevation.de/rt/webrt?serial_num=3D1334&display=3DHistory

--xkXJwpr35CY/Lc3I
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)

iD8DBQE9/QV4h9ag3dpKERYRAkADAJ9206RYXJjAIciZxh8QG3V59EzDJwCffK1x
Q5+cUKYJ+NvK+okgDv2ReiQ=
=qvUj
-----END PGP SIGNATURE-----

--xkXJwpr35CY/Lc3I--