Sorry, I forgot about this due to other duties (work and school).
This is not an active issue for me, but would be a nice touch to Ubuntu.
This still happens in Oneiric (tested in daily). There are some differences,
it just drops you into the default login screen without any explanation.
Which is
Right forgot about the variables.
After poking around in dash source I found that "$HOME/.profile" has
been hardcoded. So the change needs be made in the shell to make
".profile" safe.
Also I found a way to keep the variables from subshell
### test.sh ###
ERRCODE=0
TEST=""
VARS=$(set -e; . $HOME
The idea is simple:
###
VARS=$( # this allows to capture subshell stdout to a variable
. $HOME/script.sh 1>/dev/null # this prevents script printing something to
stdout
set # this prints all variables to stdout
alias | sed 's/.*/alias \0/' # this prints aliases to stdout and prefixes them
For the sed/eval round we can always escape the special characters
beforehand, there should be some function for that.
But I agree with your conclusion. Warning or message is a good enough
solution, even though I would like to see some hand-holding. I agree it
just isn't worth the effort and the o
Sure, silently just ignoring is just as bad. I just think that, it's a
mistake that shouldn't prevent you to login and start up everything.
The ~/.profile script can also easily be changed by non-experienced
users (ones who may not know terminal that well). If that user doesn't
get the session run
Public bug reported:
Binary package hint: gdm
After adding "function AddPath { PATH="$1:$PATH" }" to $HOME/.profile
made the Xorg startup fail. (At that moment I had already forgotten the
changes made to the .profile). As I had autologin that meant it kept
trying to login and finally showed me th
