You are not logged in.
Hi guys,
This morning, after a sudo pacman -Syyu (actually triggered by a yay -Syyu), chrome and brave stopped working. Every time I try to launch them, I get a blank screen. If I run google-chrome-stable from console, I get this:
[13928:13928:0329/091934.475193:ERROR:angle_platform_impl.cc(43)] renderergl_utils.cpp:2152 (ClearErrors): Preexisting GL error 0x00000505 as of ../../third_party/angle/src/libANGLE/renderer/gl/TextureGL.cpp, set ImageHelper:256.
[13928:13928:0329/091934.552940:ERROR:angle_platform_impl.cc(43)] renderergl_utils.cpp:2152 (ClearErrors): Preexisting GL error 0x00000505 as of ../../third_party/angle/src/libANGLE/renderer/gl/TextureGL.cpp, set ImageHelper:256.
Googling a bit, I found this .config/chrome-flags.conf:
--ignore-gpu-blocklist
--enable-gpu-rasterization
--enable-oop-rasterization
--disable-gpu-driver-bug-workarounds
--enable-accelerated-video-decode
--use-gl=desktop
--enable-zero-copy
--enable-vulkan
--enable-native-gpu-memory-buffers
and error became this:
[20784:1:0329/092811.310197:ERROR:command_buffer_proxy_impl.cc(122)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer.
[20792:1:0329/092811.403698:ERROR:command_buffer_proxy_impl.cc(122)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer.
I managed to launch chrome with --disable-gpu flag, but I'd like to enable gpu (this is a laptop with nvidia gtx 1050Ti + intel integrated). And this is what I upgraded this morning:
$ sudo find /var/cache/pacman/pkg/ -mtime -2
/var/cache/pacman/pkg/
/var/cache/pacman/pkg/less-1:563-1-x86_64.pkg.tar.zst
/var/cache/pacman/pkg/socat-1.7.4.1-1-x86_64.pkg.tar.zst
/var/cache/pacman/pkg/filezilla-3.53.1-1-x86_64.pkg.tar.zst
/var/cache/pacman/pkg/gtk3-1:3.24.28-1-x86_64.pkg.tar.zst
/var/cache/pacman/pkg/imagemagick-7.0.11.5-1-x86_64.pkg.tar.zst
/var/cache/pacman/pkg/p7zip-17.04-1-x86_64.pkg.tar.zst
/var/cache/pacman/pkg/libwpe-1.10.0-1-x86_64.pkg.tar.zst
/var/cache/pacman/pkg/libfilezilla-0.27.1-1-x86_64.pkg.tar.zst
/var/cache/pacman/pkg/libxaw-1.0.14-1-x86_64.pkg.tar.zst
/var/cache/pacman/pkg/pango-1:1.48.4-1-x86_64.pkg.tar.zst
/var/cache/pacman/pkg/ttf-dejavu-2.37+18+g9b5d1b2f-3-any.pkg.tar.zst
/var/cache/pacman/pkg/whois-5.5.9-1-x86_64.pkg.tar.zst
/var/cache/pacman/pkg/gcr-3.40.0-1-x86_64.pkg.tar.zst
Any ideas?
Last edited by ExoDoom (2021-03-30 07:45:48)
Offline
On first guess I'd say the mesa update, does standard GL work?
glxinfo -B #Needs mesa-demos
Online
name of display: :0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Collabora Ltd (0x10de)
Device: zink (GeForce GTX 1070) (0x1ba1)
Version: 21.0.1
Accelerated: yes
Video memory: 8438MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 4.1
Max compat profile version: 3.0
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 2.0
OpenGL vendor string: Collabora Ltd
OpenGL renderer string: zink (GeForce GTX 1070)
OpenGL core profile version string: 4.1 (Core Profile) Mesa 21.0.1
OpenGL core profile shading language version string: 4.10
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profileOpenGL version string: 3.0 Mesa 21.0.1
OpenGL shading language version string: 1.30
OpenGL context flags: (none)OpenGL ES profile version string: OpenGL ES 2.0 Mesa 21.0.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16
And yes, I have just realized it's a 1070, not a 1050.
Offline
Had the same issue. Downgrading mesa fixed it for me:
sudo pacman -U /var/cache/pacman/pkg/mesa-20.3.4-3-x86_64.pkg.tar.zst
Last edited by ianks (2021-03-29 18:48:56)
Offline
Thank you guys, downgrading mesa did the trick.
Offline