Bug 511617 - Dolphin continues to show already removed files until f5 is pressed
Summary: Dolphin continues to show already removed files until f5 is pressed
Status: REPORTED
Alias: None
Product: dolphin
Classification: Applications
Component: view-engine: general (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-11-04 12:26 UTC by Mike Krutov
Modified: 2025-11-04 12:26 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Krutov 2025-11-04 12:26:54 UTC 
SUMMARY

I've stumbled upon this by accident pretty much, but I've managed to get a situation where dolphin shows ghost contents of your directories until you press F5.

STEPS TO REPRODUCE
1. Have a directory /path/to/directory, populated by files: dirA, fileB.
2. Open it in dolphin
3. Close dolphin
4. In a separate terminal, run rm -rf /path/to/directory/ && mkdir /path/to/directory.
5. Reopen dolphin

OBSERVED RESULT
Dolphin loads previous session.
Dolphin shows dirA, fileB. Clicking on each does nothing (no error popup, no refresh).
If a user presses F5, directory refreshes.
`ls` in built-in terminal doesn't refresh contents, but shows correct results (empty directory or otherwise).

EXPECTED RESULT
Dolphin shows actual, new contents (be the target directory empty or otherwise)

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20250917
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.18.0
Qt Version: 6.9.2
Kernel Version: 6.16.7-1-default (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 PRO 7840U w/ Radeon 780M Graphics
Memory: 64 GiB of RAM (58.5 GiB usable)
Graphics Processor: AMD Radeon 780M
Manufacturer: LENOVO
Product Name: 21K6S0A00C
System Version: ThinkPad P14s Gen 4

ADDITIONAL INFORMATION
It is a bit finicky to reproduce; I've managed to reproduce it twice and not reproduce it thrice. When reproduced though, it is consistently failing to refresh until manual refresh is performed.