Bug 409334 - Vector Layer contains lines and non-ascii characters corrupted and missing all data after re-open
Summary: Vector Layer contains lines and non-ascii characters corrupted and missing al...
Status: RESOLVED DUPLICATE of bug 409333
Alias: None
Product: krita
Classification: Applications
Component: Layers/Vector (other bugs)
Version First Reported In: 4.2.0
Platform: Other Microsoft Windows
: NOR critical
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-30 17:01 UTC by nyaachen
Modified: 2019-06-30 17:02 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Krita logfile and the buggy file (810.48 KB, application/x-zip-compressed)
2019-06-30 17:01 UTC, nyaachen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description nyaachen 2019-06-30 17:01:27 UTC
Created attachment 121234 [details]
Krita logfile and the buggy file

SUMMARY
While I have Krita to graph an important work using the vector function, I found it just corrupt all my data in vector layer after i save it. After a suddenly crash it corrupted all my data. Then I create another one with autosaving to 1 min once. After i finish my work, save the file with no error information, close it to edit a new file, and then when i reopen it all the content in the vector layer disappear. Even with a third time I re graph all item in vector layer, saved once again with no error reported. When i reopen it is empty with all ojects missing once again. Now I'm completely disappointed with Krita.


STEPS TO REPRODUCE
1. create an vector layer with some chinese text object and graphs and lines and so on.
2. draw some symbol with your pen(opening a new layer)
3. save the file, close krita, reopen the file

OBSERVED RESULT
all content in vector layer is missing in Krita.
the thumbnail in explorer shows that the file is all fine, the vector content exists.


SOFTWARE/OS VERSIONS
Windows: Windows 10 1803 Professional

ADDITIONAL INFORMATION
Comment 1 Tiar 2019-06-30 17:02:20 UTC

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