Bug 402462

Summary: Custom gradient layer styles are not saved and loaded correctly
Product: [Applications] krita Reporter: Galaxy Silver <argentinecosmos>
Component: layer stylesAssignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: halla
Priority: NOR    
Version: git master (please specify the git hash!)   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Galaxy Silver 2018-12-22 15:36:08 UTC 
SUMMARY
Gradient effect that I make custom isn't saved, so when I reopen the file, Krita takes the current foreground color and background color as gradient effect, and also the mode is back to Normal/Multiply with 75% opacity (the default gradient effect settings.

STEPS TO REPRODUCE
1. Make a custom gradient layer style
2. Save the file, then close the file
3. Reopen the file

OBSERVED RESULT
Custom gradient isn't saved, Krita instead picks new colors from foreground and background colors as the gradient, and gradient style is always back to Normal/Multiply.

EXPECTED RESULT
Gradient colors and mode stays the same (doesn't pick new colors) after the file is saved, closed, and reopened.

SOFTWARE/OS VERSIONS
Windows: 10
MacOS: -
Linux/KDE Plasma: -
(available in About System)
KDE Plasma Version: -
KDE Frameworks Version: -
Qt Version: -

ADDITIONAL INFORMATION
Comment 1 Halla Rempt 2019-01-06 11:11:22 UTC 
Thank you for your report. I can confirm the issue. I even get an assert when trying this:

ASSERT: "segment != 0" in file /home/boud/dev/krita/libs/pigment/resources/KoSegmentGradient.cpp, line 251
ASSERT: "segment != 0" in file /home/boud/dev/krita/libs/pigment/resources/KoSegmentGradient.cpp, line 251
ASSERT: "segment != 0" in file /home/boud/dev/krita/libs/pigment/resources/KoSegmentGradient.cpp, line 251
ASSERT: "segment != 0" in file /home/boud/dev/krita/libs/pigment/resources/KoSegmentGradient.cpp, line 251
Re-raising signal for core dump handling.
Aborted (core dumped)
Comment 2 Halla Rempt 2019-05-09 10:05:06 UTC 
This seems to have been fixed now, it works for me.