[dolphin] [Bug 497159] New: With Previews enabled, Dolphin doesn't show the preview for a renamed file until the view is manually refreshed
Chris Warren
bugzilla_noreply at kde.org
Sat Dec 7 13:12:09 GMT 2024
https://bugs.kde.org/show_bug.cgi?id=497159
Bug ID: 497159
Summary: With Previews enabled, Dolphin doesn't show the
preview for a renamed file until the view is manually
refreshed
Classification: Applications
Product: dolphin
Version: git-master
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: view-engine: general
Assignee: dolphin-bugs-null at kde.org
Reporter: chrisw82 at protonmail.com
CC: kfm-devel at kde.org
Target Milestone: ---
SUMMARY
With Previews enabled, Dolphin doesn't show the preview for a file that has
been renamed until the view is manually refreshed
STEPS TO REPRODUCE
1. Have Previews enabled
2. Navigate to a directory where there's a file you'd like to rename that
currently has a content preview as its icon
3. Rename the file that is showing a preview of the file
OBSERVED RESULT
The icon associated with the file changes from a content preview to a generic
media type icon as though I either had previews turned off or there was an
issue generating a preview for the new file.
This happens in both local and remote (NFS via a mountpoint) operations. It
also happens regardless of whether I hit F2 to rename or right click -> Rename.
If I reload the file view in some way (either F5 or navigate out and then back
into the directory), the preview is regenerated under that new filename, so
that is a workaround.
EXPECTED RESULT
The preview associated with the old filename is now associated with the new
filename without needing to reload anything
SOFTWARE/OS VERSIONS
Operating System: Gentoo 2.17
KDE Plasma Version: 6.2.80
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.1
KDE Plasma/Gear/Frameworks is from git-master, most recent commits as of
2024/12/07 @ ~7:30am EST
ADDITIONAL INFORMATION
Commit for dolpin is 18ced02b2ec74b92918fc4fce42b5bba5e6b8a20, although I first
observed this issue maybe a few weeks ago I think
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the kfm-devel
mailing list