Hi, all!
I have finally fixed all your reported issues with Qt 6.11.0. Could you please do the final check of the builds? I would like to update our Qt6 builds to use Qt 6.11.0 next week, since our branches have diverged quite a bit 
The packages also include the touch refactoring changes, which were merged yesterday
Notes:
- The palette docker has been fixed. There was a regression in Qt 6.9.0. I’ve fixed our copy of Qt and added a workaround for distribution packages.
- Cursor issues when using tablet on Wayland: fixed in our version of Qt. I plan to send these patches upstream. Until then, the distribution builds will have problems on Wayland (NB: that is not fixable at Krita’s level, it is a bug in Qt).
- Fixed most of the MDI issues on Wayland:
- Tabbed interface should work perfectly on all compositors
- Subwindow interface will work only when you switch or rearrange subwindows with the menus or shortcuts (like Ctrl+Tab). Dragging windows with the mouse is broken, and broken differently on different compositors
- dragging windows works best on KWin when
General->Don't show window contents while draggingis unckecked. It will just temporarily lockup if you move the cursor too quickly (and accidentally leave the area of the window title). These two MRs for KWin will fix the issue: for mouse, for tablet.
- dragging windows works best on KWin when
Known issues:
-
There is a know issue, which is inherent to Wayland. If you paint and, while pressing the pen to the surface, your cursor accidentally temporary leaves the bounds of the canvas, the stroke will be stopped. On some compositors it may also cause mess on the rest of your desktop, since Wayland stipulates the compositor to send “Tablet Press” even to every single application you hover over
- there is long discussion about that at the Wayland level: link
- KWin plans to implement that in the next release even though it is not in the protocol: for mouse, for tablet