Bug 423126

Summary: Failed assertion when using Move Tool on Transform Mask.
Product: [Applications] krita Reporter: Emmet O'Neill <emmetoneill.pdx>
Component: Tools/MoveAssignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: crash CC: tamtamy.tymona
Priority: NOR    
Version First Reported In: git master (please specify the git hash!)   
Target Milestone: ---   
Platform: Manjaro   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Emmet O'Neill 2020-06-17 22:01:11 UTC
Krita fails an assertion when using the Move Tool on a Transform Mask.

STEPS TO REPRODUCE
1. Add a Transform Mask to a layer.
2. Select the Transform Mask in the Layers Docker.
3. Try to move the selected Transform Mask with the Move Tool.

"ASSERT: "d" in file /home/emmet/Code/krita/source/libs/global/kis_shared_ptr.h, line 180"

Backtrace:
#0  0x00007ffff24f4355 in raise () from /usr/lib/libc.so.6
#1  0x00007ffff24dd853 in abort () from /usr/lib/libc.so.6
#2  0x00007ffff2a499ac in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/libQt5Core.so.5
#3  0x00007ffff2a48d59 in qt_assert(char const*, char const*, int) () from /usr/lib/libQt5Core.so.5
#4  0x00007ffff6f4e1c7 in KisSharedPtr<KisNode>::operator-> (this=<optimized out>, this=<optimized out>)
    at /home/emmet/Code/krita/source/libs/global/kis_shared_ptr.h:180
#5  operator() (__closure=0x7fff4c009658) at /home/emmet/Code/krita/source/libs/ui/tool/strokes/move_stroke_strategy.cpp:150
#6  0x00007ffff5a7a25b in KisStrokeJob::run (this=<optimized out>) at /home/emmet/Code/krita/source/libs/image/kis_stroke_job.h:44
#7  KisUpdateJobItem::run (this=0x555559bee0e0) at /home/emmet/Code/krita/source/libs/image/kis_update_job_item.h:102
#8  0x00007ffff2a89b82 in ?? () from /usr/lib/libQt5Core.so.5
#9  0x00007ffff2a85dcf in ?? () from /usr/lib/libQt5Core.so.5
#10 0x00007ffff1ee7422 in start_thread () from /usr/lib/libpthread.so.0
#11 0x00007ffff25b7bf3 in clone () from /usr/lib/libc.so.6
Comment 1 Tiar 2020-07-31 16:54:13 UTC

*** This bug has been marked as a duplicate of bug 424638 ***