Loading a saved state stops some graphical apps from rendering until reboot

[mr.satoshi]

It is a simple problem and not critical but I need to make it work because I work with saved states a lot. I should mention that I am somewhat newbie with this guest system archlinux.

I have windows 10 and vbox7.0.2

Basically some GUI applications stop rendering properly if the VM is loaded from a saved state: midori, badwolf, spotify-launcher

I always save the state to resume it and my applications are still there without having to reopen everything, this is something quite common in virtualbox and it never gave me a problem (edited)

Apps like midori, badwolf or spotify-launcher work fine, but they stop rendering if I load a saved state and the only solution is to restart the vm, but other apps like nemo (file explorer) or the terminal (alacritty) don't have that problem.

I think the common detail is that they are gtk applications (however nemo works fine) and my guest distribution is probably not fully prepared for it because I use a very raw install of arch linux: -i3, picom (i think it could be related), midori, badwold, opera, minbrowser, spotify-launcher. I had also installed arc-gtk-themes

I have tried to log the problem without results or relevant info inside of the VM, reset i3, picom and polybar but none of that corrects the problem.

I already tried reinstalling virtualbox-guest-utils and gtk, I installed gnome but also didn't change anything.

Booted up and midori works: ​https://cdn.discordapp.com/attachments/826822179051929630/1035644709525266503/unknown.png

Saved state just fine: ​https://cdn.discordapp.com/attachments/826822179051929630/1035644710116659250/unknown.png

Loading state just right after: ​https://cdn.discordapp.com/attachments/826822179051929630/1035644711106510858/unknown.png

Some apps looks like this, they WORK but dont render properly: ​https://cdn.discordapp.com/attachments/826822179051929630/1035644711580475402/unknown.png

I believe it this most likely a problem on my end, either host or guest, so considering you may not be able to reproduce, I attached some logs.

[mr.satoshi]

Logs exported from VBox

[mr.satoshi]

I had confirmed this is not a guest issue by reproducing it on a complete different built VM, it is a virtualbox problem

[mr.satoshi]

I managed to "fix" it by disabling "3D hardware acceleration", however im not closing this until there is a proper fix in the software.