https://bugs.kde.org/show_bug.cgi?id=443806
--- Comment #16 from flan_suse <windows2li...@zoho.com> --- An ideal solution! (In reply to Marcin Gurtowski) > The previous policy, in regards to encrypted $HOME was: > "If encrypted file for which thumbnail is generated is on the same drive as > ~/.cache/thumbnails, do create cache for this file.". > > Should we change it to: > "If ~/.cache/thumbnails is on encrypted device, create cache for thumbnails > of encrypted files."? This comment was taken from another bug report, but it basically solves the issue in this bug report. I'm assuming the same logic will be used across-the-board, regardless if such encrypted files live on a LUKS device or are encrypted on a network share. If the above is implemented, it solves this issue. No need for any extra toggles or options. However, implementing the above fix will not exclude the possibility for additional toggles or options in the future. It's a win-win-win! :) -- You are receiving this mail because: You are watching all bug changes.
