https://bugs.kde.org/show_bug.cgi?id=514229
Zamundaaa <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Latest Commit| |https://invent.kde.org/plas | |ma/kwin/-/commit/c1ce6ef3f0 | |40c047cd29e482237404672ba10 | |8f5 Resolution|--- |FIXED Status|ASSIGNED |RESOLVED --- Comment #7 from Zamundaaa <[email protected]> --- Git commit c1ce6ef3f040c047cd29e482237404672ba108f5 by Xaver Hugl. Committed on 14/01/2026 at 14:18. Pushed by zamundaaa into branch 'master'. compositor: only update output layers in response to Workspace::outputsChanged Processing output changes before workspace gets a chance to create and update logical outputs can cause problems, for example if - you disable an output -> logical output gets removed - some unrelated output changes happen - you enable the output again, and different output layers get assigned than before In that case, Compositor::assignOutputLayers would get called while there's no logical output yet, and thus KWin crashes. Outputs layers can only change in situations where workspace will later emit outputsChanged, so the intermediary actions were unnecessary either way. M +0 -4 src/backends/drm/drm_pipeline.cpp M +0 -1 src/backends/drm/drm_virtual_output.cpp M +0 -4 src/compositor.cpp M +0 -2 src/core/backendoutput.h https://invent.kde.org/plasma/kwin/-/commit/c1ce6ef3f040c047cd29e482237404672ba108f5 -- You are receiving this mail because: You are watching all bug changes.
