Bug#1113713: libreoffice: LibreOffice fails to start on Trixie when AppArmor is active
Hi,
Am 01.09.25 um 18:49 schrieb Michael Hierweck:
However, I found out that LibreOffice actually was in enforce mode:
# aa-status |egrep 'mode|libreoffice'
55 profiles are in enforce mode.
libreoffice-oosplash
libreoffice-senddoc
libreoffice-xpdfimport
well, oosplash is unexpected, the other two are in enforce mode indeed (and should)
root@frodo:/home/rene# grep complain /etc/apparmor.d/usr.lib.libre*
/etc/apparmor.d/usr.lib.libreoffice.program.oosplash:profile libreoffice-oosplash /usr/lib/libreoffice/program/oosplash flags=(complain) {
/etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin:profile libreoffice-soffice /usr/lib/libreoffice/program/soffice.bin flags=(complain) {
root@frodo:/home/rene#
I also wonder why you miss the gpg submodule (see my paste below)
# aa-status |egrep 'mode|libreoffice'
35 profiles are in enforce mode.
libreoffice-senddoc
libreoffice-soffice//gpg
libreoffice-xpdfimport
25 profiles are in complain mode.
libreoffice-oosplash
libreoffice-soffice
0 profiles are in prompt mode.
0 profiles are in kill mode.
77 profiles are in unconfined mode.
5 processes are in enforce mode.
0 processes are in complain mode.
0 processes are in prompt mode.
0 processes are in kill mode.
0 processes are in mixed mode.
would be expected.
> So I explicitly switched to complain mode:
# aa-complain /usr/lib/libreoffice/program/oosplash
Setting /usr/lib/libreoffice/program/oosplash to complain mode.
Warning: profile libreoffice-oosplash represents multiple programs
Warning: profile libreoffice-oosplash represents multiple programs
[...]
$ libreoffice
ERROR 4 forking process
Interesting
Regards,
Rene
Reply to: