Some users might want to destroy the multi backend when a child backend is being destroyed. However, they can't destroy the multi backend if it's already in the process of being destroyed. The destroy signal was changed to be emitted after destroying child backends inmasterbabdd6ccf7
("backend: fix use-after-free when destroying backends"). However, this was done to accomodate for an old "output_remove" event on backends, which has long been dropped in favor of wlr_output.events.destroy. This patch follows the same principle as5d639394f3
("types/output: emit destroy event before destroying global").
parent
7c080c3b60
commit
a82fc4cb8f
Loading…
Reference in new issue