GNOME boots to black screen and X cursor in VM

[TraceyC77]

trafficstars

Summary

When booting GNOME in a test VM (EFI), it shows a black screen with an X cursor after login

Steps to reproduce

1. Install GNOME from the 4.5 ISO / snapshot in a VM
2. Reboot into the VM
3. The login screen appears normally, log in with your user

Expected result

The GNOME desktop displays

Actual result

Black screen with X cursor

Environment

• [X] Is system up to date?

Repo

Shannon (stable)

Desktop Environment

GNOME

System details

Kernel: 6.6.15-272.current arch: x86_64 X11 with Xwayland

Other comments

I'm pretty sure the VM worked normally right after installing GNOME. Today was the first time I noticed it getting the black screen after login via the GUI

Fun fact: After gathering information from the tty, I switched back to the graphical desktop session (Ctrl+Alt+F3). I was presented with the lock screen. After logging into that, I was able to access the graphical GNOME session.

Unfortunately, I wasn't able to launch the default Gnome terminal or tilix terminal, both produced a spinny cursor and then nothing happened. I was able to launch other applications (Firefox, Libre Calc, Rhymthbox etc). Except gedit. I was able to launch konsole. I can launch tilix from konsole (not from the Gnome shell) I cannot launch gnome-terminal from konsole

tracey@tracey-solus-gnome-vm ~ $ gnome-terminal
# Error creating terminal: Could not activate remote peer: startup job failed.

Attached are screenshots of the journalctl messages from this boot, from just before I switched to a tty

[joebonrichie]

Duplicate of #1107

[joebonrichie]

Sorry, the symptoms are not exactly the same, reopening

[Justinzobel]

I've just installed GNOME 4.5 ISO in VirtualBox and I get to the desktop after logging in. I wonder what the difference is. I'm not sure how to do it in KVM but in VirtualBox I always enable 3D Acceleration on the GPU and give it the max (128MB IIRC) of Video Memory, this might be the difference.

[ermo]

I can (sadly) reproduce this in virt-manager. I hit it on the third try. Asking the virt-manager gui to switch to a different tty and then back to the original tty appears to fix it for me.

I wonder if we should be documenting this as a known issue in the release notes?