I'm still seeing this on 3.16.0 -- it may be triggered by adding/removing a monitor, but not entirely sure
I'm still seeing this on 3.16.0 -- it may be triggered by adding/removing a monitor, but not entirely sure