I posted this in the Waybar issue tracker already, but the issue only started happening once I switched from Hyprland to SwayFX despite mouse warping being activated on Hyprland, so it seems like related to switching to SwayFX meaning this may be a more relevant place.
When booting Waybar with the terminal, and using the wlr/taskbar module, it will often crash upon clicking one of the open window icons. It works for a while, but after a random amount of time (usually less than a minute) the next click on a taskbar icon will crash waybar. I moved to Sway from Hyprland, and didn't have the same issue with Hyprland, so I'm not quite sure what difference has caused this to start happening.
Below is the output waybar gives on the console when it crashes:
I also have it set in Sway so that my mouse warps to the focused container, could be related to some incorrectly configured click and drag event? After setting mouse_warping to none in ~/.config/sway/config it seems to have stopped, so my best guess is that it's related to sway moving the mouse at the same time the window is activated?
I posted this in the Waybar issue tracker already, but the issue only started happening once I switched from Hyprland to SwayFX despite mouse warping being activated on Hyprland, so it seems like related to switching to SwayFX meaning this may be a more relevant place.
When booting Waybar with the terminal, and using the wlr/taskbar module, it will often crash upon clicking one of the open window icons. It works for a while, but after a random amount of time (usually less than a minute) the next click on a taskbar icon will crash waybar. I moved to Sway from Hyprland, and didn't have the same issue with Hyprland, so I'm not quite sure what difference has caused this to start happening.
Below is the output waybar gives on the console when it crashes:
Currently using Arch
I also have it set in Sway so that my mouse warps to the focused container, could be related to some incorrectly configured click and drag event? After setting
mouse_warpingtononein~/.config/sway/configit seems to have stopped, so my best guess is that it's related to sway moving the mouse at the same time the window is activated?