Skip to content
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

google-chrome: place commandLineArgs after wayland args #189199

Merged
merged 1 commit into from
Sep 1, 2022

Conversation

stefanradziuk
Copy link
Contributor

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 in commandLineArgs 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
  • Built on platform(s)
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
  • Tested, as applicable:
  • Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
  • Tested basic functionality of all binary files (usually in ./result/bin/)
  • 22.11 Release Notes (or backporting 22.05 Release notes)
    • (Package updates) Added a release notes entry if the change is major or breaking
    • (Module updates) Added a release notes entry if the change is significant
    • (Module addition) Added a release notes entry if adding a new NixOS module
    • (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes
  • Fits CONTRIBUTING.md.

cc @wmertens

@wmertens
Copy link
Contributor

wmertens commented Sep 1, 2022

Oh wow I was just wondering why the flag --enable-features=TouchpadOverscrollHistoryNavigation wasn't doing anything 😅

@wmertens wmertens merged commit 1be806f into NixOS:master Sep 1, 2022
@wmertens
Copy link
Contributor

wmertens commented Sep 1, 2022

Actually, since this is needed here, it's also needed on chromium and the other chromium-based browsers, right? @stefanradziuk would you mind updating those as well?

@stefanradziuk
Copy link
Contributor Author

Created #189371. I think it's only chromium that needs an update. Brave already has flags in the correct order. Let me know if I missed anything.

@bobby285271 bobby285271 mentioned this pull request Sep 2, 2022
13 tasks
primeos pushed a commit to primeos/nixpkgs that referenced this pull request Sep 2, 2022
primeos pushed a commit to primeos/nixpkgs that referenced this pull request Sep 2, 2022
RaitoBezarius pushed a commit to RaitoBezarius/nixpkgs that referenced this pull request Sep 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants