VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-remote-desktop (Ubuntu) |
Fix Released
|
High
|
Jeremy Bícha |
Bug Description
# lsb_release -rd
Description: Ubuntu 22.04 LTS
Release: 22.04
# apt-cache policy gnome-remote-
gnome-remote-
Instalados: 42.0-4ubuntu1
Candidato: 42.0-4ubuntu1
Tabla de versión:
*** 42.0-4ubuntu1 500
500 http://
100 /var/lib/
# uname -a
Linux fpgrpi 5.15.0-1005-raspi #5-Ubuntu SMP PREEMPT Mon Apr 4 12:21:48 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux
Summary of the bug:
-------------------
When I try to connect to gnome-remote-
I've used several VNC clients (Remmina in Ubuntu and Real VNC in Android) getting the same problem failing either in X11 or Wayland.
Notes:
- VNC connection does work in in previous Ubuntu 21.10 version with the same architecture (arm64) and same Raspberry Pi.
- VNC connection also does work in amd64 machines with Ubuntu 22.04 LTS and gnome-remote-
There is no apport info at all. Also there is almost no info in the journal regarding this problem. When I try to connect to VNC server it show this:
On Wayland:
-----------
abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 1884160 bytes), total 32768 (slots), used 3 (slots)
abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4169728 bytes), total 32768 (slots), used 3 (slots)
abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8130560 bytes), total 32768 (slots), used 83 (slots)
abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots)
abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots)
abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots)
abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots)
abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-
abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-
abr 25 00:21:43 fpgrpi gnome-shell[1497]: D-Bus client with active sessions vanished
abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-
abr 25 00:21:43 fpgrpi systemd[1381]: Stopped GNOME Remote Desktop.
abr 25 00:21:43 fpgrpi systemd[1381]: Starting GNOME Remote Desktop...
abr 25 00:21:43 fpgrpi systemd[1381]: Started GNOME Remote Desktop.
abr 25 00:21:43 fpgrpi gnome-remote-
abr 25 00:21:43 fpgrpi gnome-remote-
abr 25 00:21:43 fpgrpi gnome-remote-
abr 25 00:21:43 fpgrpi gnome-remote-
On X11:
-------
abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-
abr 25 00:12:18 fpgrpi gnome-shell[3044]: D-Bus client with active sessions vanished
abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-
abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-
abr 25 00:12:18 fpgrpi systemd[2859]: Stopped GNOME Remote Desktop.
abr 25 00:12:18 fpgrpi systemd[2859]: Starting GNOME Remote Desktop...
abr 25 00:12:18 fpgrpi systemd[2859]: Started GNOME Remote Desktop.
abr 25 00:12:19 fpgrpi gnome-remote-
abr 25 00:12:19 fpgrpi gnome-remote-
abr 25 00:12:19 fpgrpi gnome-remote-
abr 25 00:12:19 fpgrpi gnome-remote-
Changed in gnome-remote-desktop (Ubuntu): | |
status: | Confirmed → In Progress |
I managed to get a crash file from apport. It's attached.