Has anyone using GNOME noticed any odd behavior after the recent update?
To explain: I took some time this morning to perform maintenance on my four Solus VMs. (I had just recently created these VMs following a Solus installation on my laptop.) In an X11 session, that included:
- installing the last few package upgrades,
- setting a 16:9 screen resolution just under 1920x1068, so that they would not lock up a Wayland session,
- finish any remaining configuration steps for any of the installed applications,
- populate the workspace switcher with those applications, and
- hibernate the VM so that when I start it next time, it would continue where I left off.
The first problem I noticed was that GNOME would boot to a black screen when launched. For a very long time all Solus VMs have used the VBoxSVGA video driver from VirtualBox. I prefer that over the older VBSVGA driver, because the VBoxSVGA driver provides a series of 16:9 resolutions, whereas the other provides 16:10 resolutions instead. But after changing to VBSVGA, the VM would boot normally.
After doing this maintenance as described above, I asked the VM to hibernate. GNOME doesn't make that easy, but in the terminal I can use a systemctl hibernate
command, and that has always worked. But not this time. The VM's display turned to black, and that's where things remained. The GNOME VM doesn't respond to an ACPI shutdown, as all the others do, so I have to power it off. The next time I launch GNOME, it's clear that it has not hibernated at all; all the workspaces are empty, whereas they should each have an application in it.
All the Solus VMs have 4 GB of RAM, so I provide each virtual disk drive with 6 GiB of swap space, plenty of room for the VMs to hibernate.
This behavior is the same whether I'm using an X11 session or a Wayland session. Since this is all new behavior, and isn't present in the other three Solus VMs (which all behave perfectly), I'd like to know whether anyone else is seeing the same thing in GNOME, either in a VM or on hardware. I don't want to write up a bug on the Dev Tracker unless I'm sure it's really a bug, and not some unexplained phenomenon that affects only my machine.