Skip to content
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

Request: upgrade Electron version to fix X crash bug for Arch Linux #45482

Closed
l0k18 opened this issue Mar 10, 2018 · 2 comments
Closed

Request: upgrade Electron version to fix X crash bug for Arch Linux #45482

l0k18 opened this issue Mar 10, 2018 · 2 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@l0k18
Copy link

l0k18 commented Mar 10, 2018

  • VSCode Version: 1.21.0
  • OS Version: Antergos, current today
  • Video Driver: Nvidia 390.25

Steps to Reproduce:

  1. Install arch linux (or antergos) current version
  2. Install Nvidia 384+ version for an Nvidia video card (10 series)
  3. Install vscode from git repository current version
  4. Randomly it will trigger the X server to crash and drop you back to login screen

Fix is to update package.json from electron 1.7.7 to current 1.8.3. I removed the AUR package version and manually installed from the git repository and updated the electron version in package.json and the problem seems to have disappeared.

Does this issue occur when all extensions are disabled?: Yes

This problem has been plaguing VScode for maybe 3 version increments, and it's caused by using an old version of electron.

@l0k18 l0k18 changed the title Request: upgrade Electron version to fix X crash bug for linux Request: upgrade Electron version to fix X crash bug for Arch Linux Mar 10, 2018
@bpasero
Copy link
Member

bpasero commented Mar 12, 2018

/duplicate #45542

@vscodebot vscodebot bot added the *duplicate Issue identified as a duplicate of another issue(s) label Mar 12, 2018
@vscodebot
Copy link

vscodebot bot commented Mar 12, 2018

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for existing issues here. See also our issue reporting guidelines.

Happy Coding!

@vscodebot vscodebot bot closed this as completed Mar 12, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Apr 26, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

4 participants