Alessio Molinari

@neelkarma could you check that it works if you manually ask kanshi to re-enable the monitor? For example, in your kanshi config, put something like: ``` profile onlyone { output...

@neelkarma mmh, I can see from the logs that the HDMI monitor is correctly destroyed by Hyprland. This should indeed send the [finished](https://wayland.app/protocols/wlr-output-management-unstable-v1#zwlr_output_manager_v1:event:finished) event. Could you run kanshi with `WAYLAND_DEBUG=1...

Could you guys try now (commit [`2ad0038` (#6136)](https://github.com/hyprwm/Hyprland/pull/6136/commits/2ad003810abacb30fa943aaac5ff793f36562f2a))? I think the problem was that Hyprland was not sending the [done](https://wayland.app/protocols/wlr-output-management-unstable-v1#zwlr_output_manager_v1:event:done) event after the `finished` event. So, kanshi was basically waiting...

As mentioned in the issue thread, it looks like with this I can disable monitor via kanshi, but cannot re-enable it. Probably because of a similar problem. I'll try to...

@vaxerski this is ready to be reviewed

> rest ok, I assume tested and fixes the issue? Yes, a few people reported back and it looks like we can close the issue

This is also happening on Archlinux (or I guess, any distro using `gcc` 14). On Arch, this can be fixed by running: ```bash sudo pacman -S gcc13 CC=/usr/bin/gcc-13 pip install...

Thank you very much for taking the time for this. I was thinking: should we also use pre commit? I can take care of adding this over the weekend

Yes, a git hook. We can use https://pre-commit.com/

Yeah will do it myself! Not in the next days probably, as I'm a little busy with personal stuff, but will try to not forget about this!