Atom does not start when using x2go #4360
Comments
I am on 0.179.0 and facing the same issue on Ubuntu 12.04.5 LTS (precise) with the Trusty Hardware Enablement Stack. Here's some verbose command output that may help:
Ubuntu info:
And the glxinfo output:
This is a VM running on KVM, so the VGA driver for it is generic and not GLX 1.3 capable:
Is there a setting in Atom that can disable this requirement (at an expected expense in rendering quality, of course)? |
If this is the general "doesn't work without DRI GLX", consider this a me-too. Running latest release from source on Debian Jessie, in a Virtualbox VM accessed through a Cygwin X-server (which supports aiglx). Initially it crashes on startup because it can't find swrast, after installing swrast I get this error (here just using raw X from guest to host, no ssh forwarding):
and sometimes this as well:
|
Updated on Ubuntu 14.04 from v177 to the latest version (186) today without a problem, using the .deb installer. |
On Ubuntu 14.04 (Mint 17) as host (running X client) Atom.io will not run in either x2go or TurboVNC sessions for similar reasons. So is Atom usable with any remote desktop software when running under Linux? Is there a way to pass something like " --disable-webgl " to Atom? Tried with Atom editor version: 0.192. |
Answering my own question: tigervnc (v 1.4.3.) does the job! Atom starts without a hitch. |
Still would be good to know if we could disable unnecessary webgl, since there's no reason to use VNC to access a VM running on the same computer. |
Confirming that it won't work for me either under X2Go on Ubuntu 14.04 due to the lack of GLX support in an X2Go session. Chromium's |
Same here using X2Go & Xubuntu 14.04 :( |
Not that the distro's really matters it's an Atom issue, but this also is preventing Atom to work through X2Go on Manjaro. |
rdesktop over VPN connection to a Ubuntu 14.04.2 LTS desktop fails with GLX 1.3 or later is required. Atom version 0.202.0 |
Same thing on Debian Jessie amd64 using x2go client atom 1.0.11 |
@thomasjo Why is this closed without any information? Is the bug fixed? |
@jrgifford Pretty sure I didn't mean to close this one. At the very least I don't understand why I did. Thanks for the heads up! |
Another "me too" for this. Been hoping to try Atom for a while but my main dev environment is an X2go one, so no luck there. Tried every possible chromium option I could think of that disabled GPU acceleration/WebGL but no dice. Chrome/Chromium on the other hand do work over X2go. |
Me too... trying to use Atom via a manually compiled xrdp 0.9.0. Chrome, however, complaints in the same way as Atom, but starts fine: |
Same problem using Ubuntu 15.10 desktop. Any workarounds yet? |
I am also getting this issue on Ubuntu Mate 15.10 |
Same issue with dpkg install of v1.5 (atom-amd64.deb) on headless 12.04 server (bare metal) --> vnc |
I was seeing the same error message and debugged it down to an X extension "BIG-REQUESTS". You can use xtrace to trace all the X traffic and I saw an 8MB message before it crashed. |
@tonywmnix - the libxcb.so.1 hack worked for me with Ubuntu Mate 15.10 via XRDP. Thanks. |
@tonywmnix & @ironicbadger I've Windows10 host with Xubuntu 15.10 on Hyper-V and RDP session (not the most convenient solution but the only one working reasonably with UHD monitor). |
@bs-ug I just used |
@ironicbadger - So simple! Thanks! |
@tonywmnix libxcb.so.1 hack worked for me on Debian. Well done |
And why not just use a symlink to the original file? |
Just to give an update here that ubuntu 14.04 LTS with atom 1.5.4 debian package downloaded from https://atom.io/ works out of the box without any issues over xrdp. Cheers, - Nestor |
It worked for me on CentOS 7 with XFCE on X2GO with both the Website Version of Atom and the COPR Repository Version: Instructions: METHOD 1: WEBSITE VERSION OF ATOM yum install libXScrnSaver redhat-lsb-core.x86_64 libXScrnSaver.i686 -=======================================- wget https://copr-be.cloud.fedoraproject.org/results/alonid/yum-plugin-copr/epel-7-x86_64/00110045-yum-plugin-copr/yum-plugin-copr-1.1.31-508.el7.centos.noarch.rpm HOWTO INSTALL X2GO with XFCE on Cento7 #1. Add EPEL repository first. #2. Then, install X2Go server package using command: #3. Install XFCE Desktop Hope this helps! |
The libxcb.so.1 hack works for me on Fedora 25 with X2Go and XFCE. |
@zparihar |
That's interesting... Can you specify the full path of atom when you edit
the menu item?
…On Jan 20, 2017 8:09 PM, "chagara" ***@***.***> wrote:
@zparihar <https://github.com/zparihar>
this worked for me on rhel 7.2 but, I can only launch it from CL.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4360 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AApx2rV6Um66a_XVkcQaG8TszqDZezmEks5rUYUBgaJpZM4DChRJ>
.
|
@zacharysarah woks for me on CentOS latest(7.3?). |
Bug still present in Atom 1.15.0 |
Bug is also present in the 1.16 beta. If you happen to be testing the beta, remember to update the copy and said as appropriate. Using CentOS 7.3 x2go with MATE works just fine now. |
Bug is still exists in 1.15.0 but @tonywmnix hack's works well on Ubuntu 14.04.5 LTS |
The libgconf-2-4 package might be missing preventing the application to launch. |
Title is a not really Atom does not start when using x2go it more of window manager for x not x2go or tightvncserver Came across this when Debian from minimal install go thro atom install then it works for x2go and tightvncserver |
The hack does works on Ubuntu 16.04. However, I found the backspace doesn't work in the vscode editor panel(backspace works at search panel and command panel) and also, I cannot select the completion with enter. Is it possible that is the side-effect of the hack library? |
I use atom via X2GO and decided to disable the BIG-REQUESTS extension of X2Go:
Then restart the server and reconnect to have atom working in x2go |
bneijt's solution worked like a charm. Prefer it over patching shared objects with regular expressions. |
@bneijt by server do you mean service(software) or server(machine)? |
@elico service, not the whole server. It is a setting specific to the x2go service (software) |
@bneijt Thanks! |
Getting problems when running this on a server to which I connect using ssvnc.
However with more recent versions, 1.19.0 or 1.20.--beta0 a different problem occurs: atom does start but all characters inside the editor window (with the exception of the menu bar which is in Courier) are shown as reactangles (unknown character placeholders?) |
The fix for a ppa based install of Atom for both x11 forwarding and x2go using Ubuntu 16.04 and Mint is: I did not have the same problem listed by @johann-petrak. |
I experienced the atom/x2go problem on Ubuntu with atom from both the standard repository (i.e., installation via "snap") and with atom from the webupd8team launchpad repository. @bneijt's answer works, and as others have mentioned, has the advantage that it does not require patching code that may or may not need to be re-patched in the next release. Please note that you must add "-extension BIG_REQUESTS" on the server, i.e., the remote server that you're connecting to. |
Not using x2go (at least I don't believe I am), but experienced the same problem on Linux Mint 18.2 (MATE). |
Thanks @ggodreau for the easy steps specific to version 16 |
As noted in other Atom bugs this appears to be a version of an upstream bug electron/electron#2256 that affects some VNC/NX servers (note that new versions of tigervnc's server do not seem to manifest this issue). |
Thanks for your contribution! This issue has been automatically marked as stale because it has not had recent activity. Because the Atom team treats their issues as their backlog, stale issues are closed. If you would like this issue to remain open:
Issues that are labeled as triaged will not be automatically marked as stale. |
$ [20853:1201/101159:ERROR:browser_main_loop.cc(162)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
Xlib: extension "XInputExtension" missing on display ":10.0".
Xlib: extension "XInputExtension" missing on display ":10.0".
App load time: 368ms
[20877:1201/101159:ERROR:gl_surface_glx.cc(333)] GLX 1.3 or later is required.
[20877:1201/101159:ERROR:gl_surface_x11.cc(57)] GLSurfaceGLX::InitializeOneOff failed.
[20877:1201/101200:ERROR:gpu_child_thread.cc(143)] Exiting GPU process due to errors during initialization
atom: Fatal IO error 11 (Resource temporarily unavailable) on X server :10.0.
sudo add-apt-repository ppa:webupd8team/atom
sudo apt-get update
sudo apt-get install atom
However I got the same issue.
To replicate just right click on a file to get a context menu and once you start moving your mouse it will fail with the error above.
The text was updated successfully, but these errors were encountered: