How do you manage to enable your Gnome extensions

[Grraahaam]

Hi there @Electrostasy !

Hope you're doing well? Great work here, I'm wondering if your Gnome extensions are enabled declaratively through your code or are you enabling them manually?

programs.dconf.profiles.user.databases = [{
    settings = with lib.gvariant; {
      "org/gnome/shell".enabled-extensions =
        builtins.map
          (x: x.extensionUuid)
          (lib.filter (p: p ? extensionUuid) config.environment.systemPackages)
        # For extensions packaged together with `gnome-shell-extensions`, but
        # that do not have an individual uuid and package entry listed in nixpkgs'
        # pkgs/desktops/gnome/extensions/extensionRenames.nix file:
        ++ [
          "[email protected]"
          "[email protected]"
        ];
   };
]};

I'm running a simpler structure but still using the same concept behind, but my extensions don't enable.. (or at least not all, like dash-to-dock)

I'm not using flake, nor home-manager (yet), as I wanted to know if I could keep it easy without adding too many modules.

Cheers!

[Electrostasy]

Hi,

The gnome extensions are enabled declaratively, I do not have to enable them manually.

My extensions are already enabled when booting (fresh installs included), however, I did have issues with them not enabling after logging out and logging back in after a NixOS activation (for example if I declaratively enabled or disabled extensions, the changes would not take effect until I rebooted to the new generation). On normal distros, users are advised to log out and log back in for the dconf changes to take effect (at least on the Wayland session, it should enable extensions, so I thought something was wrong here).

I noticed that the NixOS dconf module does not update the dconf database in /etc/dconf on activation (it still points to the old dconf database after nixos-rebuild), so logging out and logging back in does not enable extensions.

To remedy the above, I have this activation script to ensure the database is updated on the running system, so I think you should try adding that to your configuration and see if it helps.

[Electrostasy]

That being said, this is just a workaround, I'm not entirely sure why the path was not updating on activation. But it is what solved it for me.

[Grraahaam]

Thanks for your help, and quick answer!

I've managed to finally make it work, the config was OK, but I had to reset the dconf extensions related keys, it's all explained here and there.

I've also been able to reflect my changes right after a logout/in with the above mentioned fix.

[Electrostasy]

Happy to help.

The dconf keys thing I was not aware of, most of my desktops run stateless (root wiped on every boot) so I assume that is why I did not have to explicitly reset the keys. Nice work.