The libreoffice 6.0.0 snap is ready for testing in the candidate channel. It has received a fair amount of smoke-testing, and according to the download statistics it has a large number of users.
We are keen on hearing from users for whom the snap doesn’t work well enough, or is not on par with the packages in the ubuntu archive (or your other distribution of choice, for that matter).
Please describe here your use case and expectations, and how the snap doesn’t meet them. We’ll turn those into bug reports that we can then address to raise the quality and usefulness of the libreoffice snap.
This has been in progress for a while, the most recent update is here.
This should be fixed, please comment on this thread saying it isn’t working on LibreOffice (linking back to your post here) and give them the output of snap version and the tracking and installed lines of snap info libreoffice and snap info core.
E.g. my LibreOffice snap version
$ snap info libreoffice
installed: 188.8.131.52 (53) 419MB -
$ snap version
$ snap info core
installed: 16-2.31.1 (4110) 85MB core
I suspect this is related to this bug but please can you file a new one (make sure to add ‘[snap]’ to the start of the bug title and add the ‘snap’ tag to the bug report)?
Ubuntu 18.04 here, using libreoffice 184.108.40.206 (63).
I’m sorry to report this, but LO in this form remains hardly usable:
Impossible to open documents on SMB shares mounted through Nautilus (yes I do have :removable-media enabled for libreoffice)
Impossible to open documents owned by another user.
Impossible to open documents in /tmp (the confined package has its own /tmp). This is especially annoying, since /tmp is where Thunderbird saves attached files by default. In practice this means it’s impossible to open directly a file received by email.
Impossible to sign documents using gnupg (due to no access to ~/.anything), which particularly a problem when preparing more complex templates with macros.
The current confinement is way too strict for a desktop office software suite. The problem, in my opinion, is that snap was primarily designed for a mobile phone environment, with a confinement that somewhat makes sense there, but is absolutely impossible to use on a desktop. I’m not that familiar with XDG Portals that snap will start supporting in the next cycle, maybe that would alleviate some of the problems. In the meantime, a solution could be to switch to a Classic confinement?
I think this a problem that the snap interfaces should address. Deciding that apps can’t access files owned by someone else is an arbitrary limitation that stands in the way of many legitimate and expected usage scenarios “just because”. IMO the home interface should allow the package to access any file the user can access, anywhere in file filesystem tree, in all modes the user can (read, read write, append) etc., no more, no less.
that would make having an interface at all pretty pointless
while i agree that there should be an interface that allows such access, i dont think it should be part of the home interface … snaps are used in many environments and interfaces need to be fine-grained enough to take that into account.