[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gnupg-devel
Subject:    Re: scim and pinentry-gtk2
From:       Robby Workman <rw () rlworkman ! net>
Date:       2008-03-19 5:02:08
Message-ID: 47E09E50.8040106 () rlworkman ! net
[Download RAW message or body]

Sorry for the dupe, Marcus - forgot to send to list the first time.

Marcus Brinkmann wrote:
> At Thu, 21 Feb 2008 15:46:02 -0600,
> Robby Workman <rw@rlworkman.net> wrote:
>> To make a long story short, pinentry-gtk2 doesn't receive keyboard
>> input when scim is being used.  This has previously been reported
>> to both Ubuntu and OpenSuSE, and after scim and friends were recently
>> added to Slackware, we're seeing it there.
>>
>>    https://bugs.launchpad.net/ubuntu/+source/pinentry/+bug/176815
>>
>>    https://bugzilla.novell.com/show_bug.cgi?id=330073#c5
>>
>> Any idea what's at fault?
> 
> pinentry grabs the keyboard and the screen by default (there is an
> option to switch it off).  Maybe scim doesn't work well with that?


Hi Marcus,

Sorry for the delay - I've unfortunately been short on time lately.

Starting gpg-agent with the --no-grab option has no effect.
This is quite annoying for users who need alternate input methods,
especially scim.  Maybe I'm missing something obvious, but here's
how it appears to me:

1.  Pinentry is a GTK+ app.
2.  GTK+ apps can use GTK+ input methods.
3.  Rather than using an input method, pinentry grabs the raw input.

I understand that there are perhaps security concerns with not
grabbing raw input, but surely there's a way to fix this?
pinentry-qt handles this just fine, btw...

-RW


_______________________________________________
Gnupg-devel mailing list
Gnupg-devel@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-devel
[prev in list] [next in list] [prev in thread] [next in thread]