Why do you even have command to create symlink in the script? Once a link is created, doesn't it work whenever the source is available? When you say it works when the script is run manually, does it ask for any password for you to input? If so, may be the password method you put in your script is not working. I still think it is possible your drive is not ready by the time link command runs or there is problem with permissions when run from script. That said, I try to help others by just asking some questions that may be obvious but many times missed. I did not get head or tail of the code you mentioned.

Other items in my auto-run script (calling Veracrypt, triggering pCloud once Veracrypt mounted) work fine on both systems and the refreshing the symlink works fine on Ubunt I'm afraid I can't be of help wrt codes. However when I run the script manually it works fine. This doesn't refresh the symlink on start-up. To try and isolate the problem I've created a seperate script to run on start-up so that I can work directly on solving it. Ln -sfn '/home/me/pCloudDrive/path/Work Dump' '/home/me/Desktop/Work Dump' This works perfectly at the end of my auto-run script in Ubuntu 18.04 by having On both desktops I have a symlink to a folder called 'Work Dump' which points to a folder in pCloud where I keep the documents that I'm currently working on.īecause my pCloud partition is only mounted after I decrypt a Veracrypt partition I need to recreate the symlink to Work Dump on each boot. Both are set up in a similar fashion and I use pCloud to synchronise my documents across both devices. I've 2 systems, one running Mate 20.04 and the other Ubuntu 18.04.

Ubuntu pcloud