Xserver should be using WL_SURFACE_SERIAL, not WL_SURFACE_ID

[2gn]

Steps to reproduce

1. Run xwayland-satellite
2. Run gimp or whatever

On the xwayland-satellite side, I get this:

user@computer:~/Downloads$ xwayland-satellite
 2024-10-17T12:21:54.009Z INFO  xwayland_satellite > Connected to Xwayland on :0
 2024-10-17T12:21:54.013Z INFO  xwayland_process   > The XKEYBOARD keymap compiler (xkbcomp) reports:
 2024-10-17T12:21:54.013Z INFO  xwayland_process   > > Warning:          Unsupported maximum keycode 708, clipping.
 2024-10-17T12:21:54.013Z INFO  xwayland_process   > >                   X11 cannot support keycodes above 255.
 2024-10-17T12:21:54.013Z INFO  xwayland_process   > Errors from xkbcomp are not fatal to the X server
thread 'main' panicked at src/xstate/mod.rs:366:25:
Xserver should be using WL_SURFACE_SERIAL, not WL_SURFACE_ID
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

And this from the GIMP side (fatal success):

user@computer:~/Downloads$ gimp
gimp: Fatal IO error 0 (Success) on X server :0.

My environment

wayland + debian 12 xwayland installed

$ uname -a
Linux e14 6.1.0-26-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.112-1 (2024-09-30) x86_64 GNU/Linux

$ lsb_release -a
Distributor ID: Debian
Description:    Debian GNU/Linux 12 (bookworm)
Release:    12
Codename:   bookworm

[2gn]

Turned out I was using Xwayland v22, which is not supported. I'm upgrading to Debian Trixie, but not sure it'll fix the situation.

[NickHastings]

FYI it works on Bookworm for me with xwayland backported from testing.

[Supreeeme]

This is definitely a result of too old Xwayland - thought I should improve the error message though, as it's definitely cryptic to anyone unfamiliar with Xwayland internals (https://github.com/Supreeeme/xwayland-satellite/commit/ab2d09962c425670a4a7ca6ef5d92a0f06632499). Closing.

[2gn]

FYI it works on Bookworm for me with xwayland backported from testing.

That is a smarter solution. I did a full upgrade and completely broke the entire wayland system on my machine :(

P.S. For those who don't want to take the risk You can safely try out Nix to install xwayland-satellite. This way you don't need to backport Xwayland, because Nix's going to handle all the dependency stuff, without breaking the system ;)

[CarlosNunezMX]

I have a similar error

2024-11-25T01:34:30.596Z INFO  xwayland_process > _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
 2024-11-25T01:34:30.596Z INFO  xwayland_process > _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
 2024-11-25T01:34:30.664Z INFO  xwayland_satellite > Connected to Xwayland on :2
 2024-11-25T01:34:30.664Z INFO  xwayland_satellite > Successfully notified systemd of ready state.
 2024-11-25T01:34:30.671Z INFO  xwayland_process   > The XKEYBOARD keymap compiler (xkbcomp) reports:
 2024-11-25T01:34:30.671Z INFO  xwayland_process   > > Warning:          Unsupported maximum keycode 708, clipping.
 2024-11-25T01:34:30.671Z INFO  xwayland_process   > >                   X11 cannot support keycodes above 255.
 2024-11-25T01:34:30.672Z INFO  xwayland_process   > > Warning:          Could not resolve keysym XF86KbdInputAssistPrevgrou
 2024-11-25T01:34:30.672Z INFO  xwayland_process   > > Warning:          Could not resolve keysym XF86KbdInputAssistNextgrou
 2024-11-25T01:34:30.672Z INFO  xwayland_process   > Errors from xkbcomp are not fatal to the X server

D.E: Niri Host: Arch linux Xwayland Version: 24.1.4

Edit: Solved by changing default screen from :0 to :1