I hate these type of surprises, caused by badly designed and/or published improvements. The professional way to introduce those changes, is enabling the new intrusive function in the settings function of the program introducing that change.
I store all my files in the Virtualbox Shared Folders on a separate partition, because they are in principle accessible by all my virtual machines, who need them and I have VMs for: - the normal office work - banking and other financial apps - to try out new apps - windows for compatibility with old files - to try-out alpha and beta releases of the OSes I avoid the use of the home folder for documents, since it is a dirty mix between computer settings and documents. I only use Home for my local settings and store my document in a separate set of folders on a separate partition, not influenced by any OS changes. I do not intend to change that set up. The Vbox shared folder files are owned by the root and I could get read and write access, by becoming a member of the vboxsf group. I do not intend to change all my "/etc/apparmor.d/tunables/alias" files in my VMs. Probably I will simply upgrade to LibreOffice 6, not having any access problem yet or I use Microsoft Office again in my Windows VM. I have been in IT since 1969, but I have no clue what you hope to achieve nor how it could improve my situation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751005 Title: libreoffice cannot open a document not within $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1751005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
