An AppArmor profile in this package not only fails to load, it takes an
unreasonable amount of time to parse:

# time -p apparmor_parser -K -v /etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin
Too many states (172789) for type state_t
real 819.27
user 632.74
sys 39.09

This causes the apparmor.service startup to delay the boot process
significantly, and then fail.

tag 1142389 + moreinfo
tag 1142389 + unreproducible
thanks

Am 19.07.26 um 04:26 schrieb Daniel Richard G.:

Maybe on your system..
user 7,92
sys 0,06


in my smallish pure Debian 13 VM.

With the Debian 13 kernel as of now (6.12.95+deb13-amd64). Do you use something else? Some other arch?

Unhelpfully you omit any of the reportbug info.


Besides that: if it was a general problem, it should have been happening earlier, shouldn't it? And deb13u6 didn't get any update of anything apparmor'ish, neither did get stable an apparmor update lately.


Regards,


Rene

Hi Rene,

No, this is a fresh install of trixie on amd64. I had a workaround for
this issue dating back to bookworm, and I experimentally disabled it to
see if this still comes up.

Incidentally, this only occurs on Debian. The same profile on Ubuntu
behaves perfectly fine.

I suspect the difference between your run and mine is some AppArmor
tunable. I'll try and see if I can reproduce your run on a stock system,
and then add elements of my config that might affect it.

It wouldn't have been much more helpful :]

I've only recently started looking at trixie. This is not a point-
release regression; this is a longer-term issue for which I finally got
around to filing a report.

Hi,

Am 19.07.26 um 17:35 schrieb Daniel Richard G.:

Hmm

But that VM is a clean install of Debian which all the desktop tasks. No configuration there at all.

(Don't remember whether it was bookworm and dist-upgraded or trixie installed directly.)

OK, thanks

Probably, except for the arch and (unexpected) additions/modifications..

Hmm, ok.


Regards,


Rene