https://bugs.kde.org/show_bug.cgi?id=489072
--- Comment #21 from Kacper Koniuszy <kde.eardrum...@aleeas.com> --- I "fixed" it without reverting 9838bf42 by making handleScreensChanged use nullptr as the new QScreen* if newScreen is null: https://raw.githubusercontent.com/kkoniuszy/nixpkgs/0f91836f88521c39b0fa71faf416fccfbbd270b9/pkgs/development/libraries/qt-6/patches/qtwayland-handlescreenschanged-workaround.patch This is just a workaround though. It seems to make it behave similar in this edge case to how it did before that commit, but dereferencing a null newScreen later on would still cause a crash. If it worked for me right now, that's only because window()->screen() was also null in my test case. It's weird that we get a null newScreen, shouldn't a placeholder screen exist already? -- You are receiving this mail because: You are watching all bug changes.
