Bug#1113713: libreoffice: LibreOffice fails to start on Trixie when AppArmor is active

[Rene Engelhard <rene@debian.org>]

Hi,

Am 01.09.25 um 20:50 schrieb Michael Hierweck:
> > Maybe #959399 together with whyever your profile is in enforcing?
>
> Indeed.

Thanks for confirming.

> I purged(!) and reinstalled all LibreOffice-Packages now.

Yeah, you need purge since it's a conffile...
(A Shortcut would have been to rm the profiles and do a dpkg -i --force-confmiss on libreoffice-common after downloading it manually - or from /var/cache/apt/archives if still there :) )

> I noticed that apparmor_parser runs forever (triggered by the libreoffice-common postinstall script) when both "/etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin" is present *and* the debconf variable "apparmor/homedirs" contains "/home/users/".
>
> The profiles are processed in less than 15secs when setting this variable to "/foo/bar/". (Or even when replacing "/etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin" with an empty file.)
>

> If "/etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin" is replaced with an empty file and the AppArmor cache is regenerated, LibreOffice can be started by calling the nice normal start script (/usr/bin/libreoffice).

As expected.

> There seems to be an issue with this AppArmor profile.

Yes, no one denied that given all the bugs and that it's unmaintained. (Which are not an issue per se if it's complain, except the logging...)

And as we notice (and #959399 noticed) problems when $HOME is non-standard in /home :)


> Thanks for your help on tracking down this bug,

No problem, I just wonder what to do with this... ;)


CC'ing #959399 at least since it has the same root cause. Wondering whether they should be merged...

Regards,


Rene