I started to make requests for each application for KDE snaps will need read access to kdeglobals for proper Qt theme support. dot-config-kde-globals: interface: personal-files read: - $HOME/.config/kdeglobals
And realized that doing this 200 times will like end with me banned as a spammer. Can I just make this one request for all our applications? Thanks for your consideration. Scarlett
May be instead of this, why not allow that under the desktop plug?
Would definitely agree with Soumaya here, it feels like the kind of thing we’d want everyone to benefit from. It does mean there’d need to be a snapd release corresponding with it, but, jobs worth doing properly and all!
Certainly feels like a candidate for a micro-release, given all the KDE 6 popularity boosts, yet just one line of code. (Not that I get to decide 
)
@alexmurray May be you can shed some light?
Hmm so this feels reasonable for desktop - e.g. there is already some precedent via following rules for gtk:
owner @{HOME}/.config/gtk-3.0/settings.ini r,
owner @{HOME}/.config/gtk-3.0/*.css r,
# Note: this leaks directory names that wouldn't otherwise be known to the snap
owner @{HOME}/.config/gtk-3.0/bookmarks r,
But I am not that familiar with KDE - @scarlettmoore can you provide some details on what exactly is contained within $HOME/.config/kdeglobals ? Thanks.
kdeglobals is a file that holds configuration settings much like settings.ini for gnome. It is quite important for theming as it holds custom colors and the like. Thanks, Scarlett
Adding this file to the desktop interface will make it accessible essentially by any snap. However, considering it is read-only it would be perfectly fine from my point of view if @scarlettmoore thinks there is no sensitive information in there ^^
I’m removing the individual requests from our tracking system as I don’t think it makes sense to manege them individually regardless of how we are going to handle them
No sensitive information.
Created a PR in snapd.
Thanks @soumyaDghosh !
It’s kind of my duty 
Thanks a lot.