Jack O'Quin <joq@io.com> [2002-11-08 23:13:49 -0600]: > > This is frustrating, because putting "umask 002" in ~/.profile or > ~/.bash_profile has no effect under gdm. /etc/profile doesn't seem to > run, either, or it would fix this problem. Why not? Neither Gnome nor KDE seem to run tell the shell it is a login shell at any time. The desired behavior would seem to be that the shell that starts up gnome would be told it was a login shell so that it would source the appropriate and expected places. Only that shell needs to act like a login shell and subsequent ones will be normal. > Debian appears to be carefully constructed to support user groups. My > login and group names and numbers are both the same, so 002 should be > the correct umask value. Agreed. > Is this just a bug, or did I misconfigure something somewhere? I > don't see this listed as a gdm bug. Should I report it? It seems like a bug to me. I know just enough to be dangerous here. I don't use gnome myself so take this with some caution. But a friend told me that the gnome login manager looks for ~/.gnomeprofile. I am told it needs execute permission whereas normally .profiles do not and should not need this. Also, gdm runs a .gnomerc if it exists. This must start up a gnome session if it does exist but can do whatever else you want. (Like run ssh-agent.) This is all hearsay for me but perhaps it will help. Bob
Attachment:
pgpBUWfCqHhDG.pgp
Description: PGP signature