-
-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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.2 #118753
mesa: 21.0.1 -> 21.0.2 #118753
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems OK, but I haven't tried running against the drivers.
Result of 699 packages marked as broken and skipped:
1 package failed to build:8284 packages skipped due to time constraints:
38 packages built successfully:
2 suggestions:
Note that build failures may predate this PR, and could be nondeterministic or hardware dependent. |
My initial testing was fine and I can successfully launch applications and X11 but I just noticed that I cannot launch Here's the output for starting Signal-Desktop via Cage:
@vcunat do you mind if I just revert this commit for now or should we wait and see if we find a solution before this lands in |
OK, it sounds best to revert until we know more. |
BTW, as of current |
This reverts commit e3bc983. It caused segmentation faults for at least Sway and XWayland with the iris driver, see [0]. The cause and impact of this regression is still unknown but let's revert it until we know more. [0]: #118753 (comment)
Thanks for your fast reply, I've just reverted it in 25ae1fd.
Wow, nice :) I didn't expect that the amount of rebuilds would drop that significantly, that's awesome! |
|
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]: 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
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)