Re: [voidlinux/void-packages] chromium-53.0.2785.116_1 on x86_64-musl seems broken (#4843)

Steven Dee at Mon, 26 Sep 2016 11:03:59 -0700
[chromium.txt](https://github.com/voidlinux/void-packages/files/493815/chromium.txt) [chromium-no-sandbox.txt](https://github.com/voidlinux/void-packages/files/493816/chromium-no-sandbox.txt)
Steven Dee at Mon, 26 Sep 2016 11:08:30 -0700
No chromium instance is running on subsequent start -- I'm guessing the log output is only when it first creates the config directory.
Steven Dee at Mon, 26 Sep 2016 11:28:47 -0700
Everything's upated -- this is a fresh install. I'm on a Thinkpad X220 with Intel video fwiw.
Steven Dee at Mon, 26 Sep 2016 11:33:33 -0700
Bizarre! Maybe there's some dependency one of us has installed that is needed but not listed.
Steven Dee at Mon, 26 Sep 2016 11:48:29 -0700
Fascinating! I'm also noticing that glxgears doesn't work, so this may not be a chromium issue after all. But the way glxgears is broken is slightly different: it always shows a black screen, regardless of what used to be under it.
Steven Dee at Mon, 26 Sep 2016 11:54:23 -0700
And fwiw Xorg.0.log seems to indicate that the intel module is being loaded.
Steven Dee at Mon, 26 Sep 2016 12:28:22 -0700
Huh. In linux4.8 chromium is at least usable -- in linux4.7 my success rate was 0.
zqqw at Mon, 26 Sep 2016 14:41:51 -0700
https://forum.voidlinux.eu/t/hardware-acceleration-chromium/867 You can disable various features with graphics drivers such as 3D rendering or hardware acceleration. It is usually done via conf files, kernel module options or options added to the kernel command line, and could provide a workaround. Intel are quite good with computers I have observed which might also suggest the real problem is not in the kernel. Most of the graphics stack is outside it in xorg and various rendering libs.