https://bugs.kde.org/show_bug.cgi?id=520884
mokou <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mokou.kde.undivided585@pass | |mail.net --- Comment #3 from mokou <[email protected]> --- I'm suffering this on Krita 6.0.3, running on Arch/Omarchy (Hyprland) w/ native Wayland (QT_QPA_PLATFORM=wayland). With two images open, clicking a document tab (or Ctrl+Tab) won't update the canvas; instead, it keeps showing the previously-active document's image. The layers panel, history, and other dockers DO update to match the newly-selected document; only the canvas view is stale. Interacting with the canvas (clicking/painting) re-activates the previously-focused document. Steps to reproduce: 1. Launch Krita on native Wayland with GPU/OpenGL canvas enabled. 2. Open two images. 3. Switch between the document tabs. 4. Bug occurs. Detailed environment information: - Compositor: Hyprland 0.56.2 (Wayland), Arch Linux (Omarchy), kernel 7.1.9-arch1-2 - Krita: 6.0.3-2 (Arch), Qt 6.11.2 (qt6-base), QT_QPA_PLATFORM=wayland - GPU: AMD Radeon RX 9070 (Navi 48 / RDNA4) + Intel Meteor Lake-P iGPU (hybrid graphics) - Canvas: default OpenGL (canvasState=OPENGL_SUCCESS, useOpenGLTextureBuffer=true) - Hyprland rendering already at "safe" values, i.e. not the cause: render:direct_scanout=0, render:new_render_scheduling=false Running the same build with QT_QPA_PLATFORM=xcb (XWayland) makes tab-switching work, so Wayland plus GPU-canvas path is where it breaks. Disabling either Wayland or GPU acceleration "fixes" the bug. -- You are receiving this mail because: You are watching all bug changes.
