[Bug 443693] New: g-k: keyring not unlocked at session start

older
[Bug 444960] New: Evolution always...

bugzilla_noreply＠novell.com

11 Nov 2008 11 Nov '08

11:20

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.

Show replies by thread

bugzilla_noreply＠novell.com

11 Nov 11 Nov

11:28

New subject: [Bug 443693] g-k: keyring not unlocked at session start

https://bugzilla.novell.com/show_bug.cgi?id=443693 User vuntz@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=443693#c1 --- Comment #1 from Vincent Untz 2008-11-11 04:28:53 MST --- I'm actually more worried about: 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 I need to update everything to current factory and see if I can reproduce. Can you eventually check if it happens with another user? (with a brand new user, you'll need to login at least twice, since the first login will create the keyring) -- 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.

bugzilla_noreply＠novell.com

11:30

New subject: [Bug 443693] g-k: keyring not unlocked at session start

https://bugzilla.novell.com/show_bug.cgi?id=443693 User vuntz@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=443693#c2 --- Comment #2 from Vincent Untz 2008-11-11 04:30:37 MST --- Oh, and the gconf stuff is probably http://bugzilla.gnome.org/show_bug.cgi?id=558181 -- 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.

bugzilla_noreply＠novell.com

11:45

New subject: [Bug 443693] g-k: keyring not unlocked at session start

https://bugzilla.novell.com/show_bug.cgi?id=443693 User thoenig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=443693#c3 --- Comment #3 from Timo Hoenig 2008-11-11 04:45:08 MST --- I've already looked at this code but was a little unmotivated when I saw the sources of libgcrypt. Let's see what I get when adding some more checks to decrypt_buffer. There are several g_return_val_if_fail for gerr. -- 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.

bugzilla_noreply＠novell.com

12:24

New subject: [Bug 443693] g-k: keyring not unlocked at session start

https://bugzilla.novell.com/show_bug.cgi?id=443693 User thoenig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=443693#c4 --- Comment #4 from Timo Hoenig 2008-11-11 05:24:06 MST --- This kicks in: libgcrypt-1.4.1/cipher/rijndael.c:831 if (memcmp (scratch, ciphertext, sizeof (ciphertext))) return "Rijndael-128 test encryption failed."; Strange, no? libgcrypt hasn't changed recently, let's see what adding syslog (GKR_LOG_WARN, "cih: %s, key: %s, keylen: 16", cih, key); to decrypt_buffer is telling us. -- 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.

bugzilla_noreply＠novell.com

13:19

New subject: [Bug 443693] g-k: keyring not unlocked at session start

https://bugzilla.novell.com/show_bug.cgi?id=443693 User thoenig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=443693#c5 --- Comment #5 from Timo Hoenig 2008-11-11 06:19:12 MST --- Values are set at least. Not much I can tell about their correctness, though ;-) -- 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.

bugzilla_noreply＠novell.com

13:45

New subject: [Bug 443693] g-k: keyring not unlocked at session start

https://bugzilla.novell.com/show_bug.cgi?id=443693 User thoenig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=443693#c6 --- Comment #6 from Timo Hoenig 2008-11-11 06:45:01 MST --- Created an attachment (id=251333) --> (https://bugzilla.novell.com/attachment.cgi?id=251333) Minimal test case. $ gcc `pkg-config --libs --cflags glib-2.0 libcrypto` -l gcrypt gk-test.c -o gk-test $ ./gk-test Rijndael-128 test encryption failed. ** (process:11710): CRITICAL **: main: assertion `!gerr' failed -- 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.

bugzilla_noreply＠novell.com

13:47

New subject: [Bug 443693] g-k: keyring not unlocked at session start

https://bugzilla.novell.com/show_bug.cgi?id=443693 User thoenig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=443693#c7 Timo Hoenig changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mkoenig@novell.com --- Comment #7 from Timo Hoenig 2008-11-11 06:47:12 MST --- Handle the minimal test case with care. It's hackish. I'm unsure about the input values we're passing to gcry_cipher_setkey . Matthias do you happen to know more? -- 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.

bugzilla_noreply＠novell.com

13:53

New subject: [Bug 443693] g-k: keyring not unlocked at session start

https://bugzilla.novell.com/show_bug.cgi?id=443693 User thoenig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=443693#c8 --- Comment #8 from Timo Hoenig 2008-11-11 06:53:37 MST --- selftest (void) of rijndael.c fails? Is this possible? Confused. -- 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.

bugzilla_noreply＠novell.com

14:17

New subject: [Bug 443693] g-k: keyring not unlocked at session start

https://bugzilla.novell.com/show_bug.cgi?id=443693 User mkoenig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=443693#c9 Matthias Koenig changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-gnome@forge.provo.novell.com |mkoenig@novell.com Status|NEW |ASSIGNED --- Comment #9 from Matthias Koenig 2008-11-11 07:17:26 MST --- I'm trying to track this down, it's also the reason for the failing opencdk build. The failing selftests are really strange. The fun thing is currently I can only reproduce this in the buildroot environment. -- 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.

bugzilla_noreply＠novell.com

14:27

New subject: [Bug 443693] g-k: keyring not unlocked at session start

https://bugzilla.novell.com/show_bug.cgi?id=443693 User thoenig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=443693#c10 --- Comment #10 from Timo Hoenig 2008-11-11 07:27:43 MST --- Oh, alright. Thanks for the quick reply. Let me know if I can help somehow. -- 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.

bugzilla_noreply＠novell.com

14:31

New subject: [Bug 443693] g-k: keyring not unlocked at session start

https://bugzilla.novell.com/show_bug.cgi?id=443693 User thoenig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=443693#c11 --- Comment #11 from Timo Hoenig 2008-11-11 07:31:36 MST --- thoenig@zimtstern:~> rpmch libgcrypt11 2 * Thu Oct 30 2008 olh@suse.de - obsolete old -XXbit packages (bnthoenig@zimtstern:~> rpmch libgcrypt11 2 So, libgcrypt hasn't changed for a while, right? Maybe a misscompile or so? -- 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.

bugzilla_noreply＠novell.com

14:34

New subject: [Bug 443693] g-k: keyring not unlocked at session start

https://bugzilla.novell.com/show_bug.cgi?id=443693 User thoenig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=443693#c12 --- Comment #12 from Timo Hoenig 2008-11-11 07:34:28 MST --- Another hint for that: I'm running the latest FACTORY and can easily reproduce the bug using my minimal test case (which isn't minimal anyway ;-). -- 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.

bugzilla_noreply＠novell.com

14:49

New subject: [Bug 443693] g-k: keyring not unlocked at session start

https://bugzilla.novell.com/show_bug.cgi?id=443693 User mkoenig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=443693#c13 Matthias Koenig changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rguenther@novell.com, matz@novell.com --- Comment #13 from Matthias Koenig 2008-11-11 07:49:25 MST --- I am using the native libgcrypt testsuite ('basic' test) and it shows that *all* AES selftests fail. Ok, after upgrading to gcc43-4.3.3_20081022-4.2 I can even reproduce it in my normal System. gcc43-4.3.3_20081002-1.5 (from Beta4) seems to be Ok. CCing Richi and Micha -- 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.