Feedback for Window Manager 2017 (RC1)

WindowManager segfault when no screens are connected to the board. It should not but rather output a message and exit gracefully.

This could also leads to some complication when we wanted to restart the service because socket isn't release correctly then service can't create it because of some inconsistency.

Nov 15 10:15:33 m3ulcb afbd-windowmanager-service-2017@0.1[16072]:  INFO: binding monitor added to set main [/usr/src/debug/af-binder/master+gitAUTOINC+f85485a195-r0/git
Nov 15 10:15:33 m3ulcb afbd-windowmanager-service-2017@0.1[16072]:  INFO: binding [/var/local/lib/afm/applications/windowmanager-service-2017/0.1/lib/windowmanager-servi
Nov 15 10:15:33 m3ulcb afbd-windowmanager-service-2017@0.1[16072]:  INFO: API windowmanager added [/usr/src/debug/af-binder/master+gitAUTOINC+f85485a195-r0/git/src/afb-a
Nov 15 10:15:33 m3ulcb afbd-windowmanager-service-2017@0.1[16072]:  INFO: binding windowmanager added to set main [/usr/src/debug/af-binder/master+gitAUTOINC+f85485a195-
Nov 15 10:15:33 m3ulcb afbd-windowmanager-service-2017@0.1[16072]:  INFO: Scanning dir=/usr/lib/afb for bindings [/usr/src/debug/af-binder/master+gitAUTOINC+f85485a195
Nov 15 10:15:33 m3ulcb afbd-windowmanager-service-2017@0.1[16072]:  INFO: Scanning dir=/usr/lib/afb/monitoring for bindings [/usr/src/debug/af-binder/master+gitAUTOINC
Nov 15 10:15:33 m3ulcb afbd-windowmanager-service-2017@0.1[16072]:  DEBUG: Init config done [/usr/src/debug/af-binder/master+gitAUTOINC+f85485a195-r0/git/src/main.c:603,
Nov 15 10:15:33 m3ulcb afbd-windowmanager-service-2017@0.1[16072]:  INFO: API monitor starting... [/usr/src/debug/af-binder/master+gitAUTOINC+f85485a195-r0/git/src/afb-a
Nov 15 10:15:33 m3ulcb afbd-windowmanager-service-2017@0.1[16072]:  NOTICE: API monitor started [/usr/src/debug/af-binder/master+gitAUTOINC+f85485a195-r0/git/src/afb-api
Nov 15 10:15:33 m3ulcb afbd-windowmanager-service-2017@0.1[16072]:  INFO: API windowmanager starting... [/usr/src/debug/af-binder/master+gitAUTOINC+f85485a195-r0/git/src
Nov 15 10:15:33 m3ulcb afbd-windowmanager-service-2017@0.1[16072]:  ERROR: ALERT! signal 11 received: Segmentation fault [/usr/src/debug/af-binder/master+gitAUTOINC+f854
Nov 15 10:15:33 m3ulcb afbd-windowmanager-service-2017@0.1[16072]:  ERROR: BACKTRACE due to signal Segmentation fault/11:
Nov 15 10:15:33 m3ulcb afbd-windowmanager-service-2017@0.1[16072]:  [1/1] afbd-windowmanager-service-2017@0.1(+0x2fbe0) [0xaaaad9aa8be0]
Nov 15 10:15:33 m3ulcb afbd-windowmanager-service-2017@0.1[16072]:  /usr/src/debug/af-binder/master+gitAUTOINC+f85485a195-r0/git/src/sig-monitor.c:72,dumpstack
Nov 15 10:15:33 m3ulcb afbd-windowmanager-service-2017@0.1[16072]:  ERROR: start aborted: received signal Segmentation fault [/usr/src/debug/af-binder/master+gitAUTOINC+
Nov 15 10:15:33 m3ulcb systemd[4078]: afm-service-windowmanager-service-2017@0.1.service: Main process exited, code=exited, status=1/FAILURE
Nov 15 10:15:33 m3ulcb systemd[4078]: afm-service-windowmanager-service-2017@0.1.service: Unit entered failed state.
Nov 15 10:15:33 m3ulcb systemd[4078]: afm-service-windowmanager-service-2017@0.1.service: Failed with result 'exit-code'.

Playing with latest version of HMI framework, I noticed the following trace in log:

Oct 17 09:18:02 m3ulcb afbd-windowmanager-service-2017@0.1[4150]:  ERROR: [API windowmanager] Someone created a layer without asking US! (9999)
Oct 17 09:18:02 m3ulcb afbd-windowmanager-service-2017@0.1[4150]:  ERROR: [API windowmanager] Someone created a layer without asking US! (1001)
Oct 17 09:18:02 m3ulcb afbd-windowmanager-service-2017@0.1[4150]:  ERROR: [API windowmanager] Someone created a layer without asking US! (1000)

WM had outputted these error logs for the layers which WM had created.

So these logs should not be error log, but debug log for the future analysis.

I have fixed this bug at https://gerrit.automotivelinux.org/gerrit/#/c/11769/.

Thanks.

The json configuration file will be included in wgt by https://gerrit.automotivelinux.org/gerrit/#/c/11523/.

So when the change is merged, this error will not be outputted.

atest build success but I got the following errors:

2017@0.1[4937]:  ERROR: Initialisation of service API windowmanager failed (-1): No such file or directory [/usr/src/debug/af-binder/master+gitAUTOINC+32bc7ed391-r0/git/src/afb-export.c:1373,afb_expor
2017@0.1[4937]:  ERROR: The api windowmanager failed to start (-1) /usr/src/debug/af-binder/master+gitAUTOINC+32bc7ed391-r0/git/src/afb-apiset.c:345,start_api
2017@0.1[5001]:  NOTICE: API dbus started /usr/src/debug/af-binder/master+gitAUTOINC+32bc7ed391-r0/git/src/afb-apiset.c:354,start_api
2017@0.1[5001]:  NOTICE: API monitor started /usr/src/debug/af-binder/master+gitAUTOINC+32bc7ed391-r0/git/src/afb-apiset.c:354,start_api
2017@0.1[5001]:  ERROR: Initialisation of service API windowmanager failed (-1): No such file or directory [/usr/src/debug/af-binder/master+gitAUTOINC+32bc7ed391-r0/git/src/afb-export.c:1373,afb_expor
2017@0.1[5001]:  ERROR: The api windowmanager failed to start (-1) /usr/src/debug/af-binder/master+gitAUTOINC+32bc7ed391-r0/git/src/afb-apiset.c:345,start_api
2017@0.1[5007]:  NOTICE: API auth started /usr/src/debug/af-binder/master+gitAUTOINC+32bc7ed391-r0/git/src/afb-apiset.c:354,start_api
2017@0.1[5007]:  NOTICE: API dbus started /usr/src/debug/af-binder/master+gitAUTOINC+32bc7ed391-r0/git/src/afb-apiset.c:354,start_api
2017@0.1[5007]:  NOTICE: API monitor started /usr/src/debug/af-binder/master+gitAUTOINC+32bc7ed391-r0/git/src/afb-apiset.c:354,start_api
2017@0.1[5007]:  ERROR: Initialisation of service API windowmanager failed (-1): No such file or directory [/usr/src/debug/af-binder/master+gitAUTOINC+32bc7ed391-r0/git/src/afb-export.c:1373,afb_expor
2017@0.1[5007]:  ERROR: The api windowmanager failed to start (-1) /usr/src/debug/af-binder/master+gitAUTOINC+32bc7ed391-r0/git/src/afb-apiset.c:345,start_api

I guess it misses json configuration file to correctly start.

Thanks.

I found same error in our log.

And it seems like WM's bug. As a design, WM make some layers which are defined in layers.json at initializing phase, but after that the listener which was registered to IVI is called by something trigger, and this error message appears.

We will fix it but so far there is no big side effect so it will be after RC2.