Skip to content

libei spams `Invalid object 0xff00000000000019 after serial 25, I don't yet know how to handle that` during monitor resizes

Affected version: libei/main

Using here gnome-remote-desktop/master for reproduction:

Reproduction steps:

  1. Configure gnome-remote-desktop (g-r-d) (e.g. via g-c-c to have a certificate for the connection configured, etc.)
  2. Configure g-r-d to spawn virtual monitors via gsettings set org.gnome.desktop.remote-desktop.rdp screen-share-mode extend
  3. Get/Download the dbus-session.sh script from the mutter wiki. This script is just a convenient script to run nested dbus session (Jonas wrote this one some time ago)
  4. In a terminal run that script with ./dbus-session.sh -n, then in that same terminal run gnome-shell --wayland --headless
  5. Open a second terminal and run the script again but this time with the -x flag to connect to that dbus session, i.e. ./dbus-session.sh -x
  6. Set GNOME_REMOTE_DESKTOP_TEST_RDP_USERNAME and GNOME_REMOTE_DESKTOP_TEST_RDP_PASSWORD for some test credentials (in my screencast below I use a convenience script for that (content below))
  7. Run g-r-d with the --headless option (this option avoids some annoyances with libsecret)
  8. Run an RDP client, that supports dynamic resolution resizing. I use here xfreerdp with the the following cmdline: xfreerdp3 /v:[::1] /u:user /p:passwd /dynamic-resolution /size:1920x1080 (/v: is the target server, /u: the username, /p: the password, /size the initial submitted resolution, /dynamic-resolution enable the dynamic resolution behaviour in xfreerdp).
  9. After connecting to g-r-d here, resize the virtual monitor by resizing xfreerdp. While the resize is happening, move the mouse over the xfreerdps window to send absolute mouse motion events.

Observation: libei spams the journal with errors like: Invalid object 0xff00000000000019 after serial 25, I don't yet know how to handle that

Screencast of this issue:
Bildschirmaufzeichnung_vom_2023-11-02__08-27-36

The convenience script that I use in the ./dbus-session.sh -x window (no need to use that, but posting it here, in case you are curious):

#!/usr/bin/sh

export GNOME_REMOTE_DESKTOP_TEST_RDP_USERNAME=TEST
export GNOME_REMOTE_DESKTOP_TEST_RDP_PASSWORD=1234ä
export GNOME_REMOTE_DESKTOP_TEST_VNC_PASSWORD=12345
export WLOG_LEVEL=DEBUG
export G_MESSAGES_DEBUG=all
exec /usr/lib/./gnome-remote-desktop-daemon --headless --rdp-port 3389

I assume mutter already removed something regarding the mapping-id here and libei then treats inflight events with that mapping-id as error or something like that. In any case, these error messages should not happen here.