Enter infinite loop when surface is destroyed by compositor

[fwsmit]

When a dunst surface is destroyed by the compositor, dunst enters an infinite loop of creating the surface again.
This looks like this in the debug log:

INFO: Destroying layer
WARNING: Monitor 0 doesn't exist, using focused monitor
WARNING: Monitor 0 doesn't exist, using focused monitor
INFO: Destroying layer
WARNING: Monitor 0 doesn't exist, using focused monitor
WARNING: Monitor 0 doesn't exist, using focused monitor
INFO: Destroying layer
WARNING: Monitor 0 doesn't exist, using focused monitor
WARNING: Monitor 0 doesn't exist, using focused monitor

Ref: #851

[fwsmit]

This isn't a big issue anymore, since this shouldn't happen. So it's not a priority.

[bynect]

should this be closed or is it still relevant with wayland?

[fwsmit]

I think it can technically still happen. But it should not happen if the compositor behaves normally