.bash_profile not run when using graphical login

[John]

Colin Watson wrote:

> 
>>The more I think about this, the more spurious it sounds.  The
>>assumption is that you might not be able to login because some file -
>>passwd, say - is corrupted.  But then why assume that fsck is sound? 
>>init's critical parts?  It seems like you're saving us from one or two
>>failures out of dozens of similar ones that are equally likely.  Am I
>>missing something?
> 
> 
> The point is that if we hadn't made sulogin fail open, it would ask you
> for a root password that doesn't exist, and refuse to proceed unless you
> provide it.


That is precisely what happened when I tried it on Sarge.