For a long time, Libre Office has been incompatible with the Mac
"Accessibility" feature. A growing list of software uses this feature,
and many bugs have been and will be reported that have this as a root
cause. At the least, users should be warned.
In the System Preferences Control Panel, choose Security, Privacy,
Accessibility, then "Allow these apps to control your computer".
If any of them is on, Libre Office will crash unpredictably, even when
sitting doing nothing (or also typically, when trying to save a file
or quit). This continues to happen in 18.104.22.168 RC2. Enclosed a file
which crashes a minute or so after startup (this is an .odm; I can
send the entire folder if you wish). If I turn off Accessibility for
all such applications, I can at least start LO with that file and do
some editing; I am only beginning testing this version.
Right now, I need Accessibility for the following applications:
Quickeys and Quickeys User Event Helper
Also in this category are screen readers, and some system utilities or
What are the prospects for fixing this? It may reach the point that I
might have to abandon LO, and I would rather continue using it.
Thanks for your work on this project.
Steps to Reproduce:
1. Start LO
2. Load file why_cant_we_beacon_st.odm
Crashes after a minute or so, even if idle.
User Profile Reset: Yes
OpenGL enabled: Yes
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36
Created attachment 139198 [details]
File which crashes upon startup
Nothing special about this file, just an example. The problem occurs intermittently whenever Mac Accessbility is enabled for applicaitons. It often occurs when saving a file, but can happen anytime.
It is an .odm file, let me know if you want the full folder of which this is a part.
Created attachment 139199 [details]
@Henry : this is probably a duplicate of bug 80756
*** This bug has been marked as a duplicate of bug 80756 ***
In addition, there are already a number of referenced "Accessibility-related" bugs, see the meta bug 55571, for example.
It is unlikely, although not impossible, that any of these will get fixed any time soon.