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

Bug#935148: libreoffice-common: After last upgrade libreoffice does not start properly - ERROR 4 forking process



Hi

 

Well thank you.

 

Na utorok, 20. augusta 2019 18:26:28 CEST Rene Engelhard napísali:

> tag 935148 + moreinfo

> tag 935148 + unreproducible

> thanks

>

> On Tue, Aug 20, 2019 at 10:01:49AM +0200, Branislav Staron wrote:

> > Start-Date: 2019-08-19 07:56:26

> > Commandline: apt-get upgrade

> > Requested-By: branislav.staron (1903801450)

> > Upgrade: libreoffice-wiki-publisher:amd64 (1.2.0+LibO6.1.5-3+deb10u2,

> > 1.2.0+LibO6.1.5-3+deb10u3), libreoffice-style-breeze:amd64

> > (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libreoffice-math:amd64

> > (1:6.1.5-3+deb10u2,

> > 1:6.1.5-3+deb10u3), libreoffice-script-provider-js:amd64

> > (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libavformat58:amd64 (7:4.1.3-1,

> > 7:4.1.4-1~deb10u1), libreoffice-report-builder-bin:amd64

> > (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libavfilter7:amd64 (7:4.1.3-1,

> > 7:4.1.4-1~deb10u1), libreoffice-sdbc- postgresql:amd64

> > (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libreoffice-java- common:amd64

> > (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libswresample3:amd64 (7:4.1.3-1,

> > 7:4.1.4-1~deb10u1), libreoffice-base:amd64 (1:6.1.5-3+deb10u2,

> > 1:6.1.5-3+deb10u3), libreoffice-core:amd64 (1:6.1.5-3+deb10u2,

> > 1:6.1.5-3+deb10u3), libreoffice-librelogo:amd64 (1:6.1.5-3+deb10u2,

> > 1:6.1.5-3+deb10u3), libreoffice-sdbc-firebird:amd64 (1:6.1.5-3+deb10u2,

> > 1:6.1.5-3+deb10u3), python3-uno:amd64 (1:6.1.5-3+deb10u2,

> > 1:6.1.5-3+deb10u3), libpostproc55:amd64 (7:4.1.3-1, 7:4.1.4-1~deb10u1),

> > libreoffice-script- provider-python:amd64 (1:6.1.5-3+deb10u2,

> > 1:6.1.5-3+deb10u3), libreoffice-base- core:amd64 (1:6.1.5-3+deb10u2,

> > 1:6.1.5-3+deb10u3), libreoffice-impress:amd64 (1:6.1.5-3+deb10u2,

> > 1:6.1.5-3+deb10u3), libreoffice-help-common:amd64 (1:6.1.5-3+deb10u2,

> > 1:6.1.5-3+deb10u3), libreoffice-style-colibre:amd64 (1:6.1.5-3+deb10u2,

> > 1:6.1.5-3+deb10u3), libavcodec58:amd64 (7:4.1.3-1, 7:4.1.4-1~deb10u1),

> > ure:amd64 (6.1.5-3+deb10u2, 6.1.5-3+deb10u3), libreoffice-

> > sdbc-hsqldb:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libreoffice-

> > writer:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libavutil56:amd64

> > (7:4.1.3-1, 7:4.1.4-1~deb10u1), libreoffice-common:amd64

> > (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libreoffice-kde5:amd64

> > (1:6.1.5-3+deb10u2,

> > 1:6.1.5-3+deb10u3), libreoffice-script-provider-bsh:amd64

> > (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libswscale5:amd64 (7:4.1.3-1,

> > 7:4.1.4-1~deb10u1), libreoffice-nlpsolver:amd64 (0.9+LibO6.1.5-3+deb10u2,

> > 0.9+LibO6.1.5-3+deb10u3), libreoffice:amd64 (1:6.1.5-3+deb10u2,

> > 1:6.1.5-3+deb10u3), fonts-

> > opensymbol:amd64 (2:102.10+LibO6.1.5-3+deb10u2,

> > 2:102.10+LibO6.1.5-3+deb10u3), libreoffice-report-builder:amd64

> > (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), uno- libs3:amd64

> > (6.1.5-3+deb10u2, 6.1.5-3+deb10u3), libreoffice-style-tango:amd64

> > (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libreoffice-help-en-us:amd64

> > (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libreoffice-calc:amd64

> > (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libreoffice-base-drivers:amd64

> > (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libavresample4:amd64 (7:4.1.3-1,

> > 7:4.1.4-1~deb10u1), libreoffice-draw:amd64 (1:6.1.5-3+deb10u2,

> > 1:6.1.5-3+deb10u3), libreoffice-avmedia-backend-gstreamer:amd64

> > (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), tzdata:amd64 (2019a-1,

> > 2019b-0+deb10u1) End-Date: 2019-08-19 07:56:52

>

> So uptodate buster.

>

> > * What exactly did you do (or not do) that was effective (or

> >

> > ineffective): running libreoffice applications (with non root and

> > root

> >

> > user - the same behavior)

>

> Brilliant. And by running as root you mean sudo with what $HOME set? if

> $HOME was your home LO now created stuff as root in that dir. Never run

> stuff like this as root (or be sure you sanitize your environment.)

>

> > * What was the outcome of this action: application does not run. stderr:

> > ERROR 4 forking process

>

> Works here.

>

> There was https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918499 once

> but this is a) fixed and b) apparmor is new enough.

>

> > I tried to see the following - no result:

> > - check apparmor logs (compliance apparmor profil)

> >

> > type=AVC msg=audit(1566286788.299:237): apparmor="ALLOWED"

> >

> > operation="exec" info="profile transition not found" error=-13

> > profile="">

> > name="/usr/lib/libreoffice/program/soffice.bin" pid=7336

> > comm="osl_executeProc" requested_mask="x" denied_mask="x"

> > fsuid=1903801450 ouid=0 target="/usr/lib/libreoffice/program/soffice.bin"

> [...]

>

> > -- Configuration Files:

>

> > /etc/apparmor.d/usr.lib.libreoffice.program.oosplash changed:

> ^^^^^^^^

> why did you change

> it?

 

Debian Buster was installed as RC. And apparmor reported too many AVC denials. Profile changes were made with aa-logprof.

 

>

> > /etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin changed:

> ^^^^^^^^

> why did you

> change it?

>

> > /etc/apparmor.d/usr.lib.libreoffice.program.xpdfimport changed:

> ^^^^^^^^

> why did you

> change it?

>

> In a pure buster this works.

 

 

 

>

> Regards,

>

> Rene

 

 

I have used apparmor profiles from the latest libreoffice-common update and everything now works fine.

 

I apologize for the unjustified mistake

 

--

 

Best regards

 

Branislav Staroň


Reply to: