MATLAB: Live Editor won’t start MATLAB R2018a on ArchLinux

arch linuxjxbrowserlive editorMATLAB

I am trying to use Live Editor in MATLAB R2018a on ArchLinux. Attempts to start Live Editor ends with dialogue box showing
"The Live Editor is unable to run in the current system configuration."
Unlike a previous question, I do have libXss and libgconf installed. (This is a fresh MATLAB install and all the required symlinks seemed present.)
Following the Arch wiki I tried executing
>> com.mathworks.mde.liveeditor.widget.rtc.CachedLightweightBrowserFactory.createLightweightBrowser()
on the MATLAB command line, the output is as follows and is rather opaque to me.
Java exception occurred:
com.mathworks.html.BrowserCreationException: com.mathworks.html.BrowserCreationException:
com.teamdev.jxbrowser.chromium.internal.ipc.IPCException: IPC process exited. Exit code: 127
at
com.mathworks.mlwidgets.html.LightweightBrowserBuilder.buildBrowser(LightweightBrowserBuilder.java:87)
at
com.mathworks.mlwidgets.html.LightweightBrowserBuilder.buildDefaultBrowser(LightweightBrowserBuilder.java:52)
at
com.mathworks.mlwidgets.html.LightweightBrowserFactory.createLightweightBrowser(LightweightBrowserFactory.java:36)
at
com.mathworks.mde.liveeditor.widget.rtc.CachedLightweightBrowserFactory.createLightweightBrowser(CachedLightweightBrowserFactory.java:84)
Caused by: com.mathworks.html.BrowserCreationException:
com.teamdev.jxbrowser.chromium.internal.ipc.IPCException: IPC process exited. Exit
code: 127
at
com.mathworks.html.jxbrowser.chromium.LightweightChromiumBrowser.<init>(LightweightChromiumBrowser.java:39)
at
com.mathworks.mlwidgets.html.LightweightBrowserBuilder.buildBrowser(LightweightBrowserBuilder.java:78)
... 3 more
Caused by: com.teamdev.jxbrowser.chromium.internal.ipc.IPCException: IPC process exited. Exit
code: 127
at com.teamdev.jxbrowser.chromium.internal.ipc.d.run(Unknown Source)
at java.lang.Thread.run(Thread.java:748)
Any suggestions?

Best Answer

For what it is worth, LiveEditor works on R2019b.
I never got around to getting it to work with R2018a, but I guess that is moot now.