At our university, we use a network-mounted /home directory, but it is inherently slow. Every employee is advised to store data that doesn't have to be shared among all systems in their local /scratch directory structure on that machine (desktops, practically), which is backed up regularly. So there you have a perfectly valid reason for using neither /home nor /media.
I'm speaking from an end user perspective, and it's completely inconceivable that I cannot access arbitrary files on my system. I have a snap application where I can hit "File > Open" in the menu, and the dialogue displays my Ubuntu shortcuts. All of them point to locations somewhere in /scratch. When I click on them, they don't open, and I had all kinds of suspicions but this. So really, from a user perspective, this is most definitely a bug.
Using symbolic links doens't work, and since I don't have root access to the machine, I cannot simply re-mount devices. Is there any way to work around this until the fix actually reaches users (Ubuntu 18.04, again with no choice over the OS version)?
At our university, we use a network-mounted /home directory, but it is inherently slow. Every employee is advised to store data that doesn't have to be shared among all systems in their local /scratch directory structure on that machine (desktops, practically), which is backed up regularly. So there you have a perfectly valid reason for using neither /home nor /media.
I'm speaking from an end user perspective, and it's completely inconceivable that I cannot access arbitrary files on my system. I have a snap application where I can hit "File > Open" in the menu, and the dialogue displays my Ubuntu shortcuts. All of them point to locations somewhere in /scratch. When I click on them, they don't open, and I had all kinds of suspicions but this. So really, from a user perspective, this is most definitely a bug.
Using symbolic links doens't work, and since I don't have root access to the machine, I cannot simply re-mount devices. Is there any way to work around this until the fix actually reaches users (Ubuntu 18.04, again with no choice over the OS version)?