What were you trying to do that didn't work?

When gnome-kiosk is executed in RDP mode, it doesn't create a virtual monitor automatically, only after an RDP client connects. When run with --virtual-monitor option, a virtual monitor is created, however is separate from a monitor that actually displays the hosted application (specifically Anaconda in context of RHEL-10 installation).

To add more background: This is problematic at least for Anaconda GUI test automation tool (Anabot) which internally uses dogtail to connect to the tested application. An attempt to control the application however fails when no monitor is present, as the widgets within the application appear to have negative coordinates or dimensions. At this point the only option for us is to use a workaround consisting of connecting via a local RDP client to ensure the virtual monitor is created, nevertheless this is somewhat cumbersome and introduces an unnecessary layer to the whole solution.

What is the impact of this issue to you?

It's not possible to run Anabot when Anaconda is running in gnome-kiosk without resorting to non-systematic and potentially unreliable workarounds. Also when Anaconda runs without an existing monitor, it seems the GUI is actually 'squashed' and has negative coordinates or dimensions, which can result in unforeseen issues.

Please provide the package NVR for which the bug is seen:

mutter-47.0-1.el10 (gnome-kiosk-47.0-2.el10)

Expected results

It's possible to run gnome-kiosk (or similar components providing RDP) in RDP mode with a static monitor (--virtual-monitor) using a predefined resolution. The static monitor is mirrored to an RDP one when RDP client connects (I think this functionality could be turned on using a specific command line option). As a result, it's possible to control the application (Anaconda) running in gnome-kiosk even without an existing RDP connection.