| Summary: | "Eraser Circle" and "Basic-5 Size" have become untagged | ||
|---|---|---|---|
| Product: | [Applications] krita | Reporter: | tomtomtomreportingin |
| Component: | Resource Management | Assignee: | Krita Bugs <krita-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | halla, tamtamy.tymona |
| Priority: | NOR | ||
| Version First Reported In: | 5.0.0-beta1 | ||
| Target Milestone: | --- | ||
| Platform: | Appimage | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Fresh Erasers.tag vs. my Erasers.tag | ||
|
Description
tomtomtomreportingin
2021-08-19 22:26:29 UTC
Ah, same question as with: https://bugs.kde.org/show_bug.cgi?id=441200 . The brushes are still untagged with a regenerated resourcecache.sqlite. (haven't bothered tagging them myself yet.) Created attachment 141450 [details]
Fresh Erasers.tag vs. my Erasers.tag
It looks like my .tag files were scuffed, and removing resourcecache.sqlite or KRITA_RESOURCE_VERSION didn't seem to fix them. See the attachment comparing the Erasers.tag in a fresh environment to my Erasers.tag in my typical environment.
Notably the .kpp extension for the Default Resources property is missing, along with the Resource Type property, although it's the former that affects this issue (is the Resource Type property important to have?).
The fact that removing resourcecache.sqlite or KRITA_RESOURCE_VERSION doesn't fix the tag files is reproducible in a fresh environment. However, removing KRITA_RESOURCE_VERSION does regenerate the .tag file if it's outright missing. So is this an issue?
> So is this an issue?
I guess we could close it; the changes in the .tag file look a bit weird, maybe if you encounter it again, and could pinpoint what happened to the .tag file to become changed, then we could reopen and fix the reason.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |