I can create a text element (single line, no newlines) and afterwards move it around. Everything fine. But if I double click on the existing text and then press cancel I can't move the text anymore STEPS TO REPRODUCE 1. Create a Text field (save and close) 2. Enter edit mode again and click cancel 3. Can't edit text or move it anymore OBSERVED RESULT Can't edit text or move it anymore EXPECTED RESULT Can edit text or move it SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 4.19.61-1-lts (available in About System) KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.60.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION Also happens in Krita 4.2.4 command line output of krita command $ krita Set style "fusion" Invalid profile : "/usr/share/color/icc/colord/Crayons.icc" "Crayon Colors" Invalid profile : "/usr/share/color/icc/colord/x11-colors.icc" "X11 Colors" krita.lib.widgets: The file could not be parsed. QObject::startTimer: Timers cannot have negative intervals /usr/lib/krita-python-libs/krita added to PYTHONPATH SAFE ASSERT (krita): "!m_d->readyShortcut" in file /build/krita/src/krita-4.2.4/libs/ui/input/kis_shortcut_matcher.cpp, line 579 SAFE ASSERT (krita): "!m_d->readyShortcut" in file /build/krita/src/krita-4.2.4/libs/ui/input/kis_shortcut_matcher.cpp, line 579 SAFE ASSERT (krita): "!m_d->readyShortcut" in file /build/krita/src/krita-4.2.4/libs/ui/input/kis_shortcut_matcher.cpp, line 579 KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = krita path = /usr/bin pid = 2289 KCrash: Arguments: /usr/bin/krita KCrash: Attempting to start /usr/lib/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__1
Could you also check the nightly stable build tomorrow? See https://binary-factory.kde.org/job/Krita_Stable_Appimage_Build/
I believe this is the same bug as the one I marked it a duplicate of. But yes, please check the nightly and comment here or in the other bug report about the results. *** This bug has been marked as a duplicate of bug 410459 ***
tried with krita-4.2.4-63aa0b3-x86_64.appimage seems to work (can't reproduce the bug anymore)!
Thanks for testing!