SUMMARY *** Copying a selection sometimes causes Krita to freeze up. It freezes immediately after pressing CTRL+C when the entire canvas is selected. Krita locks up writing error messages in an infinite loop to ~/.local/share/krita.log The messages look like this: 07 Nov 2022 10:48:31 -0600: SAFE ASSERT (krita): "qAbs(row) < 0x7FFF && qAbs(col) < 0x7FFF" in file /usr/src/debug/krita-5.1.1/libs/image/tiles3/kis_tile_hash_table2.h, line 151 07 Nov 2022 10:48:31 -0600: SAFE ASSERT (krita): "qAbs(row) < 0x7FFF && qAbs(col) < 0x7FFF" in file /usr/src/debug/krita-5.1.1/libs/image/tiles3/kis_tile_hash_table2.h, line 151 07 Nov 2022 10:48:31 -0600: SAFE ASSERT (krita): "qAbs(row) < 0x7FFF && qAbs(col) < 0x7FFF" in file /usr/src/debug/krita-5.1.1/libs/image/tiles3/kis_tile_hash_table2.h, line 151 ... to infinity until hard disk is full ... *** STEPS TO REPRODUCE 1. Create a new document. Any size. One layer. One brush stroke. 2. Ctrl+A to select all 3. Ctrl+C to copy 4. Locks up OBSERVED RESULT Krita locks up, enters infinite loop writing to krita.log EXPECTED RESULT - SOFTWARE/OS VERSIONS Linux: EndeavourOS; Linux 6.0.2 Qt Version: 5.15.7 ADDITIONAL INFORMATION When this occurred on my end and I forgot to kill the Krita process, it had written 250GB of data to the krita.log file and filled up my entire disk. In my case, it was a brand new document, small size, only one layer, entire canvas selected. It has happened a few times in the past, but lately it is becoming more regular.
Hi, NiO! It seems like the bug is related to the issue in the distribution packages of Qt. Could you please test the official AppImage packages of Krita instead? Official Krita 5.1.5: https://download.kde.org/stable/krita/5.1.5/krita-5.1.5-x86_64.appimage Stable Nightlies: https://binary-factory.kde.org/job/Krita_Stable_Appimage_Build/ Unstable Nightlies: https://binary-factory.kde.org/job/Krita_Stable_Appimage_Build/
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!