We are starting weston (1.9.0) for loading our application on IMx6Q sabreauto board. sometimes it fails to start and sometime it works after reboot or after restart Weston services. I found that there is some synchronisation issue occurred in loading western service at the boot time. A log file (/var/log/weston.log)is mentioned in the weston-start script file . Form the log file I get the details about error like below Date: 2018-02-09 UTC [09:47:32.751] weston 1.9.0 http://wayland.freedesktop.org Bug reports to: https://bugs.freedesktop.org/enter_bug.cgi?product=Wayland&component=weston&version=1.9.0 Build: 1.8.93-2-gb05cdb8 configure.ac: bump to version 1.9.0 for the official release (2015-09-21 18:11:26 -0700) [09:47:32.752] OS: Linux, 4.1.15-rt18-2.0.0-avb-1_1_cand20170403+gb63f3f5, #9 SMP PREEMPT RT Wed Mar 14 12:37:25 IST 2018, armv7l [09:47:32.754] Using config file '/home/root/.config/weston.ini' [09:47:32.757] Loading module '/usr/lib/weston/fbdev-backend.so' [09:47:32.981] Output repaint window is 7 ms maximum. [09:47:32.981] initializing fbdev backend [09:47:33.018] Loading module '/usr/lib/weston/gl-renderer.so' [09:47:33.026] warning: either no EGL_EXT_platform_base support or specific platform support; falling back to eglGetDisplay. [09:47:33.027] failed to create display [09:47:33.027] gl_renderer_create failed. [09:47:33.027] fatal: failed to create compositor backend Could you please help me to resolve this issue.
Sorry, I don't think upstream can support you for a couple of reasons: - you are using fbdev-backend with gl-renderer, which is an explicitly unsupported configuration and no longer exists - it seems you are using proprietary graphics drivers from which the failure originates The log seems to imply that eglGetDisplay fails. You say this happens randomly, sometimes it works and sometimes it fails. This implies that your start-up sequence is racy, but we have no idea what Weston start-up could be racing against in your system. I cannot think of any such dependency. Since the failure seems to come from eglGetDisplay, which is implemented by your proprietary graphics drivers, you will have to consult your graphics driver vendor about what you might be racing against at boot. Therefore I'm afraid I have to close this report as NOTOURBUG.
Created attachment 139272 [details] attachment-11788-0.html sachu.sanal@nestgroup.net Sent from my HTC On 27 Apr 2018 13:23, bugzilla-daemon@freedesktop.org wrote: > > Pekka Paalanen changed bug 106264 > What > Removed > Added > Resolution > --- > NOTOURBUG > Status > NEW > RESOLVED > > Comment # 1 on bug 106264 from Pekka Paalanen > > Sorry, I don't think upstream can support you for a couple of reasons: > > - you are using fbdev-backend with gl-renderer, which is an explicitly > > unsupported configuration and no longer exists > > - it seems you are using proprietary graphics drivers from which the failure > > originates > > > > The log seems to imply that eglGetDisplay fails. You say this happens randomly, > > sometimes it works and sometimes it fails. This implies that your start-up > > sequence is racy, but we have no idea what Weston start-up could be racing > > against in your system. I cannot think of any such dependency. > > > > Since the failure seems to come from eglGetDisplay, which is implemented by > > your proprietary graphics drivers, you will have to consult your graphics > > driver vendor about what you might be racing against at boot. > > > > Therefore I'm afraid I have to close this report as NOTOURBUG. > > ________________________________ > You are receiving this mail because: > You reported the bug.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.