-
Notifications
You must be signed in to change notification settings - Fork 170
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
SIGSEGV in init on Iris Xe #1538
Comments
Since |
That is totally plausible, I'd be thrilled to demonstrate the same crash with a small C program but I'm not that far in debugging yet. |
The only |
I only had a quick look at this and from what I can tell the |
Not sure if NixOS has a way to get debug symbols for Mesa. I'd personally try building Mesa from source to get better debugging output and be able to try things (and see if the issue applies to the latest Mesa commit). You could also see if |
Hmm. Smithay logs
but eglinfo with those libraries in that same setting (run on tty) says
It does pick up the Iris Xe as a "Device platform". full eglinfo output
|
It certainly needs the gbm platform, so whatever causes |
eglinfo seems to say that even on NixOS systems that work. No idea why. I'm bisecting to find the breakage but the compiles are taking a very long time. |
I bisected this on a faster computer with On that computer, nixpkgs commit NixOS/nixpkgs@ef12b15 "mesa: 24.0.7 -> 24.0.8" is what triggers the bug. Taking the current niri tree and changing its nixpkgs to point to before that, it works; after, just black. I'll continue tomorrow. |
Hi. I'm trying to use niri >v0.1.6 on NixOS 24.05 and Smithay startup is segfaulting in
The call stack is
I have debug output on both sides of EGLDisplay::new and it never returns.
That strdup SIGSEGV is typically caused by passing it a NULL string, but I haven't yet figured out what string that is (gdb isn't getting symbol tables, haven't figured that out).
The text was updated successfully, but these errors were encountered: