I have created a simple bash script called echo.sh. Which outputs a string. I've made sure its executable. And i then added it to the "startup applications" program through the GUI interface. However when i reboot my machine, it doesn't appear to of been executed, as there is no echo appearing in a terminal.

from my understanding shouldn't the script ,when executed, open up a terminal automatically from my understanding because of the STDOUT being the terminal file. However the script works fine if i launch it myself from the terminal.



echo "hello this is a bash script talking"

Making it Executable

chmod +x echo.sh

Adding to "startup applications with correct directory to file" /home/sam/Documents/bash/echo.sh


However when i reboot the system, the script doesn't run as expected, and no terminal appears with the echo message. I'm unsure as to why, and i may be completely missing the point, if so please let me know.

just to note, all my other bash scripts work , such as my "cleanup.sh" script which is also in the "startup applications" program.

Attempted fixes

I've tried redirecting the STDOUT to the terminal file /dev/tty. However this doesn't seem to work.


echo "hello this is a bash script talking" >/dev/tty

I've also tested a bash script with just a simple rm command, just to check if it was just the echo command that was having a problem. However when added to start up applications or .bashrc file, it doesn't delete the test.txt in the same directory as the script. However works when i execute manually from the terminal.


rm ./test.txt

I've also tested startup applications program itself with just opening Firefox, with just the command Firefox. Which works without an issue. So their doesn't seem to be an issue with the startup applications program itself?

  • If you want to run this script during starting terminal add it to .bashrc file. Probably it runs at startup but you cannot see the output. You can check dmesg log, but I'm not sure if it's going to be there – mrc02_kr Jul 11 '17 at 12:55
  • Thanks for the response @mrc02_kr. However it doesn't seem to work. – Hexodus Jul 11 '17 at 13:21
  • Try to avoid using relative paths in scripts. It leads to unexpected behavior and then a lot of debugging. Try to redirect echo to file: echo "bash script" > /root/test_bash.txt. Also tell us what do you want to achive ? Maybe it's a better way to do it? – mrc02_kr Jul 11 '17 at 13:37
  • Well my initial script, which called "sudo apt-get update" has similar issues. So i decided to try and start up a simple echo script. Which doesn't work. Which is really confusing as my cleanup.sh script works perfectly at boot up. – Hexodus Jul 11 '17 at 13:49
  • Don't run apt-get update at startup. Here is tutorial how to automate apt updates. – mrc02_kr Jul 11 '17 at 13:56

The script probably works, but the STDOUT of the script (wherever the output is directed to) is connected to the process on your OS that is concerned with launching startup scripts like this, which does not run in a terminal, but is a user hidden process within for example the kernel. To open up a terminal with this message you should probably edit it to

gnome-terminal -e 'echo "hello this is a bash script talking"'

(I'm not on Ubuntu right now so can't test this, but the gist is to explicitly open a terminal where you want this message to show up in)

| improve this answer | |
  • Thanks for the response, However this doesn't seem to work. – Hexodus Jul 11 '17 at 13:11
  • What happens when you enter gnome-terminal -e 'echo "hello this is a bash script talking"' in a terminal? – rien333 Jul 11 '17 at 13:28
  • Executing it manually, it flashed opened up a window and quickly closed. Not sure if it was a terminal, however from the quick flash of an application appearing, it didn't look like a terminal. When added to the startup applications and rebooted,nothing occurred. – Hexodus Jul 11 '17 at 13:37
  • 1
    @Hexodus I suggest gnome-terminal -x bash -c 'echo "hello this is a bash script talking";bash' so-that you can examine. – Pandya Jul 11 '17 at 17:44
  • ... or ad a read call to wait for the user to press Enter. – Kusalananda Mar 24 '19 at 8:15

You can check the config file of the autostart file you created with

cat ~/.config/autostart/NAME.desktop

If you want to execute your script in a terminal you should add Terminal=true to the file.
You can also set Hidden=false accordingly to what you want to achieve.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.