Hi,
Am 12. September 2025 12:27:34 MESZ schrieb Michael Hierweck
<[email protected]>:
>After installing the recent Upgrade (13.0 -> 13.1)
which didn't change anything related to this
> my workaround (empty /etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin)
> refuses to work.
(...)
>This makes apparmor_parer run forever while the package is configured.
Well, this reads all the config as it was in the package as all conffiles are
gone so your workaround also was gone, of course
># rm $(cat /var/lib/dpkg/info/libreoffice-common.conffiles)
># touch /etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin
># dpkg -i --force-confmiss
>/var/cache/apt/archives/libreoffice-common_4%3a25.2.3-2+deb13u2_all.deb
Where this probably does not because you have a (even though empty) profile
here.
>This solve the issue mentioned above but libreoffice refuses to start.
>
>Message: "ERROR 4 forking process"
>Caused by: /usr/lib/libreoffice/program/oosplash
Which is your initial report, so nothing.new here...
>I still wonder why this is related to AppArmor because oosplash is in complain
>mode only.
>
># aa-status |egrep "^[0-9]|libre|oosplash|soffice"
>176 profiles are loaded.
>54 profiles are in enforce mode.
> libreoffice-senddoc
> libreoffice-xpdfimport
>46 profiles are in complain mode.
> libreoffice-oosplash
>0 profiles are in prompt mode.
>0 profiles are in kill mode.
>76 profiles are in unconfined mode.
>35 processes have profiles defined.
>7 processes are in enforce mode.
>5 processes are in complain mode.
>0 processes are in prompt mode.
>0 processes are in kill mode.
>23 processes are unconfined but have a profile defined.
>0 processes are in mixed mode.
As I do, too.
Btw, for you home dir issue, see
<https://gerrit.libreoffice.org/c/core/+/190686>, especially the discussion at
<https://gerrit.libreoffice.org/c/core/+/190686/comments/90fcd4d9_158418fb>
Regards
Rene
