Re: [gdm-list] GDM - can't login with smart card



Hi,

On Wed, Oct 9, 2013 at 2:24 AM, jarek <jarek poczta srv pl> wrote:
Hello!

        I've configured Debian Wheezy to use smart cards (with pam-pkcs11) for
login, and it works fine from console, but fails when I'm trying to
login by gdm. GDM asks for pin, accepts it and without any error returns
to login window.
In the log I see:

authentication succeeded

but gnome session isn't started.

Can someone look inside attached log, and tell me what is wrong ?
Looks like the process that's running the pam conversation is crashing:

Oct  9 08:08:34 ADMIN1 gdm3][3441]: releasing pkcs #11 module...
Oct  9 08:08:35 ADMIN1 gdm3][3441]: authentication succeeded
Oct  9 08:08:35 ADMIN1 gdm3][3441]: ******************* START
********************************
Oct  9 08:08:35 ADMIN1 gdm3][3441]: Frame 0: gdm-session-worker
[pam/gdm3]() [0x40ebeb]
Oct  9 08:08:35 ADMIN1 gdm3][3441]: Frame 1: gdm-session-worker
[pam/gdm3]() [0x40efda]
Oct  9 08:08:35 ADMIN1 gdm3][3441]: Frame 2:
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf030) [0x7f76dfdf1030]
Oct  9 08:08:35 ADMIN1 gdm3][3441]: Frame 3:
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35) [0x7f76dfa8a475]
Oct  9 08:08:35 ADMIN1 gdm3][3441]: Frame 4:
/lib/x86_64-linux-gnu/libc.so.6(abort+0x180) [0x7f76dfa8d6f0]
Oct  9 08:08:35 ADMIN1 gdm3][3441]: Frame 5:
/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x1d143) [0x7f76e025b143]
Oct  9 08:08:35 ADMIN1 gdm3][3441]: Frame 6:
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_private_set+0x25)
[0x7f76e02c4815]
Oct  9 08:08:35 ADMIN1 gdm3][3441]: Frame 7:
/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x1cccb) [0x7f76e025accb]
Oct  9 08:08:35 ADMIN1 gdm3][3441]: Frame 8:
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_slice_alloc+0x1bd)
[0x7f76e02a248d]
Oct  9 08:08:35 ADMIN1 gdm3][3441]: Frame 9:
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_string_sized_new+0x1b)
[0x7f76e02a5ccb]
Oct  9 08:08:35 ADMIN1 gdm3][3441]: Frame 10: gdm-session-worker
[pam/gdm3](gdm_log_default_handler+0x87) [0x40e957]
Oct  9 08:08:35 ADMIN1 gdm3][3441]: Frame 11:
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_logv+0x1e3) [0x7f76e028f473]
Oct  9 08:08:35 ADMIN1 gdm3][3441]: Frame 12:
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_log+0x82) [0x7f76e028f622]
Oct  9 08:08:35 ADMIN1 gdm3][3441]: Frame 13: gdm-session-worker
[pam/gdm3]() [0x409d03]
Oct  9 08:08:35 ADMIN1 gdm3][3441]: Frame 14:
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x135)
[0x7f76e0288355]
Oct  9 08:08:35 ADMIN1 gdm3][3441]: Frame 15:
/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4a688) [0x7f76e0288688]
Oct  9 08:08:35 ADMIN1 gdm3][3441]: Frame 16:
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0x72)
[0x7f76e0288a82]
Oct  9 08:08:35 ADMIN1 gdm3][3441]: Frame 17: gdm-session-worker
[pam/gdm3]() [0x405bce]
Oct  9 08:08:35 ADMIN1 gdm3][3441]: Frame 18:
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd)
[0x7f76dfa76ead]
Oct  9 08:08:35 ADMIN1 gdm3][3441]: Frame 19: gdm-session-worker
[pam/gdm3]() [0x405c71]
Oct  9 08:08:35 ADMIN1 gdm3][3441]: ******************* END
**********************************

This could be a heap corruption bug in pam_pkcs11 (or the pkcs11
module it loads), or it might be this bug maybe:

https://git.gnome.org/browse/gdm/commit/?id=9755ca3a594a01ba7f361684af1c29b49be17856

I'd try the above patch, and if it doesn't help then getting a
stacktrace with more debug information might help.  You might also try
 running valgrind on "su" or something similar to see if there's a
memory corruption issue in the pam module or pkcs11 module.

--Ray


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]