--- Comment #16 from Patrick Ohly <patrick.ohly(a)gmx.de> ---
(In reply to comment #15)
$ ./dbus-session.sh bash
Right, I forgot that dbus-session.sh does it automatically if
gnome-keyring-daemon (not gnome-keyring) is installed.
If I then start the script below with:
(gnome-keyring:32540): Gtk-WARNING **: cannot open display:
** Message: couldn't initialize prompt:
/usr/lib/gcr/gcr-prompter exited with status 1
Sorry, another unexpected prerequisite: the keyring must be usable without an
explicit unlock via the UI.
I think this can be achieved by creating one in plain text; at least that is
what I am using in the nightly testing:
$ cat ~/.gnome2/keyrings/default
nightly@syncev:~$ cat ~/.gnome2/keyrings/default.keyring
Could it be related perhaps to
gconftool-2 being called rather than gconftool in the first two config
On my Debian Wheezy, gconftool is an alias for gconftool-2, so no, that
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.