[krita] [Bug 488714] New: Interface flickering under Wayland with any OpenGL acceleration enabled
https://bugs.kde.org/show_bug.cgi?id=488714 Bug ID: 488714 Summary: Interface flickering under Wayland with any OpenGL acceleration enabled Classification: Applications Product: krita Version: 5.2.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: OpenGL Canvas Assignee: krita-bugs-n...@kde.org Reporter: robin.l...@gmail.com Target Milestone: --- SUMMARY When using Krita under Wayland the interface is flickering severely when interacting with an open canvas. STEPS TO REPRODUCE 1. Start KDE Plasma 6 under Wayland 2. Enable OpenGL Acceleration 3. Move Cursor anywhere onto the Canvas and draw OBSERVED RESULT The interface around the Canvas is constantly flickering with every move you make inside the applications. EXPECTED RESULT Drawing on the canvas without flickering. SOFTWARE/OS VERSIONS Linux/KDE Plasma: endeavouros, 6.9.5-arch1-1 Kernel (available in About System) KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION GPU: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 Nvidia Driver version: 550.90.07 Crosstesting has been made with PopOs on a system with a 3060 Mobile, Wayland enabled, no driver tweaks, there was no flickering. The video in this post describes what the flickering looks like: https://www.reddit.com/r/hyprland/comments/1cvpttm/krita_flickering/ -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 488714] Interface flickering under Wayland with any OpenGL acceleration enabled
https://bugs.kde.org/show_bug.cgi?id=488714 Loque changed: What|Removed |Added CC||robin.l...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 488714] Interface flickering under Wayland with any OpenGL acceleration enabled
https://bugs.kde.org/show_bug.cgi?id=488714 --- Comment #2 from Loque --- (In reply to Halla Rempt from comment #1) > I cannot reproduce this on KDE Neon in a wayland session with the appimage. > Please also check with the appimage. Tested it in appimage, pacman and flatpak. The issue persists across the Krita versions. I'm on Plasma 6 on EndavourOS which is Arch-based though. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 488714] Interface flickering under Wayland with any OpenGL acceleration enabled
https://bugs.kde.org/show_bug.cgi?id=488714 --- Comment #4 from Loque --- (In reply to Halla Rempt from comment #3) > That very much looks like an nvidia driver bug. I don't have access to > systems with an nvidia card, though... Could switching to nouveau help? I've switched to nouveau but the framerate was terribly low, about 1 fps. Switched back to the prop. drivers. Good point, I might dig into options of the prop. driver though. Or maybe find out what is tweaked in endeavourOS that might have caused the issue -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 488714] Interface flickering under Wayland with any OpenGL acceleration enabled
https://bugs.kde.org/show_bug.cgi?id=488714 --- Comment #5 from Loque --- (In reply to Loque from comment #4) > (In reply to Halla Rempt from comment #3) > > That very much looks like an nvidia driver bug. I don't have access to > > systems with an nvidia card, though... Could switching to nouveau help? > > I've switched to nouveau but the framerate was terribly low, about 1 fps. > Switched back to the prop. drivers. > Good point, I might dig into options of the prop. driver though. Or maybe > find out what is tweaked in endeavourOS that might have caused the issue Small update: Open-dkms drivers run OK but also show the issue with Krita. I'll see what I can dig up further. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 488714] Interface flickering under Wayland with any OpenGL acceleration enabled
https://bugs.kde.org/show_bug.cgi?id=488714 --- Comment #7 from Loque --- (In reply to Halla Rempt from comment #6) > Thanks for investigating! You're welcome, so I've done some research on it and it's most probably a problem with explicit sync. Tested it on KDE Neon live boot which already has 6.1 while arch is on 6.0.5, on KDE Neon Krita worked pretty well (It seems to run at 30fps but I can live with that) I think explicit sync is fully implemented only in 6.1 from what I've read on the web. Should this bug report be kept open until Plasma 6.1 for arch is out of testing and it can be confirmed it's caused by missing explicit sync? (I'm not going to use the testing repo which already has 6.1) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 488714] Interface flickering under Wayland with any OpenGL acceleration enabled
https://bugs.kde.org/show_bug.cgi?id=488714 Loque changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #10 from Loque --- (In reply to Halla Rempt from comment #9) > I think we can close it; it's not something we can fix in Krita. Yes, I think so as well. Tested it under vanilla arch, it wasn't flickering with the nouveau driver plasma 6 is shipped with and performance was okay. Under EOS there was probably some driver blacklisting I've missed to remove to make nouveau work but I digress. So yeah I think it's not caused by Krita itself but rather by the proprietary driver, I'm closing it. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 490649] Kscreenlocker hanging
https://bugs.kde.org/show_bug.cgi?id=490649 Loque changed: What|Removed |Added CC||robin.l...@gmail.com --- Comment #4 from Loque --- Can confirm similar behaviour, some details: SUMMARY for me it takes about 10 seconds for the Password prompt to show up when unlocking the screen. STEPS TO REPRODUCE It also only happens when the screen is being locked automatically, If I lock it manually with meta + L it doesn't happen. Has happened on a 3060ti as well and any Kernels. It only happens on X11, Wayland is actually fine. I'm not using wayland yet because pen monitor calibration is not implemented yet for Wayland in any form. Operating System: Arch Linux KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.10.2-zen1-1-zen (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4060 Ti/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd Product Name: MS-7B86 System Version: 2.0 Video Driver: 555.58.02 Logs: Jul 21 15:08:22 archlinux kscreenlocker_greet[229412]: pam_systemd_home(kde:auth): New sd-bus connection (system-bus-pam-systemd-home-229412) opened. [unrelated] Jul 21 15:08:22 archlinux kscreenlocker_greet[229412]: QRhiGles2: Context is lost. Jul 21 15:08:22 archlinux kscreenlocker_greet[229412]: Graphics device lost, cleaning up scenegraph and releasing RHI [unrelated] Jul 21 15:09:06 archlinux kscreenlocker_greet[229412]: QRhiGles2: Context is lost. Jul 21 15:09:06 archlinux kscreenlocker_greet[229412]: Failed to create RHI (backend 2) Jul 21 15:09:18 archlinux kscreenlocker_greet[229412]: QRhiGles2: Context is lost. Jul 21 15:09:18 archlinux kscreenlocker_greet[229412]: Graphics device lost, cleaning up scenegraph and releasing RHI Jul 21 15:09:18 archlinux kscreenlocker_greet[229412]: QRhiGles2: Context is lost. Jul 21 15:09:18 archlinux kscreenlocker_greet[229412]: Graphics device lost, cleaning up scenegraph and releasing RHI Jul 21 15:09:19 archlinux kscreenlocker_greet[229412]: QRhiGles2: Context is lost. Jul 21 15:09:19 archlinux kscreenlocker_greet[229412]: Failed to create RHI (backend 2) Jul 21 15:09:19 archlinux kscreenlocker_greet[229412]: QRhiGles2: Context is lost. Jul 21 15:09:19 archlinux kscreenlocker_greet[229412]: Failed to create RHI (backend 2) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 500911] New: Interaction between pen calibration via UDEV and kcm_tablet at the same time
https://bugs.kde.org/show_bug.cgi?id=500911 Bug ID: 500911 Summary: Interaction between pen calibration via UDEV and kcm_tablet at the same time Classification: Applications Product: systemsettings Version: 6.3.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_tablet Assignee: plasma-b...@kde.org Reporter: notafu...@posteo.com CC: aleix...@kde.org, j...@redstrate.com Target Milestone: --- SUMMARY In reference to the following thread in the code base discussion, as requested by Joshua Goins: https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1833 STEPS TO REPRODUCE 1. Create an UDEV rule to manually adjust your calibration, the process is described in paragraph 1.4 of this wiki: https://wiki.archlinux.org/title/Calibrating_Touchscreen (In my case: 0.25% to the left) 2. Reload UDEV rules for the calibration to apply. 3. Also Calibrate the the pen with the tool in kcm_tablet. 4. Save the result with the Apply button. OBSERVED RESULT - The Cursor is being offset way more than it should (about 1,5cm) EXPECTED RESULT - They shouldn't affect eachother, I guess? - Current workaround is to just comment out the udev rule. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.3.2 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.5-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4060 Ti Tablet: XP-Pen Artist 24 Pro ADDITIONAL INFORMATION - I also have an HP Elite X2 G4 where the UDEV method didn't work at all but the kcm_tablet method had the expected calibration effect. There, the interaction between the two methods didn't happen at all. I couldn't make complete sense of how the PIDs for this screen work. Pen, Eraser and touch share the same ID iirc (haven't tinkered with it ever since). Also with this tablet there seems to be some sort of correction by itself using the tilt sensors like the MS Surface has (Cursor jumping to the point when actually touching the screen with the tip in Krita) -- You are receiving this mail because: You are watching all bug changes.
