-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
On Tue, Aug 23, 2005 at 11:50:10AM -0600, Hubert Chan wrote: > Since I upgraded from xdm 4.3.0.dfsg.1-12.0.1 to 6.8.2.dfsg.1-5 (another > bug prevented me from using versions in between), libpam-mount no longer > mounts my encrypted partition. Logging in from the text console works. [...] > - from xdm: > pam_mount: command: /bin/mount [-t] [crypt] > [-ocipher=twofish,hash=sha512] [/dev/hda8] [/home/hubert] [clientWindow] > and > pam_mount: command: /usr/sbin/pmvarrun [-u] [hubert] [-d] [-o] [1] > [statusAttributes] I tried to reproduce your bug and xdm just crashed. I don't even see anything from pam_mount. So where the heck are the "clientWindow" and "statusAttributes" parameters coming from? There must be some memory corruption which affects the argument lists. Looking at the somewhat confusing xdm source code (gah) I don't think it will be easy to fix this. Regards, Bastian - -- ,''`. Bastian Kleineidam : :' : GnuPG Schlüssel `. `' gpg --keyserver wwwkeys.pgp.net --recv-keys 32EC6F3E `- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDDK3beBwlBDLsbz4RAiqGAKDKPbTdd1XpK4HFewqLActObRpnRACfUCfi qn3SMr6L1hsCdmxHWmdZ+0Q= =u5/f -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
