After updates - The lock file could not be created

This was working before, with the same directory structure, though I am coming back from a break, and both the OS and libreoffice have been updated.

The error:

The lock file could not be created for exclusive access by LibreOffice, due to missing permission to create a lock file on that file location or lack of free disk space.

Libreoffice version is now:
Version: 7.4.5.1
Build ID: 40(Build:1)
CPU threads: 12; OS: Linux 6.1; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

Platform

Linux version 6.1.9-200.fc37.x86_64 (mockbuild@bkernel01.iad2.fedoraproject.org)

Details
There is plenty of free disk space.

I have group permissions for the shared directory. Editing the document in this directory used to create a lock file and allow me edit the document. But now I get said error.

For those who want the nitty-gritty, this transcript shows the following:

The shared directory folder is called documents. The document is system-startup.

The shared directory folder is owned by doc-team, and the group is called doc-team.

I am in group doc-team.

Our group has read and write privileges on the directory folder. The group sticky bit is set, so when the document is created in the folder it is owned by the group, in any case.

The document is owned by myself, and I have read and write access as the owner. It is in the group doc-team, and the group members have read and write access.

Hence I have permissions to write both the directory folder and the file.

This can be seen here:

> cd <to the project>
> ls -ld documents
drwxrws---. 1 doc-team doc-team 2418 Jan 30 21:36  documents
> groups
jonathan wheel doc-team ...
> cd documents
> ls -l system-starup.odt 
-rw-rw----. 1 jonathan doc-team 74708 Jan 30 21:36 'system-startup.odt'

Is there a setting somewhere? How are shared folder docs done now, differently? (Am I missing something? yikes, would not be the first time.)

(The hack of making a copy, editing, and putting it back is fraught with problems. Beyond co-ordination, there is also the problem of document review, i.e. doing through a bunch of documents in a short time to make small edits. Another hack would be to back rev libreoffice. But maybe these hacks are not needed? Is there a setting someone? It would be nice to not be left behind in the updates.)

My first thoughts theese days: Another distribution changed to using snap/appimage ? The other idea would go in direction of AppArmor/SE-Linux not being notified of updates.
.
And the growing number of fedora-projects from Workstation to Silverblue doesn’t help to find information…

Fedora 37 using dnf for package management. … although libreoffice comes with the distribution, so perhaps it is different.

Seems like locks don’t work with shared directories, where permissions are via group rather than via owner. Of course, if so, that would defeat the purpose of having locks in the first place. lol.

No idea what is going on here.

Yeah, the general idea behind the system update was to move to SilverBlue with Fedora 37 but the system was not stable. Instead of going back to Debian we put regular Fedora 37 and are trying it out. God forbid that this has something to do with SEL.

If they add anymore security hoops to these systems, we will have to unlock a physical safe inbetween file saves. It is all a bit much just to be able to run a word processor.

The machine libreoffice is launched from runs virtually on a host, as most machines do these days. The volume is mounted via virtiofs passthrough. I doubt this matters, but wouldn’t want anyone to get mad due to my not mentioning it.

I am under Fedora 37 too, but Server edition. I frequently edit document cross-accounts, meaning I rely on group permission. My SEL is configured as strict enforcing (with personal additions to make it even stricter) and I have no problem with it.
I have no experience with SilverBlue and containers.
I run several virtual machines but they have their own virtual volumes. No experience with passthrough volumes.

PS: you tagged base. Have you also problems with databases? If this is not the case, remove the tag.