Launching chromium-browser with --use-gl=ANYSTRING (ANYSTRING really
being any string, including invalid GL implementation names such as
"foobarbaz", or valid ones such as "swiftshader") makes the issue go
away.

Note that when passing an invalid GL implementation name, swiftshader
appears to be used, so this is the fallback option.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1696965

Title:
  First renderer process doesn't render page for chromium 59.0.3071.86
  in KVM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1696965/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to