09:29 <n3ph> just went on an upgrade today and while emerge hit a full system crash to shutoff.

09:30 <n3ph> last package merged was gegl-0.4.62

09:30 <n3ph> I am currently on mesa-25.1.1 from gentoo upstream

09:31 <n3ph> kernel is 6.14.4_p1

09:32 <n3ph> I am strating sway via greetd which now directly segfaults with `00:00:00.027 [ERROR] [wlr] [EGL] command: eglQueryDeviceStringEXT, error: EGL_BAD_PARAMETER (0x300c), message: "eglQueryDeviceStringEXT"`

09:33 <n3ph> first I thought it might be related to gegl and went back to 0.4.58, but it didn't

09:35 <n3ph> I realized, I had sys-kernel/asahi-sources 6.14.6_p1 laying around and thought it might have been build against that and as I am still running 6.14.4_p1, that could explain it, but removing sys-kernel/asahi-sources 6.14.6_p1 and rebuilding gegl (both versions) doesn't help either

09:35 <n3ph> I've tried all on mesa 25.1.0-r100 as well with no luck

09:36 <n3ph> TBH, I don't know any further.. Any help appreciated..

09:37 <n3ph> The full crash to shutoff wonders me the most

10:05 <chadmed> n3ph: can you -auvDN @world from a tty?

10:12 <n3ph> chadmed: I did - WDYM?

10:13 <n3ph> to clarify, I was invoking emerge world when I encountered this

10:16 <n3ph> here's current `emerge -pDNu @world` https://bpa.st/VVZA

10:16 <n3ph> I've removed virglrenderer to test on mesa 25.1.1

10:16 <n3ph> the rest is outstanding upgrades not finished due to the crash

10:18 <n3ph> ATM I've booted 6.14.2-p1 not fitting with mesa and falling back to SW rendering - but at least I can get sway starting that way

10:41 <chadmed> yeah i have no idea either. the kernel shouldnt matter because the uapi is stable now...

10:41 <chadmed> sounds like libdrm or something maybe? idk

10:50 <n3ph> chadmed: haven't touched libdrm for a while: https://bpa.st/PKUA

11:15 <jannau> n3ph: what does eglinfo report (on 6.14.4 or later)? full info on the installed mesa?

20:12 <n3ph> jannau: I can't redirect the output of eglinfo. I tried moving stdout to stderr but get it unbuffered, but the file I redirect to keeps being empty. I tried it with every expression I know (&>, 1>&2, &| .. ect).

20:12 <n3ph> It already segfaults before I see any backend info

20:12 <n3ph> the output is quite short, just a couple supported symbols

20:14 <n3ph> But here is a full output under 6.14.2: bpa.st/DNPQ

20:14 <n3ph> It's basically the same output just without the segfault after GBM platform

20:16 <n3ph> So regarding your question (full info on the installed mesa), no info about mesa at all.

20:23 <jannau> I meant the eix output like in https://bpa.st/VVZA for libdrm

20:36 <n3ph> m) https://bpa.st/Q7WA

20:42 <jannau> anything in the kernel log after eglinfo segfault?

20:44 <n3ph> no, nothing

20:48 <n3ph> But why can I get a full `eglinfo` output under 6.14.2 (https://bpa.st/DNPQ) but a segfault with 6.14.4?

21:00 <jannau> probably because on 6.14.2 the crashing place is not reached due to the incompatible asahi uapi