https://bugs.kde.org/show_bug.cgi?id=372963
--- Comment #6 from Jan-Matthias Braun <jan_br...@gmx.net> --- Okay. Looks like the m_screenPool-Numbering is inconsistend with the m_desktopViewforId-Numbering. THerefore, in primaryOutputChanged, the id for the old as well as the new primary DesktopView is == 0 and no swap takes place! In general, desktopForScreen does not return the correct DesktopView. This should be the reason, why the assert fails. When patching desktopForScreen, the Q_ASSERT does not explode. When using the patched desktopForScreen insted of the m_screenPool in primaryOutputChanged, then it does not explode, too, and the primary desktop is at the right place. I will attach the patch now. -- You are receiving this mail because: You are watching all bug changes.
