https://bugs.kde.org/show_bug.cgi?id=489072
--- Comment #19 from Kacper Koniuszy <kde.eardrum...@aleeas.com> ---
Arsen, you mentioned under bug 473020 that this might have started happening
with a Qt upgrade to 6.7.2.
This is interesting because 6.7.2 introduced a commit which changed this
statement in handleScreensChanged:
if (newScreen == mLastReportedScreen)
to this:
if (newScreen->screen() == window()->screen())
https://invent.kde.org/qt/qt/qtwayland/-/commit/9838bf42fe28311d7de96f74ae99d014e943b8e0
Could this have caused a regression? Before this change, the method would
return early if both newScreen and mLastReportedScreen were null (but only one
of them being null would cause issues). After this change, the method will
fail if newScreen is null.
I'll try to test it with this commit reverted.
--
You are receiving this mail because:
You are watching all bug changes.
