[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#918499: libreoffice: fails with 'ERROR 4 forking process'



severity 918499 serious
tag 918499 - unreproducible
tag 918499 - moreinfo
tag 918499 + confirmed
tag 918499 + pending
thanks

Hi,

On Mon, Jan 07, 2019 at 09:20:12PM +0700, Tunggul Arif Siswoyo wrote:
> On Mon, 7 Jan 2019 20:46:28 +0700 Tunggul Arif Siswoyo <tunggul@ptdes.net> wrote:
> 
> [skip]
> 
> I think it is related with apparmor configs. I'm not sure what caused it

Ah, good point.

[...]
> 1 profiles are in complain mode.                                                                                                                                                
>    libreoffice-oopslash                                                                                                                                                         
Note that this in complain mode only. But where is soffice.bin? ...

> Jan 07 20:13:09 ikigai apparmor[430]: AppArmor parser error for /etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin in /etc/apparmor.d/usr.lib.libreoffice.pr…ractions/mesa'
> Jan 07 20:13:09 ikigai apparmor[430]:  failed!
> Jan 07 20:13:09 ikigai systemd[1]: apparmor.service: Main process exited, code=exited, status=123/n/a
> Jan 07 20:13:09 ikigai systemd[1]: apparmor.service: Failed with result 'exit-code'.
> Jan 07 20:13:09 ikigai systemd[1]: Failed to start Load AppArmor profiles.
> Hint: Some lines were ellipsized, use -l to show in full.
> 
> Error message above caused by invalid config in apparmor profile for
> soffice.bin in line 90 :

.. ah. here... :(

> root@ikigai:~# aa-remove-unknown
> AppArmor parser error for /etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin in /etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin at line 90: Could not open 'abstrac
> tions/mesa'

Aha. :-(

But this is present in testings apparmor

rene@frodo:~$ dpkg -S /etc/apparmor.d/abstractions/mesa 
dpapparmor: /etc/apparmor.d/abstractions/mesa
rene@frodo:~$ dpkg -l apparmor
Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten
| Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/
         Halb installiert/Trigger erWartet/Trigger anhängig
|/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht)
||/ Name           Version      Architektur  Beschreibung
+++-==============-============-============-======================================
ii  apparmor       2.13.1-3+b1  amd64        user-space parser utility for AppArmor

In your other mail you (well, reportbug...) writes:

| Versions of packages libreoffice-common recommends:                                                                                                                             
| ii  apparmor            2.13-8 

Why that old version of apparmor?

Testing has 2.13.1 since last year November,
actually even a newer one migrated today. See
https://packages.qa.debian.org/a/apparmor.html

But indeed the Recommends is not strict enough, according to
http://bugs.debian.org/918499 this must be >= 2.13.1 instead of just
>= 2.13. Will fix. (And add a conflicts against older apparmors.)

But you should properly upgrade your system nevertheless.

Regards,

Rene


Reply to: