<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="FI" link="#0563C1" vlink="#954F72" style="word-wrap:break-word"> <div class="WordSection1"> Hi,<o:p></o:p> <o:p> </o:p> Thanks for the reply!<o:p></o:p> <o:p> </o:p> Jep, this might be the reason... > --modules=systemd-notify.so --modules=screen.share.so<o:p></o:p> This might be a long shot but it is screen-share.so (hyphen).<o:p></o:p> <o:p> </o:p> <o:p> </o:p> We did try the RDP-weston -session this way too…<o:p></o:p> <o:p> </o:p> 1.<o:p></o:p> Running RDP-weston -session manually via terminal and after that forcing weston-smoke to the RDP-weston -session.<o:p></o:p> <o:p> </o:p> First weston rdp-backend command via terminal. Notice, that here the “--modules=screen-share.so” is written correctly: (And after that WAYLAND_DISPLAY=wayland-0 is running…)<o:p></o:p> <o:p> </o:p> weston --backend=rdp-backend.so --modules=screen-share.so --rdp-tls-cert=/data/etc/ssh/tls.crt --rdp-tls-key=/data/etc/ssh/tls.key<o:p></o:p> <o:p> </o:p> 2.<o:p></o:p> Opening RDP session from the remote computer…still “empty” screen as it should be.<o:p></o:p> <o:p> </o:p> <img width="575" height="446" style="width:5.9916in;height:4.65in" id="Picture_x0020_6" src="cid:image001.png@01D92798.8B720D00"><o:p></o:p> <o:p> </o:p> <o:p> </o:p> 3.<o:p></o:p> Forcing weston-smoke to the RDP-weston -session with below command. root@sm2s-imx8mp:/opt/cpx# WAYLAND_DISPLAY=wayland-0 weston-smoke<o:p></o:p> <o:p> </o:p> Aaand it works like a charm!<o:p></o:p> weston-smoke appears to the RDP-weston -session and ”smoke animation is alive” when mouse is hovered from the remote computer via RDP:<o:p></o:p> <o:p> </o:p> <img width="1598" height="639" style="width:16.65in;height:6.6583in" id="Picture_x0020_7" src="cid:image002.png@01D92798.8B720D00"><o:p></o:p> <o:p> </o:p> <o:p> </o:p> 4.<o:p></o:p> However…<o:p></o:p> <o:p> </o:p> When driving the Qt GUI in RDP-weston -session, it gives a bit different failure code:<o:p></o:p> <o:p> </o:p> /opt/cpx/cpx.sh: line 84: 943 Segmentation fault ./cpx --rotate=0 "$@"<o:p></o:p> <o:p> </o:p> <o:p> </o:p> Done same way than weston-smoke…forced Qt GUI to be started in the RDP-weston -session using below command:<o:p></o:p> root@sm2s-imx8mp:~# WAYLAND_DISPLAY=wayland-0 /opt/cpx/cpx.sh<o:p></o:p> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<o:p></o:p> <o:p> </o:p> root@sm2s-imx8mp:~# WAYLAND_DISPLAY=wayland-0 /opt/cpx/cpx.sh<o:p></o:p> qt.core.logging: Loading "logging.ini" ...<o:p></o:p> qt.core.plugin.factoryloader: checking directory path "/usr/lib/plugins/platforms" ...<o:p></o:p> qt.core.plugin.factoryloader: looking at "/usr/lib/plugins/platforms/libqwayland-generic.so"<o:p></o:p> qt.core.plugin.loader: Found metadata in lib /usr/lib/plugins/platforms/libqwayland-generic.so, metadata=<o:p></o:p> <o:p> </o:p> .<o:p></o:p> .<o:p></o:p> .<o:p></o:p> The looong version from QT DEBUG log is in the attachment (wayland-qt-cpx---Segmentation fault---log file.txt)<o:p></o:p> .<o:p></o:p> .<o:p></o:p> .<o:p></o:p> <o:p> </o:p> qt.core.plugin.factoryloader: Got keys from plugin meta data QList("bradient")<o:p></o:p> qt.core.plugin.factoryloader: checking directory path "/opt/cpx/wayland-decoration-client" ...<o:p></o:p> qt.core.library: "/usr/lib/plugins/wayland-decoration-client/libbradient.so" loaded library<o:p></o:p> qml: Using display<o:p></o:p> qml: Name: rdp<o:p></o:p> qml: Model: rdp<o:p></o:p> qml: Resolution: 1024x768<o:p></o:p> qml: Pixel density: 3.94 px/mm<o:p></o:p> qml: Device pixel ratio: 1<o:p></o:p> qml: Rotation: 0<o:p></o:p> qml: Live update: false<o:p></o:p> Loaded frontend from: "qrc:/frontend/small/main.qml"<o:p></o:p> planmeca.dbus: CanUpdaterDBusInterface : Waiting for service "com.planmeca.updater"<o:p></o:p> planmeca.dbus: CanUpdaterDBusInterface : Waiting for service "com.planmeca.updater"<o:p></o:p> planmeca.dbus: CanUpdaterDBusInterface : Waiting for service "com.planmeca.updater"<o:p></o:p> planmeca.dbus: CanUpdaterDBusInterface : Waiting for service "com.planmeca.updater"<o:p></o:p> planmeca.dbus: CanUpdaterDBusInterface : Waiting for service "com.planmeca.updater"<o:p></o:p> planmeca.dbus: CanUpdaterDBusInterface : Waiting for service "com.planmeca.updater"<o:p></o:p> planmeca.dbus: CanUpdaterDBusInterface : Waiting for service "com.planmeca.updater"<o:p></o:p> planmeca.dbus: CanUpdaterDBusInterface : Waiting for service "com.planmeca.updater"<o:p></o:p> planmeca.dbus: CanUpdaterDBusInterface : Waiting for service "com.planmeca.updater"<o:p></o:p> planmeca.dbus: CanUpdaterDBusInterface : Waiting for service "com.planmeca.updater"<o:p></o:p> planmeca.dbus: CanUpdaterDBusInterface : Waiting for service "com.planmeca.updater"<o:p></o:p> planmeca.dbus: CanUpdaterDBusInterface : Waiting for service "com.planmeca.updater"<o:p></o:p> /opt/cpx/cpx.sh: line 84: 943 Segmentation fault ./cpx --rotate=0 "$@"<o:p></o:p> root@sm2s-imx8mp:~# ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<o:p></o:p> <o:p> </o:p> <o:p> </o:p> BR,<o:p></o:p> <o:p> </o:p> -Matti<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> -----Original Message----- From: Marius Vlad <marius.vlad@collabora.com> Sent: perjantai 13. tammikuuta 2023 16.05 To: Matti Ristim�ki <Matti.Ristimaki@planmeca.com> Cc: wayland-devel@lists.freedesktop.org Subject: Re: Wayland/weston, Qt and RDP connection... <o:p> </o:p> On Fri, Jan 13, 2023 at 12:13:41PM +0000, Matti Ristim�ki wrote:<o:p></o:p> > Hi,<o:p></o:p> Hi,<o:p></o:p> > <o:p></o:p> > Any tips, where/how to debug RDP related problem with Wayland/Weston. Not kind of sure if this is Weston problem or Qt problem...<o:p></o:p> > <o:p></o:p> > Goal:<o:p></o:p> > Trying to create a RDP connection to a Qt GUI-application.<o:p></o:p> What do you mean exactly? Don't you mean the other way around?<o:p></o:p> <o:p> </o:p> Weston starts with the RDP backend and you connect to it with a client that knows about the RDP protocol. Who is the client and who's the server in your case? It is no clear what you are trying to achieve.<o:p></o:p> > <o:p></o:p> > <o:p></o:p> > [Service]<o:p></o:p> > # Requires systemd-notify.so Weston plugin.<o:p></o:p> > Type=notify<o:p></o:p> > EnvironmentFile=/etc/default/weston<o:p></o:p> > ExecStart=/usr/bin/weston --log=${XDG_RUNTIME_DIR}/weston.log <o:p></o:p> > --modules=systemd-notify.so --modules=screen.share.so<o:p></o:p> This might be a long shot but it is screen-share.so (hyphen).<o:p></o:p> > <o:p></o:p> > <o:p></o:p> > Problem:<o:p></o:p> > Seems, that the Qt application doesn't start after adding the "--modules=screen.share.so" to services. And it doesn't start:<o:p></o:p> Yeah, same issue here.<o:p></o:p> > <o:p></o:p> > root@sm2s-imx8mp:~# journalctl -u cpx.service<o:p></o:p> > -- Journal begins at Fri 2023-01-13 08:19:03 CET, ends at Fri <o:p></o:p> > 2023-01-13 10:26:26 CET. -- Jan 13 08:20:06 sm2s-imx8mp systemd[1]: Started CPX Control Panel.<o:p></o:p> > Jan 13 08:20:06 sm2s-imx8mp cpx.sh[769]: qt.core.logging: Loading "logging.ini" ...<o:p></o:p> > Jan 13 08:20:06 sm2s-imx8mp cpx.sh[769]: Failed to create wl_display <o:p></o:p> > (No such file or directory) Jan 13 08:20:06 sm2s-imx8mp cpx.sh[769]: <o:p></o:p> > EGL: Warning: No default display support on wayland Jan 13 08:20:06 <o:p></o:p> > sm2s-imx8mp cpx.sh[769]: qt.qpa.wayland: EGL not available Jan 13 08:20:06 sm2s-imx8mp cpx.sh[769]: qt.qpa.plugin: Could not load the Qt platform plugin "wayland-egl" in "" even though it was found.<o:p></o:p> > Jan 13 08:20:06 sm2s-imx8mp cpx.sh[769]: This application failed to <o:p></o:p> > start because no Qt platform plugin could be initialized. Reinstalling the app> Jan 13 08:20:06 sm2s-imx8mp cpx.sh[769]: Available platform plugins are: wayland, offscreen, vnc, minimal, minimalegl, vkkhrdisplay, eglfs, waylan><o:p></o:p> > Jan 13 08:20:06 sm2s-imx8mp cpx.sh[764]: /opt/cpx/cpx.sh: line 84: 769 Aborted ./cpx --display=LVDS-1 --rotate=0 "$@"<o:p></o:p> > Jan 13 08:20:06 sm2s-imx8mp systemd[1]: cpx.service: Main process <o:p></o:p> > exited, code=exited, status=134/n/a Jan 13 08:20:06 sm2s-imx8mp systemd[1]: cpx.service: Failed with result 'exit-code'.<o:p></o:p> This kind of sounds like there's no Wayland compositor to connect to.<o:p></o:p> Maybe weston is failing to start because it can't find that module. <o:p></o:p> <o:p> </o:p> Printing that weston is saying maybe useful. Maybe journalctl -t weston says something?<o:p></o:p> > <o:p></o:p> > <o:p></o:p> > Basic overview:<o:p></o:p> > <o:p></o:p> > Running "first" weston with...<o:p></o:p> > drm-backend<o:p></o:p> > screen-share<o:p></o:p> > Qt-application (CPX Control Panel is the Qt application)<o:p></o:p> So basically your Qt application is a simple Qt application after all.<o:p></o:p> > <o:p></o:p> > ...and when the screen.share.so starts the "second" Weston, a RDP <o:p></o:p> > command is executed from weston.ini* rdp-backend fullscreen-shell<o:p></o:p> > <o:p></o:p> > <o:p></o:p> > *=weston.ini will run the rdp-backend.so<o:p></o:p> > <o:p></o:p> > [screen-share]<o:p></o:p> > command=@bindir@/weston --backend=rdp-backend.so <o:p></o:p> > --rdp-tls-cert=/data/etc/ssh/tls.crt <o:p></o:p> > --rdp-tls-key=/data/etc/ssh/tls.key --shell=fullscreen-shell.so <o:p></o:p> > --no-clients-resize --no-config start-on-startup=true<o:p></o:p> > <o:p></o:p> Right, if you use the screen-share module that would basically run that command and in turn what would start another weston instance which you can connect to it with a RDP client. It scrapes off the content and it sends it over RDP.<o:p></o:p> > <o:p></o:p> > <o:p></o:p> > More about platform(iMX8, Poky (Yocto Project Reference Distro)) and Qt debug print can be found at:<o:p></o:p> > <o:p></o:p> > <a href="https://forum.qt.io/topic/142178/qt-qpa-plugin-could-not-load-the-qt-p"> https://forum.qt.io/topic/142178/qt-qpa-plugin-could-not-load-the-qt-p</a><o:p></o:p> > latform-plugin-wayland-egl-in-even-though-it-was-found<o:p></o:p> > <o:p></o:p> > <o:p></o:p> > <o:p></o:p> > BR,<o:p></o:p> > <o:p></o:p> > <o:p></o:p> > -Matti<o:p></o:p> > <o:p></o:p> > <o:p></o:p> > Matti Ristim�ki<o:p></o:p> > Test Engineer<o:p></o:p> > Dental Care Units & CAD/CAM Division<o:p></o:p> > <o:p></o:p> > This e-mail may contain confidential or privileged information and is intended solely for the person to whom it is addressed. If you have received this e-mail in error, please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. We will not be liable for direct, indirect, special or consequential damages arising from the alteration of this e-mail, or as a result of any virus being passed on or as of transmission of this e-mail in general.<o:p></o:p> </div> This e-mail may contain confidential or privileged information and is intended solely for the person to whom it is addressed. If you have received this e-mail in error, please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. We will not be liable for direct, indirect, special or consequential damages arising from the alteration of this e-mail, or as a result of any virus being passed on or as of transmission of this e-mail in general. </body> </html>