libreoffice does no longer start with kernel 4.17

[df8oe]

If I try to start on console it only outputs "ERROR 4 forking process" and that's all.


EDIT:
I have done some more investigations. It is not related to normal updates but to the installation of a new kernel. Until yesterday I used kernel "linux-image-4.16.9-towo.1-siduction-amd64". Yesterday I installed kernel "linux-image-4.17.7-towo.1-siduction-amd64" where this error is 100% reproduceable. Starting libreoffice using "exec /usr/lib/libreoffice/program/soffice.bin" does work so I do not think it is a problem which is directly related to libreoffice but to a bug in kernel or - more recent - to a "new security feature" of kernel to protect processes - and libreoffice start script traps into this new feature. Any ideas?




Best regards
DF8OE

[thebluesman]

Code Auswählen Erweitern

jan@rechenknecht:~$ uname -a
Linux rechenknecht 4.17.7-towo.1-siduction-amd64 #1 SMP siduction 4.17-18 (2018-07-17) x86_64 GNU/Linux
jan@rechenknecht:~$


No problems here.
LO works fine.

[df8oe]

I can do before/after check. If I boot 4.16 kernel, everything is working fine. If I boot 4.17 kernel, error is present. I do have four machines running Siduction - all the same behaviour. By chance? I cannot believe...


Best regards
DF8OE

[towo]

inxi -v3

[melmarker]

Starts for me™

[dibl]

Fully updated here, and I can't make LO fail to start, terminal or GUI.

[ReinerS]

Also just updated, no problem with LibreOffice.
regards
Reiner

[dibl]

I wonder if OP is using LO from debian repo or download?

[df8oe]

I am using LO from Debian Repo.


Interesting is: If I do not start "Libreoffice" but "LO Writer" - iz starts. And if writer was started first, Libreoffice starts with its generic icon, too. As long as I do not poweroff and on PC. If I first start LO with "generic starter", error comes up again and then is present on single starters (writer, calc, presenter) too.


Very very strange.


As I do know now that I should not start generic starter first I do have a workaround and keep watching that. I am not sure if GUI (I am using KDE) does not have influence, too.


Best regards
DF8OE

[kokurya]

Doesn't matter how I start it. It always works here.

[dibl]

Lot of discussion of this or a similar problem here:

https://github.com/netblue30/firejail/issues/1703

[DeepDayze]

I started LO Writer with lowriter in a console and it opens fine for me no error in console. Perhaps something awry with OP's config?


Even started it via firejail...no error there even.