[agl-discussions] WindowManager fails

tanikawa.tadao at jp.panasonic.com tanikawa.tadao at jp.panasonic.com
Fri Jan 20 06:54:47 UTC 2017


Hi Matsuzawa-san,

Weston(Wayland compositor) should be active before launching HomeScreen and WindowManager.
So you may have to debug why weston didn't run normally.

FYI. There are variables for debug of weston,
  export MESA_DEBUG=1
  export EGL_LOG_LEVEL=debug
  export LIBGL_DEBUG=verbose
  export WAYLAND_DEBUG=1

You can set these in weston.service as Environment=, and you can check logs via journalctl command.

Regards,
Tadao Tanikawa

-----Original Message-----
From: automotive-discussions-bounces at lists.linuxfoundation.org [mailto:automotive-discussions-bounces at lists.linuxfoundation.org] On Behalf Of Takashi Matsuzawa
Sent: Friday, January 20, 2017 3:42 PM
To: Bocklage, Jens; automotive-discussions at lists.linuxfoundation.org
Subject: Re: [agl-discussions] WindowManager fails

Hello, I looked into the following message in my log.

>Jan 19 07:04:03 imx6qsabreauto WindowManager[767]: Failed to connect 
>display in libilmCommon

It means, folliwng is failing, and indicates wayland is not running?

ilm_init()
  -> wayland_init()
    ->wl_display_connect()

In fact just after these error message, weston-launch log outputs are seen, and it is using /etc/xdg/weston.ini, etc.

But it is saying fbdev-backend.so is being used as backend.
(Should it be wayland-backend.so?)
So, it seems the light-blue weston desktop is the output via framebuffer, not wayland.

In case I am not properly running wayland, where should I check?
Should there be error logs before these lines?




________________________________

From: automotive-discussions-bounces at lists.linuxfoundation.org <automotive-discussions-bounces at lists.linuxfoundation.org> on behalf of Takashi Matsuzawa <tmatsuzawa at xevo.com>
Sent: Friday, January 20, 2017 12:01 AM
To: Bocklage, Jens; automotive-discussions at lists.linuxfoundation.org
Subject: Re: [agl-discussions] WindowManager fails 
 
	This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing <http://aka.ms/LearnAboutSpoofing> 	 Feedback <http://aka.ms/SafetyTipsFeedback> 	 
Hmm, I have kbd and mouse  (both connected via USB) and LVDS touch screen display all connected to the board.  Anyway, thank you for your insight.  Will try debugging tommorow...


________________________________

From: Bocklage, Jens <Jens_Bocklage at mentor.com>
Sent: Thursday, January 19, 2017 11:05:22 PM
To: Takashi Matsuzawa; automotive-discussions at lists.linuxfoundation.org
Subject: RE: WindowManager fails 
 

The WindowManager tries to initiate a connection to the IVI-shell. If this fails, the app fails and gets restarted by system. That’s the error you describe in “i)”.

Do you have any input devices connected? I remember there was an issue that you HAVE TO had an input device (mouse, touch screen, keyboard) attached to have Weston launch correctly…

 

From: automotive-discussions-bounces at lists.linuxfoundation.org [mailto:automotive-discussions-bounces at lists.linuxfoundation.org] On Behalf Of Takashi Matsuzawa
Sent: Donnerstag, 19. Januar 2017 13:53
To: automotive-discussions at lists.linuxfoundation.org
Subject: [agl-discussions] WindowManager fails

 

Hello AGL.

 

I reconfigured my kernel to enable SMACK security, and now systemctl --failed does not show user manager failure.

However, I am still failing to see AGL homescreen, the board just shows the default ivi-shell desktop (the light-blue one.).

 

This is AGL 3.0 agl layers.

(I am trying to combine it with my pre-3.0 configuration.)

Looking into journalctl log, at least, I can see WindowManager is failing, so this may be causing AGL homescreen not shown.

 

Any clue you immediately notice?

I also attached the whole log file, but these two are are obvious Fails I noticed.

 

i) error reported by WindowManger

(It says it cannot connect display)

 

ii) ambd says it cannot open /dev/ttyUSB0

(the demo configuration expect some device connected to USB?  This error can be ignored?)

 

Log excerpt for i):

 

>Jan 19 07:04:03 imx6qsabreauto InputEventManager[764]: D-Bus: register 
>as org.agl.inputeventmanager

>Jan 19 07:04:03 imx6qsabreauto WindowManager[767]: Using display 0 Jan 
>19 07:04:03 imx6qsabreauto WindowManager[767]: -=[WindowManager]=- Jan 
>19 07:04:03 imx6qsabreauto WindowManager[767]: -=[start]=- Jan 19 
>07:04:03 imx6qsabreauto WindowManager[767]: Failed to connect display 
>in libilmCommon Jan 19 07:04:03 imx6qsabreauto WindowManager[767]: 
>ilm_init = 1 Jan 19 07:04:03 imx6qsabreauto WindowManager[767]: failed! Exiting!
>Jan 19 07:04:03 imx6qsabreauto HomeScreenAppFrameworkBinderAGL[768]: 
>D-Bus: register as org.agl.homescreenappframeworkbinder
>Jan 19 07:04:04 imx6qsabreauto systemd[734]: WindowManager.service: 
>Main process exited, code=exited, status=255/n/a Jan 19 07:04:04 imx6qsabreauto systemd[734]: Failed to start AGL Window Manager.
>Jan 19 07:04:04 imx6qsabreauto systemd[734]: WindowManager.service: Unit entered failed state.
>Jan 19 07:04:04 imx6qsabreauto systemd[734]: WindowManager.service: Failed with result 'exit-code'.

 

Log Excerpt for ii):

 

>Jan 19 07:04:02 imx6qsabreauto ambd[704]: ERROR: ioctl failed

>Jan 19 07:04:02 imx6qsabreauto ambd[704]: 27.814           | ERROR Failed to open gps tty: /dev/ttyUSB0

 



More information about the automotive-discussions mailing list