Cant get autostart to work

[ahaz86]

Hello, I have read through many posts on here about getting autostart working on the pi 2 running Jessie.

Things I have tried
1. Edited: sudo nano /etc/xdg/lxsession/LXDE-pi/autostart to include lxterminal
Looks like this now:

Code: Select all

@lxpanel --profile LXDE
@pcmanfm --desktop --profile LXDE
@lxterminal
@leafpad
@xscreensaver -no-splash

2. Edited: sudo nano /etc/xdg/lxsession/LXDE/autostart to include lxterminal
Looks like this now:

Code: Select all

@lxpanel --profile LXDE
@pcmanfm --desktop --profile LXDE
@lxterminal
@xscreensaver -no-splash

3. Attempted to edit: sudo nano ~/.config/lxsession/LXDE/autostart
The path didnt exist so I created each directory and the file but still no luck.

If I login as root and run the command startx applications launch though (not sure if this helps in figuring out what is going on or not)

None of these launch any application at startup
Any help is appreciated and I apologize in advance for this being such a newbie question!

Thanks!
Alex

[malicious]

3. Attempted to edit: sudo nano ~/.config/lxsession/LXDE/autostart
The path didnt exist so I created each directory and the file but still no luck.

If I login as root and run the command startx applications launch though (not sure if this helps in figuring out what is going on or not)

Autolaunch worked for root because:

sudo nano ~/.config/lxsession/LXDE/autostart

is editing the file for root's profile. Do the same edit as your regular, non-root account and leave out sudo. I am not sure why the autostart file under /etc is not working though.

[QuietZone]

Autolaunch worked for root because:

sudo nano ~/.config/lxsession/LXDE/autostart

is editing the file for root's profile.

No. Try: sudo echo ~

And then you will know who expands the ~ (and when).

Do the same edit as your regular, non-root account and leave out sudo.

This is correct advice, though. People should not get in the habit of prefixing every command with those 4 magic letters.

[JimmyN]

Maybe I can help you out a bit.

Hello, I have read through many posts on here about getting autostart working on the pi 2 running Jessie.

1. Edited: sudo nano /etc/xdg/lxsession/LXDE-pi/autostart to include lxterminal

2. Edited: sudo nano /etc/xdg/lxsession/LXDE/autostart to include lxterminal

3. Attempted to edit: sudo nano ~/.config/lxsession/LXDE/autostart
The path didnt exist so I created each directory and the file but still no luck.

1. That is the global autostart file, and works for all users... unless they have a user autostart. If the user has an autostart file the global one is ignored and the personal autostart is used. User settings are applied last and take precedence over global settings. Jessie creates a user's autostart file during the install, so changing settings in the global file no longer have any effect.

2. That is the "old" location, the new location uses "/LXDE-pi/". The "/LXDE/" directory may exist, but it will be ignored.

3. That attempt is close, but should have been "/LXDE-pi/" rather than "/LXDE/". Before Raspbian started including the users autostart (and switched from LXDE to LXDE-pi) you had to create your own "/lxsession/LXDE/autostart" to override the one at "/etc/xdg/". If you had used "nano ~/.config/lxsession/LXDE-pi/autostart" you would have been editing the correct autostart, but using "/LXDE/" it created a new file instead, but of course it won't use it.

To add to or edit your user's autostart:

Code: Select all

nano ~/.config/lxsession/LXDE-pi/autostart

That file belongs to the user so don't use "sudo" to edit it.

[ahaz86]

To add to or edit your user's autostart:

Code: Select all

nano ~/.config/lxsession/LXDE-pi/autostart

That file belongs to the user so don't use "sudo" to edit it.

THANK YOU SO MUCH!!!! Ugh... I cant believe it was this simple.

[gordon77]

It's usually easy when you know the answer

[JimmyN]

THANK YOU SO MUCH!!!! Ugh... I cant believe it was this simple.

You were all around it but hadn't quite hit the right combination.

[drips]

Hi. Sorry for bumping, but I still have the same problem.
I am very new to Raspberry Pi and Raspbian, so it may be a simple solution.

I am trying to autostart midori, but the Pi just boots to the default screen. I've done what you guys said and used the autostart
" nano ~/.config/lxsession/LXDE-pi/autostart "

And this is what my autostart looks like:

@lxpanel --profile LXDE-pi
@pcmanfm --desktop --profile LXDE-pi
#@xscreensaver -no-splash


@xset s off
@xset -dpms
@xset s noblank
@midori -e Fullscreen -a http://google.com

I appreciate all the help I can get!

[muuh]

same here (for 2017-02-16-raspbian-jessie), by trying to start a script with

@~/.script.sh

where ".script.sh" is chmod 744 (or 777). the script works by manually starting it. any hints?

[KLL]

~/.script.sh

? what is the file name?
i think its script.sh or absolute /home/pi/script.sh or ~/script.sh

to start it use
./start.sh
but when you are not in /home/pi/ must start it with
. ~/script.sh
where there is a "blank" between "." and "~"

! this has nothing to do with the way you want do auto start, just with the way to call your file !

[gordon77]

Hi. Sorry for bumping, but I still have the same problem.
I am very new to Raspberry Pi and Raspbian, so it may be a simple solution.

I am trying to autostart midori, but the Pi just boots to the default screen. I've done what you guys said and used the autostart
" nano ~/.config/lxsession/LXDE-pi/autostart "

And this is what my autostart looks like:

@lxpanel --profile LXDE-pi
@pcmanfm --desktop --profile LXDE-pi
#@xscreensaver -no-splash


@xset s off
@xset -dpms
@xset s noblank
@midori -e Fullscreen -a http://google.com

I appreciate all the help I can get!

I tried this on mine and it works , BUT I needed to 'sudo apt-get install midori ' first..

I use the latest Raspbian (NOT Noobs)

Code: Select all

@lxpanel --profile LXDE-pi
@pcmanfm --desktop --profile LXDE-pi
@xscreensaver -no-splash
@point-rpi

@xset s off
@xset -dpms
@xset s noblank
@midori -e Fullscreen -a http://google.com

[wheresmattdamon]

same here (for 2017-02-16-raspbian-jessie), by trying to start a script with

@~/.script.sh

where ".script.sh" is chmod 744 (or 777). the script works by manually starting it. any hints?

Hi, sorry to bump the thread.
For anyone coming here in the future, to autostart a ".sh" script, you need to add "sh " between the "@" and the file path, so that your entry looks like "@sh ~/.script.sh" instead of "~/.script.sh".