Crashing when a client connects
Package version and OS/hardware:
- gnome-remote-desktop-42.0-4ubuntu1-arm64
- Ubuntu 22.04 GNOME Wayland session
- Raspberry Pi 4 with vc4 kms driver
Steps to reproduce:
- Enable Remote Desktop from GNOME Settings -- Sharing, both RDP and VNC.
- Try to connect to the host from a client, either RDP or VNC, for example Remmina is used here.
- Connection is successful, sometimes a distorted image of the desktop shows up for a second, but then the connection is closed.
Logs:
From journalctl output it seems that gnome-remote-desktop crashed. Here the first attempt was RDP and the second was VNC.
Apr 22 18:56:22 raspberrypi systemd[916]: Starting GNOME Remote Desktop...
Apr 22 18:56:22 raspberrypi systemd[916]: Started GNOME Remote Desktop.
Apr 22 18:56:22 raspberrypi gnome-remote-desktop-daemon[135517]: Cannot load libcuda.so.1
Apr 22 18:56:22 raspberrypi gnome-remote-desktop-daemon[135517]: Cannot load libnvidia-encode.so.1
Apr 22 18:56:22 raspberrypi gnome-remote-de[135517]: RDP server started
Apr 22 18:56:22 raspberrypi gnome-remote-de[135517]: VNC server started
Apr 22 18:57:48 raspberrypi gnome-remote-desktop-daemon[135517]: [18:57:48:361] [135517:135763] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_CONTINUE_NEEDED [0x00090312]
Apr 22 18:57:48 raspberrypi gnome-remote-desktop-daemon[135517]: [18:57:48:374] [135517:135763] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_COMPLETE_NEEDED [0x00090313]
Apr 22 18:57:48 raspberrypi gnome-remote-de[135517]: [RDP.RDPGFX] CapsAdvertise: Accepting capability set with version RDPGFX_CAPVERSION_106, Client cap flags: H264 (AVC444): true, H264 (AVC420): true
Apr 22 18:57:48 raspberrypi gnome-remote-de[135517]: [RDP.CLIPRDR] Converting clipboard content failed
Apr 22 18:57:53 raspberrypi systemd[916]: gnome-remote-desktop.service: Main process exited, code=killed, status=11/SEGV
Apr 22 18:57:53 raspberrypi systemd[916]: gnome-remote-desktop.service: Failed with result 'signal'.
Apr 22 18:57:53 raspberrypi systemd[916]: gnome-remote-desktop.service: Consumed 3.454s CPU time.
Apr 22 18:57:54 raspberrypi systemd[916]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 1.
Apr 22 18:57:54 raspberrypi systemd[916]: Stopped GNOME Remote Desktop.
Apr 22 18:57:54 raspberrypi systemd[916]: gnome-remote-desktop.service: Consumed 3.454s CPU time.
Apr 22 18:57:54 raspberrypi systemd[916]: Starting GNOME Remote Desktop...
Apr 22 18:57:54 raspberrypi systemd[916]: Started GNOME Remote Desktop.
Apr 22 18:57:54 raspberrypi gnome-remote-desktop-daemon[135821]: Cannot load libcuda.so.1
Apr 22 18:57:54 raspberrypi gnome-remote-desktop-daemon[135821]: Cannot load libnvidia-encode.so.1
Apr 22 18:57:54 raspberrypi gnome-remote-de[135821]: RDP server started
Apr 22 18:57:54 raspberrypi gnome-remote-de[135821]: VNC server started
Apr 22 18:58:35 raspberrypi systemd[916]: gnome-remote-desktop.service: Main process exited, code=killed, status=11/SEGV
Apr 22 18:58:35 raspberrypi systemd[916]: gnome-remote-desktop.service: Failed with result 'signal'.
Apr 22 18:58:35 raspberrypi systemd[916]: gnome-remote-desktop.service: Consumed 2.077s CPU time.
Apr 22 18:58:35 raspberrypi systemd[916]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 2.
Apr 22 18:58:35 raspberrypi systemd[916]: Stopped GNOME Remote Desktop.
Apr 22 18:58:35 raspberrypi systemd[916]: gnome-remote-desktop.service: Consumed 2.077s CPU time.
Other screen recording software:
- gnome-remote-desktop-40.2 in Ubuntu 21.10 / GNOME 40.5 works (VNC), so this is a regression
- Initially I thought this might be a driver issue, but other screen recording software works fine. Tested: Gnome-Shell, Firefox, and in particular Chromium, which supposedly also tries to use DMA-BUF.