commit f4b5049c68a79d5e4faba06447db5440936cefeb breaks pinentry-gtk+2 on AwesomeWM. Testcase & Output: === $ pinentry-gtk-2 <<< GETPIN OK Pleased to meet you ** (pinentry-gtk-2:2746): CRITICAL **: could not grab keyboard: not viewable (3) ** (pinentry-gtk-2:2746): WARNING **: it took 4097 tries to grab the keyboard ** (pinentry-gtk-2:2746): CRITICAL **: could not grab pointer: not viewable (3) ** (pinentry-gtk-2:2746): WARNING **: it took 4097 tries to grab the pointer ERR 83886179 Operation cancelled <Pinentry> === A window will flash by very quickly. As discussed w/ K_F, this should block 1.0.0 from going stable.
Could Debian patches be applied to try to unblock this? https://anonscm.debian.org/cgit/pkg-gnupg/pinentry.git/tree/debian/patches/0006-gtk2-Fix-a-problem-with-fvwm.patch https://anonscm.debian.org/cgit/pkg-gnupg/pinentry.git/tree/debian/patches/0007-gtk2-When-X11-input-grabbing-fails-try-again-over-0..patch thanks
gnupg defaults to no-grab in later versions, so this issue isn't valid once that reaches stable (iirc it was changed in 2.1.23, so fixed in 2.2.0 as well)
Ah, thanks for the info :)
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2fabf9cabaf1f4bab9f924afa116d1c7d84680b9 commit 2fabf9cabaf1f4bab9f924afa116d1c7d84680b9 Author: Kristian Fiskerstrand <k_f@gentoo.org> AuthorDate: 2017-10-16 21:14:28 +0000 Commit: Kristian Fiskerstrand <k_f@gentoo.org> CommitDate: 2017-10-16 21:14:43 +0000 app-crypt/pinentry: Fix grabbing issue in awesomewm Bug: https://bugs.gentoo.org/609678 Package-Manager: Portage-2.3.8, Repoman-2.3.3 ...isable-tooltips-in-keyboard-grabbing-mode.patch | 47 ++++++++++++++++++++++ ...nentry-1.0.0-gtk2-Fix-a-problem-with-fvwm.patch | 47 ++++++++++++++++++++++ ...ry-1.0.0-r1.ebuild => pinentry-1.0.0-r2.ebuild} | 2 + 3 files changed, 96 insertions(+)}
