[ozone-dev] status of use_ozone=true + ozone_platform="x11" on Linux Desktop

[Julien Isorce]

Hi,

The following questions are about ozone x11, not ozone wayland which is
still on going http://crbug.com/578890 .

According to https://bugs.chromium.org/p/chromium/issues/detail?id=361137 I
understand that Ozone_x11 should now work on Linux Desktop, is it really
the case ?
I am asking because I tried few weeks ago, the build was ok but the browser
did not run.
Also according
to https://chromium.googlesource.com/chromium/src/+/master/docs/ozone_overview.md#Linux-Desktop-waterfall
it seems to be still in development but maybe the doc is not up to date.
The bot is green but I am not sure it actually run some
tests: https://build.chromium.org/p/chromium.fyi/builders/Ozone%20Linux/

Can someone confirm it works on a recent ubuntu for example ? With some
screenshots that would be awesome, not really as a proof but just because I
am curious of the visual result.

Also I guess it will replace completely the non-ozone linux x11/gtk
support, any target release ? even roughly.

Thx
Julien

[Sadrul Chowdhury]

Post by Julien Isorce
Hi,
The following questions are about ozone x11, not ozone wayland which is
still on going http://crbug.com/578890 .
According to https://bugs.chromium.org/p/chromium/issues/detail?id=361137
I understand that Ozone_x11 should now work on Linux Desktop, is it really
the case ?
I am asking because I tried few weeks ago, the build was ok but the
browser did not run.
Also according to https://chromium.googlesource.com/chromium/src/+/master/
docs/ozone_overview.md#Linux-Desktop-waterfall it seems to be still in
development but maybe the doc is not up to date.
https://build.chromium.org/p/chromium.fyi/builders/Ozone%20Linux/
Can someone confirm it works on a recent ubuntu for example ? With some
screenshots that would be awesome, not really as a proof but just because I
am curious of the visual result.

Chrome with ozone on non-chromeos linux is not expected to work right now
(on ToT), whether with x11 or any other ozone implementation. The missing
bits are not in the specific ozone implementation, but in chrome. Most of
the code in //chrome/ (and elsewhere, to be honest) expects that ozone
means chromeos. So non-chromeos build of ozone is missing some hooks needed
for the chrome browser to work.

Post by Julien Isorce
Also I guess it will replace completely the non-ozone linux x11/gtk
support, any target release ? even roughly.

I think we are still too far to predict a target release for chrome-ozone
on linux at this time. I believe tonikitoo@ et. al. have a series of
patches for chrome on ozone-wayland. You may find those useful/interesting.

Sadrul

[Antonio Gomes]

Hi Julien.

Precisely what Sadrul said. We have discussed the way forward in
BlinkOn, and I have put some slides together, including a rough plan
to get Linux/Desktop Ozone going in ToT:
https://docs.google.com/presentation/d/13TV2sjLlO8Nqqm6jgaNLwM9v03QEA0idIOS8MRouXJU/edit#slide=id.g1c52a5e48e_1_16

The "title" mentions "Wayland", but the way we are working on it will
leverage any Ozone backend (X11, Wayland, etc).

BR,

Post by Sadrul Chowdhury

Post by Julien Isorce
Hi,
The following questions are about ozone x11, not ozone wayland which is
still on going http://crbug.com/578890 .
According to https://bugs.chromium.org/p/chromium/issues/detail?id=361137
I understand that Ozone_x11 should now work on Linux Desktop, is it really
the case ?
I am asking because I tried few weeks ago, the build was ok but the
browser did not run.
Also according to
https://chromium.googlesource.com/chromium/src/+/master/docs/ozone_overview.md#Linux-Desktop-waterfall
it seems to be still in development but maybe the doc is not up to date.
https://build.chromium.org/p/chromium.fyi/builders/Ozone%20Linux/
Can someone confirm it works on a recent ubuntu for example ? With some
screenshots that would be awesome, not really as a proof but just because I
am curious of the visual result.

Chrome with ozone on non-chromeos linux is not expected to work right now
(on ToT), whether with x11 or any other ozone implementation. The missing
bits are not in the specific ozone implementation, but in chrome. Most of
the code in //chrome/ (and elsewhere, to be honest) expects that ozone means
chromeos. So non-chromeos build of ozone is missing some hooks needed for
the chrome browser to work.

Post by Julien Isorce
Also I guess it will replace completely the non-ozone linux x11/gtk
support, any target release ? even roughly.

I think we are still too far to predict a target release for chrome-ozone on
for chrome on ozone-wayland. You may find those useful/interesting.
Sadrul
--
You received this message because you are subscribed to the Google Groups
"Ozone-Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an

[Julien Isorce]

Thx you both for the clarification. Please send the list of issue trackers
once you have reached some sort of task breakdown.

Post by Antonio Gomes
Hi Julien.
Precisely what Sadrul said. We have discussed the way forward in
BlinkOn, and I have put some slides together, including a rough plan
https://docs.google.com/presentation/d/13TV2sjLlO8Nqqm6jgaNLwM9v03QEA
0idIOS8MRouXJU/edit#slide=id.g1c52a5e48e_1_16
The "title" mentions "Wayland", but the way we are working on it will
leverage any Ozone backend (X11, Wayland, etc).
BR,

On Fri, Feb 3, 2017 at 6:41 PM, Julien Isorce <

Post by Julien Isorce
Hi,
The following questions are about ozone x11, not ozone wayland which is
still on going http://crbug.com/578890 .
According to https://bugs.chromium.org/p/chromium/issues/detail?id=

361137

Post by Julien Isorce
I understand that Ozone_x11 should now work on Linux Desktop, is it

really

Post by Julien Isorce
the case ?
I am asking because I tried few weeks ago, the build was ok but the
browser did not run.
Also according to
https://chromium.googlesource.com/chromium/src/+/master/

docs/ozone_overview.md#Linux-Desktop-waterfall

Post by Julien Isorce
it seems to be still in development but maybe the doc is not up to date.
https://build.chromium.org/p/chromium.fyi/builders/Ozone%20Linux/
Can someone confirm it works on a recent ubuntu for example ? With some
screenshots that would be awesome, not really as a proof but just

because I

Post by Julien Isorce
am curious of the visual result.

Chrome with ozone on non-chromeos linux is not expected to work right now
(on ToT), whether with x11 or any other ozone implementation. The missing
bits are not in the specific ozone implementation, but in chrome. Most of
the code in //chrome/ (and elsewhere, to be honest) expects that ozone

means

chromeos. So non-chromeos build of ozone is missing some hooks needed for
the chrome browser to work.

Post by Julien Isorce
Also I guess it will replace completely the non-ozone linux x11/gtk
support, any target release ? even roughly.

I think we are still too far to predict a target release for

chrome-ozone on
patches

for chrome on ozone-wayland. You may find those useful/interesting.
Sadrul
--
You received this message because you are subscribed to the Google Groups
"Ozone-Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an

--
--Antonio Gomes

[Antonio Gomes]

Hi Julien. Sorry for the delaying in reply.

After the BlinkOn 7, where we could meet and agree with great googlers
(Robert, Fady et al, as well as sky@ and kylechar@, albeit virtually),
Frederic and I could start to really move things forward.

To be more transparent, I uploaded the slides in [1] with the break
down list of tasks and the current status.

In summary. we have the following macro tasks in the horizon:

0) Stub out ScreenManagerOzoneExternal, so that in non-chromeos
builds, we do not call out to ScreenManagerDelegate (i.e.
ws::DisplayManager), in order to get ws::Display instances created.
Instead, WindowTreeHostFactory will be used for driving the
ws::Display creation.

* https://codereview.chromium.org/2697693002/ (DONE)

1) change mus_demo to support internal and external window modes. This
was a multi CL task performed by Frederic Wang (with reviews from
sky@, kylechar@ and myself). Most relevant ones:

* https://codereview.chromium.org/2679213003/ (DONE)
* https://codereview.chromium.org/2693923004/ (DONE)
* https://codereview.chromium.org/2715533005/ (DONE)

2) Make sure multi external window creation can be tested by mus_demo

* https://codereview.chromium.org/2715533005/ (WIP, functional already
but blocked on _3_)

3) implement mojo / c++ changes in Mus so that multiple external
window can be created.

* https://codereview.chromium.org/2712203002/ (WIP)

4) Experimenting with launching the Chrome browser on this set up (Mus
+ external window mode). Note that Chrome today already the the right
thing (See DesktopWindowTreeHostMus creation in
https://cs.chromium.org/chromium/src/chrome/browser/ui/views/frame/browser_frame_mus.cc?type=cs&l=41),
so we assume it won't be too hard, once we can (3) finished.

TBD

5) Stabilize get Chrome/Mus running on top of the various Ozone
backends that matter to the desktop (X11, Wayland, etc).

TBD

I will keep updating the slides as we progressed on the tasks. Please
do not hesitate to ask questions, if any.

Best,

[1] https://docs.google.com/presentation/d/13TV2sjLlO8Nqqm6jgaNLwM9v03QEA0idIOS8MRouXJU/edit#slide=id.g1cd3a97327_0_45

On Fri, Feb 24, 2017 at 7:10 AM, Julien Isorce

Post by Julien Isorce
Thx you both for the clarification. Please send the list of issue trackers
once you have reached some sort of task breakdown.

Post by Antonio Gomes
Hi Julien.
Precisely what Sadrul said. We have discussed the way forward in
BlinkOn, and I have put some slides together, including a rough plan
https://docs.google.com/presentation/d/13TV2sjLlO8Nqqm6jgaNLwM9v03QEA0idIOS8MRouXJU/edit#slide=id.g1c52a5e48e_1_16
The "title" mentions "Wayland", but the way we are working on it will
leverage any Ozone backend (X11, Wayland, etc).
BR,

On Fri, Feb 3, 2017 at 6:41 PM, Julien Isorce

Post by Julien Isorce
Hi,
The following questions are about ozone x11, not ozone wayland which is
still on going http://crbug.com/578890 .
According to
https://bugs.chromium.org/p/chromium/issues/detail?id=361137
I understand that Ozone_x11 should now work on Linux Desktop, is it really
the case ?
I am asking because I tried few weeks ago, the build was ok but the
browser did not run.
Also according to
https://chromium.googlesource.com/chromium/src/+/master/docs/ozone_overview.md#Linux-Desktop-waterfall
it seems to be still in development but maybe the doc is not up to date.
https://build.chromium.org/p/chromium.fyi/builders/Ozone%20Linux/
Can someone confirm it works on a recent ubuntu for example ? With some
screenshots that would be awesome, not really as a proof but just because I
am curious of the visual result.

Chrome with ozone on non-chromeos linux is not expected to work right now
(on ToT), whether with x11 or any other ozone implementation. The missing
bits are not in the specific ozone implementation, but in chrome. Most of
the code in //chrome/ (and elsewhere, to be honest) expects that ozone means
chromeos. So non-chromeos build of ozone is missing some hooks needed for
the chrome browser to work.

Post by Julien Isorce
Also I guess it will replace completely the non-ozone linux x11/gtk
support, any target release ? even roughly.

I think we are still too far to predict a target release for chrome-ozone on
for chrome on ozone-wayland. You may find those useful/interesting.
Sadrul
--
You received this message because you are subscribed to the Google Groups
"Ozone-Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an

--
--Antonio Gomes

[s***@gmail.com]

I got a chance to return to this. I have copied your args and using the latest stable chrome download.
60.0.3112.90

is_debug = false
dcheck_always_on = true

use_ozone = true
ozone_platform_x11 = true
ozone_platform_gbm = false
ozone_platform_wayland = true

enable_package_mash_services = true
use_xkbcommon = true

enable_nacl = false
remove_webcore_debug_symbols = true

ninja -C out/Release/ chrome


out/Release/chrome --mus --ozone-platform=x11 --user-data-dir=/tmp/xdata --use-gl=egl
[32289:32292:0817/105700.854136:1803599963400:ERROR:instance.cc(49)] Unable to locate service manifest for ui
[32289:32292:0817/105700.854593:1803599963416:ERROR:service_manager.cc(782)] Failed to resolve service name: ui
[32289:32292:0817/105700.854603:1803599963426:ERROR:instance.cc(49)] Unable to locate service manifest for content_packaged_services
[32289:32292:0817/105700.854606:1803599963429:ERROR:service_manager.cc(782)] Failed to resolve service name: content_packaged_services

[Antonio Gomes]

Post by s***@gmail.com
I got a chance to return to this. I have copied your args and using the latest stable chrome download.
60.0.3112.90
is_debug = false
dcheck_always_on = true
use_ozone = true
ozone_platform_x11 = true
ozone_platform_gbm = false
ozone_platform_wayland = true
enable_package_mash_services = true
use_xkbcommon = true
enable_nacl = false
remove_webcore_debug_symbols = true
ninja -C out/Release/ chrome
out/Release/chrome --mus --ozone-platform=x11 --user-data-dir=/tmp/xdata --use-gl=egl
[32289:32292:0817/105700.854136:1803599963400:ERROR:instance.cc(49)] Unable to locate service manifest for ui
[32289:32292:0817/105700.854593:1803599963416:ERROR:service_manager.cc(782)] Failed to resolve service name: ui
[32289:32292:0817/105700.854603:1803599963426:ERROR:instance.cc(49)] Unable to locate service manifest for content_packaged_services
[32289:32292:0817/105700.854606:1803599963429:ERROR:service_manager.cc(782)] Failed to resolve service name: content_packaged_services

This is being worked out off-trunk for now. See
https://github.com/igalia/chromium/ , including build instructions.

Latest status:

Upstream plan is being carved out, but needs agreement with
Chromium/Google forks.

PS: we rebase our dev branch (named ozone-wayland-dev) every week.
Latest is based on Chromium 62 snapshot, as of last weekend.

-
Antonio