Re: about windowmanager timeout problem.

Hi AGL, Is there any solution about that?

I found similar situation.

If I change date using date command like "date -s 2019-01-01", same problem occurred.

Also, I Checked Window Manager Log.

If Windowmanager work well, below log is presented.

But, not work, below log isn't presented.

May 18 07:34:20 s5p4418-navi-ref afbd-windowmanager-service-2017@0.1[2990]: [4210234.610] [wm DEBUG] [policy.hpp, layout_is_valid(), Line:29] >>> Policy check returns positive
May 18 07:34:20 s5p4418-navi-ref afbd-windowmanager-service-2017@0.1[2990]: [4210234.763] [wm DEBUG] [app.cpp, operator()(), Line:378] >>> Layout: normal
May 18 07:34:20 s5p4418-navi-ref afbd-windowmanager-service-2017@0.1[2990]: [4210234.824] [wm DEBUG] [app.cpp, surface_set_layout(), Line:303] >>> surface_set_layout for surface 4 on layer 1001
May 18 07:34:20 s5p4418-navi-ref afbd-windowmanager-service-2017@0.1[2990]: [4210235.126] [wm DEBUG] [app.cpp, surface_set_layout(), Line:314] >>> Surface 4 now on layer 1001 with rect { 0, 0, 1024, 600 }
May 18 07:34:20 s5p4418-navi-ref afbd-windowmanager-service-2017@0.1[2990]: [4210235.518] [wm DEBUG] [app.cpp, send_event(), Line:604] >>> send_event: syncdraw(MoviePlayer, normal.full)
May 18 07:34:20 s5p4418-navi-ref afbd-windowmanager-service-2017@0.1[2990]: [4210235.829] [wm DEBUG] [app.cpp, send_event(), Line:612] >>> afb_event_push failed: Success
May 18 07:34:20 s5p4418-navi-ref afbd-windowmanager-service-2017@0.1[2990]: [4210235.972] [wm DEBUG] [app.cpp, enqueue_flushdraw(), Line:556] >>> Enqueuing EndDraw for surface_id 4
May 18 07:34:20 s5p4418-navi-ref afbd-movieplayer@0.1[3082]: [4210228.150] [libwm DEBUG] [libwindowmanager.cpp, activateSurface(), Line:340] >>> called
May 18 07:34:20 s5p4418-navi-ref afbd-movieplayer@0.1[3082]: [4210236.844] [libwm DEBUG] [libwindowmanager.cpp, endDraw(), Line:366] >>> called
May 18 07:34:20 s5p4418-navi-ref afbd-windowmanager-service-2017@0.1[2990]: [4210238.239] [wm DEBUG] [app.cpp, send_event(), Line:592] >>> send_event: visible(MoviePlayer)
May 18 07:34:20 s5p4418-navi-ref afbd-windowmanager-service-2017@0.1[2990]: [4210238.397] [wm DEBUG] [app.cpp, send_event(), Line:599] >>> afb_event_push failed: Success
May 18 07:34:20 s5p4418-navi-ref afbd-windowmanager-service-2017@0.1[2990]: [4210238.456] [wm DEBUG] [app.cpp, send_event(), Line:592] >>> send_event: active(MoviePlayer)
May 18 07:34:20 s5p4418-navi-ref afbd-windowmanager-service-2017@0.1[2990]: [4210238.508] [wm DEBUG] [app.cpp, send_event(), Line:599] >>> afb_event_push failed: Success
May 18 07:34:20 s5p4418-navi-ref afbd-windowmanager-service-2017@0.1[2990]: [4210238.573] [wm DEBUG] [app.cpp, send_event(), Line:592] >>> send_event: flushdraw(MoviePlayer)
May 18 07:34:20 s5p4418-navi-ref afbd-windowmanager-service-2017@0.1[2990]: [4210239.361] [wm DEBUG] [wayland.cpp, surface_visibility(), Line:598] >>> compositor::surface surface_visibility @ 4 v 1

2019년 1월 2일 (수) 오후 4:59, Young Moon Jung <jung@xxxxxxxxxxx>님이 작성:

Hi AGL.

I have a question about window manager.

I got a jounalctl log message like below after a time( I don't know exact time. )

May 18 08:33:56 s5p4418-navi-ref systemd[1]: Starting dnf automatic notification of updates...
May 18 08:33:56 s5p4418-navi-ref systemd[1]: Starting dnf automatic install updates...
May 18 08:33:56 s5p4418-navi-ref systemd[1]: Starting dnf automatic download updates...
May 18 08:33:58 s5p4418-navi-ref systemd[1]: Started dnf automatic install updates.

When I got this log, windowmanager not working with getting below log message.

May 18 08:34:09 s5p4418-navi-ref afbd-windowmanager-service-2017@0.1[3025]: [3503681.581] [wm DEBUG] [main.cpp, cbRemoveClientCtxt(), Line:169] >>> remove app OnScreenApp
May 18 08:34:09 s5p4418-navi-ref afbd-windowmanager-service-2017@0.1[3025]: [3503681.825] [wm DEBUG] [wayland.cpp, operator()(), Line:546] >>> ~surface surface 1 @ 0x4f28c0
May 18 08:34:09 s5p4418-navi-ref afbd-windowmanager-service-2017@0.1[3025]: [3503681.882] [wm DEBUG] [wayland.cpp, remove_proxy_to_id_mapping(), Line:685] >>> Remove surface proxy mapping for 0x4f28c0
May 18 08:34:09 s5p4418-navi-ref afbd-windowmanager-service-2017@0.1[3025]: [3503681.974] [wm DEBUG] [main.cpp, cbRemoveClientCtxt(), Line:178] >>> delete surfaceID 1
May 18 08:34:09 s5p4418-navi-ref afbd-windowmanager-service-2017@0.1[3025]: [3503682.012] [wm DEBUG] [main.cpp, cbRemoveClientCtxt(), Line:169] >>> remove app HomeScreen
May 18 08:34:09 s5p4418-navi-ref afbd-windowmanager-service-2017@0.1[3025]: [3503682.044] [wm DEBUG] [wayland.cpp, operator()(), Line:546] >>> ~surface surface 2 @ 0x4f3858
May 18 08:34:09 s5p4418-navi-ref afbd-windowmanager-service-2017@0.1[3025]: [3503682.071] [wm DEBUG] [wayland.cpp, remove_proxy_to_id_mapping(), Line:685] >>> Remove surface proxy mapping for 0x4f3858
May 18 08:34:09 s5p4418-navi-ref afbd-windowmanager-service-2017@0.1[3025]: [3503682.113] [wm DEBUG] [main.cpp, cbRemoveClientCtxt(), Line:178] >>> delete surfaceID 2
May 18 08:34:09 s5p4418-navi-ref afbd-windowmanager-service-2017@0.1[3025]: [3503682.144] [wm DEBUG] [main.cpp, cbRemoveClientCtxt(), Line:169] >>> remove app BottomBar
May 18 08:34:09 s5p4418-navi-ref afbd-windowmanager-service-2017@0.1[3025]: [3503682.187] [wm DEBUG] [wayland.cpp, operator()(), Line:546] >>> ~surface surface 3 @ 0x4e7a48
May 18 08:34:09 s5p4418-navi-ref afbd-windowmanager-service-2017@0.1[3025]: [3503682.227] [wm DEBUG] [wayland.cpp, remove_proxy_to_id_mapping(), Line:685] >>> Remove surface proxy mapping for 0x4e7a48
May 18 08:34:09 s5p4418-navi-ref afbd-windowmanager-service-2017@0.1[3025]: [3503682.331] [wm DEBUG] [main.cpp, cbRemoveClientCtxt(), Line:178] >>> delete surfaceID 3

I think this problem is related with dnf service.

How can I stop dnf timer or is there another solution?

Thanks & Regards,
Josh.

--

Jung Young Moon DrimAES Inc.

Address #803, Ace Twin Tower 2-cha, 273, Digital-ro, Guro-gu, Seoul, Korea
Mobile +82 (0)10 - 4907 - 2117

Mail jung@xxxxxxxxxxx