Arch Linux

n3m

Member

Registered: 2014-10-08

Posts: 10

atom-editor: libGL error on start

Hi,
I'm new to this forum but managed to setup and use arch for some time now, so maybe move it, if it's the wrong subforum.
I installed GitHub's atom-editor from the AUR. Building it didn't throw up any errors, starting it does.

[8323:1010/091409:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
libGL error: MESA-LOADER: could not create udev device for fd 12
ATTENTION: default value of option force_s3tc_enable overridden by environment.
App load time: 57ms
[8376:1010/091409:INFO:renderer_main.cc(227)] Renderer process started
The program 'atom' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 267 error_code 2 request_code 12 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Whilst the sandbox-error might be, because atom starts chromium without a sandbox, I can't understand the libGL-error. Chromium/Chrome is based on libmesa (correct me, if I'm wrong) and both are running just fine.
I use Gnome 3.12.2, if this makes any difference, and I update my system 1-2 times a day by cron.
Thanks in advance

n3m

Member

Registered: 2014-10-08

Posts: 10

Re: atom-editor: libGL error on start

It seems that libmesa was broken. The current update fixed it.