Cannot use OpenGL on Hyprland with Asahi Linux and Mesa 25.2

[oiiiiiiii]

Hyprland version

Hyprland 0.50.1 built from branch at commit 4e242d0 ([gha] Nix: update inputs).
Date: Sat Jul 19 21:37:06 2025
Tag: v0.50.1, commits: 6291
built against:
aquamarine 0.9.2
hyprlang 0.6.3
hyprutils 0.8.1
hyprcursor 0.1.12
hyprgraphics 0.1.5

Regression

No

Describe the bug

Apparently, since the update to Mesa 25.2, the GPU acceleration cannot properly be used on hyprland anymore, or at least OpenGL. When I start an app that usually makes use of the GPU (like wezterm) I get these warnings:

libEGL warning: failed to get driver name for fd -1

libEGL warning: MESA-LOADER: failed to retrieve device information

libEGL warning: failed to get driver name for fd -1

And judging by the performance the GPU is not used, but CPU rendering. Scrolling in Firefox is pretty laggy for example. When switching to Gnome this warning does not appear, and performance is much better.

Some more details can be found in this commen from a previous discussion, but since the discussion turned out to be about something else I open a new discussion here. I'm not sure I understand everything that was described there, so I thought I better link it instead of saying something wrong.

Reproduction steps

1. Install Asahi Linux with Mesa 25.2 version
2. Try to use an application using OpenGL on hyprland

System info and config

systeminfo.txt
hyprland.log
dmesg.log

Config: default config, but added

 debug {
    disable_logs = false
}

and autogenerated = 0

I hope I didn't make a mistake with the logs, for example I had to use sudo dmesg -w > ~/dmesg.log & instead of dmesg -w > ~/dmesg.log & becaus it would fail otherwise for some reason. If anything else is needed just ping me.

[vaxerski]

check #11087, does it work

[P-AS]

No, it's a new issue.

$ hyprland -v
Hyprland 0.50.0 built from branch rendernode at commit 843351e403e666d59464db51c17e9806739447cf  (MesaDRM: use the m_drmRenderNodeFD if it exist).
Date: Fri Aug 1 19:35:11 2025
Tag: , commits: 6334
built against:
 aquamarine 0.9.2
 hyprlang 0.6.4
 hyprutils 0.8.2
 hyprcursor 0.1.13
 hyprgraphics 0.1.5


no flags were set

$ kitty
libEGL warning: failed to get driver name for fd -1

libEGL warning: MESA-LOADER: failed to retrieve device information

libEGL warning: failed to get driver name for fd -1

[gulafaran]

got a hyprland.log from that session?

[P-AS]

(Ignore the previous one)
hyprland.log

[gulafaran]

(Ignore the previous one) hyprland.log

ok pushed a change that im not sure if it will help but, there is another one in your logs that im not liking. the AQ renderer uses a different node compared to hypr renderer. il look into that tomorrow

[P-AS]

Seems to work fine now.
hyprland2.log

[amirsalarsafaei]

I have the same issue and it persists even with the latest commits:

Hyprland 0.50.0 built from branch  at commit 50a242f16abfc49efc6f89ea9cd14a3544888a25  ().
Date: 2025-08-21
Tag: v0.50.0, commits:
built against:
 aquamarine 0.9.2
 hyprlang 0.6.3
 hyprutils 0.8.2
 hyprcursor 0.1.13
 hyprgraphics 0.1.5


no flags were set

[gulafaran]

I have the same issue and it persists even with the latest commits:

Hyprland 0.50.0 built from branch  at commit 50a242f16abfc49efc6f89ea9cd14a3544888a25  ().
Date: 2025-08-21
Tag: v0.50.0, commits:
built against:
 aquamarine 0.9.2
 hyprlang 0.6.3
 hyprutils 0.8.2
 hyprcursor 0.1.13
 hyprgraphics 0.1.5


no flags were set

#11087 its not merged yet

[amirsalarsafaei]

#11087 its not merged yet
@gulafaran Thanks for the reply.

I tried your commit as well, but had no luck.

version:

Hyprland 0.50.0 built from branch  at commit 43f67a270c5b85b2f33866aff258ca4c0890f6e2  ().
Date: 2025-08-20
Tag: v0.50.0, commits:
built against:
 aquamarine 0.9.3
 hyprlang 0.6.3
 hyprutils 0.8.3
 hyprcursor 0.1.13
 hyprgraphics 0.1.5


no flags were set

I believe I have no hardware acceleration. Everything is choppy. Hyprlock does not work and etc...
I've attached some journal logs(greped), and my hyprlog, I don't believe my hyprland conf is relevant but let me know if you need it. Let me now what else I can help with. Best of luck. I might just rollback...

journal-uwsm.log
journal-egl.log
journal-wayland.log
hyprland.log
dmesg.log