[krita] [Bug 375585] New: [mergedimage.png] Vectors layers are not correctly rendered anymore

[David REVOY]

https://bugs.kde.org/show_bug.cgi?id=375585

            Bug ID: 375585
           Summary: [mergedimage.png] Vectors layers are not correctly
                    rendered anymore
           Product: krita
           Version: 3.1 Beta
          Platform: Compiled Sources
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: File formats
          Assignee: krita-bugs-n...@kde.org
          Reporter: i...@davidrevoy.com
  Target Milestone: ---

Created attachment 103653
  --> https://bugs.kde.org/attachment.cgi?id=103653&action=edit
[screenshot of the bug]

Hi,
This is a very new behavior on krita/3.1 branch for the *.png inside the *.kra
archive files named 'mergedimage.png' : the vectors layers are not correctly
rendered anymore.

To reproduce:
=============
- Download the page source to reproduce the bug here:
https://share.kde.org/index.php/s/v7ZguRWnRHRHfMX
- Extract the *.zip file to get the *.kra file, open it with Krita (
krita3.1~git 2017-01-26 ). 
- Check the render on the canvas: the render is ok.
- Blink a random layer visibility ( this will trigger a fake modification to
unlock possibility to save/overwrite the file ).
- Save modifications.


Result:
=======
Check the generated mergedimage.png inside the *.kra file with an archive
editor. The rendering should be similar to screenshot in attachement to this
bug-report: the panels in white around comic page are half missing, especially
on bottom-right of the page. The vector layer 'Frame' on top of the layer stack
wasn't correctly rendered.

Test I did:
===========
This bugs breaks my 'renderfarm' to render my webcomic pages, so it's jumping
quickly on my eyes. Any older version of Krita (appimage) I have doesn't
produce this behavior ( eg. krita 3.1.1 or 3.0.94 or 3.0.1 ). I can still
workaround by opening files in a previous appimage and save/overwrite them this
way. This bug is something new since I updated Krita yesterday (25 January
2017). The previous krita3.1~git build I had didn't produce this behaviour and
probably was built a little week-ago.

-- 
You are receiving this mail because:
You are watching all bug changes.