EMU exited from an error: GL_ARB_clear_texture #5749
Comments
|
Same here, but only after also upgrading to Fedora 39 beta (I'm pretty sure I used Fedora 38 after the Sonoma upgrade).
|
|
Can either or both of your provide a debug.log? |
|
Maybe this can help:
|
|
I don't know how that's related to the issue reported here at all? |
|
Issue named appears at the screen and VM stops working |
|
I see, please post the entire debug.log |
|
I am having this problem as well. Behavior: After running Configuration Debug Log attached, but it does not appear to give much helpful information |
|
I think this is a driver issue on Kali's side. As a workaround you can disable GPU acceleration while this is getting figured out. |
|
That's my suspicion as well. Kali VM runs okay after initial install until I apt update. After rebooting after apt update it exhibits this behavior. Seems like something is up with a package in Kali. |
|
I was able to I'll have to unhold those packages later, but for now this provides a working and fairly up-to-date Kali install in UTM. |
|
Just to chime in. I'm also seeing this error with Arch Linux on Sonoma. Using KDE Plasma X11 session, it crashes as soon as I adjust display resolution. Anyway here's my debug.log |
|
I just had this issue when I upgraded some packages in Arch Linux on UTM. I'm pretty sure it was one of these bad boys: As a workaround, I've changed my Display from "virtio-gpu-gl-pci" to "virtio-gpu-pci"... I'm functional, but getting GPU acceleration back would be nice... |
|
Updated EndeavorOS today and was bit by this. Had to go back to a non 3d accelerated configuration to prevent the vm from crashing. |
FYI - I found another workaround with GPU acceleration still on! You just need to deactivate or uninstall gdm. Also, do not try to start gnome as the issue is clearly related to it. As a replacement, I'm using Xfce4 and Lxdm as display manager. UTM display is virtio-gpu-gl-pci, so I get full acceleration. |
|
sigh It seems like Mesa again committed code that just breaks virgl: https://gitlab.freedesktop.org/mesa/mesa/-/commit/a1eabeff6607cf1466df3486d2585b51909e7450 Basically the feature In the meantime, the Mesa issue is tracked in https://gitlab.freedesktop.org/mesa/mesa/-/issues/9944 |
|
Observed
Crash report |
|
For ArchLinux (aarch64) users, here is a patched set of Mesa packages that is prebuilt: https://drive.google.com/file/d/1QE73vHePjoFYjDEHu8lMsawxasYkJUQy/view?usp=sharing For all other users, here is the Mesa changes that you need to apply: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25580 |
|
I found rolling back mesa to 23.1.8-1 and mesa-utils to 9.0.0-2 did the trick for me. |
|
On Ubuntu switching to PAA that follows git daily also solves the issue (it is already past 3c1020724eca2488f13148364c1441b6c966c492 where regression was fixed) sudo add-apt-repository ppa:oibaf/graphics-drivers
sudo apt update
sudo apt upgrade
|
|
What version's of Mesa packages were you on that were broken, and what version did this PPA land you on to fix it? |
|
@thedarb Ubuntu 23.10 Daily 2023-10-05 arm64 (
|
This is fixing the error for me on (Sonoma 14 with ubuntu arm 23.10). thanks |
|
Fix for kali linux
This fix will only be necessary until kali updates mesa on its repo, then revert the changes in your repos and do a full-upgrade |
This one really helped bro.Thanks so much |
|
Hi guys I'm just starting to learn the linux system, but I decided to use UTM on my macbook, today I updated the system and then I ran into a problem that everyone is discussing here. I might be stupid, sorry in advance. I have not fully understood how to fix this problem, what exactly is meant by adding a new snapshot repository, and disabling the standard one, how to do it in the format of commands, console executions. If the last solution in this topic is working, please help me to understand in detail what actions are needed, more thanks to all in advance! |
Hi @morganb1ackhand, good decision to get into Linux! 😃 Unfortunately, your question is off-topic for this issue, and I recommend to search for help in the forum or IRC channels or mailing lists that belong to your Linux distribution. Some hints on this issue, that help you ask for support there: You ran into this issue, because the To get your Linux booting again, change the emulated display card in the settings for your VM as mentioned above as a workaround. As soon as the new mesa package got released, you'll get it on updating your Linux. Enabling a snapshot repository means to alter the settings of your Linux distro, which repositories are used (from which packages are retrieved for installation). A snapshot repo contains bleeding edge packages, that are not considered stable. How to change the repo setting to enable or disable a repository differs from Linux distribution to Linux distribution and depends on the package manager you are using. Please ask that somewhere else. |
|
I can confirm that the patch worked for me on Fedora 39. Additionally, since it uses LLVM 17, another patch must also be applied in order for compilation to succeed at all. (I don’t like to use PPAs, third-party repos, or anything like that, hence all the manual patching.) |
|
Mesa 23.3.0 released and fixed this bug, so stay tuned unless your linux distro update this version. |
|
We should probably report it to ANGLE, I just didn't work out where to so that yet, it might help them prioritise implementing it at their end. |
|
Added a feature request to ANGLE https://bugs.chromium.org/p/angleproject/issues/detail?id=8444 |
Just tried this on Fedora 39 as well, and I was able to build mesa after applying those patches. For anyone impatient waiting for Mesa 23.3.0 to come to Fedora 39 like me and not sure how to rebuild mesa, here are the steps I used to rebuild mesa with the patches (may or may not be idiomatic RPM building steps):
cd ~
sudo dnf install rpmdevtools
rpmdev-setuptree
dnf download --source mesa
sudo dnf builddep mesa
rpm --install mesa-23.2.1-2.fc39.src.rpm
cd ~/rpmbuild/SOURCES
mv /path/to/25580.diff ./first-patch.patch
mv /path/to/24879.diff ./second-patch.patch
Before: release_number = 2;... Patch0: 0001-radeonsi-prefix-function-with-si_-to-prevent-name-co.patch
Patch10: gnome-shell-glthread-disable.patchAfter: release_number = 3;... Patch0: 0001-radeonsi-prefix-function-with-si_-to-prevent-name-co.patch
Patch10: gnome-shell-glthread-disable.patch
Patch20: first-patch.patch
Patch30: second-patch.patch
cd ~/rpmbuild/SPECS
rpmbuild -bb mesa.spec
cd ~/rpmbuild/RPMS/aarch64
sudo dnf install mesa-*.rpm |
|
permanent fix for kali linux
Fix Power manager to fix xfce4-power-manager you can follow these steps
|
|
Mesa 23.3 landed in Ferdora 39, works in my case But still there are issues - I can't spawn IntelliJ intellij - just getting black window |
|
Has any body got a minimal program that can trigger this using opengl - keen to find out if my own freeze is this or something else. |
|
@stuaxo If it's a freeze, then this isn't the issue. This issue results in an outright crash of the QEMU instance, not merely a freeze. |
|
@tpasternak Are you using Wayland mode or X mode? I am using IntelliJ on Fedora 39 just fine. |
|
Thanks, I think I'm hitting multiple issues - but the UI not working is the first one, I can still SSH in at that point, and use the Qemu console, recently I noticed that at some point after that the Qemu console stops responding and I can't SSH in any more, at all so it probably is frozen. Anyway, will jump off this now, cheers for the clarification. |
|
@cky the default one, in general it works, but some apps (IntelliJ) don't |
|
@tpasternak I use Xorg mode. Maybe you can get IntelliJ to work for you in Xorg mode too?
|
|
so maybe it's a wayland-only problem, but still |
|
It would be great if there was a way to debug further and see the difference is when X is used vs Wayland. It may be down to IntelliJ rendering differently when on X vs Wayland, and then one of those is hitting this black screen bug. I guess the black screen is somewhere between Qemu, and ANGLE ? |
|
But without gpu acceleration it works ok |
|
@tpasternak Xwayland support with virgl has always been busted, it's not new with this ticket. I say Xwayland because the only programs I see that exhibit this behaviour are ones that are native X apps; native Wayland apps seem to work fine. |
|
ok, thank you! |
|
In case it wasn't clear to anyone else, you can disable GPU acceleration by switching the Emulated Display Card from I was trying to run Fedora 39 Silverblue. |
|
As per @tpasternak's comment, Fedora 39 works fine with mesa-libGL 23.3:
|
|
Hopefully someone will come on here and update whether this works on Ubuntu (e.g. with the oibaf PPA) as well. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
After i upgraded macos ventura to macos Sonoma 14.0 after booting the kali linux and showing this error message EMU exited from an error: GL_ARB_clear_texture
Configuration
The text was updated successfully, but these errors were encountered: