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

xscreensaver with pam crashes


Since  the  version 4.22 of xscreensaver, I cannot use any German character in
my passwords any more eg. 'ยง'. When I had changed my password to have just 127
ASCII  chars  I  noticed  xscreensaver  crashes  with any password and with it
unlocks the screen. gdb suggest it has something to do with my pam:

(gdb) run -sync -verbose -no-capture
Starting program: /usr/local/bin/xscreensaver -sync -verbose -no-capture
xscreensaver: 21:34:44: grabbing server...
xscreensaver: 21:34:44: 0: ungrabbing mouse (was 0x48).
xscreensaver: 21:34:44: 0: grabbing mouse on 0x40000e... GrabSuccess.
xscreensaver: 21:34:44: ungrabbing server.
xscreensaver: 21:34:44: 0: child pid 5858 (endgame) stopped with signal 19.
xscreensaver:  21:34:45:  pam_start  ("xscreensaver",  "lynx",  ...)   ==>   0
xscreensaver: 21:34:45:   pam_set_item (p, PAM_TTY, ":0.0") ==> 0 (Success)
xscreensaver: 21:34:45:     PAM ECHO_OFF("Password: ") ==> password

Program received signal SIGSEGV, Segmentation fault.
_unix_verify_password   (pamh=0x8094380,  name=0x80a1e38  "lynx",  p=0x80a1070
"sldfj", ctrl=512) at support.c:829
829     support.c: No such file or directory.
        in support.c

In modules/pam_unix/support.c at line 829 is no reference to any file:
    new->count = old->count + 1;

Can anybody tell me, what I could do about it?
I have an LFS here, and everywhere else pam is working nicely.


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