On 4/12/22 08:02, Anthony Callegaro wrote:
Hi guys, I tried a few additional things to try to sort it out : - downgraded to my latest upgrade date : cat /etc/apt/sources.list.d/snapshot.list deb [check-valid-until=no] http://snapshot.debian.org/archive/debian-security/20220404T151623Z/ stable-security main contrib non-free cat /etc/apt/preferences.d/snapshot.pref Package: * Pin: origin snapshot.debian.org Pin-Priority: 1001 apt update apt upgrade - Also downgraded the flatpak dependencies (as there was some mesa.GL upgrade) So I guess that during the first Chromium run it changed a default parameter in my profile (enabling some hardware accelaration or so) which broke it. So I will try to reset my profile and keep you updated. Cheers
Speaking of mesa.GL, it occurs to me that libgles2 and other GL libraries should really be in your depends/recommends/suggests lists, but they're not (probably because they're detected and dlopened at runtime, similar to the problem we had in #1005230). What version of the following packages do you have installed?
libgles2 libgl1-mesa-dri libllvm11 libdrm-amdgpu1 libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 libdrm2 libva-drm2 libva-x11-2 libigdgmm11 libvulkan1 libglapi-mesa libglx-mesa0 libglx0 libgl1 libglvnd0
We don't have swiftshader enabled in debian chromium packages, so if there's something wrong with your hardware acceleration stuff, we don't have a good fallback.
