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 this with mutter 42.9 and gnome-shell 42.0. So I think you're right - this is probably a mutter bug. When I was testing initially, I relied on the built in chrome 'relaunch' button, which does not give a full clean restart. I have to fully restart the application for the bug to manifest (after re-enabling hardware acceleration). I tried to downgrade mutter to confirm that this package was the problem, but I can't go all the way back to v42.0 without apt trying to remove a whole bunch of critical packages. Unfortunately, I couldn't find v42.5 in my local cache or the repositories, either, to test with. Maybe you have a better suggestion that I could do to try and isolate the offending package? > Also can you find any other app affected? I haven't been able to reproduce this with any other applications, though I don't really use anything that stresses the GPU (likes games and such). I could look this weekend for something to try -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2026886 Title: [amdgpu] google chrome hardware acceleration broken on 42.9-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026886/+subscriptions -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
