And the symbolic link workaround doesn't cure the problem; I'm still
getting write errors saving a file to an NFS mount, but /without any
apparmor messages/.
$ ls -l /etc/apparmor.d/disable/
total 0
lrwxrwxrwx 1 root root 52 May 20 12:15 usr.lib.libreoffice.program.oosplash ->
This apparmor problem -- preventing saves on remote filesystems -- is
suddenly back on Libreoffice 6.
$ soffice --version
LibreOffice 6.4.7.2 40(Build:2)
$ uname -a
Linux prospero 5.4.0-58-generic #64-Ubuntu SMP Wed Dec 9 08:16:25 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux
$ cat /etc/lsb-release
This issue was specific to the deb package, not the snap.
Regarding the snap, it is a known limitation. If you can mount your separate
partition under /media or /run/media, then connecting the removable-media
interface (snap connect libreoffice:removable-media) should make this work for
you.
I just did a dual-boot clean install with W$10 and Ubuntu 18.04, with a
separate partition for my files, auto-mounted via fstab edit. I did a
'minimal install', and added LibreOffice via the software centre, which
delivered me the snap version.
If I understand the last few comments correctly, the
Thank you!
So this behavior is freezed and I cannot expect a "fix" for this?
Opening documents directly in the home directory is intended to only
work read-only?
We also have libreoffice extensions which require accessing files in the
.hidden directory.
If I move them to the documents
Please continue this discussion on bug #1766192, this bug tracked a
differente issue and is now closed (would you mind copying that last
comment there?). Thanks.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
Ack. This is expected, the "home" interface for snaps doesn't allow
reading/writing files to .dot directories directly under $HOME. This is
to mitigate access to sensitive information. See
https://docs.snapcraft.io/reference/interfaces.
--
You received this bug notification because you are a
One more issue:
Opening
* /home//.Hidden.odt DOES NOT WORK (access denied)
Opening
* /home//Document.odt DOES NOT WORK
(LibreOffice complains that it can't create a lock file (which is a
hidden file), and opens the document only read only)
Seems that accessing hidden files in the first
I have installed libreoffice manually as snap with the command "sudo
snap install libreoffice".
Ubuntu 18.04
libreoffice build ID: libreoffice-6.0.4.2-snap1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
Dominik, can you confirm that this is when running libreoffice installed
as a snap? (check the Build ID in the about dialog)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1751005
Hello!
I find it weird that accessing
* /home//.hidden/Document.odt DOES NOT WORK
* /home//Documents/.hidden/Document.odt WORKS
* /home//myfolder/.hidden/Document.odt WORKS
We have several applications which access documents under
/home//.hidden which now does not work any more. Of course I
** Bug watch removed: Document Foundation Bugzilla #116086
https://bugs.documentfoundation.org/show_bug.cgi?id=116086
** Tags added: regression-update
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
Thankyou Oliver that worked.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1751005
Title:
libreoffice cannot open a document not within $HOME
Status in libreoffice package in
David, that bug was for the version of libreoffice in the ubuntu
archive.
The snap is a different thing altogether. With it, you should be able to
access your files under /media by issuing the following command in a
terminal:
snap connect libreoffice:removable-media
Files in other locations
I have just updated Ubuntu 17.10 and LibreOffice 6.0.1.1 snap1, Rebooted my PC
(even though it did not ask for it. Tested and still do not have access to my
media/Acer files, access denied. Works fine in home directory. Also tried a
libreoffice spread sheet file (with macros) in my home
I ran into a similar problem on Ubuntu 17.10 that I think is related to
the apparmor profile, because it appeared recently, but has gone away
with the newest release. I have an ODT file (in my home folder) that
has no ".odt" at the end of the filename.
It has never had problems in the past
Thanks for the report @magowiz!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1751005
Title:
libreoffice cannot open a document not within $HOME
Status in libreoffice package
> if we executed the preliminary work around to disable the profiles,
> do we need to take action to revert those and go back to "stock"
> configuration?
No, no further action is needed on your part, as the update does
essentially the same as the workaround you applied.
> what about the snap
So 2 questions still remain:
- if we executed the preliminary work around to disable the profiles, do we
need to take action to revert those and go back to "stock" configuration?
- what about the snap version of LO? As I mentioned it does not honor "classic"
confinement
--
You received this
I see, so libreoffice staff generates their own apparmor profiles, thank you
for the explanation.
Here it is the upstream bug report :
https://bugs.documentfoundation.org/show_bug.cgi?id=116086
I hope I've been clear in explaining the issue.
** Bug watch added: Document Foundation Bugzilla
@magowiz: yes, the apparmor profiles are maintained as part of the
upstream project (here:
https://cgit.freedesktop.org/libreoffice/core/tree/sysui/desktop/apparmor/),
so issues with them should be filed upstream.
--
You received this bug notification because you are a member of Desktop
@Olivier Tilloy (osomon): in response to #47 :
I don't understand, do you mean that the fact that apparmor blocks the opening
of xlsm files (xls with https://fileinfo.com/extension/xlsm) by libreoffice is
a libreoffice upstream bug?
This type of documents can be opened if the libreoffice
Apparmor profiles were not enabled before the 1:5.4.5-0ubuntu0.17.10.1 SRU.
The SRU accidentally enabled them and broke a flurry of use cases. That was a
very bad regression.
The 1:5.4.5-0ubuntu0.17.10.4 SRU disabled them again. Regression fixed, hence
the status.
We will work towards enabling
If the bug is that terrorists abruptly divert aircrafts into high buildings,
then the total disabling the whole air traffic IS NOT A BUGFIX, but it is a
TEMPORARY WORK AROUND only! The real bug fix is when you reopen the public
air traffic with a better safety configuration!
To disable the
I can confirm that the just released version 1:5.4.5-0ubuntu0.17.10.4
fixes the problem for me. No more issue opening files from within a
/srv hierarchy.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
This bug was fixed in the package libreoffice - 1:5.4.5-0ubuntu0.17.10.4
---
libreoffice (1:5.4.5-0ubuntu0.17.10.4) artful; urgency=medium
* debian/libreoffice-common.preinst.in: added to disable apparmor profiles on
fresh installs and upgrades from 1:5.4.5-0ubuntu0.17.10.1
@magowiz: thanks for confirming! Can you please file a bug against the
upstream project (https://bugs.documentfoundation.org/enter_bug.cgi) to
track the issue with the xlsm extension?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Ok Christian I tried with an odt, I removed links
/etc/apparmor.d/disable/usr.lib.libreoffice.program.* and I rebooted to
be sure to restore apparmor in previous state.
With odt file I can open it while it is in my home directory, I cannot open it
if it is elsewhere,
so in this case the issue
It looks like the "xlsm" extension is not included in the profile
(checked with upstream LibreOffice 6.0.1.1). [Unless someone fixes this
quickly and says so, this is probably worth a separate bugreport.]
To find out if the encrypted partition is a problem, try to open a file
with a more common
just to add mine experience :
libreoffice v. 5.4.5-0ubuntu0.17.10.1 ubuntu 17.10
I cannot open files at all, even if they are in /home/${USER}/ , I
copied an xlsm file to ~/ and I cannot open it, disabling apparmor
profile did the trick.
Does the issue came out because I got an encrypted home
Very sorry. I was exploring the site and didn't understand the purpose of
the button. I was surprised to find that I had changed the status and was
even more surprised that having changed it I hadn't the authority to change
it back.
On Mon, Feb 26, 2018 at 10:54 PM, Olivier Tilloy <
Hello everybody,
Thanks to informations given in #10 comment, I fully managed to get my LO work
perfectly.
I can tell you this bug gave me hard headache because I wasn't able to
open the documents I created myself and needed them to give my student
their diplomas ...
Thanks a lots :-)
Hope
Please do not change the bug status. The fix is being tested and hasn't
been released yet.
** Changed in: libreoffice (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in
I Just did an update of Ubuntu 17.10 and Libreoffice6 and still have the same
problem with access denied on the windows partition of my hard disk. In Ubuntu
Home directory all is fine. Problem with access only occurred after carrying
out updates of Ubuntu 17.10 & LibreOffice (5.3 to 6) on the
** Changed in: libreoffice (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1751005
Title:
libreoffice cannot open a document
Updated fix:
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?id=87024bdf8f6900b9ee2e757cb9027d0c98f6e7bf
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
Same problem here. Since installing 1:5.4.5-0ubuntu0.17.10.1.
My files are located in /daten/, where I have a complex structure with
multiple volumes, which is identical over all my machines and never made
any problems since 15 years.
If this is not ok anymore, because it's not LSB, this rule
I have the libreoffice snap installed using classic confinement, yet I
seem to have this issue. By comparison the Atom snap works as expected.
Is the libreoffice snap version impacted by this as well?
--
You received this bug notification because you are a member of Desktop
Packages, which is
Hi,
I cannot read LibreOffice docs under /home/$USER/ in Artful either.
I hope it's fixed, though in the meanwhile, shall we disable the apparmor
profile?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
Hi
Unable to create or read document files in normal $HOME /home/userid/
Both in Artful and Bionic (1:5.4.5-0ubuntu0.17.10.1)
What a fail. Please never try that again.
--
Johan Thelmén
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
OK. Thank you ads2. I think, it really complicates the system for a
home user. I'm completely happy with the restrictions per user. I know
many home users, who even run into problems with that.
At the moment I have some VMs running LibreOffice 5.1 and 6.0 and those
have no AppArmor issues.
BertN45 you can read this: https://wiki.ubuntu.com/AppArmor
As I understand it, an AppArmor profile on a program restricts what it can do
to your computer, whereas without AppArmor or something similar to it, a
program will have unrestricted access to your computer (except for what
requires
OK, but where can I find, what the purpose is of this functionality? How
could it improve my security? Do you have any reading material?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
To everyone affected, please read again comment #24. An update is being
prepared that will disable the apparmor profiles by default, effectively
reverting to the old behaviour.
Enabling the profiles by default on upgrade was not intended, it's a
human mistake.
--
You received this bug
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
If AppArmor configuration is needed for mounted directories, I think we
need better information pushed to the users. If you say "add all your
mountpoints with user files need to be in file X" I am fine with that. I
just need to know.
Goes for snaps as well.
And I still think AppArmor provides
edit /etc/apparmor.d/tunables/alias
add the line: alias /home/ -> /data/
On 24.02.2018 10:10, sandeep wrote:
> I am also facing the same issue.
>
> I am using Ubuntu 17.10 as my daily driver. I have created a separate
> partition like home for storage /data of ext4 type.
>
> Today, after
I am also facing the same issue.
I am using Ubuntu 17.10 as my daily driver. I have created a separate
partition like home for storage /data of ext4 type.
Today, after updated my system using apt dist-upgrade. I am unable to
access all my documents from /data partition.
--
You received this
As more applications get AppArmor profiles, this may come up more
frequently.
Installations with "home directories" not under /home/ may want to
install AppArmor alias rules so that user-oriented tools with profiles
can function as desired. The usual place to write them is in
Fixed with
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?id=98706ce75e58ac57e02f0fb52050903376f18171
** Changed in: libreoffice (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages,
There are enough real use cases that got broken that this warrants a SRU
to disable the apparmor profiles by default. Thank you for the feedback
everyone, I'm working on that, expect another update as soon as
possible. In the meantime, comment #10 explains how to disable the
profiles yourself.
**
I'm experiencing the same issue with files mounted under
/mnt/user/sshfs/user@server/home/user where user is the username of
the individual and server is the server they are accessing. This means
/mnt is also affected.
Removing the apparmor rules resolves the issue.
I have to say I agree
First a question for clarity: is this apparmor issue related to having
libreoffice installed as a snap, or is this native to the archive
version as well?
Second: I honestly can't grasp these kind of policy changes are rolled
out without having the slightest idea on what impact this might cause on
Same issue here. My documents are on a NFS share on /media/commun/ .
Assuming that all documents are in /home is kind of stupid... What about
all the companies that use shares (NFS or others...) ??
I solved my problem with the worst answer : stop and disable apparmor.
Security without usability
I was running into the same issue after the latest upgrade of 17.10 and
libreoffice, and I tried a couple of things that have both failed. I
have my libreoffice files sitting on FAT filesystem that I mount in
fstab. Earlier I was mounting it at /data which I changed to /mnt/data.
Yet I am unable
Eventually those apparmor changes will hit the backported PPA builds
too.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1751005
Title:
libreoffice cannot open a document not
actually to avoid all of this:
sudo add-apt-repository ppa:libreoffice/ppa
sudo apt-get update
sudo apt-get upgrade
libreoffice starts without any tweaks and you are running the latest and
greatest
--
You received this bug notification because you are a member of Desktop
Packages, which is
I have just run upgrades, and am now at LibreOffice 5.4.5.1 on Kubuntu
17.10 . I found this thread because I had the "access was denied"
issue.
My Thinkpad has original Windows 7 disk (where data is obviously stored
on NTFS), and a mSATA on which I have a triple boot install (i.e.
Kubuntu 17.10,
> deny access to my owned files if not under $HOME.
> Is this a good default?
That's arguable of course. The expectation is that a vast majority of
users will have a default setup where they store their documents under
$HOME/, and for those the confinement provided by apparmor will be
useful and
Exotic?
I am a developer and run several different flavors of Linux for testing.
I have done this for years for files accessible to all flavors.
If the file ownership and permissions are OK, I think I should be able
to access them by default. Apparmor seems to be configured to
another default
After getting over the confusion caused by your example, and inputting
the entire command on one line, it did solve the problem. Thanks. The
diagnostic could have been less cryptic.
On 22.02.2018 12:06, Olivier Tilloy wrote:
> The error message about
>
@Jan: if you mount your external disk under /mnt or /media (and change
your symlinks to point there), that should allow you to use libreoffice
confined, which IMHO is better than permanently disabling the apparmor
profiles.
@Nick: the files you're attempting to open are neither in your home
Hi, I have the same issue - with a relatively new vanilla install of
17.10 - the last upgrade broke the ability to load the file with the
same permission denied
disabling the apparmor profile fixed the issue
--
You received this bug notification because you are a member of Desktop
Packages,
setup is actually like this:
user data is on an extra disk. that disk is mounted in fstab
UUID=7707da2d-a878-40db-9311-f53ed74c821f /export ext4 defaults 0 1
then soft links for /home/janw to /export/home/janw is done.
yes that is not standard i know..
but it makes reinstallations of OS
No, that's not a solution, because as soon as libreoffice 6 is in the
ubuntu archive it will have the working apparmor profiles. If you want
to disable the apparmor profiles permanently, you can do the following:
sudo ln -s /etc/apparmor.d/usr.lib.libreoffice.program.*
think i understand now. i guess what the apparmor_parser command does is
to temporarily disable the profiles for libreoffice.
and disable it permanently does not sound like a good idea. i guess.
so: i guess the solution is to get a new version of libreoffice. right?
--
You received this bug
as you said: this is temporary. how do i make it permanent?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1751005
Title:
libreoffice cannot open a document not within $HOME
okay. looks promising.
i did this:
sudo ppa-purge ppa:libreoffice/ppa. now libreoffice 5 installed again
and gives the error.
sudo apparmor_parser -R /etc/apparmor.d/usr.lib.libreoffice.program.*
libreoffice starts up and seems to be working..
--
You received this bug notification
i have to downgrade libreoffice first i guess.have no
installation left with libreoffice 5 for the moment
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1751005
Title:
Jan, if you installed LO 6 from the PPA, it might not have all the
required fixes for the apparmor profiles. But the version in the archive
(currently in bionic-proposed) will have them.
Can you please confirm that the command I suggested in comment #3
resolves your issue (that's temporary until
olivier: i read your answer and is a bit confused. why does upgrading to
libreoffice 6 not suffer from this problem?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1751005
Title:
The error message about
~/.libreoffice/{3,4}/user/config/javasettings_Linux_*.xml is unrelated,
it is simply telling you libreoffice cannot find a JRE (but it will work
fine without it, for the most part).
What you're seeing is apparmor confinement finally working as intended. The
package had
I get the problem with system complaining about permissions on
.config/libreoffice/4 since latest libreoffice upgrade on ubuntu 17.10.
This problem has arrived on 3 installs up to now. Only solution I have
found is to add the ppa on libreoffice and upgrade it to the latest
libreoffice 6. Then it
73 matches
Mail list logo
