<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> 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> <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 --modules=systemd-notify.so --modules=screen.share.so<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> <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 2023-01-13 10:26:26 CET. --<o:p></o:p> 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 (No such file or directory)<o:p></o:p> Jan 13 08:20:06 sm2s-imx8mp cpx.sh[769]: EGL: Warning: No default display support on wayland<o:p></o:p> Jan 13 08:20:06 sm2s-imx8mp cpx.sh[769]: qt.qpa.wayland: EGL not available<o:p></o:p> 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 start because no Qt platform plugin could be initialized. Reinstalling the app><o:p></o:p> 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 exited, code=exited, status=134/n/a<o:p></o:p> Jan 13 08:20:06 sm2s-imx8mp systemd[1]: cpx.service: Failed with result 'exit-code'.<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> <o:p> </o:p> …and when the screen.share.so starts the “second” Weston, a RDP command is executed from weston.ini*<o:p></o:p> rdp-backend<o:p></o:p> 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 --rdp-tls-cert=/data/etc/ssh/tls.crt --rdp-tls-key=/data/etc/ssh/tls.key --shell=fullscreen-shell.so --no-clients-resize --no-config<o:p></o:p> start-on-startup=true<o:p></o:p> <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> <a href="https://forum.qt.io/topic/142178/qt-qpa-plugin-could-not-load-the-qt-platform-plugin-wayland-egl-in-even-though-it-was-found">https://forum.qt.io/topic/142178/qt-qpa-plugin-could-not-load-the-qt-platform-plugin-wayland-egl-in-even-though-it-was-found</a><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> </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>