https://bugzilla.novell.com/show_bug.cgi?id=443693 Summary: g-k: keyring not unlocked at session start Product: openSUSE 11.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome@forge.provo.novell.com ReportedBy: thoenig@novell.com QAContact: qa@suse.de CC: vuntz@novell.com Found By: --- g-k: keyring not unlocked at session start. Here's the log (g-k with http://tmp.vuntz.net/gnome-keyring-log.patch applied): gdm-session-worker[26201]: gkr-pam: authenticate: auto_start = 0 gdm-session-worker[26201]: gkr-pam: session: auto_start = 16 gdm-session-worker[26201]: gkr-pam: session: shall we start? gdm-session-worker[26201]: gkr-pam: service: gdm gdm-session-worker[26201]: gkr-pam: session: starting gdm-session-worker[26201]: gnome-keyring-daemon: couldn't lookup keyring component setting: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Not running within active session)gnome-keyring-daemon: couldn't lookup ssh component setting: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Not running within active session)gnome-keyring-daemon: couldn't lookup pkcs11 component setting: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Not running within active session) gdm-session-worker[26201]: gkr-pam: session: started gdm-session-worker[26201]: gkr-pam: session: shall we unlock? gnome-keyring-daemon[26279]: gcrypt: Rijndael-128 test encryption failed. gnome-keyring-daemon[26279]: decrypt_buffer: assertion `!gerr' failed gnome-keyring-daemon[26279]: error parsing keyring gnome-keyring-daemon[26279]: Couldn't unlock login keyring with provided password gnome-keyring-daemon[26279]: Failed to unlock login on startup gnome-session[26359]: WARNING: Failed to acquire org.gnome.SessionManager gnome-session[26359]: ******************* START ******************************** gnome-session[26359]: Frame 0: /usr/bin/gnome-session [0x4171a7] gnome-session[26359]: Frame 1: /usr/bin/gnome-session [0x417306] gnome-session[26359]: Frame 2: /lib64/libpthread.so.0 [0x7fed437f9a50] gnome-session[26359]: Frame 3: /usr/bin/gnome-session [0x418a49] gnome-session[26359]: Frame 4: /lib64/libc.so.6(__libc_start_main+0xe6) [0x7fed434ad586] gnome-session[26359]: Frame 5: /usr/bin/gnome-session [0x40ab29] gnome-session[26359]: ******************* END ********************************** gnome-session[26345]: WARNING: Application 'gnome-wm.desktop' failed to register before timeout I guess the "Not running within active session" doesn't sound very healthy. Dunno if the gnome-session error is related. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.