Summary: | gnome-base/gdm-2.18.4 behaves strangely (including crashing) when sys-auth/thinkfinger-0.3 is installed and set up in /etc/pam.d/system-auth | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | rhywek |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | The relevant part of /var/log/messages showing the crash of gdm. |
Description
rhywek
2007-11-13 23:59:59 UTC
Created attachment 135925 [details]
The relevant part of /var/log/messages showing the crash of gdm.
this is more likely to be an upstream issue. Try reporting this to either the pam module developer or on bugzilla.gnome.org. what's going on here ? Is it fixed in 2.20, was a bug filled upstream ? please get back to us I have an almost identical setup to the one in the report. Seems this problem still exists when using: gdm-2.20.3 pam-0.99.9.0 thinkfinger-0.3 I don't know if any bugs have been reported upstream to the PAM people, I'm about to check that out. Looks like nothing has been submitted to ThinkFinger. Meanwhile, I ran through GDM code and put in some gdm_debug()s. Now I don't know how GDM works - first time I looked at it's code - but anyway, the last debug message that gets printed seems to be in daemon/pam-verify.c just before if ((pamerr = pam_authenticate (pamh, null_tok)) != PAM_SUCCESS) { I enabled PAM debugging but didn't see anything interesting. Also noteworthy: There is a bug logged against ThinkFinger, someone says it makes their sshd segfault. Finally: It's known that ThinkFinger can crash gksu/gksudo because of the "Password:" prompt. Even with the prompt changed back to "Password:", GDM still segfaults. |