Chromium is not running on Wayland

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Chromium is not running on Wayland

4,093 Views
senthilkumar_s1
Contributor II

Hello All,

We are tying to run chromium on Wayland Weston compositor.

I am using YOCTO linux distribution in i.MX6Q Sabre SD board.

Chromium version = 48.0.25

Kernel version = 4.1.28-fslc+g0844f

Weston Version = 1.9.0

EGL version = 1.4

Used following command to run on Weston terminal.

> google-chrome

Getting following error

[534:534:0725/083535:ERROR:desktop_window_tree_host_ozone.cc(572)] Not implemented reached in virtual void view

s::DesktopWindowTreeHostOzone::SetWindowIcons(const gfx::ImageSkia&, const gfx::ImageSkia&)

[534:534:0725/083535:ERROR:ozone_webui.cc(60)] Not implemented reached in virtual void views::OzoneWebUI::GetDe

faultFontDescription(std::__cxx11::string*, int*, int*, gfx::FontRenderParams*) const

[534:534:0725/083535:ERROR:ozone_webui.cc(51)] Not implemented reached in virtual gfx::FontRenderParams views::

OzoneWebUI::GetDefaultFontRenderParams() const

[534:534:0725/083535:ERROR:ozone_webui.cc(51)] Not implemented reached in virtual gfx::FontRenderParams views::

OzoneWebUI::GetDefaultFontRenderParams() const

[534:534:0725/083535:ERROR:ozone_webui.cc(51)] Not implemented reached in virtual gfx::FontRenderParams views::

OzoneWebUI::GetDefaultFontRenderParams() const

[534:534:0725/083535:ERROR:ozone_webui.cc(51)] Not implemented reached in virtual gfx::FontRenderParams views::

OzoneWebUI::GetDefaultFontRenderParams() const

[534:534:0725/083535:ERROR:ozone_webui.cc(51)] Not implemented reached in virtual gfx::FontRenderParams views::

OzoneWebUI::GetDefaultFontRenderParams() const

[562:562:0725/083535:ERROR:sandbox_linux.cc(338)] InitializeSandbox() called with multiple threads in process g

pu-process

[534:534:0725/083535:ERROR:ozone_webui.cc(51)] Not implemented reached in virtual gfx::FontRenderParams views::

OzoneWebUI::GetDefaultFontRenderParams() const

/usr/bin/google-chrome: line 11:   534 Segmentation fault      /usr/bin/chromium/chrome ${CHROME_EXTRA_ARGS} $@

Please help me to resolve this issue.

Thanks,

Senthil.

Labels (4)
0 Kudos
3 Replies

2,132 Views
chadwagner
Contributor I

I would like to see it working as well.

0 Kudos

2,132 Views
thomasgrimault
Contributor I

Hi All,

I have the similar problem with the same version of chromium, but with the following system:

Device : imx6qdl (custom board, based on SabreSD)

Kernel version = 3.14.52+g5f6f0a5
Weston Version = 1.9.0

imx-gpu-viv = 5.0.11.p7.4

Terminal output:

root@imx6qh120:~# /usr/bin/chromium/chrome --use-gl=egl --user-data-dir=/home/chrome
[2702:2702:0922/105852:FATAL:browser_main_loop.cc(202)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on devel.
#0 0x00007319780a <unknown>
#1 0x0000731a6f8e <unknown>
#2 0x000074bbd210 <unknown>
#3 0x000074a69bd4 <unknown>
#4 0x000074a690b0 <unknown>
#5 0x000073168ef0 <unknown>
#6 0x00007316874a <unknown>
#7 0x000072e97b5c ChromeMain
#8 0x00007207bcf8 __libc_start_main

Aborted

If someone got Chromium 48 working on a linux-imx kernel and weston 1.9.0, I am interested in knowing about the kernel+imc-gpu-viv config, as well as the chromium launch command involved.

Thanks,

Thomas

0 Kudos

2,132 Views
igorpadykov
NXP Employee
NXP Employee

Hi Senthil

one can try with nxp bsp and please refer to attached Yocto Guide

sect.5.6.6 Chromium Browser on X11 and Wayland

i.MX 6 Series Software and Development Tool|NXP

regarding l4.1.28-fslc one can post on  meta-fsl-arm mailing list,

so that someone familiar with that version could try to assist you.

https://lists.yoctoproject.org/listinfo/meta-freescale

community (fslc) vs nxp official bsp :

https://community.freescale.com/message/402940#402940

Best regards

igor

-----------------------------------------------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer button. Thank you!

-----------------------------------------------------------------------------------------------------------------------

0 Kudos