Bug 456261

Summary:	opening lower version of krita killed existing resource library
Product:	[Applications] krita	Reporter:	John <crazyjerick>
Component:	Resource Management	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	griffinvalley, halla, tomtomtomreportingin
Priority:	NOR
Version First Reported In:	5.0.6
Target Milestone:	---
Platform:	Mint (Ubuntu based)
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description John 2022-07-02 20:37:20 UTC

SUMMARY
***
Opening image in Krita 5.0.2 appimage after working a time in 5.0.6 caused the resource library to be re-written, thereby erasing my entire tagging scheme as well as resetting my bundle configuration.
***


STEPS TO REPRODUCE
1. (From Xviewer) Open With > Krita 5.0.2
2. 
3. 

OBSERVED RESULT
Krita prompted that the resource library will be rebuilt. No apparant means available to cancel or halt operation.

EXPECTED RESULT
Load image without alteration to existing resource library scheme.

Comment 1 Halla Rempt 2022-07-02 20:41:09 UTC

Yes? That's not a bug. Don't do this. This simply isn't supported.

Comment 2 tomtomtomreportingin 2022-07-02 22:02:26 UTC

If your resource database configuration was pretty intricate, keep in mind Krita stores database backups at $HOME/.local/share/krita/, so renaming a backup to resourcecache.sqlite should bring your configuration back.

Comment 3 Halla Rempt 2022-07-03 10:12:45 UTC

Note that krita itself first makes a backup of the database, too.

Comment 4 John 2022-07-03 17:50:48 UTC

(In reply to Halla Rempt from comment #1)
> Yes? That's not a bug. Don't do this. This simply isn't supported.

Supported or not, having a small sidestep in version (where all tools used are supported by the earlier version) blow up the resources and giving a fellah a headache as he goes about trying to remember everything he did to set up his workflow sounds quite a deal like a bug situation to me. The current state of resource management is leaps and bounds better than it used to be. It used to be so touchy that if you breathed on it wrong, something would be overwritten somewhere and updating Krita became a nightmare at times. Much better now, hands down... but could still use some improvements.

If for whatever reason an older version is opened, it really should not override anything at all if it uses the current resource management system. In my case, it really happened by accident due to an overlooked shortcut pointing to the older appimage. While that detail isn't super important, a small goofup like that should never result in raised blood pressure. If for some reason the ideal solution isn't happening, then at least consider having a prompt appear explaining that X, Y and Z is about to happen and give the option to halt the operation instead of Krita marching forward with the re-writes. Then at least there will be peace and cooperation.

Thank you for taking the time to read through this.

Comment 5 Halla Rempt 2022-07-04 13:35:25 UTC

But we cannot _change_ anything in 5.0.2 -- its behaviour cannot be changed. Same goes for 5.0.6. It's released, it's out there, it's fixed... And 5.1.0 (currently in beta) actually exports and imports the tags on a database schema change.

Comment 6 John 2022-07-05 01:52:26 UTC

Good