Weird that it doesn’t work. The usual way to run scripts on startup is through systemd units though. That has the added benefits of automatically logging all output and letting you control it through commands like systemctl enable <unit name>. It’s a really neat system, and I highly recommend learning it if you see yourself doing this kind of automation more often.

I’ve found out the hard way: Running the script during startup, and running it using the proper user authorization, are two different things.

When all else fails…

crontab -e

@reboot sleep 300 && sudo ./myshell.sh

(this is actually broken on some distros)