No, in your VPNAppVM.
Some places (like your home directory) are persistent over the AppVMs restarts. If you modify them in your template, you will see no change in your AppVM as it will get those folders from your last shutdown. As this is modifying a file in your home, you need to do this in your actual running AppVM.
At what specific command? They all seem fine to me, looking at the permissions. But i think i know where the error is: Your username is not user!
So quick linux Bash 101:
Alternatively you can do all of this manually. Here is what those commands do:
Creates an “autostart” directory in /home/user/.config/ and any parent directories needed.
Writes:
[Desktop Entry]
Type=Application
Name=Nordvpn connect
Exec=nordvpn connect <country>
To the file /home/user/.config/autostart/nordvpn-connect.desktop
chmod +x /home/user/.config/autostart/nordvpn-connect.desktop
makes this file executable.
As you might not use user for your name, one can use variables, as the term $HOME (or ~) will point to your home directory, regardless of your name. The directory /home/ holds all your user directoriers. If your are called “userA” on your qubes, your only have permission to write to your $HOME which would be /home/userA. Therefore the creation of (or stuff in) /home/user/ is denied.
Here is a name independed version that should work:
mkdir -p $HOME/.config/autostart
cat << EOF > $HOME/.config/autostart/nordvpn-connect.desktop
[Desktop Entry]
Type=Application
Name=Nordvpn connect
Exec=nordvpn connect <country>
EOF
chmod +x $HOME/.config/autostart/nordvpn-connect.desktop
I know, this stuff seems hard at first, but try to understand what is going on. It will help you a lot for your understanding of how linux works “under the hood”.
Extra!
cat does read files to your terminal. But with
cat << EOF
hello
EOF
You instruct it to read the next lines below that command, until it reads EOF (can be anything else too).
With:
cat << EOF > somefile
content of somfile
EOF
You instruct it to read the next lines until EOF, but instead of writing it into your terminal, it writes that to the file somefile.
If it still fails:
Try doing this manually or at least step by step. If one command does not work, try posting the whole error message, of everything so we can see what command fails, and how exactly.
