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

Use the grahical environment.

What is the impact of this issue to you?

I can't use the graphical environment, absolutely necessary to administer our DB.

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

gnome-shell-47.8-1.el10.s390x
mutter-47.5-11.el10.s390x
package mesa is not installed
gdm-47.0-10.el10.s390x

How reproducible is this bug?:

100%

Steps to reproduce

1. Install a graphical environment on s390x, either
   1. headless as described here or
   2. using the virtual graphics device virtio-gpu with kvm

      1.  virt-install --disk size=10 --location <install-tree-url> --memory 9000 --vcpus 2 --graphics vnc,listen=0.0.0.0 --input keyboard,bus=virtio --input tablet,bus=virtio --name vm --os-variant rhel10-unknown

      2. The VNC port has to be opened it can be retrieved via

         virsh dumpxml vm --xpath //graphics

      3. firewall-cmd --add-port <port>/tcp

      4. Install Sever with GUI (for that the url has to be switched to compose/unified/s390x/ because RHEL 10 doesn't allow for more than 1 repo url anymore)
      5. Start the VM => log in screen is shown
2. log in => desktop is displayed
3. open shell with META key or click on top left corner => shell is displeyd
4. select a program like terminal or text editor

Expected results

The terminal or text editor is opened and displayed

Actual results

The desktop is displayed. If I open the shell again I see with a dot that apparently the program was launched but I cannot see it.

The gnome-shell logs show for example

surface_state_changed: assertion 'wl_window->has_last_sent_configuration' failed

which I don't know is relevant but it's the only message from gnome-shell after the application is opened and I can't see it on x86_64.

Additional info

1. attaching screenshots
2. this doesn't reproduce on x86_64 with virtio-vga device and the same package versions
3. i remember there was trouble enabling virtio-gpu graphics on RHEL 10 (s. links), I don't know if the display of windows was tested back then, will try to see if this reproduces on RHEL 10.0 RC.