-
-
Notifications
You must be signed in to change notification settings - Fork 15k
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
mesa: 21.0.1 -> 21.0.3 #120325
mesa: 21.0.1 -> 21.0.3 #120325
Conversation
Ok, I can confirm that #119558 (comment) applies here as well. So when using a single Nixpkgs revision for the whole system this will work as expected but at least Problems like this where already caused by glibc updates (#95808) and it seems like we can now add Mesa to that list (which would be bad as we update Mesa much more often). Unfortunately I don't know what caused this regression, if it's avoidable, and if it only affects wlroots-based Wayland compositors or also other Wayland compositors and X11. Not sure what to do about this PR. Should we merge it or not and do we even have a choice? @GrahamcOfBorg eval |
Ok, so my current plan is the following: Wait for the NixOS 21.05 branch-off on May 21st then merge this (likely 21.0.4 by then) into master and merge #119558 a few days/weeks after that (also depending on how it goes). |
Note: The update to Mesa 21.0.2 was reverted (25ae1fd) because it caused major issues with Sway (segfault on startup [0]). This is still the case and might affect all packages that directly depend on "mesa" (for libgbm or libglapi) but it only causes issues when the package depends on a "mesa" version that differs from "mesa.drivers" used for "/run/opengl-driver/". I've noticed this while testing Mesa updates with the NixOS option "hardware.opengl.package" (as usual) instead of rebuilding my whole system (which would work). Unfortunately this can/will likely also cause issues when mixing different channels, using Flakes/Overlays, etc. The cause of this should be similar to [1] ("mesa" updates now cause the same issues that "glibc" updates already do, maybe triggered by certain Mesa changes) and some additional discussions is in [2],[3]. Note: Don't backport this to NixOS 21.05, at least not without careful consideration. [0]: NixOS#118753 (comment) [1]: NixOS#95808 [2]: NixOS#120325 [3]: NixOS#119558
I've updated the commit message to make this more discoverable and to briefly summarize the issues/implications. Edit: Forgot to mention: Launching Sway also works with the following configuration: system.replaceRuntimeDependencies = [
({ original = pkgs.mesa; replacement = (import /srv/nixpkgs-test { }).pkgs.mesa; })
({ original = pkgs.mesa.drivers; replacement = (import /srv/nixpkgs-test { }).pkgs.mesa.drivers; })
];
# Or instead of mesa.drivers: hardware.opengl.package = (import /srv/nixpkgs-test { }).pkgs.mesa.drivers; |
Note: The update to Mesa 21.0.2 was reverted (25ae1fd) because it caused major issues with Sway (segfault on startup [0]). This is still the case and might affect all packages that directly depend on "mesa" (for libgbm or libglapi) but it only causes issues when the package depends on a "mesa" version that differs from "mesa.drivers" used for "/run/opengl-driver/". I've noticed this while testing Mesa updates with the NixOS option "hardware.opengl.package" (as usual) instead of rebuilding my whole system (which would work). Unfortunately this can/will likely also cause issues when mixing different channels, using Flakes/Overlays, etc. The cause of this should be similar to [1] ("mesa" updates now cause the same issues that "glibc" updates already do, maybe triggered by certain Mesa changes) and some additional discussions is in [2],[3]. Note: Don't backport this to NixOS 21.05, at least not without careful consideration. [0]: NixOS#118753 (comment) [1]: NixOS#95808 [2]: NixOS#120325 [3]: NixOS#119558
Note: The update to Mesa 21.0.2 was reverted (25ae1fd) because it caused major issues with Sway (segfault on startup [0]). This is still the case and might affect all packages that directly depend on "mesa" (for libgbm or libglapi) but it only causes issues when the package depends on a "mesa" version that differs from "mesa.drivers" used for "/run/opengl-driver/". I've noticed this while testing Mesa updates with the NixOS option "hardware.opengl.package" (as usual) instead of rebuilding my whole system (which would work). Unfortunately this can/will likely also cause issues when mixing different channels, using Flakes/Overlays, etc. The cause of this should be similar to [1] ("mesa" updates now cause the same issues that "glibc" updates already do, maybe triggered by certain Mesa changes) and some additional discussions is in [2],[3]. Note: Don't backport this to NixOS 21.05, at least not without careful consideration. [0]: #118753 (comment) [1]: #95808 [2]: #120325 [3]: #119558
Motivation for this change
Builds fine but still causes regressions, see #118753 (comment). This time I've tested it using the
r600
driver and Sway doesn't launch either. Given that this wasn't fixed since 20.0.2 it seems like a packaging / Nixpkgs specific problem (I suspected the shader cache could be causing it but removing~/.cache/mesa_shader_cache
doesn't help either). I can hopefully take a look at it later but help is welcome.Unfortunately I'm not getting much output (even with
sway --debug
,LIBGL_DEBUG=verbose
, andMESA_DEBUG=1
) so I might have to analyze the stack trace:Edit: GDB backtrace:
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)