-
Notifications
You must be signed in to change notification settings - Fork 152
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
Linux Build issues #46
Comments
The latest commit where electron was bumped 5 major versions broke this. I get the same error message but window actually renders, however the choose file button is completely broken. if i revert to c76f20c, everything works as expected. |
I reverted to this commit c76f20c and it successfully built on Linux and runs without error |
I ran into similar issues, using Debian. although I'm currently running sid so i have: node -v reverting to c76f20c did not work for me i still get the unmovable white box |
I ran into the same issue however was able to build the standalone apps on Debian 11 successfully again, no white screen or errors and all apps functional It's important to use Node.js v14.x as the other versions won't work. to have a clean sweep I deleted the following folders ~/.node-gyp/ and cleared ~/.cache using bleachbit I was able to install on another system without having to clean folders, however it was a fresh install next step.... install Node.js v14.x: If Using Ubuntu
If Using Debian, as root (sudo -i)
Verify versions, should be similar to....
|
I was able to build magenta-studio standalone app on Debian Stretch in the past but have never been able to on Debian Buster
yarn -v
1.22.4
npm -v
6.14.5
node -v
v14.5.0
I decided to try again and am still encountering problems. The first is this when trying to run any of the apps for example
./Continue
Returns this error:
does not resolve it
However running
sudo sysctl kernel.unprivileged_userns_clone=1
will allow the program to run but now presents a new error...
./Continue
in the command line and this pop up
The text was updated successfully, but these errors were encountered: