severity 336214 normal thanks This bug really is a gdm bug, in that it overrides (rather than ignores) configuration values, so I'm setting this at important instead of "minor" (it would be minor or wishlist in case it fails to read configuration outside of /etc/gdm, but as outlined below, that's not the issue). I've been thinking of raising this to RC severity, but that may be overdoing it; I'll leave that to your prerogative.
I have a system set up with pam_umask in common-session; yet after logging in with gdm, umask is set to 0022. The reason isn't hard to find; grepping through the gdm source code reveals several instances of hard-coded "umask (022);", which destroys everything that may have been set up through PAM or otherwise. Workaround: set the umask in /etc/gdm/Init/Default. Doing this in scripts in /etc/gdm/PostLogin, .../PostSession, and the script /etc/gdm/Xsession will fail, because gdm still will muck with those settings afterwards. -- <Lo-lan-do> Home is where you have to wash the dishes. -- #debian-devel, Freenode, 2004-09-22 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
