Thank you for responding so quickly :-) Danial van Vugt wrote: > When reporting bugs in the future please use apport by using 'ubuntu-bug' and > the name of the package affected.
Can do :-) > Or if you prefer to collect info manually, please run these commands while the problem is happening [...] and attach the resulting text files here. Done. Let me know if I can provide anything else > Was it only downgrading gnome-shell that helped or were you actually > downgrading the mutter packages too? I only downgraded gnome-shell and gnome-shell-common. I left mutter as it was. Something else strange that I noticed: if I disable hardware acceleration, then enable it again, chrome appears to work fine. So the behavior I'm seeing looks like: - Start at v42.0 of gnome-shell and gnome-shell-common - Upgrade to v42.9 of gnome-shell and gnome-shell-common - Note strange rendering in chrome - Logout/login - Note strange rendering in chrome persists - Reboot - Note strange rendering in chrome persists - Disable hardware acceleration in chrome - Note rendering in chrome is now fixed - Enable hardware acceleration in chrome - Note rendering in chrome still works -- 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: 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 desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
