Created attachment 161174 [details] krita usage and system log SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. copy text into the clipboard 2. hit ctrl+v on the krita window with any type of layer selected OBSERVED RESULT instant crash EXPECTED RESULT do nothing. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: kubuntu 22.04 (available in About System) KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I'm using the appimage version
Hi, Fausto! Could you please check if this bug is still reproducible in Krita 5.2.0 Beta2? I guess wee have fixed a bug like that quite recently, so there should be no crash in 5.2.x branch anymore... Here is the page for downloading the beta-version: https://krita.org/en/item/second-beta-for-krita-5-2-0-released/ If you can still reproduce the issue, please tell what software you copy text from (and website, if it is chrome/firefox). And whether you somehow close the source application in the meantime before pasting into Krita.
(In reply to Dmitry Kazakov from comment #1) > Hi, Fausto! > > Could you please check if this bug is still reproducible in Krita 5.2.0 > Beta2? I guess wee have fixed a bug like that quite recently, so there > should be no crash in 5.2.x branch anymore... > > Here is the page for downloading the beta-version: > https://krita.org/en/item/second-beta-for-krita-5-2-0-released/ > > If you can still reproduce the issue, please tell what software you copy > text from (and website, if it is chrome/firefox). And whether you somehow > close the source application in the meantime before pasting into Krita. Hi, Dmitry I downloaded the beta 2, and tried to reproduce the bug in all the ways that it used to happen and looks like it's fixed. I tried copying text from browser and other apps and krita beta2 doesn't crash. so, thank you!!
Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information.
Hi, Fausto! Thank you very much for your help with testing! :)