Remote input events only work if a physical keyboard is connected at least once per boot (wayland)
Version: gnome-remote-desktop 0.1.9-2.fc33, gnome-shell 3.38.2-5.fc33
I'm running a headless server with a dummy DP plug in order to get a local desktop suitable for remote session sharing. I can access the remote session without any problems.
If I reboot the machine and do not have a keyboard plugged in, I can still log in remotely and interact with gnome-shell ONLY with my mouse and keyboard (but no other applications). For example, if I open an application or settings window using GNOME search I then cannot pass any mouse or keyboard events to the window after it has opened. I can still use the Super key to pull up the activities overview and otherwise interact with the GNOME DE, except open windows (so maybe this is a mutter problem and we need to create a virtual input device, not sure).
However, if I then plug and unplug a keyboard into the headless machine, I can start interacting with all of the open application windows again from the remote session. I just need to do this once per boot to restore input access to my applications.
Here's some logs, I don't see any difference before/after connecting the keyboard:
Jan 04 13:24:35 htpc-new gnome-remote-de[7357]: Failed to initialize RDP server: Couldn't find the server certificate or private keyfile
Jan 04 13:25:11 htpc-new gnome-remote-desktop-daemon[7357]: Failed to mlock memory 0x7f6d1b518000 589888: This is not a problem but for best performance, consider increasing RLIMIT_MEMLOCK
Jan 04 13:25:12 htpc-new pipewire[4148]: (gnome-remote-desktop-daemon-32) client too slow! status:awake
Jan 04 13:26:04 htpc-new pipewire[4148]: (gnome-remote-desktop-daemon-32) client too slow! status:awake
Jan 04 13:26:43 htpc-new gnome-remote-desktop-daemon[7357]: Failed to mlock memory 0x7f6d30081000 589888: This is not a problem but for best performance, consider increasing RLIMIT_MEMLOCK
Jan 04 13:26:44 htpc-new pipewire[4148]: (gnome-remote-desktop-daemon-32) client too slow! status:awake
Jan 04 13:28:01 htpc-new pipewire[4148]: (gnome-remote-desktop-daemon-32) client too slow! status:awake
Jan 04 13:31:25 htpc-new gnome-remote-desktop-daemon[7357]: Failed to mlock memory 0x7f6d30081000 589888: This is not a problem but for best performance, consider increasing RLIMIT_MEMLOCK
Jan 04 13:31:39 htpc-new systemd[2215]: gnome-remote-desktop.service: Succeeded.
Jan 04 13:31:39 htpc-new systemd[2215]: gnome-remote-desktop.service: Consumed 2min 56.966s CPU time.
Jan 04 13:32:21 htpc-new gnome-remote-de[1565]: Failed to initialize RDP server: Couldn't find the server certificate or private keyfile
Jan 04 13:32:29 htpc-new gnome-remote-desktop-daemon[1565]: Failed to mlock memory 0x7f77f1308000 589888: This is not a problem but for best performance, consider increasing RLIMIT_MEMLOCK
Jan 04 13:36:23 htpc-new systemd[1060]: gnome-remote-desktop.service: Succeeded.
Jan 04 13:36:23 htpc-new systemd[1060]: gnome-remote-desktop.service: Consumed 15.255s CPU time.
Jan 04 13:37:03 htpc-new gnome-remote-de[1605]: Failed to initialize RDP server: Couldn't find the server certificate or private keyfile
Jan 04 13:37:45 htpc-new gnome-remote-desktop-daemon[1605]: Failed to mlock memory 0x7fe70530e000 589888: This is not a problem but for best performance, consider increasing RLIMIT_MEMLOCK
Jan 04 14:03:06 htpc-new systemd[1060]: gnome-remote-desktop.service: Succeeded.
Jan 04 14:03:06 htpc-new systemd[1060]: gnome-remote-desktop.service: Consumed 28.091s CPU time.
Jan 04 14:03:51 htpc-new gnome-remote-de[1575]: Failed to initialize RDP server: Couldn't find the server certificate or private keyfile
Jan 04 14:06:40 htpc-new gnome-remote-desktop-daemon[1575]: Failed to mlock memory 0x7fe268201000 589888: This is not a problem but for best performance, consider increasing RLIMIT_MEMLOCK