<div>Noted. </div><br><br><div class="gorgias_extra"><br><div class="gorgias_quote">
On Mon, May 18 2020, at 02:22 PM, Klaus Espenlaub
<span dir="ltr"><<a href="mailto:klaus.espenlaub@oracle.com" target="_blank">klaus.espenlaub@oracle.com</a>></span>
<br>
<blockquote class="gorgias_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hans,
I can totally understand the pain - but from a different angle we can
ask why Fedora 32 chose to break VirtualBox (which no other distribution
seems to have done to date, and even RHEL8 defaults to Wayland which I
see as excessively optimistic).
Yes, the fix is simple, but in our plan the fix will go first into the
Fedora 32 specific RPM package which we're working on already. Which we
need to do because the Fedora 31 one no longer can be installed on
Fedora 32 (usual dependency problems).
It's simply a risk management question. Who guarantees that the
environment variable tweak will not backfire on some old Qt install?
Klaus
_______________________________________________
vbox-dev mailing list<div class="gorgias_extra"><br><div class="gorgias_quote">
On Mon, May 18 2020, at 12:58 PM, Hans de Goede
<span dir="ltr"><<a href="mailto:hdegoede@redhat.com" target="_blank">hdegoede@redhat.com</a>></span>
<br>
<blockquote class="gorgias_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
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.<div class="gorgias_extra"><br><div class="gorgias_quote">
On Sun, May 17 2020, at 09:13 PM, Johnathan Bendwick
<span dir="ltr"><<a href="mailto:noscrubs679@gmail.com" target="_blank">noscrubs679@gmail.com</a>></span>
<br>
<blockquote class="gorgias_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<html><body><div dir="ltr">Ah, I see. Perhaps try a different language? I've heard cobalt works a bit better...</div><br></body></html><div class="gorgias_extra"><br><div class="gorgias_quote">
On Thu, May 14 2020, at 12:43 PM, Frank Batschulat
<span dir="ltr"><<a href="mailto:frank.batschulat@oracle.com" target="_blank">frank.batschulat@oracle.com</a>></span>
<br>
<blockquote class="gorgias_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hans, I have filed the following bug to track this:
[Oracle VM VirtualBox] #19583: GUI crashes when using Qt on Xwayland
sessions
<a href="https://www.virtualbox.org/ticket/19583">https://www.virtualbox.org/ticket/19583</a>
the possible fix for this is still being discussed internally.
</blockquote>
</div></div>
</blockquote>
</div></div>
</blockquote>
</div></div>
</blockquote>
</div></div>