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

[Michael Hierweck <michael@hierweck.de>]

Hi,

On 01.09.25 19:29, Rene Engelhard wrote:
> Hi,
>
> Am 01.09.25 um 13:35 schrieb Michael Hierweck:
> > Stacktrace:
>
> strace is system call trace :)

Of course. Sorry. I tried to figure out what system calls where issued just before the crash.

> BTW, maybe related, maybe not, but at least "interesting"...
>
> I notice /home/user/michael there: e.g.
> [...]
> Maybe #959399 together with whyever your profile is in enforcing?

Indeed.

I purged(!) and reinstalled all LibreOffice-Packages now. 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).

There seems to be an issue with this AppArmor profile.

Thanks for your help on tracking down this bug,

Michael