I have a 24.12 live iso and a virtual box vm with a 40GB hard drive, 8GB memory, 256MB video memory, 3D acceleration enabled. I am running on a windows 11 host with an intel i7-9700k, 32 GB of memory and a NVidia 4060Ti. The VM vdi is stored on spinning rust.
My steps:
Install from Gnome x86_64 iso, fully erasing the destination disk.
Use a swap file. All other options are defaults.
Reboot.
At this time, the installation appears to be functioning normally.
Install all available updates.
Reboot.
At this time, the installation is no longer able to reach the desktop.
For me 3D Acceleration won’t work for OMLx VBox VM’s running on OMLx host machine.
Couple of things to try
When you boot go to Advanced Options>Select Console Mode at the prompt login and type startx or whatever the executable is for the Gnome desktop. That command should start the desktop or produce some error that will help find a cause for this problem.
Also booted in to Console Mode user can dnf in icewm. When that installs the IceWM desktop. Then type starticewm and see if that boots you in to the IceWM desktop which is a very simple but graphical desktop where it may be easier to problem solve what is causing the problem.
Another thing one could do in Console Mode if we know the exact name of the window manager you could use sudo systemctl restart gdm or sudo systemctl stop gdm followed by sudo systemctl start gdm. I think it would be either gdm or gdm3 for Gnome. That command should restart gdm and take you to the gdm login screen or produce some error message that might clear this up.
Insert whatever I forgot here…
This I am not sure about but I was fairly certain that any recent Cooker or ROME Gnome iso would be using Wayland not X11. I’ll have to look in to that for my own education… Hope I typed all the commands above correctly, I’m tired.
I checked and the most recent ROME x86_64 Gnome iso (#3498) is indeed X11 not Wayland. Assigned @AngryPenguin to bug report #3107. @AngryPenguin is the creator and maintainer of the Gnome, Cosmic, and XFCE isos and a great OM Contributor.
and there is also:
lib64wayland-client0 x86_64 1.23.1-1 rolling-x86_64 31 k
lib64wayland-cursor0 x86_64 1.23.1-1 rolling-x86_64 16 k
lib64wayland-egl1 x86_64 1:1.23.1-1 rolling-x86_64 9.4 k
lib64wayland-server0
Wayland is used here by default, xserver is available on iso as fallback session. Whole desktop is configured to start to wayland. Gnome iso differs from the plasma iso in that it contains both sessions at once: the default wayland and the fallback xsession
It’s basically an upstream requirement that gradually stops development of the outdated xserver.
The problem that affected the user may be due to several things:
Incorrect operation of the graphics driver in virtualbox
Incorrect operation of the nvidia nouveau driver
Incomplete system update (since the system worked after installation but stopped after the update)
For example, I installed the said rome iso in virtualbox and updated it and the system started correctly for me.
I repeated the operation in qemu (boxes) and after installation and update the system worked correctly.
But the exception is that I have an amd radeon card, and the problem is probably related to nvidia - which I personally have no way to test because I do not have such a card.
