https://bugs.kde.org/show_bug.cgi?id=438309
--- Comment #3 from ratijas <[email protected]> --- Turned out little bit more complicated than I expected. Strangely enough, profiles are identified by their name, not some internal UUID or stuff like that. Which means, some migration code path is needed to ensure that no user-crated profile with as stupid name as "Built-in/Hardcoded" would mess up their uniqueness. Second, internally code base itself is not consistent about naming things: the "Default" profile aka "Built-in/Hardcoded" is also called "fallback" profile. I think that requires a proper uniform refactoring across all profile-related code. -- You are receiving this mail because: You are watching all bug changes.
