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

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]

Reply via email to