google-chrome: place commandLineArgs after wayland args #189199
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of changes
Working around what seems to be a bug in Chrome. I noticed Chrome would only observe
--enable-features=WebUIDarkMode
if it was placed after--enable-features=UseOzonePlatform --ozone-platform=wayland
.I haven't been able to find a relevant upstream issue yet so can't fully confirm the consequences of this bug. It might be possible that users will need to pass some flags before and some flags after the wayland flags to work around some issues. A temporary workaround could be to have users unset
NIXOS_OZONE_WL
and instead put all the args incommandLineArgs
in the necessary order.ungoogled-software/ungoogled-chromium#1778 (comment) seems to describe the same issue, so chances are this also affects other chrom* packages, but I haven't had a chance to test that.
Things done
sandbox = true
set innix.conf
? (See Nix manual)nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)nixos/doc/manual/md-to-db.sh
to update generated release notescc @wmertens