Closed kintopp closed 3 months ago
I tried one more thing. Deleted WolframEngine and WolframScript and front-end completely. Created a new Wolfram user account. Installed WolframEngine and WolframScript and activated it with the new Wolfram user account. Installed v2.5.0 front-end. Pointed it to WolframScript binary, same error as before.
Thank you for the detailed info! This error message usually has nothing to do with a license, but just a default message thrown on any exceptions.
By looking into logs I see an issue,probably we need to recompile libuv for OSX x86 on Wolfram Engine 14. I have this machine around and going to test it.
I tried one more thing. Deleted WolframEngine and WolframScript and front-end completely. Created a new Wolfram user account. Installed WolframEngine and WolframScript and activated it with the new Wolfram user account. Installed v2.5.0 front-end. Pointed it to WolframScript binary, same error as before.
I think it is just a library loader turned out to be different in Wl14. Wolfram Research don't explicitly write in release notes, when they change its version, which is quite annoying...
We will recompile this binary for a new version, don't worry :)
I have removed the dust from my hackintosh x86, and it looks it is working.
I have updated the libraries with new one. If you just click reinstall
on the launcher's window (assuming you are using one from the releases) during the startup it should download all fresh libraries.
It works! I had v2.5.0, hit reinstall and is started up as v2.5.3 (although the About info for the app still says v2.5.0). But I assume that's a small bug.
I am glad it has been resolved. :) However, this is still a mystery for me...
A desktop application acts more like a wrapper over a web-server (WLJS Notebook). Since there is no big changes to this wrapper from version to version, we update the core (web server + supporting libs) separately. Then users do not have to redownload the whole bundle.
I've been trying to get the front-end to recognise my WolframEngine + WolframScript installation to no avail. I always end up with, 'The Wolfram Engine exited because of a license error'.
My set-up is Mac OSX x86 (64-bit) MacBook Pro, with WolframScript 1.11.0 and WolframEngine v14.0.0 installed and activated on OSX v14.5 with v.2.4.5 of the wolfram-js-front-end. I've looked around in the older issues and although I can see that some others have run into this as well, I wasn't able to find instructions for how to resolve the problem. I'd be happy to help troubleshoot.
Below is what I see after I reinstall the front-end.
Wolfram Language 14.0.0 Engine for Mac OS X x86 (64-bit) Copyright 1988-2023 Wolfram Research, Inc. In[1]:=
LibraryFunction::libload: The function run_uvloop was not loaded from the file /Users/abosse/Library/Application Support/wljs-notebook/wl_packages/KirillBelov_CSockets/LibraryResources/7 /MacOSX-x86-64/csockets.dylib.