Chromium segfault
#1
Sun, 2015-11-22 09:22
pwFoo
-
- Offline
- 7 months 1 week ago
- 2015-08-27
Chromium segfault during start (Alpine 3.2, Fluxbox).
libGL error: failed to open drm device: Permission denied libGL error: failed to load driver: i965 libGL error: unable to load driver: swrast_dri.so libGL error: failed to load driver: swrast [2949:2949:1122/091108:ERROR:gl_context_glx.cc(54)] Failed to create GL context with glXCreateContextAttribsARB. [2949:2949:1122/091108:ERROR:gpu_info_collector.cc(41)] gfx::GLContext::CreateGLContext failed [2949:2949:1122/091108:ERROR:gpu_info_collector.cc(95)] Could not create context for info collection. [2949:2949:1122/091108:ERROR:gpu_main.cc(429)] gpu::CollectGraphicsInfo failed (fatal). [2949:2949:1122/091108:ERROR:gpu_child_thread.cc(235)] Exiting GPU process due to errors during initialization [2831:2831:1122/091108:ERROR:background_mode_manager_aura.cc(14)] Not implemented reached in virtual void BackgroundModeManager::EnableLaunchOnStartup(bool) [2831:2851:1122/091108:ERROR:browser_gpu_channel_host_factory.cc(132)] Failed to launch GPU process. [2831:2851:1122/091108:ERROR:browser_gpu_channel_host_factory.cc(132)] Failed to launch GPU process. Segmentation fault
Workaround:
chmod 777 /dev/dri/card0
But again chromium isn't starting.
MESA-LOADER: could not create udev device for fd 88 [3838:3838:1122/091251:ERROR:background_mode_manager_aura.cc(14)] Not implemented reached in virtual void BackgroundModeManager::EnableLaunchOnStartup(bool) [3:3:0100/000000:FATAL:zygote_linux.cc(449)] Check failed: len > 0 (0 vs. 0) Received signal 6 r8: 0000000000000061 r9: 0000000000000048 r10: 0000000000000008 r11: 0000000000000246 r12: 000079bba0fdf448 r13: 000079bba0fdf450 r14: 0000000000000000 r15: 0000000000000000 di: 0000000000000002 si: 000079bba0fdee70 bp: 000079bba0fdee70 bx: 0000000000000006 dx: 0000000000000000 ax: 0000000000000000 cx: 00006f7a1f751f1a sp: 000079bba0fdee58 ip: 00006f7a1f751f1a efl: 0000000000000246 cgf: 0000000000000033 erf: 0000000000000000 trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000 [end of stack trace] [19:19:0100/000000:FATAL:zygote_linux.cc(420)] Failed to synchronise with parent zygote process Received signal 6 r8: 00000a8b7a53fe4f r9: 0000000000000048 r10: 0000000000000008 r11: 0000000000000246 r12: 000079bba0fdf5e0 r13: 000079bba0fdf5e8 r14: 0000000000000000 r15: 0000000000000000 di: 0000000000000002 si: 000079bba0fdee70 bp: 000079bba0fdee70 bx: 0000000000000006 dx: 0000000000000000 ax: 0000000000000000 cx: 00006f7a1f751f1a sp: 000079bba0fdee58 ip: 00006f7a1f751f1a efl: 0000000000000246 cgf: 0000000000000033 erf: 0000000000000000 trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000 [end of stack trace] Segmentation fault
It's possible to run chromium as root.
sudo chromium-browser --no-sandbox
Tested with xfce instead of fluxbox and chromium starts as normal user without problems...
So why it doesn't work with fluxbox ?!
Remove linux-grsec with linux-vanilla solved some problems. Now this one appears...
try
Hi ScrumpyJack,
thank you for your reply.
Here the tests.
--enable-sandbox
sudo chmod 777 /dev/dri/card0
Any idea what's wrong with udev / eudev?
chromium-browser --no-sandbox
Working command: sudo chromium-browser --no-sandbox
Browser window opens and is usable...