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

bug: config.lib.nixGL.wrap leads to missing Chromium extensions #6608

Open
2 tasks done
DocBrown101 opened this issue Mar 12, 2025 · 9 comments · May be fixed by #6632
Open
2 tasks done

bug: config.lib.nixGL.wrap leads to missing Chromium extensions #6608

DocBrown101 opened this issue Mar 12, 2025 · 9 comments · May be fixed by #6632
Assignees
Labels
bug triage Issues or feature request that have not been triaged yet

Comments

@DocBrown101
Copy link

Are you following the right branch?

  • My Nixpkgs and Home Manager versions are in sync

Is there an existing issue for this?

  • I have searched the existing issues

Issue description

There seems to have been a similar error in #6016.

Here is an example configuration:

programs.chromium = {
    enable = true;
    package = config.lib.nixGL.wrap pkgs.brave;
    extensions = [
      "nngceckbapebfimnlniiiahkandclblb" # Bitwarden Passwortmanager
      "eimadpbcbfnmbkopoojfekhnkhdbieeh" # Dark Reader
    ];
  };

Workaround: remove config.lib.nixGL.wrap from programs.chromium.package to get back the defined extensions.

Maintainer CC

@Smona

System information

- system: `"x86_64-linux"`
 - host os: `Linux 6.11.0-19-generic, Linux Mint, 22.1 (Xia), nobuild`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.26.2`
 - channels(root): `"nixpkgs"`
 - nixpkgs: `/nix/store/ldwapm29wjwan94c9nqjv57jssqrs0rh-nixpkgs/nixpkgs`
@DocBrown101 DocBrown101 added bug triage Issues or feature request that have not been triaged yet labels Mar 12, 2025
@Smona
Copy link
Contributor

Smona commented Mar 12, 2025

Hmm it's not immediately obvious to me how the wrapper would cause this. Do the files in External Extensions in the config dir end up being generated?

@DocBrown101
Copy link
Author

What is the easiest way to check this?

@Smona
Copy link
Contributor

Smona commented Mar 12, 2025

looks like they should be in ~/.config/<chromium_or_brave_or_similar>.

@DocBrown101
Copy link
Author

Without nixGL.wrap, the extensions are located in this path:
~/.config/BraveSoftware/Brave-Browser/External Extensions

With nixGL.wrap the folder “External Extensions” does not exist at all.

@DocBrown101
Copy link
Author

Hello @Smona, could it possibly be because the name cannot be determined correctly and therefore the path is no longer correct?

Image

@Smona
Copy link
Contributor

Smona commented Mar 14, 2025

@DocBrown101 great find! that could absolutely be the issue. Do the files end up in a ~/.config/nixGL-brave directory?

@DocBrown101
Copy link
Author

Bingo!

Image

@Smona
Copy link
Contributor

Smona commented Mar 14, 2025

I don't have time to test at the moment, but could you give #6632 a try?

@Smona Smona linked a pull request Mar 14, 2025 that will close this issue
6 tasks
@DocBrown101
Copy link
Author

I would like to test this, but so far I have never had to. Are there any instructions on what I need to do to test this pull request?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug triage Issues or feature request that have not been triaged yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants