Version: unspecified OS: Linux the new transform tool does it's work in the background, so that the userinterface is not blocked. this can cause various crashes: o if clicking on apply button a second time o if changing to the brush tool and draw o if scaling the layer or image by the function in the menu o if deleting the current layer Reproducible: Always
I think it is partly connected with https://bugs.kde.org/show_bug.cgi?id=248374. At least first three crashes.
SVN commit 1176731 by langkamp: also check for systemLocked BUG:251389 M +1 -1 kis_tool_transform.cc WebSVN link: http://websvn.kde.org/?view=rev&revision=1176731
reopening, as it is still possible to crash krita by using the menu or deleting the layer.
SVN commit 1177167 by langkamp: don't remove node while working on them BUG:251389 M +2 -0 kis_layer_box.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1177167
SVN commit 1177239 by pegon: Fixed crash on removing layer while in transform tool. BUG:251389 M +20 -2 kis_tool_transform.cc WebSVN link: http://websvn.kde.org/?view=rev&revision=1177239
Closed the wrong bug.. Let's reopen this one.
I tried those : o if changing to the brush tool and draw o if scaling the layer or image by the function in the menu o if deleting the current layer It doesn't crash anymore. Can someone else confirm ?
The crashing itself is fixed, by the lock. We are currently discussing on the mailinglist how this can be solve in a better way.
See the discussion on the mailing list: http://lists.kde.org/?l=kde-kimageshop&m=128505006220448&w=2
Is the bug solved for 2.3 ? (even if a better solution is needed for later) In which case, could we remove the release_blocker tag ?
Yes, the tag can be removed since we also demoted this bug from major to normal.
This now awaits porting all tools/actions to the strokes framework, afaik
This bug affects Backspace shortcut as well. Can be seen really well on 16bit images
Make it a duplicate of 284457 "Remaining tools need to be ported to the strokes framework " *** This bug has been marked as a duplicate of bug 284457 ***