Bug 2274566
| Summary: | GTK4 apps render badly on VMware with 3D acceleration passthrough enabled | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Adam Williamson <awilliam> |
| Component: | mesa | Assignee: | Adam Jackson <ajax> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 40 | CC: | ajax, bskeggs, garib.dow, gnome-sig, igor.raits, jexposit, j, kdlgates, klember, kparal, lyude, mclasen, nerijus, rhughes, rstrode, tstellar, walter.pete |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | AcceptedFreezeException | ||
| Fixed In Version: | mesa-24.0.5-1.fc40 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2024-04-14 17:13:37 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2187795 | ||
|
Description
Adam Williamson
2024-04-11 19:10:28 UTC
Mybe to help a little bit, just to confirm that I tested in a Linux host (Fedora 39 and Fedora 40 beta) with VMWare and QEMU/KVM and saw the issue in both of them when 3D is enabled, therefore it should be happening at least in VMWare, QEMU/KVM and VirtualBox. I am not sure you're reporting the same issue. This issue is to do with a new GTK renderer which is not in Fedora 39. Also, I'd be surprised if this issue affects qemu the same way, as virtio 3D acceleration is pretty different from vmware or virtualbox. I'll ask a few more folks to test. oh, are you saying you tested F39 and F40 on the *host* side? Okay. I'm still a bit surprised if it affects qemu with 3D passthrough, but it's possible... Yes you are right, I tested F40 VMs on a Linux host with F39 and F40 and apps are not rendering properly with 3D enabled. In summary, this answer your question about being only on Windows. When I had the issue with VMware I switched to QEMU/KVM, but found the same problem. Please let me know if I can be of any help testing. Adam, I just did a fresh download and install on both VMware and QEMU (using the live iso) and they both are working now with 3D enabled. On VMware I had to install with 3D disabled since the issue was there with the installer, but after it finished installing and I did a full update, then I enabled 3D and it is working fine now. It seems that something in the update corrected the issue. On QEMU it worked fine even with 3D enabled during installation, so now I'm not sure if the issue was there too in QEMU (and now my host machine is with F40, cannot test again on F39.) The good news is that it seems the problem should be gone by now if the final iso contains the updates so far. Sorry for any confusion. Hope this helps a little bit in your testing. I did a fresh install on VMware and just updated Mesa from 24.0.0.-2 (that comes with the iso) to 24.0.5-1 and that solved the issue. So if you include that version in the final iso it will work even during installation (at least on VMware.) I will try to do the same testing on VirtualBox but I guess it should work too. On a side note, the installation initial screen takes about 2 minutes to appear what is kind of weird. I even thought if haven't started, but it was running. Exact same result on VirtualBox. Mesa 24.0.5 solves the issue. It is not a gtk4 issue. I am a beginner so it's possible I am adding confusion to the issue. But I looked up the commands sudo dnf update; sudo dnf install mesa-libGLU and glxinfo | grep "OpenGL version" and it looks like I updated to Mesa 24.0.5 and unfortunately I still have the GNOME and Desktop corruption on enabling 3D Acceleration in VirtualBox and restarting the VM, which if I used the valid lines I think suggests either I am suffering a different bug/issue with the same corruption outcome or this version does not solve the bug/issue. But I have no real idea how to update Mesa or check the version so it's also entirely possible I fumbled the upgrade. Using VirtualBox 7.0.14 and Fedora 40 recently upgraded from the ISO install. +3 in https://pagure.io/fedora-qa/blocker-review/issue/1589 , marking accepted. I'm going to split this into two bugs, because based on my testing, the VMWare and VirtualBox issues are not actually the same. VMWare appears to be fixed by mesa 24.0.5. VirtualBox is not. FEDORA-2024-449369d66d (mesa-24.0.5-1.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-449369d66d VirtualBox bug: https://bugzilla.redhat.com/show_bug.cgi?id=2274930 FEDORA-2024-449369d66d (mesa-24.0.5-1.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report. |