You are not logged in.
https://www.archlinux32.org/packages/pe … /chromium/
pentium4 pentium4/extra chromium 87.0.4280.141-1.0
chromium
[3714:3714:0220/211401.573148:ERROR:angle_platform_impl.cc(43)] Display.cpp:805 (initialize): ANGLE Display::initialize error 12289: OpenGL ES 2.0 is not supportable.
[3714:3714:0220/211401.581446:ERROR:gl_surface_egl.cc(773)] EGL Driver message (Critical) eglInitialize: OpenGL ES 2.0 is not supportable.
[3714:3714:0220/211401.587962:ERROR:gl_surface_egl.cc(1322)] eglInitialize OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type
[3714:3714:0220/211401.668644:ERROR:angle_platform_impl.cc(43)] Display.cpp:805 (initialize): ANGLE Display::initialize error 12289: Intel or NVIDIA OpenGL ES drivers are not supported.
[3714:3714:0220/211401.669267:ERROR:gl_surface_egl.cc(773)] EGL Driver message (Critical) eglInitialize: Intel or NVIDIA OpenGL ES drivers are not supported.
[3714:3714:0220/211401.669806:ERROR:gl_surface_egl.cc(1322)] eglInitialize OpenGLES failed with error EGL_NOT_INITIALIZED
[3714:3714:0220/211401.670369:ERROR:gl_initializer_linux_x11.cc(160)] GLSurfaceEGL::InitializeOneOff failed.
[3714:3714:0220/211401.723688:ERROR:viz_main_impl.cc(150)] Exiting GPU process due to errors during initialization
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0360
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0422
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0360
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0422
[3728:3728:0220/211402.243880:ERROR:vaapi_wrapper.cc(541)] vaInitialize failed: unknown libva error
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0372
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0372
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0360
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0372
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0360../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0422
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0360
[3827:3827:0220/211412.299812:ERROR:vaapi_wrapper.cc(541)] vaInitialize failed: unknown libva error
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0372
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0372
[3865:3865:0220/211419.717364:ERROR:vaapi_wrapper.cc(541)] vaInitialize failed: unknown libva error
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0372
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0372
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0372
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0372
[3913:3913:0220/211426.165919:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
Hello,
one archlinux32 start this one problem. :-((
No Chromiium doesn't work.
Greets
arch322(yes)
https://bugs.chromium.org/p/chromium/is … id=1052263
Last edited by arch322yes (2021-02-20 22:19:08)
Offline
Already logged, I think: https://bugs.archlinux32.org/index.php? … ask_id=162
Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.
Offline
Hello Developer, did we have the solution?
Is the problem solved?
Offline
Yes, there is a solution.
Record all syscalls happending in chromium when doing stuff, then adding those to the chromium source code and provide a patch.
The record is solved when a new chromium package gets released and the bug report above gets set to fixed.
Offline