Hi. I did a dist-upgrade and then I had to restart tint2 to see it.
So I read somewhere to change all && to & like so...
(\ nitrogen --restore & \ cb-compositor --start & \ sleep 2s & \ conky -q & \ tint2 \ ) &
And it's back normal.
Last edited by talkshowhost85 (2014-07-20 08:48:36)
"&&" means "when the command has completed successfully, then go on to the next one". It sounds like one of the processes is causing an error, which you are now ignoring.
If you run the commands in a terminal, you will probably see where the problem is happening. It may be something simple like increasing the sleep time, because tint2 was trying to start before the compositor had finished doing its thing.
Thanks guys! Maybe I'll change it again afterwards and tweak the sleeptime. The installation was messy on my part and I was too eager to see everything works. So far everything works and earlier I had a problem with bluetooth but it is ok now. But like Damo said I probably ignore some errors which I feel that I am still doing besides the autostart file
Just to note: if you're running Stable, then you shouldn't have to run dist-upgrade --- just plain old apt-get upgrade is enough
It doesn't hurt and may be better based on the following explanation:
If one is using Backports, it's probably better to use apt-get dist-upgrade. I always use the aptitude equivalent of dist-upgrade.