Bug 441874

Summary: Custom Palettes are not loaded unless Krita is ran as administrator
Product: [Applications] krita Reporter: Tyler Breau <tylerbreau>
Component: * UnknownAssignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: minor CC: tomtomtomreportingin
Priority: NOR    
Version First Reported In: 4.4.5   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Tyler Breau 2021-09-01 16:04:55 UTC
SUMMARY


STEPS TO REPRODUCE
1. Open without administrator permission krita document
2. Create a custom palette and check "Save Palette in the Current Document"
3. Open krita document without administrator permission
4. See custom palette is missing from your available palettes
5. Close krita
6. Open krita with administrator permission ("Run as Administrator")
7. Open your krita document
8. See your custom palette is in the available palette options


OBSERVED RESULT
Custom Palettes that are saved in the document disappear after closing and re-opening the krita document, unless krita was opened with "Run as Administrator".

EXPECTED RESULT
When Krita opens the document, it should be able to open palettes that were saved in the document without administrator permissions.

SOFTWARE/OS VERSIONS
Windows:  10.0.19043 Build 19043
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 5.12.9

ADDITIONAL INFORMATION
I didn't see anything regarding KDE Plasma or KDE Frameworks versions in Help -> Show system information for bug reports.
If I am looking in the wrong place please notify me and I get the information required.

A temporary work around for this issue is to notify users in the UI that custom palettes saved in the document will not load unless krita is opened with the "Run as Administrator" option.
This wouldn't really look pretty and is not really a solution but at least users would be informed.
Comment 1 tomtomtomreportingin 2021-09-01 17:24:56 UTC
See https://bugs.kde.org/show_bug.cgi?id=440812

Does upgrading to 4.4.8 resolve your issue?
Comment 2 Tyler Breau 2021-09-01 20:42:11 UTC
(In reply to tomtomtomreportingin from comment #1)
> See https://bugs.kde.org/show_bug.cgi?id=440812
> 
> Does upgrading to 4.4.8 resolve your issue?

Ah it does seem to resolve the issue. My bad.
Comment 3 tomtomtomreportingin 2021-09-01 22:02:45 UTC
Not a problem.

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