On Thu, Feb 25, 2010 at 08:45:27PM +, Mick wrote:
> > So maybe file a bug? I
> > don't know whether this is a configuration/USE issue or something
> > hardcoded in the distribution.
>
> I will file a bug, but I am not entirely sure what I should file it under, so
> that it does not get reject
On Thursday 25 February 2010 11:18:54 Willie Wong wrote:
> On Thu, Feb 25, 2010 at 07:01:12AM +, Mick wrote:
> > Why is it trying to call /usr/bin/pinentry-qt?!
> >
> >`ERR 67109133 can't exec `/usr/bin/pinentry-qt'
> >
> > Is this a valid binary these days, or an older qt3 version? I thi
On Thu, Feb 25, 2010 at 07:01:12AM +, Mick wrote:
> 2010-02-25 06:48:32 gpg-agent[6741] starting a new PIN Entry
> gpg-agent[6741]: can't connect server: `ERR 67109133 can't exec
> `/usr/bin/pinentry-qt': No such file or directory'
> 2010-02-25 06:48:32 gpg-agent[6741] can't connect to the PIN
On Thursday 25 February 2010 00:09:17 Willie Wong wrote:
> On Wed, Feb 24, 2010 at 10:51:38PM +, Mick wrote:
> > Why is this? Invoking gpg to decrypt different (encrypted) files always
> > brings up that socket '/tmp/gpg-pNLb9Y/S.gpg-agent'. Shouldn't it be a
> > different socket each time?
On Wed, Feb 24, 2010 at 10:51:38PM +, Mick wrote:
> eval "$(gpg-agent --daemon --no-detach --debug-level guru --log-file gpg-
> agent.log)"
> gpg-agent[7276]: enabled debug flags: command mpi crypto memory cache memstat
> hashing assuan
>
> The log file shows:
> ==
On Wednesday 24 February 2010 15:03:06 Willie Wong wrote:
> Hum, also, try getting some debug output from gpg-agent:
>
> (1) 'killall gpg-agent' (and run ps aux to see if they are really
> killed)
> (2) Restart gpg-agent via
>
> eval 'gpg-agent --daemon --no-detach --debug-level guru --log-f
On Wed, Feb 24, 2010 at 11:31:34AM +, Mick wrote:
> Since invoking gpg on the CLI does not ask for a passphrase and it returns:
>
> gpg: problem with the agent: No pinentry
>
> I assume that the problem is with pinentry. Is there some other
> application involved here that I should look in
On Wed, Feb 24, 2010 at 11:31:34AM +, Mick wrote:
> Since invoking gpg on the CLI does not ask for a passphrase and it returns:
>
> gpg: problem with the agent: No pinentry
>
> I assume that the problem is with pinentry. Is there some other
> application involved here that I should look in
On 22 February 2010 06:49, Mick wrote:
> On Sunday 21 February 2010 17:01:13 Willie Wong wrote:
>> On Sun, Feb 21, 2010 at 03:32:00PM +, Mick wrote:
>> > On Sunday 21 February 2010 15:08:28 Willie Wong wrote:
>> > > On Sun, Feb 21, 2010 at 02:50:09PM +, Mick wrote:
>> > > > Yesterday I upd
On Sunday 21 February 2010 17:01:13 Willie Wong wrote:
> On Sun, Feb 21, 2010 at 03:32:00PM +, Mick wrote:
> > On Sunday 21 February 2010 15:08:28 Willie Wong wrote:
> > > On Sun, Feb 21, 2010 at 02:50:09PM +, Mick wrote:
> > > > Yesterday I updated my system and after a series of:
> > > >
On Sun, Feb 21, 2010 at 03:32:00PM +, Mick wrote:
> On Sunday 21 February 2010 15:08:28 Willie Wong wrote:
> > On Sun, Feb 21, 2010 at 02:50:09PM +, Mick wrote:
> > > Yesterday I updated my system and after a series of:
> > >
> > > revdep-rebuild --library libjpeg.so.7
> > >
> > > and
> >
On Sunday 21 February 2010 15:08:28 Willie Wong wrote:
> On Sun, Feb 21, 2010 at 02:50:09PM +, Mick wrote:
> > Yesterday I updated my system and after a series of:
> >
> > revdep-rebuild --library libjpeg.so.7
> >
> > and
> >
> > revdep-rebuild -v -i
> >
> > I thought all was good to go. Unf
On Sun, Feb 21, 2010 at 02:50:09PM +, Mick wrote:
> Yesterday I updated my system and after a series of:
>
> revdep-rebuild --library libjpeg.so.7
>
> and
>
> revdep-rebuild -v -i
>
> I thought all was good to go. Unfortunately, I now noticed that I cannot
> open
> encrypted messages
Yesterday I updated my system and after a series of:
revdep-rebuild --library libjpeg.so.7
and
revdep-rebuild -v -i
I thought all was good to go. Unfortunately, I now noticed that I cannot open
encrypted messages anymore and signing mail fails. This points towards gnupg
which I remerged
14 matches
Mail list logo
