diff options
author | 2018-10-20 12:34:39 +1000 | |
---|---|---|
committer | 2018-10-20 13:07:33 +1000 | |
commit | ed771a6a6e147d667c3791f897ad62e307b260fe (patch) | |
tree | 04892c5c4a3002c378439bf0ca160a6dbdc6919b /swaymsg | |
parent | Merge pull request #2872 from RyanDwyer/cursor-rebase (diff) | |
download | sway-ed771a6a6e147d667c3791f897ad62e307b260fe.tar.gz sway-ed771a6a6e147d667c3791f897ad62e307b260fe.tar.zst sway-ed771a6a6e147d667c3791f897ad62e307b260fe.zip |
Fix crash when view unmaps while no outputs connected
When a view unmaps, we call workspace_consider_destroy. This function
assumed the workspace would always have an output, but this is not the
case when hotplugged down to zero. The function now handles this and
allows itself to be destroyed when there is no output.
This means that workspace_begin_destroy must remove the workspace from
the root->saved_workspaces list to avoid an eventual dangling pointer,
so it does that now.
Lastly, when an output is plugged in again and it has to create a new
initial workspace for it, we must emit the workspace::init IPC event
otherwise swaybar shows no workspaces at all. I guess when you start
sway, swaybar is started after the workspace has been created which is
why this hasn't been needed earlier.
Diffstat (limited to 'swaymsg')
0 files changed, 0 insertions, 0 deletions