[meta-freescale] Chromium against Wayland on Krogoth?

[Mark Farver]

Of course the moment I said that I realized I had not tried the
"--ignore-gpu-blacklist" option.  Now it at least starts.

On Mon, Dec 19, 2016 at 4:42 PM, Mark Farver <mfarver at mindbent.org> wrote:
> Has anyone successfully run Chromium on Krogoth using Wayland/weston?
> I'm stuck on the "InitializeSandbox() called with multiple threads in
> process gpu-process" bug that a lot of people seem to have reported,
> but I haven't found any good solutions for.
>
>
> # google-chrome
> [585:585:1211/052605:ERROR:desktop_window_tree_host_ozone.cc(572)] Not
> implemented reached in virtual void
> views::DesktopWindowTreeHostOzone::SetWindowIcons(const
> gfx::ImageSkia&, const gfx::Im)
> [585:585:1211/052605:ERROR:ozone_webui.cc(60)] Not implemented reached
> in virtual void
> views::OzoneWebUI::GetDefaultFontDescription(std::__cxx11::string*,
> int*, int*, gfx::FontRenderParams*) cot
> [585:585:1211/052605:ERROR:ozone_webui.cc(51)] Not implemented reached
> in virtual gfx::FontRenderParams
> views::OzoneWebUI::GetDefaultFontRenderParams() const
> [585:585:1211/052605:ERROR:ozone_webui.cc(51)] Not implemented reached
> in virtual gfx::FontRenderParams
> views::OzoneWebUI::GetDefaultFontRenderParams() const
> [613:613:1211/052605:ERROR:sandbox_linux.cc(338)] InitializeSandbox()
> called with multiple threads in process gpu-process
> /usr/bin/google-chrome: line 11:   585 Segmentation fault      (core
> dumped) /usr/bin/chromium/chrome ${CHROME_EXTRA_ARGS} $@