.bash_profile not run when using graphical login

[John]

Martin Maney wrote:
> On Wed, Oct 06, 2004 at 10:43:50AM +0800, John wrote:
> 
>>Martin Maney wrote:
>>
>>>On Wed, Oct 06, 2004 at 12:26:13AM +0100, Colin Watson wrote:
> 
> 
>>>>That was deliberate, actually, since otherwise there's no way to recover
>>>
>>>>from e.g. fsck on your root filesystem failing. We were happy to do this
>>>
>>>Really?  That's odd, because I have, from time to time, had fsck fail,
>>>and it wasn't impossible to recover as you suggest it must be.  It's
> 
>    ...
> 
>>>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.  
> 
> 
>>On Debian, how do you get to single-user mode if root is disabled?
> 
> 
> Dunno, I've never disabled root.  Never really thought about it until I
> ran into it in Ubuntu.
> 
> And what does that have to do with recovering from a failed fsck, when
> any of the pieces you need may be missing?  There are quite a lot of
> pieces between mounting the root ro and getting a shell prompt, only
> one of which is passwd - two, I suppose, with shadowing.
> 
> Oh.  Wait.  Did you mean only that going straight to the root prompt
> was the only way to get to work when root login is disabled?  Yeah, I
> knew that.  That was where I started - with the assumption that this
> was a cost of disabling root login.  If that was all you meant then I
> was trying to read more into your reply than you meant to say.  Sorry
> if that's what's been going on.
> 

Seemed to me that's what Colin meant.