You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Libreoffice snap cannot read files from the /tmp directory. Running libreoffice /tmp/some-file-that-exists.docx from the command line results in libreoffice being launched and then reporting
before closing again when you hit OK - even though the file does exist and is readable by the current user. The syslog indicates that apparmor is intervening to block this.
It is not possible to open files from a web browser, mail client, or other applications that save documents to /tmp, since the same thing occurs. I have only encountered this problem since switching to the snap version of libreoffice, so presume it's an issue with the snap configuration and how it interacts with apparmor.
I've checked whether there are other snap interfaces available I could connect to for libreoffice to overcome this, but the only ones the libreoffice snap provides and is not already connected to are bluez and cups-control, and they are unrelated.
For info, I'm also having problems working with files on samba shares using the snap package, which I wasn't having before that. With the snap package, I can only obtain read-only access to files on a samba share. I haven't investigated yet, but I suspect the cause of the problem may be similar, but this time relating to /run/user/<uid>/gvfs/... rather than /tmp.
Details
(I've obfuscated some system-specific information in the output below.)
Problem
Libreoffice snap cannot read files from the
/tmp
directory. Runninglibreoffice /tmp/some-file-that-exists.docx
from the command line results in libreoffice being launched and then reportingbefore closing again when you hit OK - even though the file does exist and is readable by the current user. The syslog indicates that apparmor is intervening to block this.
It is not possible to open files from a web browser, mail client, or other applications that save documents to
/tmp
, since the same thing occurs. I have only encountered this problem since switching to the snap version of libreoffice, so presume it's an issue with the snap configuration and how it interacts with apparmor.I've checked whether there are other snap interfaces available I could connect to for libreoffice to overcome this, but the only ones the libreoffice snap provides and is not already connected to are bluez and cups-control, and they are unrelated.
For info, I'm also having problems working with files on samba shares using the snap package, which I wasn't having before that. With the snap package, I can only obtain read-only access to files on a samba share. I haven't investigated yet, but I suspect the cause of the problem may be similar, but this time relating to
/run/user/<uid>/gvfs/...
rather than/tmp
.Details
(I've obfuscated some system-specific information in the output below.)
Syslog output:
ls -l / | grep tmp
The text was updated successfully, but these errors were encountered: