MeBrains
April 4th, 2010, 11:49 AM
I installed minimal karmic koala with openbox lxde on an old notebook.
when i boot up, I automatically get logged in through /etc/init/tty1.conf
# tty1 - getty
#
# This service maintains a getty on tty1 from the point the system is
# started until it is shut down again.
start on stopped rc RUNLEVEL=[2345]
stop on runlevel [!2345]
respawn
exec /bin/login -f USER < /dev/tty1 > /dev/tty1 2>&1
it starts .bash_profile:
#startx
echo "is this parsed?"
case "`tty`" in
/dev/tty1) echo "case start" && wait && startx;;
esac
and runs up to startx.
there I get the error that it can not open display 0 and that I should remove .X0-lock from /tmp
strange thing is: there is no .X0-lock. when I ty startx immediately after getting the prompt and immediately after receiving the lock error, it does work.
when i exit the command prompt and log in again. .bash_profile is correctly parsed and x starts automatically...
what can be wrong? why does it fail the first time around?
when i boot up, I automatically get logged in through /etc/init/tty1.conf
# tty1 - getty
#
# This service maintains a getty on tty1 from the point the system is
# started until it is shut down again.
start on stopped rc RUNLEVEL=[2345]
stop on runlevel [!2345]
respawn
exec /bin/login -f USER < /dev/tty1 > /dev/tty1 2>&1
it starts .bash_profile:
#startx
echo "is this parsed?"
case "`tty`" in
/dev/tty1) echo "case start" && wait && startx;;
esac
and runs up to startx.
there I get the error that it can not open display 0 and that I should remove .X0-lock from /tmp
strange thing is: there is no .X0-lock. when I ty startx immediately after getting the prompt and immediately after receiving the lock error, it does work.
when i exit the command prompt and log in again. .bash_profile is correctly parsed and x starts automatically...
what can be wrong? why does it fail the first time around?