Bug 369492 - Krita config is lost on snap update
Summary: Krita config is lost on snap update
Status: RESOLVED UPSTREAM
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: 3.0.1
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-28 17:26 UTC by supaiku
Modified: 2016-10-03 11:17 UTC (History)
1 user (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description supaiku 2016-09-28 17:26:32 UTC 
Whenever the Krita snap is updated, 

Reproducible: Always
Comment 1 supaiku 2016-09-28 17:27:22 UTC 
Damn, hit enter too early.
Comment 2 supaiku 2016-09-28 17:32:38 UTC 
Don't know how to edit, but anyway.

Whenever the snap is updated, Krita loads from a new ~/snap/something/.local/share/krita directory.

It's not really user-friendly and quiet annoying to have to copy the old one to the new location.

I don't know if Snap can be configured to share the configs between updates. But the way it is now, it's totally broken from a user perspective.
Comment 3 Halla Rempt 2016-10-03 11:17:37 UTC 
This is what Michael Hall told me:

29.09.2016-15:16 < mhall119> it should be using ~/snap/krita/<version>/ for saving user settings
29.09.2016-15:17 < mhall119> and those files will be copied over to the next version when you update

So if that doesn't happen, it would be a bug in snap, not in Krita. There isn't much that we can do...