weston issueshttps://gitlab.freedesktop.org/wayland/weston/-/issues2024-02-07T11:52:21Zhttps://gitlab.freedesktop.org/wayland/weston/-/issues/874[DRM] Alpha Background Support for the Kiosk Shell2024-02-07T11:52:21ZThomas Devoogdt[DRM] Alpha Background Support for the Kiosk ShellThis issue is a follow-up to this discussion: https://gitlab.freedesktop.org/wayland/weston/-/issues/710#note_2264604.
To summarize shortly. I'm trying to render a transparent Weston shell targeting a DRM backend. Then, that frame buffe...This issue is a follow-up to this discussion: https://gitlab.freedesktop.org/wayland/weston/-/issues/710#note_2264604.
To summarize shortly. I'm trying to render a transparent Weston shell targeting a DRM backend. Then, that frame buffer will be blended on top of a video stream using FPGA logic.
So I started with a small hack to get alpha support in the kiosk shell:
```diff
diff --git a/kiosk-shell/kiosk-shell.c b/kiosk-shell/kiosk-shell.c
index 28805322..73902964 100644
--- a/kiosk-shell/kiosk-shell.c
+++ b/kiosk-shell/kiosk-shell.c
@@ -632,7 +632,7 @@ kiosk_shell_output_recreate_background(struct kiosk_shell_output *shoutput)
curtain_params.r = ((bg_color >> 16) & 0xff) / 255.0;
curtain_params.g = ((bg_color >> 8) & 0xff) / 255.0;
curtain_params.b = ((bg_color >> 0) & 0xff) / 255.0;
- curtain_params.a = 1.0;
+ curtain_params.a = ((bg_color >> 24) & 0xff) / 255.0;
curtain_params.pos = output->pos;
curtain_params.width = output->width;
```
At first, I was using the Wayland backend natively to check what was going on, and that is where the first issue was. See the video, the window beneath it is flickering randomly and has a bunch of strange effects. Yes, I know, this is probably not supported, but what exactly could cause this, where do I start to get these flickers fixed?
![VID_20240205_145430_2](/uploads/ab9df941d7372e36cc796fa91ebdb439/VID_20240205_145430_2.mp4)
Then, I proceeded with my embedded device, and thus now I'm using the DRM backend. There, I see another effect, the alpha works at first sight, but everything that gets drawn does stick. So e.g. if I move my mouse, I see the whole track of where my mouse passed. So this is somewhat different from using the Wayland backend but also doesn't work.
What I did check; alpha_{min,max} is set to 0 & 0xffff, and the used pixel format is ARGB8888.
I'm using Weston 13.0.0 and the Pixman render.
Btw, this issue is potentially a duplicate (e.g. #9 and !1258).https://gitlab.freedesktop.org/wayland/weston/-/issues/873Touchscreen not rotating along with display.2024-02-06T10:36:50ZDebojit DasTouchscreen not rotating along with display.We are implementing auto-rotation feature in the yocto linux (i.mx6) having LVDS connector (Display and Touch Integrated H/w) but we are facing issues from touch during screen rotation.
Screen rotation works fine but the touchscreen does...We are implementing auto-rotation feature in the yocto linux (i.mx6) having LVDS connector (Display and Touch Integrated H/w) but we are facing issues from touch during screen rotation.
Screen rotation works fine but the touchscreen doesn't rotate. The configuration in weston.ini (ver 9) and touchscreen.rules doesn't seem to work. We have a calibration helper script as well to make the rules persistent. It writes to touchscreen.rules file, the rules are persistent across reboots. Despite that the touchscreen doesn't rotate. Could you please provide the details, what changes need to do in configurations to make touchscreen works with screen rotation ?https://gitlab.freedesktop.org/wayland/weston/-/issues/871Video playback using GStreamer very slow compared to X.Org on old computer2024-02-01T10:51:58ZThomasVideo playback using GStreamer very slow compared to X.Org on old computerI have been experimenting with an old computer and noticed that when playing a video using `gst-play-1.0` through Weston/Wayland it was much more laggy than an X.Org session using startx and mwn.
I am running Debian 12 on a single core ...I have been experimenting with an old computer and noticed that when playing a video using `gst-play-1.0` through Weston/Wayland it was much more laggy than an X.Org session using startx and mwn.
I am running Debian 12 on a single core Intel Pentium 4 at 2793MHz, kernel 6.1.0-17-686-pae i686, Memory 500MB, Dell DE051 model 0CF458, Graphics Intel 82865G Intergted Grapghic, driver i915.
Here are video of playback on each type of session:
X.Org: ![XOrg](/uploads/3098bc3914782c940cbf663484613f4f/XOrg.mov)
Weston glimagesink: ![Weston](/uploads/cbe59e392215a7c6c487ecf757128a67/Weston.mov)
Weston waylandsink: ![Weston-waylandsink](/uploads/23e8bc4df772297f862b6fa411b7e3fe/Weston-waylandsink.mov)
Here are logs fromm the gst-play command, although recorded from different runs:
X.Org: [XOrg.log](/uploads/4494cbf8a95189fd97d3544a8aebe203/XOrg.log)
Weston glimagesink: [Weston.log](/uploads/d2e63eb060d15ef0c9cde9c1a0356fae/Weston.log)
Weston waylandsink: [weston-waylandsink.log](/uploads/47919d5c95572dd6ef245005fbb4a916/weston-waylandsink.log)
GStreamer is using a xvimagesinl on X.Org.
The video uses in available here: https://download.blender.org/peach/bigbuckbunny_movies/big_buck_bunny_720p_stereo.avi
I would be happy to provide any missing information if requested.
If this is a problem with another non-weston project (GStreamer) then I would be fine with moving this issue to the correct project.https://gitlab.freedesktop.org/wayland/weston/-/issues/867Only llvmpipe is available on Intel Calistoga (Gen3)2024-02-05T15:44:51Zk8ieOnly llvmpipe is available on Intel Calistoga (Gen3)I recently got an old laptop with an Intel Core 2 T7200 and integrated graphics (Intel Calistoga - Gen3) and I tried using it as a daily driver. It's surprisingly usable, but that's besides the point.
The problem is, whenever running a ...I recently got an old laptop with an Intel Core 2 T7200 and integrated graphics (Intel Calistoga - Gen3) and I tried using it as a daily driver. It's surprisingly usable, but that's besides the point.
The problem is, whenever running a Wayland session (I tried GNOME and Weston), only software llvmpipe OpenGL rendering is used. When using GNOME on X.Org, the integrated GPU is used as expected.
This is a bit confusing to me, because on my ThinkPad X201 (Gen5 GPU, but the same OpenGL version), everything works as expected with Wayland.
Is there something about this generation of Intel graphics that's a known limiting factor preventing using Wayland? I can provide any logs you might need.
Wayland:
```
$ glxinfo | grep OpenGL
MESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INCOMPATIBLE_DRIVER)
glx: failed to create drisw screen
failed to load driver: zink
OpenGL vendor string: Mesa
OpenGL renderer string: llvmpipe (LLVM 16.0.6, 128 bits)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 23.3.3-arch1.1
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.5 (Compatibility Profile) Mesa 23.3.3-arch1.1
OpenGL shading language version string: 4.50
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 23.3.3-arch1.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:
```
X.Org:
```
$ glxinfo | grep OpenGL
OpenGL vendor string: Mesa Project
OpenGL renderer string: i915 (chipset: 945GM)
OpenGL version string: 2.1 Mesa 23.3.3-arch1.1
OpenGL shading language version string: 1.20
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 23.3.3-arch1.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16
OpenGL ES profile extensions:
```
In case I'm opening this issue in the wrong place, I apologize. I figured that if Weston doesn't work, that could a good place to start.https://gitlab.freedesktop.org/wayland/weston/-/issues/859Weston 5 cross-compile issues with makefile2024-01-19T14:08:55ZSwaroop MuralidharanWeston 5 cross-compile issues with makefilehttps://gitlab.freedesktop.org/wayland/weston/-/issues/842Weston (Kiosk Mode) Launches Black Screen in X112023-11-21T17:23:01ZVehementHamWeston (Kiosk Mode) Launches Black Screen in X11The normal mode works fine. Whin I add `client=` to the config, things get messy. Here is the conig
```ini
[launcher]
icon=/usr/share/icons/Adwaita/32x32/ui/checkbox-symbolic.symbolic.png
path=/usr/bin/foot
[core]
idle-time=0
seat=seat-...The normal mode works fine. Whin I add `client=` to the config, things get messy. Here is the conig
```ini
[launcher]
icon=/usr/share/icons/Adwaita/32x32/ui/checkbox-symbolic.symbolic.png
path=/usr/bin/foot
[core]
idle-time=0
seat=seat-0
[shell]
background-image=/home/vehementham/.local/share/wallpapers/wallpaper.JPG
client=/usr/bin/foot
```
Here is the output of `weston --shell=kiosk-shell.so`
```
Date: 2023-11-15 CST
[14:39:18.619] weston 11.0.1
https://wayland.freedesktop.org
Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
Build: 11.0.1
[14:39:18.619] Command line: weston --shell=kiosk-shell.so
[14:39:18.619] OS: Linux, 6.1.60-gentoo-dist-hardened, #1 SMP PREEMPT_DYNAMIC Sun Nov 12 08:36:48 CST 2023, x86_64
[14:39:18.619] Flight recorder: enabled
[14:39:18.619] Using config file '/home/vehementham/.config/weston.ini'
[14:39:18.619] Output repaint window is 7 ms maximum.
[14:39:18.619] Loading module '/usr/lib64/libweston-11/x11-backend.so'
[14:39:18.627] Loading module '/usr/lib64/libweston-11/gl-renderer.so'
libEGL warning: DRI2: failed to authenticate
[14:39:18.649] warning: failed to query rendering device from EGL
[14:39:18.649] EGL version: 1.5
[14:39:18.649] EGL vendor: Mesa Project
[14:39:18.649] EGL client APIs: OpenGL OpenGL_ES
[14:39:18.649] warning: Disabling render GPU timeline and explicit synchronization due to missing EGL_ANDROID_native_fence_sync extension
[14:39:18.649] EGL features:
EGL Wayland extension: no
context priority: no
buffer age: no
partial update: no
swap buffers with damage: no
configless context: yes
surfaceless context: yes
dmabuf support: no
[14:39:18.658] GL version: OpenGL ES 3.2 Mesa 23.1.8
[14:39:18.659] GLSL version: OpenGL ES GLSL ES 3.20
[14:39:18.659] GL vendor: Mesa
[14:39:18.659] GL renderer: llvmpipe (LLVM 16.0.6, 256 bits)
[14:39:18.668] GL ES 3.2 - renderer features:
read-back format: ARGB8888
wl_shm 10 bpc formats: yes
wl_shm 16 bpc formats: yes
wl_shm half-float formats: yes
internal R and RG formats: yes
OES_EGL_image_external: yes
[14:39:18.668] Using gl renderer
[14:39:18.675] Registered plugin API 'weston_windowed_output_api_v1' of size 16
[14:39:18.675] Color manager: no-op
[14:39:18.675] Output 'screen0' attempts EOTF mode: SDR
[14:39:18.675] Output 'screen0' using color profile: built-in default sRGB SDR profile
[14:39:18.676] Chosen EGL config details: id: 11 rgba: 8 8 8 0 buf: 24 dep: 0 stcl: 0 int: 1-1 type: win|pix|pbf|swap_preserved vis_id: 0x21
[14:39:18.676] x11 output 1024x600, window id 27262981
[14:39:18.676] Output 'screen0' enabled with head(s) screen0
[14:39:18.676] Compositor capabilities:
arbitrary surface rotation: yes
screen capture uses y-flip: yes
cursor planes: no
arbitrary resolutions: no
view mask clipping: yes
explicit sync: no
color operations: yes
presentation clock: CLOCK_MONOTONIC_RAW, id 4
presentation clock resolution: 0.000000001 s
[14:39:18.677] libwayland: unable to lock lockfile /run/user/1000/wayland-1.lock, maybe another compositor is running
[14:39:18.677] Loading module '/usr/lib64/weston/kiosk-shell.so'
[14:39:18.730] Chosen EGL config details: id: 11 rgba: 8 8 8 0 buf: 24 dep: 0 stcl: 0 int: 1-1 type: win|pix|pbf|swap_preserved vis_id: 0x21
[14:39:20.267] Chosen EGL config details: id: 11 rgba: 8 8 8 0 buf: 24 dep: 0 stcl: 0 int: 1-1 type: win|pix|pbf|swap_preserved vis_id: 0x21
[14:39:21.906] Chosen EGL config details: id: 11 rgba: 8 8 8 0 buf: 24 dep: 0 stcl: 0 int: 1-1 type: win|pix|pbf|swap_preserved vis_id: 0x21
```
I compiled Weston on Gentoo
```
USE="X desktop drm fullscreen gles2 jpeg* kiosk pipewire resize-optimization seatd suid -editor -examples -headless -ivi -lcms -rdp -remoting -screen-sharing -systemd -test -wayland-compositor -webp -xwayland"
```https://gitlab.freedesktop.org/wayland/weston/-/issues/840simple-dmabuf-egl: screen tearing2024-01-19T17:02:56ZAlbert Ladislasimple-dmabuf-egl: screen tearingWe're tried running simple-dmabuf-egl on our system (weston 8.0.0, 1024x600, 60Hz, Vivante GC400, etnaviv/mesa 21.2.5) and got tearing on the animated box (pls see attached video and wesgr plot). What could be causing this?
![simple-dma...We're tried running simple-dmabuf-egl on our system (weston 8.0.0, 1024x600, 60Hz, Vivante GC400, etnaviv/mesa 21.2.5) and got tearing on the animated box (pls see attached video and wesgr plot). What could be causing this?
![simple-dmabuf-egl-tearing](/uploads/222e8b63abb5f9d0586f98f452f81f5d/simple-dmabuf-egl-tearing.mp4)
![weston-simple-dmabuf-egl-3-explicit-sync-1024.svg](/uploads/85d37d7c5a6d759105446a497cc65d4c/weston-simple-dmabuf-egl-3-explicit-sync-1024.svg)
Thanks.https://gitlab.freedesktop.org/wayland/weston/-/issues/838Launching application in Weston Kiosk from systemd service2023-12-06T10:55:58ZJean-Francois BETTELaunching application in Weston Kiosk from systemd serviceHi,
I am trying to launch an application in a Weston Kiosk using a Linux service (systemd or whatever).
The purpose is to control the application from outside Weston (for example start and stop the application).
Without the kiosk mode...Hi,
I am trying to launch an application in a Weston Kiosk using a Linux service (systemd or whatever).
The purpose is to control the application from outside Weston (for example start and stop the application).
Without the kiosk mode, i launch the application using WAYLAND_DISPLAY env variable using a dedicated socket for my Weston instance => The application shows in Weston well.
command example: `WAYLAND_DISPLAY=/some/path/wayland-1 /some/command`
With the kiosk mode enable, the application is started but not showing inside the Weston screen.
Here is how I launch weston : `weston --socket=/some/path/wayland-1 --shell=kiosk-shell.so`
What am i doing wrong?
The weston version is 11.0.1.https://gitlab.freedesktop.org/wayland/weston/-/issues/824[imx8mp]Weston-rdp screen share issue2023-10-23T08:06:32ZHimanshu Bhavani[imx8mp]Weston-rdp screen share issueI have imx8m board which has one display connected. and i want to share custom board display screen to any host machine(in my case it it Linux system)
For that i used to weston-rdp service for sharing screen and below configuration i ha...I have imx8m board which has one display connected. and i want to share custom board display screen to any host machine(in my case it it Linux system)
For that i used to weston-rdp service for sharing screen and below configuration i have done in bot side client and host.
In yocto add below lines into the weston bb file “weston_10*.imx.bb” to enable freerdp support.
`DEPENDS += "freerdp"`
`EXTRA_OEMESON += "-Dbackend-rdp=true"`
On client side:
Add below module into the /etc/xdg/weston/weston.ini file.
```
[core]
modules=screen-share.so
```
Add below command into the `/etc/xdg/weston/weston.ini` file
`command=@bindir@/weston --no-config –backend=rdp-backend.so`
Generate TLS certificate/key.
Modify ExecStart command into the `/lib/systemd/system/weston.service` file.
`ExecStart=/usr/bin/weston --backend=rdp-backend.so –rdp-tls- cert=/home/root/server.crt --rdp-tls-key=/home/root/server.key`
restart the weston service.
3) On Host side:-
Run xfreerdp with client ip address and display resolution.
`xfreerdp /v:192.168.200.59 /size:800x480`
When I restart weston service after all changes the service not started and weston not created socket into the /run/user/0/ location. this issue created when i add “–backend=rdp-backend.so” into the service file.
```
[11:14:50.666] weston 10.0.1
https://wayland.freedesktop.org
Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
Build: lf-5.15.52-2.1.0+
[11:14:50.666] Command line: weston
[11:14:50.666] OS: Linux, 5.15.77-6.4.0-devel+git.ddc6ca4d76ea, #1 SMP PREEMPT Thu Jun 29 10:14:22 UTC 2023, aarch64
[11:14:50.666] Flight recorder: enabled
[11:14:50.666] fatal: environment variable XDG_RUNTIME_DIR is not set.
Refer to your distribution on how to get it, or
http://www.freedesktop.org/wiki/Specifications/basedir-spec
on how to implement it.
```
In normal state without --backend=rdp-backend.so the weston created socket into the /run/user/0/ location.
Why weston failed in when i add rdp-backend.so in weston.service file ? can someone help me ?https://gitlab.freedesktop.org/wayland/weston/-/issues/808unknown child process exited2023-09-04T11:25:28ZKjeld Flarupunknown child process exitedI'm trying to start weston on a system without systemd, but it gives me some problems.
Thus I'm trying to start weston manually on a target with systemd first to be sure that I got the configuration correct, and I ends up in the same p...I'm trying to start weston on a system without systemd, but it gives me some problems.
Thus I'm trying to start weston manually on a target with systemd first to be sure that I got the configuration correct, and I ends up in the same problem as in non systemd.
My question is why do I get the message `unknown child process exited`
The primary difference is that when I run manually, I run as `root` and not `weston` user.
```
weston --debug --backend=rdp-backend.so --shell=fullscreen-shell.so --no-clients-resize --rdp-tls-cert=/var/keys/deif/rdp/server.crt --rdp-tls-key=/var/keys/deif/rdp/server.key
export DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/0/bus"
export EDITOR="vi"
export HOME="/home/root"
export INVOCATION_ID="e2ffa4076d5545419708a020a07679f4"
export LISTEN_FDS="1"
export LOGNAME="root"
export NOTIFY_SOCKET="/run/systemd/notify"
export OLDPWD="/"
export PATH="/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin"
export PWD="/home/root"
export SHELL="/bin/sh"
export SHLVL="0"
export SSH_CLIENT="172.17.165.18 45760 22"
export SSH_CONNECTION="172.17.165.18 45760 172.17.165.40 22"
export SSH_TTY="/dev/pts/0"
export TERM="xterm-256color"
export USER="root"
export WAYLAND_DISPLAY="wayland-0"
export WESTON_CONFIG_FILE="/etc/xdg/weston/weston.ini"
export XDG_RUNTIME_DIR="/run/user/0"
export XDG_SEAT="seat0"
export XDG_SESSION_CLASS="user"
export XDG_SESSION_DESKTOP="weston"
export XDG_SESSION_ID="c4"
export XDG_SESSION_TYPE="wayland"
export XDG_VTNR="7"
export XWAYLAND_NO_GLAMOR="1"
Date: 2023-08-31 UTC
[13:40:20.318] weston 10.0.1
https://wayland.freedesktop.org
Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
Build: lf-5.15.52-2.1.0+
[13:40:20.323] Command line: weston --debug --backend=rdp-backend.so --shell=fullscreen-shell.so --no-clients-resize --rdp-tls-cert=/var/keys/deif/rdp/server.crt --rdp-tls-key=/var/keys/deif/rdp/server.key
[13:40:20.323] OS: Linux, 5.15.32-rt39-06050-g9b4b5d3d25b3, #1 SMP PREEMPT_RT Fri Jul 28 08:37:26 UTC 2023, aarch64
[13:40:20.323] Flight recorder: enabled
[13:40:20.324] Using config file '/etc/xdg/weston/weston.ini'
WARNING: debug protocol has been enabled. This is a potential denial-of-service attack vector and information leak.
[13:40:20.325] Output repaint window is 16 ms maximum.
[13:40:20.328] Loading module '/usr/lib/libweston-10/rdp-backend.so'
[13:40:20.515] using FreeRDP version 2.6.1
[13:40:20.515] TLS support activated
[13:40:20:497] [3674:3674] [INFO][com.freerdp.core.listener] - Listening on [0.0.0.0]:3389
[13:40:20.533] Registered plugin API 'weston_rdp_output_api_v1' of size 8
[13:40:20.533] Color manager: no-op
[13:40:20.533] Output 'rdp' using color profile: built-in default sRGB SDR profile
[13:40:20.533] Output 'rdp' enabled with head(s) rdp
[13:40:20.533] Compositor capabilities:
arbitrary surface rotation: yes
screen capture uses y-flip: no
cursor planes: no
arbitrary resolutions: yes
view mask clipping: yes
explicit sync: no
color operations: no
presentation clock: CLOCK_MONOTONIC_RAW, id 4
presentation clock resolution: 0.000000001 s
[13:40:20.538] Loading module '/usr/lib/weston/fullscreen-shell.so'
[13:40:20.541] Loading module '/usr/lib/weston/screen-share.so'
Date: 2023-08-31 UTC
[13:40:20.576] weston 10.0.1
https://wayland.freedesktop.org
Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
Build: lf-5.15.52-2.1.0+
[13:40:20.576] Command line: /usr/bin/weston --backend=rdp-backend.so --shell=fullscreen-shell.so --no-clients-resize --rdp-tls-cert=/var/keys/deif/rdp/server.crt --rdp-tls-key=/var/keys/deif/rdp/server.key
[13:40:20.577] OS: Linux, 5.15.32-rt39-06050-g9b4b5d3d25b3, #1 SMP PREEMPT_RT Fri Jul 28 08:37:26 UTC 2023, aarch64
[13:40:20.577] Flight recorder: enabled
[13:40:20.577] Using config file '/etc/xdg/weston/weston.ini'
[13:40:20.577] Output repaint window is 16 ms maximum.
[13:40:20.577] Loading module '/usr/lib/libweston-10/rdp-backend.so'
[13:40:20.587] using FreeRDP version 2.6.1
[13:40:20.587] TLS support activated
[13:40:20.588] unable to bind rdp socket
[13:40:20.588] BUG: layer_list is not empty after shutdown. Calls to weston_layer_fini() are missing somwhere.
[13:40:20.588] fatal: failed to create compositor backend
[13:40:20.601] Screen share failed: No wl_shm found
[13:40:20.601] unknown child process exited
```https://gitlab.freedesktop.org/wayland/weston/-/issues/807unable to bind rdp socket2023-09-05T11:14:35ZKjeld Flarupunable to bind rdp socketWhen I start rdp-backend on my Yocto imx8 system, I get these listings in syslog
```
# journalctl -b | grep rdp
Aug 31 13:08:05 iE250-0d02f9 weston[871]: [13:08:05.198] Command line: /usr/bin/weston --backend=rdp-backend.so --shell=fulls...When I start rdp-backend on my Yocto imx8 system, I get these listings in syslog
```
# journalctl -b | grep rdp
Aug 31 13:08:05 iE250-0d02f9 weston[871]: [13:08:05.198] Command line: /usr/bin/weston --backend=rdp-backend.so --shell=fullscreen-shell.so --no-clients-resize --rdp-tls-cert=/var/keys/deif/rdp/server.crt --rdp-tls-key=/var/keys/deif/rdp/server.key
Aug 31 13:08:05 iE250-0d02f9 weston[871]: [13:08:05.208] Loading module '/usr/lib/libweston-10/rdp-backend.so'
Aug 31 13:08:05 iE250-0d02f9 weston[871]: [13:08:05.401] Registered plugin API 'weston_rdp_output_api_v1' of size 8
Aug 31 13:08:05 iE250-0d02f9 weston[871]: [13:08:05.401] Output 'rdp' using color profile: built-in default sRGB SDR profile
Aug 31 13:08:05 iE250-0d02f9 weston[871]: [13:08:05.401] Output 'rdp' enabled with head(s) rdp
Aug 31 13:08:05 iE250-0d02f9 weston[872]: [13:08:05.440] Command line: /usr/bin/weston --backend=rdp-backend.so --shell=fullscreen-shell.so --no-clients-resize --rdp-tls-cert=/var/keys/deif/rdp/server.crt --rdp-tls-key=/var/keys/deif/rdp/server.key
Aug 31 13:08:05 iE250-0d02f9 weston[872]: [13:08:05.441] Loading module '/usr/lib/libweston-10/rdp-backend.so'
Aug 31 13:08:05 iE250-0d02f9 weston[872]: [13:08:05.489] unable to bind rdp socket
Aug 31 13:08:05 iE250-0d02f9 weston[873]: [13:08:05.533] Command line: /usr/bin/weston --backend=rdp-backend.so --shell=fullscreen-shell.so --no-clients-resize --rdp-tls-cert=/var/keys/deif/rdp/server.crt --rdp-tls-key=/var/keys/deif/rdp/server.key
Aug 31 13:08:05 iE250-0d02f9 weston[873]: [13:08:05.534] Loading module '/usr/lib/libweston-10/rdp-backend.so'
Aug 31 13:08:05 iE250-0d02f9 weston[873]: [13:08:05.545] unable to bind rdp socket
```
What I can see it that weston forks twice, and these two forks each tries to start RDP, but only the parent succeeds on this.
I assume that "unable to bind rdp socket" is ignorable.https://gitlab.freedesktop.org/wayland/weston/-/issues/798weston-launch2023-08-11T07:19:28Zjax wangweston-launchHi everyone, I try to compile weston9.0.0 for my machine.
And now when I launch `weston-launch`, it shows
> weston: weston-launch must be run from a virtual terminal
I launch `weston-launch` by serial and ssh, it's the same.
I don't fi...Hi everyone, I try to compile weston9.0.0 for my machine.
And now when I launch `weston-launch`, it shows
> weston: weston-launch must be run from a virtual terminal
I launch `weston-launch` by serial and ssh, it's the same.
I don't find the available information in the network, what happened to it?
Thank you,
Best regards.https://gitlab.freedesktop.org/wayland/weston/-/issues/794How to configure multi-seat2023-08-29T09:22:03ZYaNing LuHow to configure multi-seatI recently used weston to configure multi-seat on debian12. I tried a variety of methods but failed. How to configure it so that I can use multi-seat. Can anyone help me? Thank you
weston: 10.0.1I recently used weston to configure multi-seat on debian12. I tried a variety of methods but failed. How to configure it so that I can use multi-seat. Can anyone help me? Thank you
weston: 10.0.1https://gitlab.freedesktop.org/wayland/weston/-/issues/773weston-screenshooter2023-08-09T09:26:40ZBaskar Rweston-screenshooterThe Weston Wayland is integrated with yocto kirkstone machine and is working on lvds interface display .
We are tried to use “weston-screenshooter” tool in command line capture the live screen with debug enable.
But we are getting the ...The Weston Wayland is integrated with yocto kirkstone machine and is working on lvds interface display .
We are tried to use “weston-screenshooter” tool in command line capture the live screen with debug enable.
But we are getting the following error, so our doubt is about the “weston-screenshooter” screen capture procedure.
If we able to capture the screen using this tool , then share step procedure to follow for the weston-screenshooter.
Please find steps which followed:
root@Alpha-22:/usr/lib/weston# loginctl
SESSION UID USER SEAT TTY
c1 1000 weston seat0 tty7
c3 0 root ttyLP0
2 sessions listed.
root@Alpha-22:/usr/lib/weston# echo $XDG_RUNTIME_DIR
/run/user/1000
root@Alpha-22:/usr/lib/weston# weston-screenshooter
weston_screenshooter@5: error 0: screenshooter failed: permission denied. Debug protocol must be enabled
root@Alpha-22:/usr/lib/weston#https://gitlab.freedesktop.org/wayland/weston/-/issues/771What can cause frequent calls to glDrawArrays in Weston?2023-07-05T08:40:21ZEdgar NeubauerWhat can cause frequent calls to glDrawArrays in Weston?I have to debug a scenario in a PowerVR based embedded Linux system where there is high resource consumption and 2D rendering is heavily loaded. Using a call tracer it seems to me that a lot of glDrawArrays calls are set off not in the a...I have to debug a scenario in a PowerVR based embedded Linux system where there is high resource consumption and 2D rendering is heavily loaded. Using a call tracer it seems to me that a lot of glDrawArrays calls are set off not in the apps themselves but in weston, usually with these callstacks:
```
#0 0x0000007f9e03edb0 in glDrawArrays () from /usr/lib/libGLESv2.so.2
#1 0x0000007f9e1cf1fc in ?? () from /usr/lib/libweston-8/gl-renderer.so
#2 0x0000007f9e1cf5d8 in ?? () from /usr/lib/libweston-8/gl-renderer.so
#3 0x0000007f9e1d00fc in ?? () from /usr/lib/libweston-8/gl-renderer.so
#4 0x0000007f9e22b564 in ?? () from /usr/lib/libweston-8/drm-backend.so
#5 0x0000007f9e224f9c in ?? () from /usr/lib/libweston-8/drm-backend.so
#6 0x0000007f9e225120 in ?? () from /usr/lib/libweston-8/drm-backend.so
#7 0x0000007f9ebfbe50 in ?? () from /usr/lib/libweston-8.so.0
#8 0x0000007f9ebabf90 in wl_event_loop_dispatch () from /usr/lib/libwayland-server.so.0
#9 0x0000007f9ebaa798 in wl_display_run () from /usr/lib/libwayland-server.so.0
#10 0x0000007f9edab47c in wet_main () from /usr/lib/weston/libexec_weston.so.0
#11 0x0000007f9ec50d78 in __libc_start_main () from /lib64/libc.so.6
#12 0x00000000004007a0 in ?? ()
#0 0x0000007f9e03edb0 in glDrawArrays () from /usr/lib/libGLESv2.so.2
#1 0x0000007f8fceaa6c in ?? () from /usr/lib/libweston-8/gl-renderer.so
#2 0x0000007f8fd3e3c0 in ?? () from /usr/lib/libweston-8/drm-backend.so
#3 0x0000007f8e836c80 in update_buffer_nativesurface ()
from /usr/lib/weston/libtsd.ivi.shell.ivi_shell.so
#4 0x0000007f8e836a2c in ?? ()
from /usr/lib/weston/libtsd.ivi.shell.ivi_shell.so
#5 0x0000007f903774a4 in ffi_call_SYSV () from /usr/lib/libffi.so.6
#6 0x0000007f90377c80 in ffi_call () from /usr/lib/libffi.so.6
#7 0x0000007f906c80f4 in ?? () from /usr/lib/libwayland-server.so.0
#8 0x0000007f906c56a8 in ?? () from /usr/lib/libwayland-server.so.0
#9 0x0000007f906c7034 in wl_event_loop_dispatch ()
from /usr/lib/libwayland-server.so.0
#10 0x0000007f906c5798 in wl_display_run ()
from /usr/lib/libwayland-server.so.0
#11 0x0000007f908c647c in wet_main () from /usr/lib/weston/libexec_weston.so.0
#12 0x0000007f9076bd78 in __libc_start_main () from /lib64/libc.so.6
#13 0x00000000004007a0 in ?? ()
```
These glDrawArrays calls seem to be caused by messages from some of the OpenGL apps but I don't know which ones. Other apps also use OpenGL but do not cause such callstacks in weston.
My concern is that these glDrawArrays calls compete with the calls from the other apps for gpu and slow those down. Can someone tell me if such behaviour is normal and what exactly makes weston cast these calls?
Regards.https://gitlab.freedesktop.org/wayland/weston/-/issues/754remoting-plugin doesn't work2023-05-19T09:12:10ZLeturemoting-plugin doesn't workI tried to add the remoting-plugin, but it didn't work when Weston started.
Here is the configuration in weston.ini file:
```code
[core]
...
remoting=remoting-plugin.so
[remote-output]
name=remote-output
mode=1280x800
host=0.0.0.0
port=...I tried to add the remoting-plugin, but it didn't work when Weston started.
Here is the configuration in weston.ini file:
```code
[core]
...
remoting=remoting-plugin.so
[remote-output]
name=remote-output
mode=1280x800
host=0.0.0.0
port=5000
```
To figure out why it wasn't working,I added logging to the relevant processes in the remoting-plugin.
In the end, I traced the issue to an exception occurring in the third call to the gl_renderer_repaint_output() function, after two repaint processes. This exception occurs on the here
```code
if (gr->swap_buffers_with_damage && !gr->fan_debug) {
...
ret = gr->swap_buffers_with_damage(gr->egl_display,
go->egl_surface,
egl_rects, n_egl_rects);
free(egl_rects);
...
```https://gitlab.freedesktop.org/wayland/weston/-/issues/743Unable to fork repository due to max limit reached2023-04-19T08:15:39ZAshwin PrabhakarUnable to fork repository due to max limit reachedHi, I am trying to fork the weston repository. I have the fork button greyed out with "You have reached your project limit". I would appreciate if someone can help me with the access.Hi, I am trying to fork the weston repository. I have the fork button greyed out with "You have reached your project limit". I would appreciate if someone can help me with the access.https://gitlab.freedesktop.org/wayland/weston/-/issues/672Running weston 10.0.1 on EGL without GL_EXT_unpack_subimage extension2022-09-28T14:54:45ZKamel BOUHARARunning weston 10.0.1 on EGL without GL_EXT_unpack_subimage extensionDue to [593d5af43a8e2c2a3371088fa7ae430d0517c82d](https://gitlab.freedesktop.org/wayland/weston/-/commit/593d5af43a8e2c2a3371088fa7ae430d0517c82d) it is no more possible to run weston on plaftorm with an EGL/GL implementation (here TI SG...Due to [593d5af43a8e2c2a3371088fa7ae430d0517c82d](https://gitlab.freedesktop.org/wayland/weston/-/commit/593d5af43a8e2c2a3371088fa7ae430d0517c82d) it is no more possible to run weston on plaftorm with an EGL/GL implementation (here TI SGX on beaglebone) that doesn't provide the GL_EXT_unpack_subimage extension.
Is there a solution to avoid reverting this commit and maintain weston compatibility across opengl implementation ?
Here are the weston logs on the beaglebone platform:
```
[07:39:09.943] weston 10.0.1
https://wayland.freedesktop.org
Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
Build: 2022.08-rc2-24-g4477c9c336+
[07:39:09.943] Command line: weston --backend=drm-backend.so --tty=4 -c /etc/weston.ini
[07:39:09.943] OS: Linux, 5.10.100, #1 SMP PREEMPT Mon Sep 19 19:18:16 CEST 2022, armv7l
[07:39:09.944] Flight recorder: enabled
[07:39:09.944] Using config file '/etc/weston.ini'
[07:39:09.945] Output repaint window is 7 ms maximum.
[07:39:09.945] Loading module '/usr/lib/libweston-10/drm-backend.so'
[07:39:09.979] initializing drm backend
[07:39:09.980] Trying logind launcher...
[07:39:09.981] logind: cannot find systemd session for uid: 0 -61
[07:39:09.981] logind: cannot setup systemd-logind helper error: (No data available), using legacy fallback
[07:39:09.981] Trying weston_launch launcher...
[07:39:09.981] could not get launcher fd from env
[07:39:09.981] Trying direct launcher...
[07:39:10.015] using /dev/dri/card0
[07:39:10.015] DRM: supports atomic modesetting
[07:39:10.015] DRM: does not support GBM modifiers
[07:39:10.015] DRM: supports picture aspect ratio
[07:39:10.015] Loading module '/usr/lib/libweston-10/gl-renderer.so'
[07:39:10.131] EGL client extensions: EGL_EXT_client_extensions
EGL_EXT_device_base EGL_EXT_device_enumeration
EGL_EXT_device_query EGL_EXT_platform_base
EGL_KHR_client_get_all_proc_addresses EGL_KHR_debug
EGL_EXT_platform_wayland EGL_MESA_platform_gbm
EGL_MESA_platform_surfaceless
[07:39:10.135] EGL device extensions: EGL_EXT_device_drm
[07:39:10.135] EGL version: 1.5
[07:39:10.135] EGL vendor: Mesa Project
[07:39:10.135] EGL client APIs: OpenGL_ES
[07:39:10.135] EGL extensions: EGL_EXT_buffer_age
EGL_EXT_create_context_robustness EGL_EXT_image_dma_buf_import
EGL_IMG_cl_image EGL_KHR_config_attribs EGL_KHR_create_context
EGL_KHR_fence_sync EGL_KHR_get_all_proc_addresses
EGL_KHR_gl_renderbuffer_image EGL_KHR_gl_texture_2D_image
EGL_KHR_gl_texture_cubemap_image EGL_KHR_image
EGL_KHR_image_base EGL_KHR_image_pixmap
EGL_KHR_no_config_context EGL_KHR_reusable_sync
EGL_KHR_surfaceless_context EGL_EXT_pixel_format_float
EGL_KHR_wait_sync EGL_MESA_configless_context
EGL_MESA_drm_image EGL_WL_bind_wayland_display
[07:39:10.136] warning: Disabling render GPU timeline and explicit synchronization due to missing EGL_ANDROID_native_fence_sync extension
[07:39:10.136] EGL_KHR_surfaceless_context available
[07:39:10.149] GL version: OpenGL ES 2.0 build 1.17@4948957
[07:39:10.149] GLSL version: OpenGL ES GLSL ES 1.00 build 1.17@4948957
[07:39:10.149] GL vendor: Imagination Technologies
[07:39:10.149] GL renderer: PowerVR SGX 530
[07:39:10.149] GL extensions: GL_OES_compressed_ETC1_RGB8_texture
GL_OES_depth24 GL_OES_depth_texture GL_OES_egl_sync
GL_OES_element_index_uint GL_OES_EGL_image
GL_OES_EGL_image_external GL_OES_fbo_render_mipmap
GL_OES_fragment_precision_high GL_OES_get_program_binary
GL_OES_mapbuffer GL_OES_packed_depth_stencil
GL_OES_required_internalformat GL_OES_rgb8_rgba8
GL_OES_standard_derivatives GL_OES_surfaceless_context
GL_OES_texture_float GL_OES_texture_half_float
GL_OES_vertex_array_object GL_OES_vertex_half_float
GL_EXT_blend_minmax GL_EXT_discard_framebuffer
GL_EXT_multi_draw_arrays GL_EXT_multisampled_render_to_texture
GL_EXT_shader_texture_lod GL_EXT_texture_format_BGRA8888
GL_EXT_texture_rg GL_IMG_multisampled_render_to_texture
GL_IMG_program_binary GL_IMG_read_format GL_IMG_shader_binary
GL_IMG_texture_compression_pvrtc GL_IMG_texture_format_BGRA8888
GL_IMG_texture_npot GL_IMG_uniform_buffer_object GL_KHR_debug
GL_EXT_texture_storage
[07:39:10.150] GL_EXT_unpack_subimage not available.
[07:39:10.150] EGL error state: EGL_SUCCESS (0x3000)
[07:39:10.152] failed to initialize egl
[07:39:10.170] fatal: failed to create compositor backend
Internal warning: debug scope 'drm-backend' has not been destroyed.
```https://gitlab.freedesktop.org/wayland/weston/-/issues/668Running weston 10 without weston-launch on containers2023-12-29T11:44:28ZMatheus CastelloRunning weston 10 without weston-launch on containersThis is not an issue, I think. If I'm posting in the wrong place, please let me know the right way to make this question.
Before Weston 10 I used weston-launch inside containers without problems. Now on Weston 10 I saw that weston-launch...This is not an issue, I think. If I'm posting in the wrong place, please let me know the right way to make this question.
Before Weston 10 I used weston-launch inside containers without problems. Now on Weston 10 I saw that weston-launch is deprecated, and not included as default. I tried to use the `seatd-launch` without success:
```
seatd-launch -- weston --backend=drm-backend.so --tty=/dev/tty7 --user=torizon
00:00:00.000 [seatd/seat.c:39] Created VT-bound seat seat0
00:00:00.007 [seatd/seatd.c:194] seatd started
Date: 2022-09-23 UTC
[04:35:14.132] weston 10.0.1
https://wayland.freedesktop.org
Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
Build: 10.0.1
[04:35:14.136] Command line: weston --backend=drm-backend.so --tty=/dev/tty7 --user=torizon
[04:35:14.136] OS: Linux, 5.19.0-nezha, #1 PREEMPT Wed Sep 14 05:26:45 UTC 2022, riscv64
[04:35:14.137] Flight recorder: enabled
[04:35:14.137] warning: XDG_RUNTIME_DIR "/tmp/1000-runtime-dir" is not configured
correctly. Unix access mode must be 0700 (current mode is 0700),
and must be owned by the user UID 0 (current owner is UID 1000).
Refer to your distribution on how to get it, or
http://www.freedesktop.org/wiki/Specifications/basedir-spec
on how to implement it.
[04:35:14.140] Using config file '/etc/xdg/weston/weston.ini'
[04:35:14.144] Output repaint window is 7 ms maximum.
[04:35:14.146] Loading module '/usr/lib/riscv64-linux-gnu/libweston-10/drm-backend.so'
[04:35:14.186] initializing drm backend
[04:35:14.188] Trying logind launcher...
[04:35:14.192] logind: cannot find systemd session for uid: 0 -61
[04:35:14.194] logind: cannot setup systemd-logind helper error: (No data available), using legacy fallback
[04:35:14.197] Trying weston_launch launcher...
[04:35:14.197] could not get launcher fd from env
[04:35:14.199] Trying direct launcher...
[04:35:14.201] <stdin> not a vt
[04:35:14.201] if running weston from ssh, use --tty to specify a tty
[04:35:14.201] fatal: drm backend should be run using weston-launch binary, or your system should provide the logind D-Bus API.
[04:35:14.202] fatal: failed to create compositor backend
Internal warning: debug scope 'drm-backend' has not been destroyed.
00:00:00.198 [seatd/seatd.c:218] seatd stopped
```
I'm pretty sure I'm missing something here, but weston tells me i should have weston-launch ...https://gitlab.freedesktop.org/wayland/weston/-/issues/657Error: Failed to connect to parent Wayland compositor2022-09-05T12:10:11ZTom DError: Failed to connect to parent Wayland compositorHello !
I am simply trying to run weston on my IMX8 device but i have the following error and no clue about what this means :
```
ciele@gateway:~$ export WAYLAND_DISPLAY=wayland-0
ciele@gateway:~$ weston --backend=wayland-backend.so
D...Hello !
I am simply trying to run weston on my IMX8 device but i have the following error and no clue about what this means :
```
ciele@gateway:~$ export WAYLAND_DISPLAY=wayland-0
ciele@gateway:~$ weston --backend=wayland-backend.so
Date: 2022-09-05 UTC
[09:21:05.044] weston 9.0.0
https://wayland.freedesktop.org
Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
Build: 9.0.0
[09:21:05.045] Command line: weston --backend=wayland-backend.so
[09:21:05.045] OS: Linux, 5.4.110-ciele+, #35 SMP PREEMPT Thu Jun 2 14:23:32 CEST 2022, aarch64
[09:21:05.045] Starting with no config file.
[09:21:05.046] Output repaint window is 7 ms maximum.
[09:21:05.046] Loading module '/usr/lib/aarch64-linux-gnu/libweston-9/wayland-backend.so'
[09:21:05.064] Error: Failed to connect to parent Wayland compositor: No such file or directory
display option: (none), WAYLAND_DISPLAY=wayland-0
[09:21:05.065] fatal: failed to create compositor backend
```
Am i missing something here ?