After a large system update yesterday I cannot start OO any more.
Trying through the console gives:
So I followed the workaround suggested by Len E. in the thread mentioned, but i am not sure, i've understood that well!/opt/openoffice4/program/soffice: Zeile 121: 3277 Speicherzugriffsfehler (Speicherabzug geschrieben) "$sd_prog/$sd_binary" "$@"
I downgraded the glibc* libraries from 2.22-4.9.1 (just updated yesterday) to the previous version 2.22-4.6.3, then I restarted the system. -> NO SUCCESS !!
In the mentioned Thread dacha wrote:
How can I launch OO in a debugger? The OO install pack does contain no debug program.Please run it in a debugger and post the output, ie.:
$ gdb /path/to/soffice.bin
(gdb) run
You'll eventually get something like this:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 80d806400 (LWP 101000/soffice.bin)]
Type these:
(gdb) backtrace
(gdb) quit
and post the output.
Alternative: other possible solutions or suggestions?
Many thanks in advance for the any hint
SOME ENVIRONMENT DATA
OS: OpenSUSE Leap 42.2 (64 bit)
Desktop: KDE-Plasma 5.8.6 / KDE-Frameworks 5.26.0 / Qt 5.6.1