*** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY Both Flatpak and AppImage versions of Krita become unresponsive to UI input for ~25s after attempting to paste an image, creating a new image, or selecting a tool, or trying to use a tool, or really just about any interaction whatsoever other than hovering over menu items. STEPS TO REPRODUCE 1. Open Kirta 2. Create a new image 3. Observe that UI is unresponsive and mouse cursor doesn't even appear OBSERVED RESULT Krita is unresponsive to UI input for ~25s at a time after just about any action and, during this period, the mouse cursor will not even appear in the window. EXPECTED RESULT Krita is responsive to UI input and doesn't freeze for 25s on ever action. SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: Bazzite 40 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION
I cannot reproducce this issue on my Linux laptop or desktop with the appimage (both running KDE Neon). Could you attach the contents of help->system information for bug reports and help->krita log for bug reports to this bug?
Created attachment 173441 [details] Krita Usage Log Krita window unresponsive for ~25s after creating the new image
Created attachment 173442 [details] Krita System Information
Ok, so this is wild: Since the log was so useless I wanted to try and get more information, so I ran the flatpak from the terminal (flatpak run org.kde.krita) and the issue was not present. I then closed that session and re-ran krita from the .desktop menu entry and could not reproduce the issue. I even went and removed the flatpak, removed the .var/app/org.kde.krita directory, and reinstalled the flatpak and could not reproduce the issue. This leads me to believe some other component may be at fault, but you've got me as to what.
Heh, I cannot guess either. Then let's just close this report. Thanks for testing again!