Now that you mention it, that sounds like bug 1511278 which is probably related. Made progress on that last year with a proof of concept workaround. Essentially I think this is related to the fact that Xorg expects and requires single buffering (or at least back buffer preservation), but Mir supports neither of those yet.
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1510025 Title: Chrome/Chromium browser in Xmir (in DRI2 mode): Page contents never visible, all black, all white, or flickering Status in Canonical System Image: New Status in xorg-server package in Ubuntu: Triaged Bug description: Chromium browser in Xmir (in DRI2 mode): Page contents never visible (all white) and/or all black windows DRI2 mode is the default mode for Xmir on desktop and it fails in similar ways for both rootless and non-rootless Xmir. In chromium- browser, fully loaded pages often display as all white. Or you get the whole window being black. In both cases for -rootless and non-rootless mode, using the software rendering fallback works around the problem: Xmir -sw To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1510025/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
