Dear Debian folks,
Am Montag, den 06.04.2009, 08:04 +0000 schrieb Paul Menzel: > Am Sonntag, den 05.04.2009, 12:20 +0200 schrieb Joachim Breitner: > > > 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. > > I found that the daemon simply dies on my system after some time. > > $ gnome-keyring-daemon -s -f […] > gnome-keyring-daemon: egg-secure-memory.c:324: sec_check_guards: Zusicherung > »((void**)cell->words)[cell->n_words - 1] == (void*)cell« nicht erfüllt. > Abgebrochen > > Is there a debug package to track this down or something else I can do? I am pretty sure, that the crash of gnome-keyring-daemon has something to do with this error message, since I have gotten it a second time. Maybe it has something to do with this change [1]? Thanks, Paul [1] http://mail.gnome.org/archives/svn-commits-list/2009-February/msg02943.html
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
