https://bugs.kde.org/show_bug.cgi?id=464590
--- Comment #4 from Guillaume Castagnino <casta+...@xwing.info> --- (In reply to Fushan Wen from comment #3) > The patch looks sane, would you like to create a merge request? Honestly, I do not think that’s the correct fix. It hides the crash, but I assume there is some flaw before this somewhere in the logic. In this case, we may fall under the case where the monitor is already primary but still disabled (here: https://invent.kde.org/plasma/libkscreen/-/blob/master/src/setconfigoperation.cpp#L175) . But is this not a race condition? Shouldn’t the screen be already woken-up when entering this code? With my patch, you may end with no primary at all, or multiple primary when exiting fixPrimaryOutput(). So I think there is something better to do than this patch that is just hiding things. The only purpose of this patch was in fact to narrow down the crash location and workaround until we get a proper fix :) -- You are receiving this mail because: You are watching all bug changes.
