x11-apps/xdm-1.1.6-r1 adds support for pambase. /etc/pam.d/xdm is now different, and one of the things that's different, is that now pam_lastlog.so gets loaded. xdm can't handle pam_lastlog.so, because it sends a message after xdm expects to receive no more messages. And by "can't handle" I mean it access and modifies freed memory, and in my case, this happens to crash in various ways, sometimes taking X with it (leaving me with a working console), sometimes freezing X. When X freezes, it forces me to do an unclean shutdown. Nothing else works. I can't get out of X, I can't take X down, I can't do anything at all but turn off the power. I will attach a patch shortly.
Created attachment 145395 [details, diff] xdm-pam-crash.patch The fact that this patch allows me to log in without problems should tell you pretty much everything. After XtDestroyWidget (toplevel) is called, pamconv will be called again with a message containing the last login time. Since login is no longer usable, I've made pamconv simply return an error code. I don't know what the most appropriate behaviour would be, and if returning immediately is the most appropriate, I don't know which status should be returned.
/me starts wondering what did most people test Thanks Harald, I'll package.mask the new xdm until this is fixed. Markus I suppose this is what you hit too.
Hi Diego, That sounds very much like my problem, just that in my case PAX detected the illegal access and killed xdm right away. Thanks, Markus
I'm bumping xdm to 1.1.7 without the pambase patches, so you'll need a revbump to that whenever you get this fixed.
ping here, what's the status? Thanks
I'll assume this bug is now fixed. If not, please don't hesitate to reopen. Thanks
While I'm not aware of a fix for this bug, the trigger for it has been removed and it doesn't look like it's coming back, so I'm fine with this being closed. (Sorry for not responding sooner.)
