Open luiswirth opened 5 months ago
Hi, sometimes this also happens to me, and it's most likely due to monitors layout changing (in your case, internal monitor going off). I think this happens because the plugin by default tries to remember layouts and workspaces, but it's not easy to track when the workspace change is triggered by the user or by hyprland.
I'll take a look into this. In the meantime, if vdeskreset doesn't work, you could try specify rememberlayout = none
in the configuration options
PS. How are you switching off your monitor? Do you use something like kanshi?
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 causes a bug, where there is a weird workspace setup.
Setting rememberlayout = none
still makes the problem happen. To only apparently sure way to have a working setup, is to start hyprland with all monitors I want plugged in (for now just one addiontal one) and then not messing with the monitor layout.
Can you check if this happens on hyprland 0.39.1 as well?
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.
I see. I use arch, so unfortunately cannot really help there. Also, you forgot to say which tool you're using to shutdown/ power up the monitors
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 ...
Yeah, this happens every now and then unfortunately. Just yesterday night I opened this PR on another small tool which is using hyprctl directly. Until hyprland stabilises, it might be a better solution IMO.
Anyway, please also attach hyprland logs of when this behaviour happens
Hi! The kanshi problem was fixed upstream. Does this happen with kanshi too? If you can reproduce it, could you attach the hyprland log?
Maybe it was fixed. I don't think I've ever experienced anything like this issue, except possibly when I first installed the plugin, but such things aren't uncommon when tinkering with window settings on my particular NixOS setup. Either restarting a service, logging out, or rebooting solved the issue, I don't recall.
That's good to know! Unfortunately, I think this problem (vdesks going crazy etc) is still present, despite rather unpredictable. One day I'll look into it. Most likely, it will require changes in Hyprland itself to send an event before/after workspaces have been "adjusted", following a monitor connection/disconnection
Hmm, come to think of it I generally keep my monitors on at all times. I will test when I have access to them.
It's remarkable that your first plugin is so good considering the complex nature of the situation. I'm repeating myself but virtual desktops kept me on Plasma until now so I'm very grateful for this project.
Thanks for the kind words. And yes, I also just can't work without this metaphor anymore :)
hey, just curious. Is this still happening? I feel like on aquamarine this stuff kind of fixed itsef (?)
I don't use this plugin anymore, since it wasn't working for me at the time.
I don't know what exactly causes it, but sometimes the virtual desktops become completly broken... The only way to remedy this I found is to restart Hyprland and to hope to not trigger it again.
Based on the workspace indicators on my waybar, I can tell, that this happens whenever both workspaces representing a single desk (e.g. workspaces 1,2 for desk 1) are somehow one the same monitor (according to waybar). Then I get very glitchy behavior. I get unrendered some unrendered windows. Also just the act of moving the mouse from one monitor to the other makes the workspaces somehow swap between monitors and I can't get to the other workspace anymore... It's very weird.
Running
hyprctl reload
orhyprctl dispatch vdeskreset
cannot fix this.One thing that might play a role is, the fact, that when starting hyprland I first deactivate the internal monitor (monitor 3 if you want so).