bug: firefox crashes attempting to use non-default profile

[andar1an]

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

When trying to use a secondary (likely any subsequent) firefox profile configured with home-manager, firefox crashes.

Error:

AdapterDeviceID: 0x9b41
AdapterDriverVendor: mesa/iris
AdapterDriverVersion: 23.1.9.0
AdapterVendorID: 0x8086
AvailablePageFile: 12270559232
AvailablePhysicalMemory: 6238195712
AvailableSwapMemory: 18038820864
AvailableVirtualMemory: 10067980288
BackgroundTaskMode: 0
BuildID: 20231221041616
CrashTime: 1704471697
DOMFissionEnabled: 1
DOMIPCEnabled: 1
DesktopEnvironment: kde
EventLoopNestingLevel: 1
GraphicsCriticalError: |[0][GFX1-]: vaapitest: ERROR (t=0.363659) |[1][GFX1-]: vaapitest: VA-API test failed: failed to initialise VAAPI connection.
 (t=0.363659)
GraphicsNumActiveRenderers: 1
GraphicsNumRenderers: 1
HeadlessMode: 0
InstallTime: 1704471695
IsWayland: 1
Notes: FP(D00-L1000-W0000000-T010) WR? WR+ EGL? EGL- GL Context? GL Context+
ProductID: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
ProductName: Firefox
ReleaseChannel: default
SafeMode: 0
StartupCrash: 1
StartupTime: 1704471695
SubmittedFrom: Client
Throttleable: 1
TotalPageFile: 34439561216
TotalPhysicalMemory: 16400740352
UptimeTS: 2.48464449
Vendor: Mozilla
Version: 121.0
XPCOMSpinEventLoopStack: default: AppWindow::ShowModal
This report also contains technical information about the state of the application when it crashed.

Rough Code:

 programs.firefox = {
   profiles = {
      profile0 = {
        isDefault = true;
        id = 0;
        path = "profiles/profile0";
        };
      profile1 = {
        id = 1;
        path = "profiles/profile1";
        };
    };
};

Maintainer CC

@rycee @kira-bruneau

System information

- system: `"x86_64-linux"`
 - host os: `Linux 6.1.69, NixOS, 24.05 (Uakari), 24.05.20240102.bd645e8`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - channels(stephen): `""`
 - channels(root): `"nixos-23.05"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

[andar1an]

I have not actually tested without a nested profile path, will try that now.

Update: No change. Same crash.

[andar1an]

Could Policies being applied generally instead of per profile be problematic?

[andar1an]

Could this be due to firefox multi install profile settings being required?

e.g.

[Install4F96D1932A9F858E]
Default=profile1
Locked=1

[rbreslow]

This has always happened for me @andar1an. One of those things I never tried to dig into.

Interestingly enough, if I launch via CLI with the explicit path firefox --profile ~/.mozilla/firefox/my-special-profile it works. But firefox --profile my-special-profile yields profile not found.

[andar1an]

I am not using this at moment, but I think that it may be related to a folder not existing, or Installatuon field not being in configuration file based on messing with config using bash. I bumped into this there, and when I created the folder I may have needed to populate it. It was a few weeks ago so I don't remember completely.

[rbreslow]

Whatever it is, I'd definitely say it's a bug. I'd expect the home-manager config to "just work."

[andar1an]

I agree it should be considered a bug, but that is beauty of iteration. Baby steps. I am personally not able to contribute, but I think what I mentioned above could help.

[div72]

https://github.com/nix-community/home-manager/issues/3117#issuecomment-1716921180

[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.

[andar1an]

Closing - Stale