https://bugs.kde.org/show_bug.cgi?id=411919
--- Comment #26 from Marcin Gurtowski <halftough...@gmail.com> --- (In reply to flan_suse from comment #25) > How and where do I submit a merge request? I'm just an end-user that > believes in practicality and usability. :) I'll do it, just need to know the > proper method. https://community.kde.org/Infrastructure/GitLab#Submitting_a_merge_request is a good guide. If you also need information on development, I used https://community.kde.org/Get_Involved/development when I looking into this problem for the first time > > Caching thumbnails in $HOME when $HOME is encrypted is reasonable. To clarify, that's not exactly how the problem was previously solved. Kio would save thumbnail for files on encrypted partition if $HOME was on the same partition. If both were encrypted, but were different devices, thumbnail would be created, but not saved. > 2) The user's $HOME is where we expect cache to be consolidated, and it's > the main "driver" of daily work. I'd assume most users that utilize > encrypted volumes use them nearly exclusively on their *own* system, rather > than on someone else's system. It can complicate things if KDE is an outlier > in that it caches thumbnails on the folder/volume itself (where the media > resides), while other desktop environments continue to use $HOME/.cache > consistently. If someone uses both unencrypted $HOME and some encrypted devices, it implies they don't care as much about data from $HOME being leaked as they do about from encrypted media. Catching data from encrypted drive gives access to data that shouldn't be given. I'll try to look into the problem and fix previous solution (create thumbnails, but don't save them), but if you want to add extra options to this, is sounds fine to me. -- You are receiving this mail because: You are watching all bug changes.
