Bug 1898073 - LibreOffice doesn't preserve facls (create new files on save and ignores old facls)
Summary: LibreOffice doesn't preserve facls (create new files on save and ignores old ...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: libreoffice
Version: 32
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL: https://bugs.documentfoundation.org/s...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-16 10:25 UTC by Edgar Hoch
Modified: 2020-11-16 16:34 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-16 11:45:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Edgar Hoch 2020-11-16 10:25:01 UTC
Description of problem:
When LibreOffice saves a file, it removes the old file and creates a new file.
But it doesn't preserve facls.

Instead, LibreOffice should either write the new content in the same file (creating a backup file as a new file before modifying the original file), or create the new file with exact the same permissions, facls, SELinux context, etc. as the old file.


Version-Release number of selected component (if applicable):
libreoffice-6.4.7.2-3.fc32.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Open LibreOffice.
2. Create new LibreOffice document and save it
   (on a local file system, so we can use setfacl and getfacl)
3. Check facls:
   getfacl filename
4. Set some facls, for example
   setfacl -m g:wheel:rw- filename
5. Check facls:
   getfacl filename
6. Note which inode the file has, for example with stat:
   stat filename
7. Open the file in LibreOffice, change something, so it is modified, and save it.
8. Check if the file has the same or another inode now:
   stat filename
9. Check facls:
   getfacl filename


Actual results:
FACLs are lost.

Expected results:
FACLs are preserved.

Comment 1 Edgar Hoch 2020-11-16 11:56:28 UTC
Does the fact that you immediately closed this bug report mean that I should not open a bug report at Fedora when I report the bug upstream?

Comment 2 Caolan McNamara 2020-11-16 16:34:13 UTC
its just reflects that I have limited resources and probably will not personally implement this, but someone upstream might take it on


Note You need to log in before you can comment on or make changes to this bug.