Closed maximyurevich closed 1 day ago
I upgraded my cargo build from 33.1 to 33.2 today and now I get this "Bad Event" error in some cases when I bring a window from the scratchpad.
It happens when I use "i3-msg -q '[id="xxx"]' move to workspace current, focus
with an id criteria or any other.
It happen also when I use i3switcher or i3-msg -q scratchpad show
.
The unknown variant 'changed'
error:
I checked for i3 and the 'changed' state is expected:
scratchpad_state (string)::
Whether the window is not in the scratchpad ("none"), freshly moved to
the scratchpad but not yet resized ("fresh") or moved to the scratchpad
and resized ("changed").
The bug comes from the cargo.lock for swayipc-types.
The version used is 1.3.2 but the 'changed' state for the scratchpad was introduced in 1.4.0 in september.
Building without --locked works fine.