I think I had the same issue on 23.04 and changing the setting to
Wayland fixed it for me.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2026886
Title:
[amdgpu] google chrome hardw
Have you tried running Chrome in native Wayland mode? Does it make a
difference to this bug?
chrome://flags/#ozone-platform-hint
Change the setting “Preferred Ozone platform” to “Wayland”, then click
Relaunch.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bu
awesome, thank you. I will keep the flag set :-)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2026886
Title:
[amdgpu] google chrome hardware acceleration broken on 42.9-0ubuntu2
Upstream has already "fixed" it by reverting the change in a later
release:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3030
Although this seems to be because they were waiting on a fix in Xwayland
version 23.1.0 which Ubuntu 22.04 doesn't have yet. It looks like the
downside they were
Hi Daniel, sorry for the delayed response.
MUTTER_DEBUG_SEND_KMS_MODIFIERS=1 fixes the issue. I can now use chrome
with hardware acceleration enabled without rendering problems.
Is there any long-term downside with leaving this flag set? Or should I
drop the environment entry when upstream has fi
Thanks! Sounds like this change in mutter 42.7:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2734
So a workaround might be to add MUTTER_DEBUG_SEND_KMS_MODIFIERS=1 to
/etc/environment
** Changed in: mutter (Ubuntu)
Status: New => Incomplete
--
You received this bug notificatio
** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2026886
Tit
Daniel van Vught wrote:
> I'm still struggling to understand how gnome-shell is triggering the
> corruption. Maybe try switching between 42.5 and 42.9 a few times again and
> verify in both cases the mutter packages remain 42.9.
I tried everything again from the beginning, and I _can_ reproduce
I'm still struggling to understand how gnome-shell is triggering the
corruption. Maybe try switching between 42.5 and 42.9 a few times again
and verify in both cases the mutter packages remain 42.9.
Also can you find any other app affected?
--
You received this bug notification because you are a
Daniel van Vugt wrote:
> On the slight chance this is related to another AMD GPU issue I've heard
> about in 42.9, please try adding this to /etc/environment:
> MUTTER_DEBUG_USE_KMS_MODIFIERS=0
This didn't help, unfortunately. What I did:
- Re-enabled hardware acceleration in chrome
- Confirmed
Also strange - your screenshots show corruption which should only be
relevant to mutter and the graphics drivers (kernel / mesa). I cannot
imagine how gnome-shell is related. More like gnome-shell is triggering
a bug in mutter, mesa, the kernel, or Chrome.
On the slight chance this is related to a
** Summary changed:
- google chrome hardware acceleration broken on 42.9-0ubuntu2
+ [amdgpu] google chrome hardware acceleration broken on 42.9-0ubuntu2
** Tags added: amdgpu regression-update
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscr
12 matches
Mail list logo
