Skip to content

EMU exited from an error: GL_ARB_clear_texture #5749

Open

Description

@aceaf

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

  • UTM Version: 4.3.5
  • macOS Version: Sonoma 14.0
  • Mac Chip (Intel, M1, ...): M2

Activity

  1. zuzzurro commented on Sep 28, 2023

    @zuzzurro

    Same here, but only after also upgrading to Fedora 39 beta (I'm pretty sure I used Fedora 38 after the Sonoma upgrade).

    • UTM Version: 4.3.5 and 4.4.1
    • macOS Version: Sonoma 14.0
    • Linux version: Fedora 39 beta (with kernel 6.5.5)
  2. osy commented on Sep 29, 2023

    @osy
    Contributor

    Can either or both of your provide a debug.log?

  3. azagulyaev commented on Sep 29, 2023

    @azagulyaev

    Maybe this can help:
    Once I try to change the Display resolution, I got in my debug log:

    2023-09-29 23:50:18.984 UTM[34759:2987438] Debug JSON recieved <- { data = { offset = 1; "qom-path" = "/machine/unattached/device[7]"; }; event = "RTC_CHANGE"; timestamp = { microseconds = 984191; seconds = 1696020618; }; } 2023-09-29 23:50:22.600 UTM[34759:2988263] Debug JSON send -> { execute = "query-mice"; } 2023-09-29 23:50:22.603 UTM[34759:2988264] Debug JSON recieved <- { return = ( { absolute = 0; current = 0; index = 2; name = "QEMU HID Mouse"; }, { absolute = 1; current = 1; index = 1; name = "QEMU HID Tablet"; } ); } 2023-09-29 23:50:22.605 UTM[34759:2988263] found index:1 absolute:1 2023-09-29 23:50:22.605 UTM[34759:2988263] Debug JSON send -> { arguments = { "command-line" = "mouse_set 1"; }; execute = "human-monitor-command"; } 2023-09-29 23:50:22.606 UTM[34759:2988264] Debug JSON recieved <- { return = ""; } ** Message: 23:50:43.337: main channel: closed 2023-09-29 23:50:43.338 UTM[34759:2987438] Failed to connect to SPICE: (null) 2023-09-29 23:50:43.338 UTM[34759:2987438] Stop operation timeout or force quit 2023-09-29 23:50:43.338 UTM[34759:2988263] Debug JSON send -> { execute = quit; } 2023-09-29 23:50:43.338 UTM[34759:2987438] Exit operation timeout or force quit 2023-09-29 23:50:43.338 UTM[34759:2988263] RPC: Error Domain=com.utmapp.utm Code=-1 "Port is not connected." UserInfo={NSLocalizedDescription=Port is not connected.}

  4. osy commented on Sep 29, 2023

    @osy
    Contributor

    I don't know how that's related to the issue reported here at all?

  5. azagulyaev commented on Sep 29, 2023

    @azagulyaev

    Issue named appears at the screen and VM stops working

  6. osy commented on Sep 29, 2023

    @osy
    Contributor

    I see, please post the entire debug.log

  7. eccramer commented on Sep 30, 2023

    @eccramer

    I am having this problem as well.

    Behavior: After running apt get update and installing all updates, Kali 2023 boots to login, but after entering login creds and hitting enter, VM crashes, and UTM dialog appears with message "QEMU exited from an error: GL_ARB_clear_texture"

    Configuration

    UTM Version: 4.3.5
    macOS Version: Ventura 13.6
    Mac Chip (Intel, M1, ...): M1 (13 inch M1 Macbook Pro 2020)
    

    Debug Log attached, but it does not appear to give much helpful information

    debug.log

  8. osy commented on Sep 30, 2023

    @osy
    Contributor

    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.

  9. added
    crashApplication crashes
    virglvirglrenderer issues
    on Sep 30, 2023
  10. added this to the Future milestone on Sep 30, 2023
  11. eccramer commented on Sep 30, 2023

    @eccramer

    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.

  12. eccramer commented on Oct 1, 2023

    @eccramer

    I was able to sudo apt update without breaking UTM by running the following command

    kali@kali:~$ sudo apt-mark hold mesa-vulkan-drivers libgl1-mesa-dri libglapi-mesa libx11-6 libx11-data
    kali@kali:~$ apt-mark showhold
    libgl1-mesa-dri
    libglapi-mesa
    libx11-6
    libx11-data
    mesa-vulkan-drivers
    

    I'll have to unhold those packages later, but for now this provides a working and fairly up-to-date Kali install in UTM.

  13. wzxu commented on Oct 3, 2023

    @wzxu

    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.
    Using KDE Plasma Wayland session, changing resolution works fine, but it crashes when I launch Vivaldi browser?! (Edit: Firefox as well.)

    Anyway here's my debug.log
    Problem looks to be this:

    2023-10-03 21:19:40,346 DEBUG (null)-/Users/runner/Library/Developer/Xcode/DerivedData/UTM-gnwjeapbifchcjczzvitjgckdhnq/SourcePackages/checkouts/CocoaSpice/Sources/CocoaSpice/CSDisplay.m:207 [CocoaSpice] cs_gl_draw
    No provider of glClearTexSubImageEXT found.  Requires one of:
        GL_EXT_clear_texture
        Desktop OpenGL 4.4
        GL_ARB_clear_texture
    
  14. 3uzbcqje commented on Oct 4, 2023

    @3uzbcqje

    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:

    [evans@archlinux ~]$ grep -oP '2023-10-04.*upgraded \K.*' /var/log/pacman.log
    blas (3.11.0-2 -> 3.11.0-3)
    bluez (5.69-1 -> 5.70-1)
    bluez-libs (5.69-1 -> 5.70-1)
    bolt (0.9.5-1 -> 0.9.6-1)
    btrfs-progs (6.5.1-1 -> 6.5.2-1)
    ca-certificates-mozilla (3.93-1 -> 3.94-1)
    cairomm (1.14.4-1 -> 1.14.5-1)
    coreutils (9.3-1 -> 9.4-1)
    docker (1:24.0.5-1 -> 1:24.0.6-1)
    enchant (2.5.0-1 -> 2.6.0-1)
    gnome-color-manager (3.36.0+r42+g90481514-1 -> 3.36.0+r51+gcf7ee2b5-1)
    gnutls (3.8.1-1 -> 3.8.1-2)
    imagemagick (7.1.1.18-1 -> 7.1.1.19-1)
    lapack (3.11.0-2 -> 3.11.0-3)
    libcups (1:2.4.7-1 -> 1:2.4.7-2)
    libnm (1.44.0-1 -> 1.44.2-1)
    libnvme (1.5-1 -> 1.6-1)
    libpeas (1.36.0-2 -> 1.36.0-3)
    libphonenumber (1:8.13.20-1 -> 1:8.13.22-1)
    libportal (0.7-1 -> 0.7.1-1)
    libx11 (1.8.6-1 -> 1.8.7-1)
    libportal-gtk3 (0.7-1 -> 0.7.1-1)
    libportal-gtk4 (0.7-1 -> 0.7.1-1)
    libvpx (1.13.0-2 -> 1.13.1-1)
    libxpm (3.5.16-1 -> 3.5.17-1)
    python-cryptography (41.0.3-1 -> 41.0.4-1)
    python-fastjsonschema (2.18.0-1 -> 2.18.1-1)
    python-identify (2.5.29-1 -> 2.5.30-1)
    python-wcwidth (0.2.6-1.1 -> 0.2.8-1)
    kmod (30-3 -> 31-1)
    mesa (1:23.1.8-1 -> 1:23.2.1-1)
    nss (3.93-1 -> 3.94-1)
    pinentry (1.2.1-2 -> 1.2.1-3)
    ruby-bundler (2.4.13-1 -> 2.4.20-1)
    sdl2 (2.28.3-1 -> 2.28.4-1)
    vim-runtime (9.0.1882-1 -> 9.0.1976-1)
    vim (9.0.1882-1 -> 9.0.1976-1)
    xdg-desktop-portal (1.16.0-3 -> 1.18.0-2)
    xdg-desktop-portal-gtk (1.14.1-1 -> 1.14.1-3)
    xdg-desktop-portal-gnome (44.2-1 -> 44.2-2)
    

    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...

  15. 24 remaining items

  16. cky commented on Jan 7, 2024

    @cky
    Sponsor

    @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.

  17. cky commented on Jan 7, 2024

    @cky
    Sponsor

    @tpasternak Are you using Wayland mode or X mode? I am using IntelliJ on Fedora 39 just fine.

  18. stuaxo commented on Jan 8, 2024

    @stuaxo

    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.

  19. tpasternak commented on Jan 9, 2024

    @tpasternak

    @cky the default one, in general it works, but some apps (IntelliJ) don't

  20. cky commented on Jan 10, 2024

    @cky
    Sponsor

    @tpasternak I use Xorg mode. Maybe you can get IntelliJ to work for you in Xorg mode too?

    Fleet in virgl
    RustRover in virgl

  21. tpasternak commented on Jan 11, 2024

    @tpasternak

    so maybe it's a wayland-only problem, but still

  22. stuaxo commented on Jan 11, 2024

    @stuaxo

    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 ?

  23. tpasternak commented on Jan 11, 2024

    @tpasternak

    But without gpu acceleration it works ok

  24. cky commented on Jan 11, 2024

    @cky
    Sponsor

    @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.

  25. tpasternak commented on Jan 11, 2024

    @tpasternak

    ok, thank you!

  26. ajs1998 commented on Mar 12, 2024

    @ajs1998

    In case it wasn't clear to anyone else, you can disable GPU acceleration by switching the Emulated Display Card from virtio-gpu-gl-pci to virtio-ramfb. The actual checkbox for "GPU Acceleration Supported" can't be unchecked so you need to change the selected device.

    I was trying to run Fedora 39 Silverblue.

  27. ivanfilhoz commented on Mar 29, 2024

    @ivanfilhoz

    As per @tpasternak's comment, Fedora 39 works fine with mesa-libGL 23.3:

    1. Disable GPU acceleration by switching the display card to virtio-ramfb.
    2. Boot the VM, and run in the terminal:
    sudo dnf update mesa-libGL
    
    1. Ensure the correct version (23.3.x) is installed by running:
    sudo dnf list mesa-libGL
    
    1. Turn off the VM and switch back to virtio-gpu-gl-pci.
  28. stuaxo commented on Apr 4, 2024

    @stuaxo

    Hopefully someone will come on here and update whether this works on Ubuntu (e.g. with the oibaf PPA) as well.

  29. mvysny commented on Jan 15, 2025

    @mvysny

    Intellij can now run in pure Wayland mode: https://blog.jetbrains.com/platform/2024/07/wayland-support-preview-in-2024-2/ . That means that Intellij now works correctly in Ubuntu 24.04+ with virtio-gpu-gl-pci. Xwayland is still busted though: #6968

  30. tamyr3195-create commented on Dec 29, 2025

    @tamyr3195-create

    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

    • UTM Version: 4.3.5

    • macOS Version: Sonoma 14.0

    • Mac Chip (Intel, M1, ...): M2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    crashApplication crashesvirglvirglrenderer issues

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions