Of relation, Bug 32653 - Review options for improving both security and backwards compatibility of glibc 2.41 dlopen / execstack handling, https://sourceware.org/bugzilla/show_bug.cgi?id=32653 , regarding the December 2024 release of glibc 2.41, which was a response to CVE-2023-38408.
>From Brave AI, "Bug 32653 (glibc 2.41+): dlopen() now strictly fails if a >library requires an executable stack but the main process doesn't have one >(error: cannot enable executable stack). No intrinsic bug in libraptor. The >error occurs because your build (or a dependency like libxml2) lacks the >PT_GNU_STACK header, defaulting to "executable" due to older toolchains or >missing assembly annotations. dlopen-based loads (e.g., Python/Ruby bindings) >crash on glibc 2.41+ (Debian 13, Fedora 41+). Rebuild with -z noexecstack or >run execstack -c on the .so file." On 6 November 2025, after discussion, Pedro shared Apache_OpenOffice_4.2.0_Linux_x86-64_install-deb_en-GB (AOO420m5(Build:9824) - Rev. C51e9806e6), which worked without issue. I also have a much older build, that did not feature this issue. As mentioned below, was fixed in #483 which added ".IF "$(OS)"=="LINUX" || "$(OS)"=="FREEBSD"; LDFLAGS+:=-Wl,-z,noexecstack; .ENDIF # "$(OS)"=="LINUX" || "$(OS)"=="FREEBSD"" into main/redland/raptor/makefile.mk I was experiencing this issue on my system, which did not have SELinux installed, and even disabling apparmor made no difference. It was due to the CVE-2023-38408 -> release of glibc 2.41 -> the use of dlopen making stack executable, which is now blocked because of https://access.redhat.com/security/cve/cve-2023-38408. Sorry if this posting was unnecessary, as it duplicates/drags up stuff from previous discussions. Faithfully, Dean ________________________________ From: Rory O'Farrell <[email protected]> Sent: 01 August 2026 22:37 To: [email protected] <[email protected]> Subject: Re: OpenOffice 4.1.16 on (X)ubuntu 26.04 On Sat, 1 Aug 2026 13:04:03 +0100 Rory O'Farrell <[email protected]> wrote: > Thank you for the below reply. > > I will try these options out and report back when completed, but real life > always gets in the way!. > > Rory I tried your option (3), downloading execstack from https://archive.ubuntu.com/ubuntu/pool/universe/p/prelink/execstack_0.0.20131005-1.1_amd64.deb installing it, then executing sudo execstack -c /opt/openoffice4/program/libraptor2.so.0 as you suggested OpenOffice 4.1.16 now opens files in Writer without any general error. Many thanks. I have not yet tried this fix on MXLinux - will do so later. Rory > On Sat, 1 Aug 2026 13:45:50 +0200 > Arrigo Marchiori <[email protected]> wrote: > > > Hello Rory, > > > > On Sat, Aug 01, 2026 at 11:43:19AM +0100, Rory O'Farrell wrote: > > > > > Is anyone using Xubuntu 26.04, or any of the linux versions based on > > > that? > > > > > > I have tried OpenOffice 4.1.16 on two machines, one using Xubuntu 26.04 > > > (64 bit) > > > and the other using Xubuntu 26.04 minimal. On opening a Writer file I > > > get a "General error", then the file opens. On closing a modified file > > > I may get another General error; these show up as segmentation faults in > > > the logs. > > > > There is an issue with SELinux, that is enabled by default on some > > distributions. > > > > You can also check this long thread: > > https://lists.apache.org/thread/2y50cgsjcy7l9shm06yt7p8w2s021d6m > > > > The issue was fixed with pull request #483, this means that the next > > version will not be affected. > > > > There are many possible workarounds to this issue: > > > > 1- disable SELinux; > > > > 2- mark the OpenOffice executable as requiring executable stack > > (you need to compile the execstack program, that is most probably > > not available in your distro repository) > > https://lists.apache.org/thread/sg5trgwvj01n92yv904z20k2398jzzll > > $ sudo execstack -s /opt/openoffice4/program/soffice.bin > > > > 3- mark file /opt/openoffice4/program/libraptor2.so.0 to not require > > executable stack > > $ sudo execstack -c /opt/openoffice4/program/libraptor2.so.0 > > > > The safest choice should be 3- but I did not test it yet. > > > > I hope this helps. > > > > Best regards, > > -- > > Arrigo > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > -- > Rory O'Farrell <[email protected]> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Rory O'Farrell <[email protected]> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
