https://bugs.kde.org/show_bug.cgi?id=463475

Bernhard Übelacker <bernha...@mailbox.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bernha...@mailbox.org

--- Comment #27 from Bernhard Übelacker <bernha...@mailbox.org> ---
The same crash I reported already in:
https://bugs.kde.org/show_bug.cgi?id=461723

Which led to this Qt bug report:
https://bugreports.qt.io/browse/QTBUG-109226

Unfortunately this change in Qt did not reach the 5.15 branch?
https://code.qt.io/cgit/qt/qtbase.git/commit/src/plugins/platforms/xcb/qxcbwindow.cpp?id=6a3627b6c5aa5109a80024f3d7b0f938504f7ffe

But it made it at least into the Debian package:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025997
https://sources.debian.org/src/qtbase-opensource-src/5.15.10%2Bdfsg-1/debian/patches/qxcbwindow_set_geometry.diff/

But the bad thing is, I still receive this crash with the Debian package
(yesterday with kate).
Therefore this patch is not sufficient.

Other notes:
- This happens for me just for just for maximized windows. As a workaround
having them just near full screen seems avoiding the crash.
- My last crash was with two monitors connected, but one was switched off.
(Monitors of different brand, different size, same resolution.)
- Initially I reported it when doing explicit changes to dual monitor setup,
   but the last crash was when monitor just went to standby and woke up again.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to