From: Michael Albinus <michael.albinus@gmx.de>
To: Ken Brown <kbrown@cornell.edu>
Cc: "33568@debbugs.gnu.org" <33568@debbugs.gnu.org>
Subject: bug#33568: 27.0.50; Failing secrets tests on Cygwin
Date: Wed, 12 Dec 2018 10:59:15 +0100 [thread overview]
Message-ID: <874lbjdq18.fsf@gmx.de> (raw)
In-Reply-To: <91308dcb-36b8-2676-c5c3-8b465b374baa@cornell.edu> (Ken Brown's message of "Sun, 2 Dec 2018 12:23:55 +0000")
Ken Brown <kbrown@cornell.edu> writes:
> Hi Michael,
Hi Ken,
sorry for the delay. Finally, I found a machine running cygwin for my tests.
>> Thanks for the report. I don't know whether there is a better way; let's
>> explore your system.
>>
>> What do you get if you call (secrets-list-collections) ? (Maybe you must
>> load the library `secrets' first)
>
> (load "secrets")
> t
>
> (secrets-list-collections)
> ("session")
Hmm, same here, when using the GNOME desktop. I always thought that the
"login" keyring exist per default, but it doesn't. Maybe this is due to
different invocations od gnome-keyring-daemon. On my Ubuntu 18.10
system, it is
--8<---------------cut here---------------start------------->8---
$ ps -eaf | grep gnome-keyring
albinus 6340 1 0 Dec04 ? 00:02:03 /usr/bin/gnome-keyring-daemon --daemonize --login
--8<---------------cut here---------------end--------------->8---
OTOH, on cygwin I see
--8<---------------cut here---------------start------------->8---
$ ps -eaf | grep gnome-keyring
albinmic 5676 1 ? 16:09:48 /usr/bin/gnome-keyring-daemon
--8<---------------cut here---------------end--------------->8---
I can create the "login" keyring interactively, via seahorse. But this
doesn't count.
So I have removed the respective checks in secrets-tests.el, they are
not important. Could you pls check, whether this works for you?
> Ken
Best regards, Michael.
next prev parent reply other threads:[~2018-12-12 9:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-01 23:02 bug#33568: 27.0.50; Failing secrets tests on Cygwin Ken Brown
2018-12-02 9:17 ` Michael Albinus
2018-12-02 12:23 ` Ken Brown
2018-12-02 12:36 ` Michael Albinus
2018-12-12 9:59 ` Michael Albinus [this message]
2018-12-12 18:28 ` Ken Brown
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=874lbjdq18.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=33568@debbugs.gnu.org \
--cc=kbrown@cornell.edu \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.