Hi,
On 5/14/20 2:43 PM, Frank Batschulat wrote:
Hans, I have filed the following bug to track this:
Thank you, I wonder though why not ship the next 6.1.z / 6.0.z
release with my workaround for now?
Coming up with a proper fix for this is likely going to
require some time and in the mean time users are being
bitten by this bug.
Also given that I reported this serious bug, which basically
makes VirtualBox completely unusable on default Fedora 32
installs over a month ago I must say I'm a bit disappointed
by how VirtualBox upstream is handing this.
You could have fixed this with the April 14th 6.1.4 release
by including my 1 line workaround for now. Instead you have
let users of VirtualBox on Fedora 32 out in the cold.
Regards,
Hans
[Oracle VM VirtualBox] #19583: GUI crashes when using Qt on Xwayland sessions
https://www.virtualbox.org/ticket/19583
the possible fix for this is still being discussed internally.
On Tue, 07 Apr 2020 14:00:47 +0200, Hans de Goede <[email protected]> wrote:
Hi,
I noticed that with a default Fedora 32 workstation install (default GNOME3 on
Wayland session) VirtualBox crashes immediately at startup. The problem is that
QT5 now defaults to the Wayland backend and VirtualBox assumes the X11 backend
is used and makes a bunch of unchecked X11 calls which cause NULL pointer
derefs.
The attached patch is a simple fix which fixes this by setting the QT backend
back to X11.
As usual, the patch is released under the MIT license.
Regards,
Hans
_______________________________________________
vbox-dev mailing list
[email protected]
https://www.virtualbox.org/mailman/listinfo/vbox-dev
