Please direct such questions to a mailing list. This is a bug tracker and not a
support forum.

Please direct such questions to a mailing list. This is a bug trcker and not a
support forum.

Please direct such questions to a mailing list. This is a bug trcker and not a
support forum.

Testing pinentry-qt Version: 0.8.0.svn234-0kk1 (the changelog indicates
that the change is in) on Debian Lenny with KWin from KDE 3.

May we close this bug now?

I did not have a chance to test 2.0.17 or the patch yet, but for the archive:
I just have an instance of gpg-agent, which does not allow ttys matching
"/dev/pts/??", i.e. two digits. On three-digit-ttys it works. Maybe the
behaviour depends on the length of tty when the gpg-agent was started first or
something similar.

A 2.0.17 will be released soon.

oops. Website fixed. The branch names are
STABLE-BRANCH-2-0
STABLE-BRANCH-1-4
Note the dashs. We don't use a dot because the names date back to CVS and that
does not allow a dot in the name.

From http://gnupg.org/download/cvs_access.en.html:
the stable 2.0 version (currently version 2.0.16) is known as STABLE-BRANCH-2.0;
the stable 1.4 version of GnuPG (1.4.11) is known under as STABLE-BRANCH-2.0.
I guess I should look at the first of the two :)

STABLE-BRANCH-2-0 344d72b
has the fix. Patch below.

Sounds good. I'll test it as soon as we have a kk package for the next release.

This looks pretty much like T1311.

Should probably beretested with Gnupg 2.1(beta or later)
because agent startup might have changed.

This is not a pinentry problem but one of gpg-agent. What version of gpg-agent
are you using?

Werner, please note: this issue is kkc.

Today I just had the problem again (/dev/pts/9, still same verisons as in T1203 (thomas on Jul 29 2010, 03:35 PM / Roundup))

Just had the problem on /dev/pts/9 while no problems since 2010-07-29 (because I
usually start mutt in a certain screen window where I made sure that it has a
high-enough tty number)

OpenPGP!
Marcus means, we need a similar pinentry message which ask for correctness of
fingerprint of the certificate which the user want to certified (like the
pinentry if you enabled allow-mark-trusted option for S/MIME).

OpenPGP or CMS?

Still a problem with gnupg-agent 2.0.14-0kk2 and pinentry (or pinentry-qt in
curses mode because of unset $DISPLAY) 0.7.6-0kk1 on Debian lenny:
Does not work on /dev/pts/7, works on /dev/pts/72

Actually there is a queue. However it needs a redesign to check again right
before the passpharse dialog comes up. I think this is a real bug.

note:
changing windows 7 to my Canadian locale solves the problem.

Could be a gpg-agent problem.
If I don't start a gpg-agent and run the export, it will work.
If I start a gpg-agent before, it won't work and pinentry will run amok.

When GNOME a11y is enabled, every gtk2 application loads 2 dynamic modules (gail
and atk-bridge) that are initialized at gtk_init. These modules installs some
hooks to provide the at-spi with information about the widgets.

Sorry, I have no clue about GNOME a11y. Given that pinentry uses its own widget
it is likely that tools which take over the input run into problems. As a quick
workaround you may want to try "pinentry -g".

Applied to trunk.

D116: 298_pinentry-qt-fix-1162.diff

Am Dienstag, 8. Juni 2010 12:29:40 schrieb Marc Mutz:

so I've attached the diff to current
pinentry SVN here. Works for me. Kwin/qt3 from etch for Qt3-version,
Qt-4.4.3 (self-compiled) + kwin/qt3 for Qt4-version.

The docs say on some X11 WM's, this flag will have no effect when not also
WX11BypassWM is passed, but the latter robs pinentry of it's title bar and
borders, so I left it out.

Werner, again see my tests with Kwin (default windows manager of KDE).
I believe that we should solve the issue for very common window managers.
KWin is very common for pinentry-qt3. Maybe we can ask some KDAB folks for help
on this one, should not be that hard I guess.

If you enter something on another desktop the pinentry should notice it and
return a cancel error. It all depends on the windows manager, though.

Your logs show /dev/pts/7 and as I wrote in T1203:
other bug reports indicate that any /dev/pts/(single-digit) exposes the problem.

Testing pinentry Version: 0.8.0.svn231-0kk1
with window manager kwin from kdebase Version: 4:3.5.9.dfsg.1-6+lenny1.

Applied. Thanks.

That seems to be a bad interaction between gpg-agent and keychain. AFAICS both
programs try to do the same: gpg-agent also implements the gpg-agent protocol.
It needs to be enabled, though.

Here's the link to the GTK+ 3 transition:

D129: 294_0002-Add-gseal-gtk-compat.h-from-gedit.patch

Compat with older GTK+

D130: 293_0001-Make-DSEAL-safe.patch

Let me know if I shall do a 0.8.1 release.

Fixed in the current svn. At least it works for me on Debian GNU/Linux sid and
Debian GNU/kfreebsd sid. The pinentry nows sticks to the the top and you should
not be able to change this - it is in the responsibility of the WM, though. I
am using xfwm.

I can't replicate this with pinentry-qt 0.8.0 but still with the gtk2 version
with or without the Debian keyboard race fix.

(this is a regression we should fix for the customers.)

• Werner Koch via BTS <gnupg@bugs.g10code.com> [20100317 16:00]:

Werner Koch <wk@gnupg.org> added the comment:

What pinentry version are you using (qt or another one)?

What pinentry version are you using (qt or another one)?
Did you set the GPG_TTY envvar?

Please be patient until we find time to join a russian language class.