Unable to run X-clients over Weston through XWayland

Devashish Tiwari devashish at cdot.in
Wed Nov 27 10:55:46 UTC 2019


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.

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                                                                             
[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)              
[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

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.

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.

Kindly see if you can help.

On Tue, 26 Nov 2019 14:46:35 +0200, Pekka Paalanen wrote

On Tue, 26 Nov 2019 17:10:35 +0530 
 "Devashish Tiwari" <devashish at cdot.in> wrote:

 > Hello, 
 > 
 > Thanks for your response. 
 > 
 > I am sorry if the link I attached was not visible to you. It's this 
 > one: Xwayland Compilation

 Hi,

 sorry, I don't do HTML emails, so there is no link in that.

 > I don't know if my cross-build is wrong, because there were no errors 
 > during compilation. Can you please tell how should I check if it's 
 > compiled correctly or not?

 I have no way of knowing. All I know is that Weston 2.0.0 source code 
 does not have a function named weston_compositor_init(), not defined 
 nor called. But your error message referred to such function, so I can 
 only assume that you are not running what you intended to.

 > 
 > Also, how should I specify the DRM-backend explicitly? Right now, my 
 > weston.ini file looks like this:

 See 'man weston' and 'man weston.ini' for how to specify the backend.

 The DRM-backend should be the default though, unless you configured the 
 build to use something else, or you have WAYLAND_DISPLAY or DISPLAY 
 environment variables defined.

 Defining WAYLAND_DISPLAY environment variable manually would be a 
 mistake that could cause Weston to choose the Wayland-backend.

 > 
 > [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=/mnt/Xwayland 
 > 
 > I have commented the xwayland entries because weston throws error on including them.

 What errors?

 If you refer to

 >  > [02:19:21.735] Failed to load module: /usr/lib/libweston-2/wayland-backend.so: undefined symbol: weston_compositor_init 
 >  > [02:19:21.735] fatal: failed to create compositor backend

 then those are not caused by the xwayland entries.

 Thanks, 
 pq

--

Thanks & Regards,

Devashish Tiwari 
Fault Tolerance 
#8587

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/wayland-devel/attachments/20191127/6adda851/attachment-0001.html>


More information about the wayland-devel mailing list