Chromium is initially hidden when launched
Activity
Walt Miner February 11, 2019 at 11:11 PM
Close for FF 6.0.4 and GG 7.0.0

Julie Kim November 2, 2018 at 8:58 AM

Julie Kim November 2, 2018 at 1:11 AM
Oct 16 20:19:19 m3ulcb afbd-windowmanager-service-2017@0.1[3720]: [1153542.900] [wm DEBUG] [wayland_ivi_wm.cpp, surface_created(), Line:618] >>> compositor::controller @ 0xaaaaff2305a0 surface 0 (0)
Oct 16 20:19:19 m3ulcb afbd-windowmanager-service-2017@0.1[3720]: [1153542.961] [wm DEBUG] [wayland_ivi_wm.cpp, add_proxy_to_sid_mapping(), Line:688] >>> Add surface proxy mapping for 0xaaaaff2305a0 (0)
Oct 16 20:19:19 m3ulcb afbd-windowmanager-service-2017@0.1[3720]: [1153542.983] [wm DEBUG] [window_manager.cpp, surface_created(), Line:593] >>> Newly created surfce 0 is not associated with any layer!
....
Oct 16 20:19:19 m3ulcb afbd-windowmanager-service-2017@0.1[3720]: [1153589.162] [wm INFO] [window_manager.cpp, doEndDraw(), Line:1158] >>> req 5: do endDraw
Oct 16 20:19:19 m3ulcb afbd-windowmanager-service-2017@0.1[3720]: [1153589.180] [wm ERROR] [window_manager.cpp, layoutChange(), Line:1218] >>> req 5: client doesn't have surface with role(browser)
Oct 16 20:19:19 m3ulcb afbd-windowmanager-service-2017@0.1[3720]: [1153589.193] [wm WARNING] [window_manager.cpp, doEndDraw(), Line:1173] >>> req 5: Failed to manipulate surfaces while state change : Not registeredOct 16 20:19:19 m3ulcb afbd-windowmanager-service-2017@0.1[3720]: [1153589.205] [wm:pm DEBUG] [policy_manager.cpp, undoState(), Line:240] >>> Undo State !!!
I think WindowManager doesn't expect that application has surface
id 0 and that could be a root cause.

Julie Kim November 2, 2018 at 1:11 AM
After I checked some examples and comments, I updated browser role,
https://github.com/jkim-julie/chromium53-browser-service/commit/de1a900f669eb06df854fc058e3e9879fe6c694f

Julie Kim November 2, 2018 at 1:10 AM
m3ulcb:~# LayerManagerControl get surfaces
3 Surface(s):
Surface 1 (0x1)
Surface 2 (0x2)
Surface 0 (0x0)
First, I checked surfaces and found that browser has surface 0.
m3ulcb:~# LayerManagerControl get surface 0
surface 0 (0x0)
---------------------------------------
created by pid: 4115
original size: x=945, y=1060
destination region: x=0, y=0, w=945, h=1060
source region: x=0, y=0, w=945, h=1060
opacity: 1
visibility: 0
frame counter: 197
on layer: 1001(0x3e9)
And I found it doesn't have visibility. So, I forced to set visibility with the
command below.
m3ulcb:~# LayerManagerControl set surface 0 visibility 1
After that, browser's showed up.
Details
Details
Assignee

Reporter

When running Chromium, I have to make it visible manually:
/opt/chromium53/chrome --user-data-dir /opt/chromium53/workdir --in-process-gpu`
LayerManagerControl get surfaces && LayerManagerControl get surface 0
visibility
is 0LayerManagerControl set surface 0 visibility 1