https://bugs.kde.org/show_bug.cgi?id=411919
--- Comment #39 from flan_suse <windows2li...@zoho.com> --- (In reply to Nate Graham from comment #38) > I still think each mounted volume's thumbnails should be stored *on* that > mounted volume. It solves basically all the problems. I think it might lead into new issues down the line. I listed the reasons why. And I absolutely don't want thumbnails being cache'd on a network share / volume. Not to mention some people might mount an external drive as read-only, or not have sufficient permissions. Not to mention that external media is usually slower than where someone's $HOME resides. And finally, it means that KDE will stand out as the odd-ball desktop environment, straying for other standards. If one switches between desktops (Xfce, GNOME, Mate, KDE), then with only KDE will it try to write and read thumbnails from each separate volume, while on the others they will write and read thumbnails directly from $HOME. We've been using KDE with no problems until this "fix" was implemented, and now we don't have thumbnails being cached. And now thumbnails might in fact attempt to write outside of home? What does that mean for network shares? That would be a step backwards. -- You are receiving this mail because: You are watching all bug changes.
