Hi, I can confirm this problem. Although "gnome-keyring-manager --start" is executed by the gnome session manager, which can be seen in .xsession-errors by this entry: GNOME_KEYRING_SOCKET=/tmp/keyring-kqwr1i/socket
the daemon seems to quit itself right afterwards. Other programs, in my case mail-notification, will spit error messages like ** (mail-notification:6248): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-kqwr1i/socket: Verbindungsaufbau abgelehnt ** (mail-notification:6248): WARNING **: couldn't communicate with gnome keyring daemon via dbus: Failed to execute program gnome-keyring-daemon: Success and not work properly. Starting gnome-keyring-manager also gives these error messages. For some reason, dbus can not start the gnome-keyring-daemon, it seems. OTOH, starting "gnome-keyring-daemon --start" manually from a terminal makes it work properly. Applications still say ** (gnome-keyring-manager:6737): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-kqwr1i/socket: Verbindungsaufbau abgelehnt but it seems they manage to talk to the running daemon via dbus. I’d rate this bug as important, as it severely impacts the usefulness of the package. Greetings, Joachim -- Joachim "nomeata" Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
