The workaround suggested for this bug of putting the umask setting in /etc/gdm/Init/Default doesn't work. Hardly surprising really as that script ends with an "exit 0" line, so whatever instance of the shell was executing it dies, and the modified umask dies with it.
The workaround which actually works is to put the umask specification in /etc/gdm/Xsession, as suggested in bug #314791. I put it just after the "Beginning session setup..." message so that it would affect as much as possible, and it doesn't seem to get messed up again by gdm. This is a horrible bug. I've spent half today re-discovering it. Once you've worked out that it's gdm doing the dirty deed it's easy to find previous records, but until that particular piece of information falls into place it's a stinker. I hate to think how many other people have wasted that much time on it. -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
