[Bug 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap

2024-03-11 Thread Nathan Teodosio
For Chromium users: Can you verify if either of snap remove chromium snap install --beta chromium or snap remove chromium snap install --channel internal-libdrm chromium fixes the issue? Note: A refresh will *not* work for the first case, it really needs to be removed and installed

[Bug 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap

2024-03-08 Thread Dexter
Is there any known workaround for the spotify breakage? It has been broken for quite a while now... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2004532 Title: Hardware acceleration broken for

[Bug 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap

2024-03-07 Thread Nathan Teodosio
** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap

[Bug 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap

2024-03-06 Thread Dave Zielinski
This issue affected me as well on Ubuntu 22.04.4, running on a AMD Ryzen 9 7950X3D integrated graphics CPU. Took a late Feb update and it broke. I tried the various snap yaml modifications + snap try with no success. Workaround seems to be to run Firefox does work outside of snap:

[Bug 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap

2024-03-01 Thread Nathan Teodosio
** Description changed: - Possible, proposed solutions - - - Option 1: Please install from these channels and report back with - success or failure. - -   snap refresh --channel candidate/core22 firefox - - Option 2: - -   chromium --ozone-platform=wayland -   

[Bug 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap

2024-03-01 Thread Nathan Teodosio
It looks like this regressed in Chromium (probably when Chromium switched to core22) judging by LP:2054887. The fix for the lack of /usr/share/libdrm/amdgpu.ids is currently released on beta and will be soon in other channels too. ** Changed in: chromium-browser (Ubuntu) Status: Fix