Creating a bug report/issue
I have searched the existing open and closed issues
Required Information
- DietPi version |
cat /boot/dietpi/.version
- G_DIETPI_VERSION_CORE=9
G_DIETPI_VERSION_SUB=19
G_DIETPI_VERSION_RC=2
G_GITBRANCH=‘master’
G_GITOWNER=‘MichaIng’
- Distro version |
echo $G_DISTRO_NAME $G_RASPBIA
- trixie
- Kernel version |
uname --al
- Linux RPi-NEU-X 6.12.47+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.47-1+rpt1 (2025-09-16) aarch64 GNU/Linux
- Architecture |
dpkg --print-architecture
- arm64
- SBC model |
echo $G_HW_MODEL_NAME or (EG: RPi3)
- RPi 5 Model B (aarch64)
- Power supply used | (EG: 5V 1A RAVpower): Original Raspberry
- SD card used | (EG: SanDisk ultra) Various
Additional Information (if applicable)
- Some Issues after the update from Bookworm to Trixie: With the older Versions of Dietpi (9.12 to 9.18) all is working fine. We’re using the RPi5 as ThinClients with Gnome and Remmina (V1.4.39). With Trixie Multi-Monitor didn’t work. The Session is only shown on one Screen and will not expand to all screens. (with worked before); some strange behaviour at logon to the Terminal-Servers (Authentication is needed twice). RealVNC-Server wouldn’t shown and isn’t working.
With Bookworm all is working fine and it doesen’t matter if I install Trixie from the image fresh and clear or make the Distribution-Update over an existing and working installation of Bookworm (e.g. DietPi 9.18)
Steps to reproduce
- …
- …
Expected behaviour
Actual behaviour
Extra details
For clarification: The RPi 5 has two monitors attached, from which only one is showing the desktop now, while Remmina + RealVNC is a dedicated topic?
I just tested RealVNC very recently on RPi 5 and it was working perfectly fine. KMS needs to be enabled, but this was the case on Bookworm already, and should be done automatically. Also notice that the RealVNC packages on Bookworm and Trixie are exactly the same, just copy&pasted into the new APT suite by RPi Ltd. Also the kernel should be essentially the same, same version at least, just AFAIK the build is a different one. So debugging would need to focus on X11 and desktop components.
Starting with the multi-monitor topic: Such is usually configured in the desktop environment settings, in any case handled by X11. So I assume you are using Gnomes monitor settings? And what exactly is the issue then? No second monitor detected, or some error message when trying to expand the screen, if so which?
Ans what do you mean with “Terminal-Servers”? Local? Remote/VNC? GUI or plain Linux console?
Hi,
the RPi5 has two monitors attached and they are working fine with the expanded desktop over all screens. But if I want to connect with Remmina to our Windows-Terminal-Servers with RDP the Window will only shown on one of the two monitors. I can’t expand it to all of the monitors. The same settings are working fine in bookworm.
Where could I check that KMS is enabled?
Okay, so you use the Remmina client on the RPi 5 to access other systems. Hmm, if the desktop and other GUI applications use the split screen just fine, this sounds more like a change in Remmina. Though the version shipped by Debian Bookworm and Trixie is exactly the same, just a rebuild against new dependencies.
Did you just apt install remmina, or did you use their own repo or builds from elsewhere? And can you expand other application windows beyond the two screens? How odes Remmina behave their, does the window stick to just one screen or is just the content (remote desktop/terminal) on the second screen empty/black or so?
To check whether KMS is enabled:
/boot/config.txt should contain dtoverlay=vc4-kms-v3d, with or without ,noaudio suffix if HDMI audio is enabled or not.- This results in the following two paths exist:
/dev/dri/card* /sys/class/drm/card*
Yes, and we want to use it in Fullscreen over all monitors. So it works with bookworm.
Yes, I’ve installed all packages from apt.
Remmina starts only at one screen and didn’t expand over all screens. I could move the window between both screens and so it is with other applications. Really strange behaviour.
KMS seems enabled. The entry in config.txt exists, also the paths