Luis Wirth
Luis Wirth
Can confirm, since hyprland v40, kanshi can no longer disable monitors permenantly. Hyprland immediatly reenables it.
I don't think this is related to the issue you mentioned. Since in this issue, the reporter at least gets a wayland error. For me oculante doesn't event try to...
For me oculante is still running under xwayland on hyprland... I don't know why.
Yes I agree, changing layouts does seem to cause this. Also when first having no monitor connected and my internal monitor turned on and then just connecting a 2nd monitor...
I'm having a hard time downgrading on NixOS... Using an old `flake.lock` gives a build error... I will however try to investigate the error further and provide new information.
Usually I do use kanshi, but unfortunatly it doesn't work for hyprland v40, see hyprwm/Hyprland#5978. So instead I currently modify my monitor setup manually using `hyprctl keyword monitor ...`
I don't use this plugin anymore, since it wasn't working for me at the time.
Doesn't this approach of setting the hyprland `follows` destroy the hyprland cachix? It seems that upon switching the configuration, everything gets build locally on my machine, instead of fetching the...
Is this a good method? This at least doesn't invalidate the hyprland cache, by swapping the dependence (plugins follow main hyprland, not the other way around). ```nix hyprland.url = "git+https://github.com/hyprwm/Hyprland?submodules=1&ref=refs/tags/v0.40.0";...
also creating tags for the different hyprland versions, might be good move