New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 841539 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

[Ozone Wayland] Cannot run content_shell or ozone_demo

Project Member Reported by dnicoara@chromium.org, May 9 2018

Issue description

ToT build

GN args:

target_os = "chromeos"                                                          
                                                                                
use_ozone = true                                                                
ozone_platform_wayland = true                                                   
ozone_platform_x11 = true                                                       
ozone_platform_gbm = false                                                      
ozone_platform_headless = false                                                 
ozone_auto_platforms = false                                                    
                                                                                
use_xkbcommon = true

In a wayland session run:
content_shell --no-sandbox --ozone-platform=wayland

Nothing is shown.

In a wayland session run:
ozone_demo --ozone-platform=wayland

zxdg_surface_v6@14: error 3: xdg_surface has never been configured

 
Note, if I pass --in-process-gpu to content_shell, I see the same zxdg_surface_v6 error.
Components: Internals>GPU
Labels: -Pri-3 Proj-Ozone Pri-2
Owner: maksim.sisov@chromium.org
Status: Assigned (was: Untriaged)
Maksim: can you comment? I thought --in-process-gpu was suppose to work? Let's get the ECS build (and some sort of test) on the linux/ozone builders in the near future?

Sign in to add a comment