On Fri, 07 Sep 2018 15:19:34 -0400
Daniel Kahn Gillmor wrote:
> On Fri 2018-09-07 14:31:16 +0200, Kristian Fiskerstrand wrote:
> > On 9/5/18 4:20 PM, Daniel Kahn Gillmor wrote:
> >> I'm unable to replicate this. here's a transcript of my session,
> >> testing pinentry-qt 1.1.0-1+b1 and gnupg
On 9/7/18 9:19 PM, Daniel Kahn Gillmor wrote:
> On Fri 2018-09-07 14:31:16 +0200, Kristian Fiskerstrand wrote:
>> On 9/5/18 4:20 PM, Daniel Kahn Gillmor wrote:
>>> I'm unable to replicate this. here's a transcript of my session,
>>> testing pinentry-qt 1.1.0-1+b1 and gnupg 2.2.10-1 on debian
>>>
On Fri 2018-09-07 14:31:16 +0200, Kristian Fiskerstrand wrote:
> On 9/5/18 4:20 PM, Daniel Kahn Gillmor wrote:
>> I'm unable to replicate this. here's a transcript of my session,
>> testing pinentry-qt 1.1.0-1+b1 and gnupg 2.2.10-1 on debian
>> testing/unstable:
>
> which desktop manager / window
On 9/7/18 2:31 PM, Kristian Fiskerstrand wrote:
> On 9/5/18 4:20 PM, Daniel Kahn Gillmor wrote:
>> I'm unable to replicate this. here's a transcript of my session,
>> testing pinentry-qt 1.1.0-1+b1 and gnupg 2.2.10-1 on debian
>> testing/unstable:
>
> which desktop manager / window manager? I
On 9/5/18 4:20 PM, Daniel Kahn Gillmor wrote:
> I'm unable to replicate this. here's a transcript of my session,
> testing pinentry-qt 1.1.0-1+b1 and gnupg 2.2.10-1 on debian
> testing/unstable:
which desktop manager / window manager? I can replicate on cleanly
installed debian testing with
On Wed 2018-09-05 09:39:31 +0200, Kristian Fiskerstrand wrote:
> On 9/4/18 6:10 PM, Daniel Kahn Gillmor wrote:
>> or do you mean something else?
>
> without DISPLAY env var, qt version automatically falls back to curses
> variant despite the argument
>
> kristianf@ares ~ $ unset DISPLAY
>
On 9/5/18 9:39 AM, Kristian Fiskerstrand wrote:
> without DISPLAY env var, qt version automatically falls back to curses
> variant despite the argument
Wrote too quickly there; This is actually wrong, it never actually falls
back to curses, it just fails.
--
On 9/4/18 6:10 PM, Daniel Kahn Gillmor wrote:
> or do you mean something else?
without DISPLAY env var, qt version automatically falls back to curses
variant despite the argument
kristianf@ares ~ $ unset DISPLAY
kristianf@ares ~ $ /usr/bin/pinentry-qt4 --display :0
(pinentry-qt4:6370):
On Mon 2018-09-03 09:58:24 +0200, Kristian Fiskerstrand wrote:
> Just to have it mentioned, turned out this was an issue with missing
> keep-display in gpg-agent.conf, without this the Qt4/5 pinentry fail
> (although I've been told it is not an issue in KDE environment).
to be clear, keep-display
On 08/29/2018 12:41 AM, Kristian Fiskerstrand wrote:
> On 08/28/2018 08:22 PM, Daniel Kahn Gillmor wrote:
>> On Sat 2018-08-25 08:18:48 +0200, sunri...@gmx.com wrote:
>>> Hi all, since some days I'm having an issue with pinentry, I've set the
>>> default agent as pinentry-qt4
>>> from
On 08/28/2018 08:22 PM, Daniel Kahn Gillmor wrote:
> On Sat 2018-08-25 08:18:48 +0200, sunri...@gmx.com wrote:
>> Hi all, since some days I'm having an issue with pinentry, I've set the
>> default agent as pinentry-qt4
>> from update-alternatives (I've also tried pinentry-qt and pinentry-gnome)
On Sat 2018-08-25 08:18:48 +0200, sunri...@gmx.com wrote:
> Hi all, since some days I'm having an issue with pinentry, I've set the
> default agent as pinentry-qt4
> from update-alternatives (I've also tried pinentry-qt and pinentry-gnome) but
> when I run gpg --decrypt file
> it's always
Hi all, since some days I'm having an issue with pinentry, I've set the default
agent as pinentry-qt4
from update-alternatives (I've also tried pinentry-qt and pinentry-gnome) but
when I run gpg --decrypt file
it's always falling on the cli for prompting the password. In
.gnupg/gpg-agent.conf
13 matches
Mail list logo
