Unable to run X-clients over Weston through XWayland

Pekka Paalanen ppaalanen at gmail.com
Wed Nov 27 13:48:48 UTC 2019


On Wed, 27 Nov 2019 16:25:46 +0530
"Devashish Tiwari" <devashish at cdot.in> wrote:

> Hello,
> 
> Thanks for your response.
> 
> I rebooted my EVM after making changes to /etc/weston.ini file and I
> found out in /var/log/weston.log that it is using DRM-backend now.

> When I used to run ./Xwayland by hand it used to take Wayland-backend.

Hi,

no, I don't think Xwayland had anything to do with it. More likely you
had WAYLAND_DISPLAY set in your environment, too, maybe from some
random experimenting. That causes Weston to pick the wayland-backend.

> However, it still shows some error regarding EGL library, although I have already specified LD_LIBRARY_PATH.
> 
> Date: 2019-04-06 UTC                                                                                                 
> [01:57:12.089] weston 2.0.0                                                                                          
>                http://wayland.freedesktop.org                                                                        
>                Bug reports to: https://bugs.freedesktop.org/enter_bug.cgi?product=Wayland&component=weston&version=2.0.0
>                Build: 1.99.94-2-g4c4f13d configure.ac: bump to version 2.0.0 for the official release (2017-02-24 16:19:03 -0800)
> [01:57:12.089] Command line: weston --idle-time=0                                                                                
> [01:57:12.089] OS: Linux, 4.14.79-ge669d52447, #1 SMP PREEMPT Sat Apr 6 02:23:36 UTC 2019, armv7l                                
> [01:57:12.090] Using config file '/etc//weston.ini'                                                                              
> [01:57:12.090] Output repaint window is 7 ms maximum.                                                                            
> [01:57:12.090] Loading module '/usr/lib/libweston-2/drm-backend.so'                                                              
> [01:57:12.091] initializing drm backend                                                          
> [01:57:12.092] using /dev/dri/card0                                                              
> [01:57:12.093] Loading module '/usr/lib/libweston-2/gl-renderer.so'
> failed to load module: /usr/lib/gbm/gbm_dri.so: cannot open shared object file: No such file or directory
> failed to load module: /usr/lib/gbm/gbm_gallium_drm.so: cannot open shared object file: No such file or directory
> loaded module : gbm_pvr.so                                                                                       
> found valid GBM backend : gbm_pvr.so                                                                             

Is gbm_pvr a prorietary driver library? We cannot generally help with
anything related to proprietary drivers, you'll have to reach out to
the vendor instead.

> [01:57:12.114] EGL client extensions: EGL_EXT_client_extensions                                                  
>                EGL_EXT_platform_base EGL_KHR_client_get_all_proc_addresses                                       
>                EGL_KHR_debug EGL_EXT_platform_wayland EGL_EXT_platform_x11                                       
>                EGL_MESA_platform_gbm                                      
> [01:57:12.114] failed to initialize display                               
> [01:57:12.114] EGL error state: EGL_NOT_INITIALIZED (0x3001)              

A problem with EGL, that is the graphics driver stack.

> [01:57:12.114] failed to initialize egl                                   
> [01:57:12.140] fatal: failed to create compositor backend                
> 
> My /etc/weston.ini file looks like this:
> 
> [core]
> require-input=false
> xwayland=true
> 
> [shell]
> locking=false
> animation=zoom
> panel-position=top
> startup-animation=fade
> 
> [screensaver]
> # Uncomment path to disable screensaver
> #path=@libexecdir@/weston-screensaver
> 
> [xwayland]
> path=/usr/local/XORG/bin/Xwayland

The weston.ini looks fine and has nothing that could cause the EGL
failure.

> 
> Please note that I have not set any environment variables manually. I
> have only copied the libraries required by Xwayland on my EVM and
> added the path to LD_LIBRARY_PATH.
> 
> The values of WAYLAND_DISPLAY & DISPLAY is null on my system which
> makes me think that it takes the default values.

If they are set to empty, that is different from being unset.

> Also, if I undo the changes to /etc/weston.ini file and comment the
> xwayland entries, weston works like a cake. I have also attached the
> logs with this email when weston runs successfully without xwayland.

I have a hard time believing that. None of the weston.ini keys you
listed above can affect anything related to the EGL failure.

I also don't see such attachment in this email, just the HTML copy.

LD_LIBRARY_PATH could be a factor here though. Try explicitly with it
set vs. untouched, but otherwise with the setup where Weston worked for
you. That's the only thing I can guess. Maybe it needs to have a
specific value for the proprietary drivers to work.


Thanks,
pq
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.freedesktop.org/archives/wayland-devel/attachments/20191127/941b6bd9/attachment.sig>


More information about the wayland-devel mailing list