Unable to run X-clients over Weston through XWayland

[Devashish Tiwari]

Hello,

Thanks for your response.

I am sorry if the link I attached was not visible to you. It's this one: Xwayland Compilation

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?

Also, how should I specify the DRM-backend explicitly? Right now, my 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=/mnt/Xwayland

I have commented the xwayland entries because weston throws error on including them.

On Tue, 26 Nov 2019 11:16:19 +0200, Pekka Paalanen wrote

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

 > Hi All, 
 > 
 > I have written a third party application that utilities SDL-X11 to 
 > draw a window. 
 > 
 > I have successfully cross-compiled Xwayland (that is used for X 
 > clients under Wayland) for my EVM. I have used instructions from this 
 > official website and did the cross-compilation. However, when I run 
 > the command: 
 > 
 > root at am57xx-evm:/# /mnt/Xwayland

 Hi,

 you are not supposed to run that by hand. Let Weston launch Xwayland 
 automatically instead. Weston will do that in any case with the 
 configuration below, which means you might have had two Xwayland's 
 running.

 > a black screen appears on top of weston display on my EVM. I don't 
 > see any logs on command line. Also, I am not able to run my X11 based 
 > application or even simple X11 demo apps (like xeyes, xclock) 
 > cross-compiled for my EVM. 
 > 
 > As suggested in the above attached link, I even did changes

 What link?

 > to /etc/weston.ini file as - 
 > 
 >  [core] 
 > xwayland=true 
 > 
 > [xwayland] 
 > path=/mnt/Xwayland 
 >

 That looks ok.

 > and I restarted weston to get following error: 
 > 
 > [02:19:21.709] weston 2.0.0 
 > http://wayland.freedesktop.org 
 > Bug reports to: bugs.freedesktop.org/enter_bug.cgi 
 > 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) 
 > [02:19:21.709] Command line: weston 
 > [02:19:21.709] OS: Linux, 4.14.79-ge669d52447, #1 SMP PREEMPT Sat Apr 6 02:23:36 UTC 2019, armv7l 
 > [02:19:21.709] Using config file '/etc//weston.ini' 
 > [02:19:21.710] Output repaint window is 7 ms maximum. 
 > [02:19:21.720] Loading module '/usr/lib/libweston-2/wayland-backend.so' 
 > [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 
 > 
 > I have no idea, which part I did wrong. But I'd really appreciate if 
 > you guys can help me out.

 You have two problems in that.

 1. Your cross-build or runtime is somehow broken. The undefined symbol 
 does not exist and is not referenced anymore in Weston 2.0.0. You 
 probably have stale binaries around.

 2. Wayland-backend is the wrong backend. The Wayland-backend is used 
 when you run Weston on top of another Wayland compositor in a window. 
 Just like the X11-backend is used for running Weston in a window on 
 Xorg. Use the DRM-backend instead to run "directly on hardware".

 Neither of the two problems above are related to Xwayland at all.

 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/20191126/699f0658/attachment-0001.html>