Bug 409307 - Comics Manager Removes Pages Upon Save, Also Crashes
Summary: Comics Manager Removes Pages Upon Save, Also Crashes
Status: RESOLVED DUPLICATE of bug 410409
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: 4.2.2
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-29 15:20 UTC by cadaverous.doll
Modified: 2019-09-04 16:05 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description cadaverous.doll 2019-06-29 15:20:07 UTC
I can add pages all day to my hearts content, but when I have one of those files open and save it with new changes, it is automatically removed from the comics manager page list. However reopening Krita and reselecting the json file it appears again.


STEPS TO REPRODUCE
1. Add page
2. Open that page and save it
3. Page is removed from the pages list completely.
4. Reopening the file completely, loading up the .json file again, it now appears as if it were never removed. Only now it's at the bottom of the page list vs the top (ex: page 1 should always be at the top, but now its not).
5. If you do not reload the file but attempt to reload the .json Krita crashes. After loading up the comcis manager repeatedly causes krita to crash for me.

OBSERVED RESULT
Is Krita treating this as brand new document upon save, thus removing it temporarily from the list?

EXPECTED RESULT
Leave that page in the comics manager regardless of how many times you save it (provided you're not changing the file name).

SOFTWARE/OS VERSIONS
Windows: windows 10
Comment 1 cadaverous.doll 2019-06-29 15:47:15 UTC
Another note: When it crashes the docker stays in view when reopening krita. after a few restarts it works sort of like normal again, just reverts back to not keeping a working + saved page in the comics manager.
Comment 2 wolthera 2019-09-04 16:05:00 UTC

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