From: Tassilo Horn <tsdh@gnu.org>
To: ding@gnus.org
Subject: Re: Username for gnus-notifications
Date: Fri, 31 Aug 2012 09:54:03 +0200 [thread overview]
Message-ID: <87sjb3ebtw.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <87ehmoxv9r.fsf@dex.adm.naquadah.org> (Julien Danjou's message of "Thu, 30 Aug 2012 17:19:12 +0200")
Julien Danjou <julien@danjou.info> writes:
>> Another thing: I get new mail and am queried for my password, and
>> then the notifications work fine. If I receive another new mail
>> within a given period of time, the notifications still work fine.
>> But after about an hour or so, I have to provide my password again.
>>
>> Is there some expiry happening? That's probably a GNOME3 issue, but
>> since you also seem to use it, maybe you know what to do.
>
> If you're talking about your keyring password, that's indeed a GNOME 3
> issue. You can probably configure the keyring daemon to not expire your
> keyring access.
Now this is really strange. As said, I get that GNOME3 password dialog
about once in a hour. But it is totally irrelevant what I type in
there! I can leave it empty and just hit RET and Gnus goes on
successfully with
Decrypting /home/horn/.emacs.d/oauth2.plstore...done
Huh?
Bye,
Tassilo
prev parent reply other threads:[~2012-08-31 7:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 6:25 Tassilo Horn
2012-08-30 6:45 ` Julien Danjou
2012-08-30 6:54 ` Tassilo Horn
2012-08-30 8:08 ` Julien Danjou
2012-08-30 8:40 ` Tassilo Horn
2012-08-30 11:01 ` Peter Münster
2012-08-30 13:10 ` Tassilo Horn
2012-08-30 15:18 ` Julien Danjou
2012-08-30 17:45 ` Tassilo Horn
2012-08-30 19:04 ` Peter Münster
2012-08-30 19:46 ` Tassilo Horn
2012-08-30 21:02 ` Julien Danjou
2012-08-31 6:23 ` Tassilo Horn
2012-08-30 15:17 ` Julien Danjou
2012-08-30 14:13 ` Tassilo Horn
2012-08-30 15:19 ` Julien Danjou
2012-08-30 17:47 ` Tassilo Horn
2012-08-31 7:54 ` Tassilo Horn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sjb3ebtw.fsf@thinkpad.tsdh.de \
--to=tsdh@gnu.org \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).