[dolphin] [Bug 474931] New: [UX] Caching thumbnails on local network, network shares. Whitelisting thumbnail caching on network shares.

bugzilla_noreply at kde.org bugzilla_noreply at kde.org
Wed Sep 27 12:29:43 BST 2023


https://bugs.kde.org/show_bug.cgi?id=474931

            Bug ID: 474931
           Summary: [UX] Caching thumbnails on local network, network
                    shares. Whitelisting thumbnail caching on network
                    shares.
    Classification: Applications
           Product: dolphin
           Version: 23.08.1
          Platform: Debian testing
                OS: Linux
            Status: REPORTED
          Severity: wishlist
          Priority: NOR
         Component: general
          Assignee: dolphin-bugs-null at kde.org
          Reporter: jakubby at protonmail.com
                CC: kfm-devel at kde.org
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
Users have low frequency of change network shares, thumbnails regeneration over
network even on an local ethernet gigabit connection is fairly slow.
Users should be able to mark network shares which dolphin would cache and
thumbnail.

STEPS TO REPRODUCE
1. Enter a folder with music on an sftp share.
2. Navigate out.
3. Navigate in.

OBSERVED RESULT
Thumbnails are being re-generated.

EXPECTED RESULT
Thumbnails are cached.

Also would be nice if thumbnails would cache persistently not just for the
session.
So that this state would be consistent on subsequent mounting of a network
share.
Dolphin should try to regenerate the thumbnails as it does now, but in the
background in case files change on a subsequent network share session.


SOFTWARE/OS VERSIONS
I'm on my phone right now, but I use debian testing 13/trixie and it's up to
date.

ADDITIONAL INFORMATION
One step closer into UX heaven, one step further away from UX hell.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the kfm-devel mailing list