I have done this in the past as well, on a few strange Debian derivatives. I do not think it will work in this case, because the issue lies in how LibreOffice is run, not necessarily how it is installed.
After reviewing the information we’ve all managed to compile in this thread, I refined my Google search queries a bit and tried approaching the problem from a narrower angle.
I stumbled upon this thread, the gist of which was to run LibreOffice thusly:
SAL_USE_VCLPLUGIN=gtk libreoffice --writer. This solved the issue for me!
Now we have two things: a solution, and the knowledge that this issue doesn’t seem specific to Void. Or at least, the issue is not something that originates from the repositories. My next goal is to determine how other distros avoid this problem. There must be an intelligent way to determine how to set this variable so that LO does not crash.
There appears to be more information available here which details a permanent solution, but the files referenced by that page don’t exist on my system, so I’ll give it a rest for now… I am happy to have LibreOffice working for the moment. I will return to the problem tomorrow.
@bluemoon confirm this works for you?
EDIT: It was discovered post-haste that booting with
stack_guard_gap=1 is necessary to solve the issue completely. This can be done temporarily at the GRUB prompt, or permanently by editing