-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NW.js above version 0.38.4 not starting on Ubuntu 18.04.1; needs libatomic? #7213
Comments
libatomic1 is required by Node.js in recent versions. |
I see, thanks for the explanation! After having a look I've found a related ticket on the Node.js issue tracker: nodejs/node#29718 Also, possibly, where the decision may have been made to link it: nodejs/node#28231 I guess I shall close this then, if it's out of scope for this project. |
If so, why is it still not distributed with nwjs? It seems that is a core lib which doesn't depend on application's domain. |
Also found this issue after trying to deploy our NW.js app to various Ubuntu distros. Fixed the issue on Ubuntu distros by installing libatomic1 via apt. Is it possible to distribute libatmlic1 with an NW.js app or does it have to be installed using apt or other package manager? |
======== TEMPLATE BUG FORM ========
NWJS Version : 0.42.4 SDK (latest at time of writing)
Operating System : Ubuntu Mate 18.04.1
Expected behavior
On attempting to launch NW.js, I'd expect it to load and operate just like older versions up to 0.38.4 (the last version that seemed to work without issue).
Actual behavior
Versions after 0.38.4 seem to hang on initialisation with:
It doesn't crash; it just sits there until you CTRL+C out.
Libatomic is not installed on the system; if I install it with
sudo apt-get install libatomic1
, these NW.js versions will open as expected.So in theory, I can get it running OK. However I'm used to NW.js not having any external dependencies (that can't be found by default on a vanilla Debian system like Ubuntu, at least); is this no longer the case?
Does this new external dependency on libatomic affect licensing/distribution obligations in any way? Is it just for SDK variants past 0.38.4 (I have yet to investigate non-SDK builds past 0.35.4).
Additionally, I am trying to autostart the process (I have a .deb installer through which NW.js is installed and intended to run after boot). Needless to say it doesn't come up, but nor does it seem to exit, in which case, any attempts to launch it see the following via terminal:
How to reproduce
./nw .
in the terminal; in my tests, this causes the aforementioned explosion about libatomicThe text was updated successfully, but these errors were encountered: