(In reply to comment #15) > Allright. Starting > > $ ./dbus-session.sh bash > > now shows > > GNOME_KEYRING_CONTROL=/run/user/1000/keyring-g51NwC > GNOME_KEYRING_PID=32508 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: > > password=xxxxxx ./setup.sh > > I get > > > (gnome-keyring:32540): Gtk-WARNING **: cannot open display: > ** Message: couldn't initialize prompt: > GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process > /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 default nightly@syncev:~$ cat ~/.gnome2/keyrings/default.keyring [keyring] display-name=default lock-on-idle=false lock-after=false > Could it be related perhaps to > gconftool-2 being called rather than gconftool in the first two config > commands? On my Debian Wheezy, gconftool is an alias for gconftool-2, so no, that shouldn't matter.