Hi, we are facing Windowmanager service failed error on our raspberrypi 3 b+ board.

#weston --version
weston 2.0.0

#systemctl

• afm-service-windowmanager-service-2017-0.1-main@0.service loaded failed failed Window Manager
• weston-ready.service
  loaded failed failed Wait for Weston readiness

#systemctl status afm-service-windowmanager* afm-api-windowmanager*

• afm-service-windowmanager-service-2017-0.1-main@0.service - Window Manager
  Loaded: loaded (/var/local/lib/systemd/system/afm-user-session@.target.wants/../afm-service-windowmanager-service-2017-0.1-main@.service; disabled; vendor preset: enabled)
  Active: failed (Result: exit-code) since Wed 2019-09-25 11:04:47 UTC; 14min ago
  Process: 1321 ExecStart=/usr/bin/afb-daemon --name afbd-windowmanager-service-2017@0.1 --rootdir=/var/local/lib/afm/applications/windowmanager-service-2017/0.1 --workdir=/home/0/app-data/windowmanager-service-2017 --no-httpd --binding=/var/local/lib/afm/applications/windowmanager-service-2017/0.1/lib/windowmanager-service.so --ws-server=sd:windowmanager (code=exited, status=1/FAILURE)
  Process: 1320 ExecStartPre=/bin/mkdir -p /home/0/app-data/windowmanager-service-2017 (code=exited, status=0/SUCCESS)
  Main PID: 1321 (code=exited, status=1/FAILURE)
  CPU: 72ms
  Sep 25 11:04:47 raspberrypi3 systemd[1]: Starting Window Manager...
  Sep 25 11:04:47 raspberrypi3 afbd-windowmanager-service-2017@0.1[1321]: [2667487.613] [wm ERROR] [window_manager.cpp, init_layers(), Line:746] >>> ivi_controller global not available
  Sep 25 11:04:47 raspberrypi3 afbd-windowmanager-service-2017@0.1[1321]: [2667487.706] [wm ERROR] [main.cpp, _binding_init(), Line:141] >>> Could not connect to compositor
  Sep 25 11:04:47 raspberrypi3 afbd-windowmanager-service-2017@0.1[1321]: ERROR: Initialisation of service API windowmanager failed (-1): No such file or directory [/usr/src/debug/af-binder/flounder+gitAUTOINC+622beae804-r0/git/src/afb-export.c:1706,afb_export_start]
  Sep 25 11:04:47 raspberrypi3 afbd-windowmanager-service-2017@0.1[1321]: ERROR: The api windowmanager failed to start [/usr/src/debug/af-binder/flounder+gitAUTOINC+622beae804-r0/git/src/afb-apiset.c:799,start_api]
  Sep 25 11:04:47 raspberrypi3 systemd[1]: afm-service-windowmanager-service-2017-0.1-main@0.service: Main process exited, code=exited, status=1/FAILURE
  Sep 25 11:04:47 raspberrypi3 systemd[1]: Failed to start Window Manager.
  Sep 25 11:04:47 raspberrypi3 systemd[1]: afm-service-windowmanager-service-2017-0.1-main@0.service: Unit entered failed state.
  Sep 25 11:04:47 raspberrypi3 systemd[1]: afm-service-windowmanager-service-2017-0.1-main@0.service: Failed with result 'exit-code'.
• afm-api-windowmanager@0.socket - Provides websocket api windowmanager for user 0
  Loaded: loaded (/usr/local/lib/systemd/system/afm-api-windowmanager@.socket; static; vendor preset: enabled)
  Active: active (listening) since Wed 2019-09-25 11:04:47 UTC; 14min ago
  Listen: /run/user/0/apis/ws/windowmanager (Stream)
  Sep 25 11:04:47 raspberrypi3 systemd[1]: Listening on Provides websocket api windowmanager for user 0.
• afm-api-windowmanager@0.service - Provides api windowmanager for user 0
  Loaded: loaded (/usr/local/lib/systemd/system/afm-api-windowmanager@.service; static; vendor preset: enabled)
  Drop-In: /etc/systemd/system/afm-api-windowmanager@.service.d
  `-weston-ready.conf
  Active: active (exited) since Wed 2019-09-25 11:03:55 UTC; 15min ago
  Process: 463 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
  Main PID: 463 (code=exited, status=0/SUCCESS)
  Sep 25 11:03:55 raspberrypi3 systemd[1]: Starting Provides api windowmanager for user 0...
  Sep 25 11:03:55 raspberrypi3 systemd[1]: Started Provides api windowmanager for user 0.

While running QML based application, we got following errors,
#afm-util run db410c-temp@0.1
eb 01 12:39:27 raspberrypi3 afbd-db410c-temp@0.1[673]: [1862255.669] [libwm ERROR] [libwindowmanager.cpp, getDisplayInfo(), Line:461] >>> api_call() failed
Feb 01 12:39:27 raspberrypi3 afbd-db410c-temp@0.1[673]: [1862267.155] [libwm ERROR] [libwindowmanager.cpp, operator()(), Line:455] >>> Windowmanager-service is not initialized: {
Feb 01 12:39:27 raspberrypi3 afbd-db410c-temp@0.1[673]: "jtype":"afb-reply",
Feb 01 12:39:27 raspberrypi3 afbd-db410c-temp@0.1[673]: "request":{
Feb 01 12:39:27 raspberrypi3 afbd-db410c-temp@0.1[673]: "status":"unknown-api",
Feb 01 12:39:27 raspberrypi3 afbd-db410c-temp@0.1[673]: "info":"api windowmanager not found (for verb GetDisplayInfo)"
Feb 01 12:39:27 raspberrypi3 afbd-db410c-temp@0.1[673]: }
Feb 01 12:39:27 raspberrypi3 afbd-db410c-temp@0.1[673]: }
Feb 01 12:39:27 raspberrypi3 afbd-db410c-temp@0.1[673]: [1862267.241] [libwm ERROR] [libwindowmanager.cpp, api_call(), Line:685] >>> calling windowmanager/GetDisplayInfo failed: No such file or directory
Feb 01 12:39:27 raspberrypi3 afbd-db410c-temp@0.1[673]: [1862267.292] [libwm ERROR] [libwindowmanager.cpp, getDisplayInfo(), Line:461] >>> api_call() failed

While running html5 based launcher application, we got following errors,
#afm-util run webapps-html5-launcher@1.0
Feb 01 12:43:03 raspberrypi3 systemd[1]: weston-ready.service: Main process exited, code=exited, status=1/FAILURE
Feb 01 12:43:03 raspberrypi3 systemd[1]: Failed to start Wait for Weston readiness.
Feb 01 12:43:03 raspberrypi3 systemd[1]: Dependency failed for Provides api windowmanager for user 0.
Feb 01 12:43:03 raspberrypi3 systemd[1]: Dependency failed for Launcher application for AGL based on html5 technologies.
Feb 01 12:43:03 raspberrypi3 systemd[1]: afm-appli-webapps-html5-launcher-1.0main@0.service: Job afm-appli-webapps-html5-launcher1.0-main@0.service/start failed with result 'dependency'.
Feb 01 12:43:03 raspberrypi3 systemd[1]: afm-api-windowmanager@0.service: Job afm-api-windowmanager@0.service/start failed with result 'dependency'.
Feb 01 12:43:03 raspberrypi3 systemd[1]: weston-ready.service: Unit entered failed state.
Feb 01 12:43:03 raspberrypi3 systemd[1]: weston-ready.service: Failed with result 'exit-code'.

Hoping to hear from you sooner and these issues are on high priority in our project.