bug: programs.firefox settings don't apply when package = pkgs.firefox-devedition

[ivandimitrov8080]

Are you following the right branch?

• [X] My Nixpkgs and Home Manager versions are in sync

Is there an existing issue for this?

• [X] I have searched the existing issues

Issue description

I just spent several hours trying to configure Firefox because I couldn't get it to work with the package that I had picked. After successfully running out of options I changed the package to just pkgs.firefox and it started working as expected.

There are many errors around this so you can choose which one you want to look at.

For example the profiles don't work - when you start ff with a home-manager profile it tells you that the profile sux and it's not gonna load it and start.

Policies don't work - they just don't get applied.

Settings? forget about it.

Nothing works with that package.

Maintainer CC

No response

System information

- system: `"x86_64-linux"`
 - host os: `Linux 6.1.63, NixOS, 24.05 (Uakari), 24.05.20231124.8b8c940`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - channels(root): `"home-manager-23.05.tar.gz, nixos-23.05"`
 - channels(ivand): `"nixos"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

[AlecsFerra]

I'm having the same issue with my custom firefox-unwrapped, some times ago the extraPolicies were applied but right now they are just ignored for some reason

[lelgenio]

I stumbled upon the fact that, for devedition, you need to prefix the profile name(or path?) with dev-edition for it to work:

programs.firefox = {
  package = pkgs.firefox-devedition;
  profiles = {
    dev-edition-main = {
      isDefault = true;
      settings = {
        "browser.aboutConfig.showWarning" = false;
      };
    };
  };
};

[gepbird]

For me naming the profile dev-edition-main didn't work (even with applying isDefault = true on the profile), but naming it dev-edition-default works.

programs.firefox = {
  enable = true;
  package = pkgs.firefox-devedition;
  profiles = {
    dev-edition-default = {
      settings = {
        "browser.aboutConfig.showWarning" = false;
      };
    };
  };
};

Some side notes: while testing this, I always deleted ~/.mozilla and made sure nix would correctly symlink home manager built files to ~/.mozilla by rebuilding with firefox disabled, then rebuilding with firefox enabled. This way, when firefox didn't like the config, instead of ignoring it and loading the previous/default profile, it crashed with the error "Your Firefox profile cannot be loaded. It may be missing or inaccessible."

[stale[bot]]

Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

• If this is resolved, please consider closing it so that the maintainers know not to focus on this.
• If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough.
• If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

• If you are also experiencing this issue, please add details of your situation to help with the debugging process.
• If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.