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

Atom does not run over NX #2256

Closed
Weuxel opened this issue Jul 17, 2015 · 10 comments
Closed

Atom does not run over NX #2256

Weuxel opened this issue Jul 17, 2015 · 10 comments

Comments

@Weuxel
Copy link

Weuxel commented Jul 17, 2015

Atom does not start in an NX environment.

App load time: 150ms
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[7643:0716/110551:ERROR:gl_surface_glx.cc(357)] GLX 1.3 or later is required.
[7643:0716/110551:ERROR:gl_surface_x11.cc(56)] GLSurfaceGLX::InitializeOneOff failed.
[7643:0716/110551:ERROR:sandbox_linux.cc(325)] InitializeSandbox() called with multiple threads in process gpu-process
[7643:0716/110551:ERROR:gpu_child_thread.cc(146)] Exiting GPU process due to errors during initialization
atom: Fatal IO error 11 (Ressource is not available) on X server :1000.0.

Sent here from: atom/atom#7928

@zcbenz
Copy link
Member

zcbenz commented Jul 20, 2015

If Chromium works in it Electron should probably support it too, but I don't think anyone would actually look into it.

@Weuxel
Copy link
Author

Weuxel commented Aug 12, 2015

Yeah, Chromium works without problems, in fact Atom is the first Application i encountered that does not.
Would be sad if noone would look into it.

@codebytere
Copy link
Member

Closing due to abandonment.

@timholy
Copy link

timholy commented Feb 1, 2018

This issue still has reasonably recent activity: microsoft/vscode#3451
I was able to hack around this problem using tips in that issue, but modifying Xlibs is a little on the scary side.

@rob3c
Copy link

rob3c commented Jun 6, 2018

What does "abandonment" mean? This is listed as the upstream issue for both the Atom and VS Code editors, two fundamentally important parts of Atom Shell's...err, Electron's history.

@daviddesberg
Copy link

Why is this issue abandoned?

@gabefair
Copy link

This should really be reopened.

@jblee123
Copy link

Does "Closing due to abandonment" mean, " We're choosing to abandon this because we don't care," or "It looks the community doesn't care,"? Because if it's the latter, I think people still obviously care. Hacking a binary file isn't a quality solution (and that only worked once for me -- I'm now back to getting the same error even with the hacked file).

@sitsofe
Copy link

sitsofe commented Nov 22, 2018

(Note that ArcticaProject/nx-libs#729 strongly suggests this occurs due to servers (that are acting as X) not containing an old fix from 2007)

@electron-triage
Copy link

The Electron version reported on this issue is no longer supported. See our supported versions documentation.

If you're still experiencing this issue on a supported version, please open a new issue with an updated repro - a Fiddle is very appreciated.

Electron has a large issues backlog. To help our team prioritize, we're closing older issues and asking for new issues with updated repro steps if it affects a supported version. This helps sort what issues are still relevant and helps us fix them more quickly.

Thanks for your patience and understanding!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

12 participants