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
Won't run on Pop OS #91
Comments
hey there, appreciate you raising this issue. seems some other users have encountered some similar problems on Windows as well. Will investigate this weekend |
i am having same issue using react on debian, after checking syslog i found there is segmantation fault during startup.
|
I'm also having this issue on debian buster. |
Have the same issue |
I am having this problem after I created an arch package out of this with debtap and installed it. Installation was smooth but when I tried to run it -> segfault. I thought it was just because I was doing a nasty thing and converting a deb package into arch package but because debian and ubuntu users are also having problems maybe it was not that. |
Will have this resolved in the next release for 2020. |
Getting the same notification "Segmentation fault"
|
With Ubuntu Same issue as well. |
Hi everyone, |
Any updates about this issue? |
Same error here node 15.5 debian bullseye using the .deb package.
If then just yarn start it fails with the css-loader loading the styles.css |
Similary for me:
|
Still no luck with this one? |
Any update on this issue |
Hi, I am facing the same issue. Cannot run the app. |
it doesn't seem like they're developing the app anymore. |
React-Prot Version: Latest
Details
I downloaded the Debian installer package for Linux but on clicking on the icon nothing happens. Running the application from the terminal I got the following output
Expected Behavior
App should run
Actual Behavior
App does not start, terminal outputs a segmentation fault
Possible Fix
Additional Info
Your Environment
v10.15.1
6.10.2
19.04
Steps to Reproduce
Stack Trace
Terminal output when running
react-proto
The text was updated successfully, but these errors were encountered: