In reply to @donskifarrell:matrix.org
I've suddenly ran into an issue with my local build tho. My boot sequence gets stuck on [ ok ] Started Display Manager and doesn't load gdm.
This is using the most recent pull from github branch, yet I was successful in building and running it from a previous pull around 10th Oct.

actually if it builds fine for you it is probably how i am using it in my configuration- i have a member of inputs in my system flake.nix pointing to github:NixOS/nixpkgs/gnome, and then in my modules i've added:

{
  nixpkgs.overlays = [
    (self: super: {
      gnome = inp.gnomeNixpkgs.legacyPackages.x86_64-linux.gnome;
    })
  ];
}

actually if it builds fine for you it is probably how i am using it in my configuration- i have a member of inputscalled gnomeNixpkgs in my system flake.nix pointing to github:NixOS/nixpkgs/gnome, and then in my modules i've added:

{
  nixpkgs.overlays = [
    (self: super: {
      gnome = gnomeNixpkgs.legacyPackages.x86_64-linux.gnome;
    })
  ];
}

In reply to @donskifarrell:matrix.org
That looks fine. I was using that way initially then I had an issue with mismatched GLIBC versions, so I made the gnome branch the primary nixpkgs url (which triggered a massive rebuild) in order to resolve it.
I haven't experienced the tracker issue yet but there were some related convos earlier in the chat if you scroll back.
The only similar issue to yours was with libsecret, which was caused by 100% CPU usage. I kept restarting the builds and it eventually got there

In reply to @shortcutz:matrix.org
by any chances was the CPU usage error related to a TIMEOUT [...] signal 15 sigterm message? hadn't seen that before this build