-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UTM crash with SIGTRAP QEMU Launcher quits unexpectedly #5761
Comments
I installed a new VM. gdm causes the trouble. lightdm starts GNOME without problems. |
lightdm also crashes UTM, as soon as I change the display resolution in the GNOME settings. Leaving the display resolution unchanged and installing |
Your first crash log seems to be a sandbox error. Did you build UTM from source? |
No. It's on running The first crash occurred on running There were quite a few crash reports in console, and I wasn't sure, which one belonged to the first crash, so I run the app again yesterday evening and attached that crash log. At that time, I'll delete the current app and re-install Please let me know if you need anything else. |
Logs from |
To ease analysing this, I made a new VM to reproduce the issue. You can download it here: https://my.hidrive.com/lnk/29ClHadT Just |
Okay I get the error message "QEMU error: QEMU exited from an error: GL_ARB_clear_texture", is this what you mean? |
Yes. |
Okay you should have mentioned that :) |
Duplicate of #5749 |
Well, I grepped through the crash report. The term "GL_ARB_clear_texture" does not appear there at all. I couldn't be sure, whether this is the same as bug as #5749 and thought, that it's better to let you know and check. |
Okay but next time please mention it and it'll save everyone some time |
Installing the latest package updates (24 packages) on Arch Linux aarm64 prevents the VM from starting
Configuration
Crash log
I am not sure, but suspect this package update to cause the crash:
bolt-0.9.6-1
.QEMULauncher-2023-10-02-203609.ips.zip
debug.log
The text was updated successfully, but these errors were encountered: