https://bugs.documentfoundation.org/show_bug.cgi?id=148019
--- Comment #10 from Callegar <[email protected]> --- @Michael Weghorn Thanks for the clarification. Let me try to summarize to see if I am getting this right; - it looks like the issue with Qt that is troubling LibO with the Qt and kf VCLs is fixed in Qt6, but not in Qt5, so everything is fine on the Qt6 and kf6 VCLs, but not on the Qt5 and kf5 ones; - it might be the case that there is already a Qt5 patch floating around, because the issue is not present in Debian derivatives (that builds Qt5 from the Qt sources + its own huge set of patches), but is present in Arch derivatives (that build Qt5 from the KDE sources). The development model of Qt5 results in patches being only applied downstream with the chance that they get lost. - it might also be the case that the issue is not visible in debian derivatives, since they may be stuck at plasma5 and the issue is only triggered in plasma6. Regarding the last point, I wonder if it is possible to test the Qt5 VCL on a non debian system with a non KDE wayland windows manager, to see if the issue is present or not there. This would help clarify if it is plasma6 to trigger the issue. -- You are receiving this mail because: You are the assignee for the bug.
