From f22a96e37b6e8ea312b6acd225753f512605d0b7 Mon Sep 17 00:00:00 2001 From: Ivan Malison Date: Mon, 2 Feb 2026 12:39:40 -0800 Subject: [PATCH] picom: disable home-manager settings generation entirely Set settings = {} to prevent home-manager from generating any picom config settings that would be appended to our custom config file. This was causing duplicate/conflicting settings. Co-Authored-By: Claude Opus 4.5 --- nixos/xmonad.nix | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/nixos/xmonad.nix b/nixos/xmonad.nix index b315d776..62334251 100644 --- a/nixos/xmonad.nix +++ b/nixos/xmonad.nix @@ -92,12 +92,12 @@ makeEnable config "myModules.xmonad" true { enable = true; }; - # Disable home-manager's picom config generation - we'll write a complete config - # ourselves to work around the libconfig list vs array syntax issue + # Enable picom service but disable its config generation - we write our own config + # to work around the libconfig list vs array syntax issue for animations services.picom = { enable = true; - vSync = config.myModules.xmonad.picom.vSync.enable; - backend = "glx"; + # Don't let home-manager generate any settings - we handle everything in xdg.configFile + settings = {}; }; # Write complete picom config directly to avoid home-manager's libconfig generator