Apache OpenOffice (AOO) Bugzilla – Issue 128193
Fedora 29: DE 4.1.6 segmentation fault since a few days
Last modified: 2019-09-13 14:32:14 UTC
Hi, i get segmentation faults like this: $ openoffice4 /opt/openoffice4/program/soffice: Zeile 121: 12344 Speicherzugriffsfehler (Speicherabzug geschrieben) "$sd_prog/$sd_binary" "$@" [marius@eve RPMS]$ when i open an empty impress and .. - try to change the master page configuration - switch to the tab "Handzettel", thats "normal" -> "Table of Content -> Notices -> "Handzettel" aka "flyers" the presentation is empty, one page, directly after starting impress. # execute soffice binary "$sd_prog/$sd_binary" "$@" & trap 'kill -9 $!' TERM wait $! <----- CRASH line 121 sd_ret=$? A normal usage is no longer possible. An actual recompiled and updated version is needed, asap. After a document recovery, oo starts WRITER instead of IMPRESS, which is annoying to say the least.
This is an Issue on your machine and not an issue of the program. please use users@openoffice.apache.org or forums.openoffice.org.
of course it happens on my machine, thats why i opened a bugreport :) Or do you want segmentation faults to happen within your product? The OO v4.1.6 is from 2018, we had 2 new releases of Fedora in this time. Do you agree, that a system can have a major change from one release to another? If so, the only way to compensate this, is to relase more frequent updates for your product ;) Please recompile it at least 4x times a year.
This sounds a bit like issue 127929: https://bz.apache.org/ooo/show_bug.cgi?id=127929 Can you please test one of these test builds? https://home.apache.org/~jim/AOO-builds/AOO417-test/Rev-46059c9/ Maybe the underlying problem is the same. Should be fixed in 4.1.7.
I do not think an upstream rebuild would fix the issue. We build on CentOS. I would recommend localizing the root cause for the segmentation fault which is if caused by an fedora update the removal of a library. you can find that out by doing an ldd on the soffice.bin file in the openoffice folder. For me this is still a downstream issue. I am on Arch Linux and have no issues you describe. If you want 4 builds a year do it yourself we have guides on the wiki. We are already thin spread with the volunteers we have.
This is indeed reproducible, and fixed in 4.1.7 #0 0x00007ffff4489a50 in () at /home/ariel/aoo/aoo416/program/libvcl.so #1 0x00007ffff07746f3 in FT_Glyph_Get_CBox () at /lib64/libfreetype.so.6 #2 0x00007ffff3eb0770 in () at /home/ariel/aoo/aoo416/program/libvcl.so #3 0x00007ffff3eb6eaa in ServerFont::GetGlyphData(unsigned int) () at /home/ariel/aoo/aoo416/program/libvcl.so #4 0x00007ffff3eb5bcf in () at /home/ariel/aoo/aoo416/program/libvcl.so #5 0x00007ffff3eb539e in () at /home/ariel/aoo/aoo416/program/libvcl.so #6 0x00007ffff3eb50fc in ServerFontLayout::LayoutText(ImplLayoutArgs&) () at /home/ariel/aoo/aoo416/program/libvcl.so #7 0x00007ffff3fe6456 in () at /home/ariel/aoo/aoo416/program/libvcl.so #8 0x00007ffff3fe78fb in OutputDevice::GetTextArray(String const&, int*, unsigned short, unsigned short) const () at /home/ariel/aoo/aoo416/program/libvcl.so #9 0x00007ffff04dc27e in drawinglayer::primitive2d::TextLayouterDevice::getTextWidth(String const&, unsigned int, unsigned int) const () at /home/ariel/aoo/aoo416/program/libdrawinglayer.so By the way, asking a user who makes a bug report to solve the issue and/or build the beast by him/herself is (IMHO) not very polite and may end up with the user not willing to contribute never ever again
Yes you are right, Ariel. I have been very unpolite. I have gotten it all wrong, mostly because I took his thread for a bad media campaign in another bug very personal. Thanks for reminding me in this. I do the best to deal with my negative feelings, but sometimes I fail. I do apologize for my bad behavior. That is all I can do now asking for forgiveness of my failures. All the Best Peter Note about the: build the beast by him/herself It is one of the main reasons OpenOffice can not evolve. The code and the build system is to crazy for new people. Unless we solve this we will never manage more then we do now. So we need help. Please understand that if I write learn to build, as unpolite as it might be, it is always a call for help. Note2: Since we know now that Matthias had the right hunch, I change it to duplicate. Thanks Ariel and Matthias for the support! *** This issue has been marked as a duplicate of issue 127929 ***