VirtualBox

Opened 4 years ago

Last modified 4 years ago

#20014 new defect

VirtualBox GUI broken after update from 5.2.44 to 6.1.14

Reported by: artlytic_dave Owned by:
Component: VMM Version: VirtualBox 6.1.14
Keywords: Cc:
Guest type: Linux Host type: Linux

Description

After struggling all day trying to keep 5.2.44 working with VVV, I decided to try updating to 6.1.14. As a result, when I open up the VirtualBox Manager GUI, I get this broken display. The contents are in the incorrect location and aren't clickable. If I expand the window, all of the content disappears. Luckily, I don't need to use the configuration tools there at the moment but this will be a problem for me quite soon.

Attachments (3)

virtualbox bug.jpg (70.5 KB ) - added by artlytic_dave 4 years ago.
Small window size, showing some content
virtualbox bug 01.png (204.2 KB ) - added by artlytic_dave 4 years ago.
Medium sized window, showing some other content
virtualbox bug 02.png (32.9 KB ) - added by artlytic_dave 4 years ago.
Large window size, showing no content and just columns/rows

Download all attachments as: .zip

Change History (4)

by artlytic_dave, 4 years ago

Attachment: virtualbox bug.jpg added

Small window size, showing some content

by artlytic_dave, 4 years ago

Attachment: virtualbox bug 01.png added

Medium sized window, showing some other content

by artlytic_dave, 4 years ago

Attachment: virtualbox bug 02.png added

Large window size, showing no content and just columns/rows

comment:1 by artlytic_dave, 4 years ago

Here is some additional information:

  • Host OS: Pop!_OS 20.04 LTS x86_64
  • Kernel (because this was giving me trouble before): 5.8.0-7625-generic
  • GNOME Shell: 3.36.4

I installed VirtualBox via apt, so I'm not sure why I can't update to 6.1.16 but I'm at 6.1.14.

Everything was working well with 5.2.44 but I tried to update VVV and it's associated VM and it broke my entire VirtualBox application so I couldn't start any VMs, whether made by VVV or manually by myself (not the first time this has happened). Looks like the kernel update from the VVV VM update couldn't be handled by VirtualBox 5.2.44 (or 5.2.42).

Note: See TracTickets for help on using tickets.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette