electron: Electron not working when running in terminal on Ubuntu Linux
- Electron Version: 2.0.0
- Operating System (Platform and Version): Lubuntu/Ubuntu 17.10
- Last known working Electron version: 1.8.x
Expected Behavior Electron should open and be functional when run from the terminal
Actual behavior Electron either doesn’t open, opens to a black screen, or freezes shortly after opening. The command doesn’t exit, it just hangs there.
To Reproduce
$ git clone https://github.com/electron/electron-quick-start
$ npm install
$ npm start
Additional Information
If you run npm start > /dev/null, npm start 2> /dev/null, or npm start &> /dev/null, the issue cannot be reproduced. This makes me suspect that there’s some bug with streaming to a terminal emulator (perhaps the terminal emulator gives backpressure that electron can’t handle?)
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 12
- Comments: 22 (4 by maintainers)
I found this (temporary) solution: https://github.com/electron/electron/issues/13624#issuecomment-404537806 (use
--disable-gpu). It worked for me.Same here.
Debian 9.6 Node v11.1.0 Electron 3.0.9
Works fine using
--disable-gpuas @Klooven mentioned.Same issue running Ubuntu 18.04/18.10 through VMWare 14.1.3, Intel® UHD Graphics 630. Running “npm start” from the terminal locks up after a few seconds, sometimes rendering the entire VM unresponsive to mouse input (but can alt-tab to the terminal and control-c to restore it.) Running as suggested “npm start > /dev/null” solves the problem, but running with “–disable-gpu” does not.
Thank you for your issue!
We haven’t gotten a response to our questions in our comment above. With only the information that is currently in the issue, we don’t have enough information to take action. I’m going to close this but don’t hesitate to reach out if you have or find the answers we need, we’ll be happy to reopen the issue.
Thank you for taking the time to report this issue and helping to make Electron better.
The version of Electron you reported this on has been superseded by newer releases.
If you’re still experiencing this issue in Electron v4.2.x or later, please add a comment specifying the version you’re testing with and any other new information that a maintainer trying to reproduce the issue should know.
I’m setting the
blocked/need-infolabel for the above reasons. This issue will be closed 7 days from now if there is no response.Thanks in advance! Your help is appreciated.