Graphical corruption with VB 7.0.14 and Ubuntu 22.04.3

Discussions about using Linux guests in VirtualBox.
Post Reply
mkdr
Posts: 3
Joined: 30. Jan 2024, 05:37

Graphical corruption with VB 7.0.14 and Ubuntu 22.04.3

Post by mkdr »

I installed VB 7.0.14 on Windows 11 host (winver 23h2 22631.3085) with Nvidia RTX4080 driver 551.23 with a fresh Ubuntu 22.04.3 quick installation, installed included Guest Additions, rebooted and now have randomly graphical corruptions which look like this:

The mouse cursor is a large black rectangle. It mostly gets triggered when you click VB window so it gets focus and you move around the mouse. Rebooting the virtual machine often fixes the glitch, but then it randomly comes back.
Attachments
VirtualBox_2024-01-30_04-43-59.png
VirtualBox_2024-01-30_04-43-59.png (24.72 KiB) Viewed 6361 times
VirtualBoxVM_2024-01-29_15-41-32.jpg
VirtualBoxVM_2024-01-29_15-41-32.jpg (61.99 KiB) Viewed 6361 times
johnzeng
Posts: 10
Joined: 25. Apr 2011, 23:28
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Arch

Re: Graphical corruption with VB 7.0.14 and Ubuntu 22.04.3

Post by johnzeng »

bertje
Posts: 58
Joined: 4. Nov 2010, 09:49
Primary OS: MS Windows 10
VBox Version: OSE other
Guest OSses: Ubuntu/MATE/Server 16.04, 18.04, 20.04, 21.04, 22.04, 23.10, Windows XP/7/10/11

Re: Graphical corruption with VB 7.0.14 and Ubuntu 22.04.3

Post by bertje »

Same issue and 100% reproducible as reported here: Heavy screen flickering VirtualBox 6.1.50 / 7.0.14 Ubuntu guest kernels 6.4 / 6.5. See also the hint how to temporary downgrade the kernel until VirtualBox releases a fix.
VirtualBox bugreport: https://www.virtualbox.org/ticket/21955. Not confirmed by VirtualBox yet, no progress yet.
mkdr
Posts: 3
Joined: 30. Jan 2024, 05:37

Re: Graphical corruption with VB 7.0.14 and Ubuntu 22.04.3

Post by mkdr »

Thank you, hopefully it will be fixed soon.

My host system is:

AMD 7800x3d
Nvidia RTX4080
atomick
Posts: 6
Joined: 31. Jan 2024, 00:16

Re: Graphical corruption with VB 7.0.14 and Ubuntu 22.04.3

Post by atomick »

Just experienced the once so far 7.0.14 on amd-7950x3D/64g ram host.

a thought of my own change, unchk in Display 3D support box. although a jazzed 4070Ti nVidia my vid memory is not cranked to full 128meg of display need. User need may vary.

Noticed as such prior to crash audio stream in playback started to jitter, and attempt at email response edit simply stopped non responsive. Not exactly a tenor to stressing any cpu performance something simply injected the error.

odd saw the update 0.14 , had to try. New sometimes has other Stuff involved. Await a patch and or fix if numerous experience persists.
kept my previous 7.10.deb file in case a need to step back.

not dependent only a hobby set user. Awaiting.
so far issue has not reappeared by this clear of 3D support.
Cheers.
bertje
Posts: 58
Joined: 4. Nov 2010, 09:49
Primary OS: MS Windows 10
VBox Version: OSE other
Guest OSses: Ubuntu/MATE/Server 16.04, 18.04, 20.04, 21.04, 22.04, 23.10, Windows XP/7/10/11

Re: Graphical corruption with VB 7.0.14 and Ubuntu 22.04.3

Post by bertje »

Thanks for sharing your experiences.

We always see problems with 3D graphics enabled, even with latest VB 7.0.14. For this reason, Change default display settings as 3D accelaration is not supported has been created to remove the 3D option in the VM Settings Display settings menu.

Disabling 3D graphics does not solve the heavy screen flicking issue as reported here: Heavy screen flickering VirtualBox 6.1.50 / 7.0.14 Ubuntu guest kernels 6.4 / 6.5. See also the hint how to temporary downgrade the kernel until VirtualBox releases a fix.

VirtualBox bugreport: https://www.virtualbox.org/ticket/21955. 3 weeks later, still no confirmation from Oracle yet.
mkdr
Posts: 3
Joined: 30. Jan 2024, 05:37

Re: Graphical corruption with VB 7.0.14 and Ubuntu 22.04.3

Post by mkdr »

I have done what was told in the bug report:

"I tried different things and now found that the easiest workaround is to simply switch off Wayland as described here  ​https://linuxconfig.org/how-to-enable-d ... 04-desktop which replaces Wayland by Xorg as display manager."

and that seems to have fixed the issue.

sudo nano /etc/gdm3/custom.conf
WaylandEnable=false
save and reboot
Post Reply