VirtualBox

Opened 4 years ago

Last modified 4 years ago

#19950 new defect

UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated: 0x0 1920x1173

Reported by: burdi01 Owned by:
Component: GUI Version: VirtualBox 6.1.14
Keywords: UIDesktopWidgetWatchdog Cc:
Guest type: Linux Host type: Linux

Description

Recently I migrated my multi-boot system from an i7-6700 to a Ryzen 9 3900XT.
Since then when VB is started under Slackware Current64 all VM's fail to start, whereas when VB is started under Xubuntu 20.04.1 these VM's start as expected.
The failure occurs very early in the start sequence: the big "starting arrow" remains shown and the system freezes all over. A hard restart is required.

From the VBox.log's it seems that the Slackware problem is:

GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated:[[BR]]
 Screen 0 work area is actually resized to: 0x0 x 1920x1173

whereas the Xubuntu VBox.log reads:

GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated:[[BR]]
 Screen 0 work area is actually resized to: 0x25 x 1920x1150

Note the "0x0" versus "0x25".

As via symlinks the VB settings and VM definitions are shared between the sundry Linux instances an error like a "leftover" file definition is highly unlikely.

Some other differences beween the VBox.logs are:
-- Xubuntu kernel 5.4.0-48-generic, Slackware 5.8.14-burdi64;
-- Xubuntu VB QT version 5.12.6, Slackware 5.6.1;
-- Xubuntu X release 12008000, Slackware 12009000;
-- Xubuntu loads a VMMR0.so, Slackware does not.

I started out with VB 6.1.14-140239. For Slackware I then tested VB testbuild 6.1.15-6.1.15-140809 asis with kernel 5.8.14-burdi64 and the same testbuild but patched (see #19845) with kernel 5.9.0-rc8-burdi64.
However the problem persists ...

Attachments (3)

Xubuntu.VBox.log (158.0 KB ) - added by burdi01 4 years ago.
Slackware.VBox.log (2.2 KB ) - added by burdi01 4 years ago.
Slackware.VBox.log.1 (158.5 KB ) - added by burdi01 4 years ago.

Download all attachments as: .zip

Change History (7)

by burdi01, 4 years ago

Attachment: Xubuntu.VBox.log added

by burdi01, 4 years ago

Attachment: Slackware.VBox.log added

comment:1 by burdi01, 4 years ago

Please disregard.

Last edited 4 years ago by burdi01 (previous) (diff)

comment:2 by burdi01, 4 years ago

I took virtualbox-6.1_6.1.14-140239~Ubuntu~eoan_amd64.deb (".deb" from now on) and with some trickery "installed" (untarred) it on my Slackware Current64 instance. The GUI came up OK, but booting the VM failed with a message like "the console is not enabled". This looks like a systemd thing and Slackware is non-systemd -- it still uses ConsoleKit2 and optionally elogind. As this might be the first worm out of a whole can I cut this experiment short.

To my surprise the VB Qt version was indicated as 5.15.1 (the Slackware version!), not 5.12.6 as I expected. I verified that the Xubuntu Qt version is 5.12.6, so the .deb version picks up the instance's Qt version. The fact that VirtualBox-6.1.14-140239-Linux_amd64.run (".run" from now on) reports its Qt version to be 5.6.1 on this Slackware Current64 instance indicates that the .run version brings its own QT version with it.
In other words: my "just a thought" as I described in my previous post should be more nuanced ...

Version 0, edited 4 years ago by burdi01 (next)

by burdi01, 4 years ago

Attachment: Slackware.VBox.log.1 added

comment:3 by burdi01, 4 years ago

Please disregard

Last edited 4 years ago by burdi01 (previous) (diff)

comment:4 by burdi01, 4 years ago

This thread should be regarded as superseded by #20021

Last edited 4 years ago by burdi01 (previous) (diff)
Note: See TracTickets for help on using tickets.

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