| Summary: | Dolphin does not update search results view after a file is deleted or renamed | ||
|---|---|---|---|
| Product: | [Applications] dolphin | Reporter: | Federico Acosta <acoguemovil> |
| Component: | search | Assignee: | liweinan <liweinan> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | 16f87xa, bugseforuns, feifel, fernandommuniz, germano.massullo, greg, heri+kde, hi, ionica, jens-bugs.kde.org, karl, mail, mfiresix2, nate, popov895, postix, ricky.tigg, stefan.bruens, tagwerk19, tejada.c7, witchhunterpro, wooden445, yusq77 |
| Priority: | VHI | ||
| Version First Reported In: | 19.12.0 | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Federico Acosta
2018-03-28 15:39:17 UTC
When I Delete a file listed in a search, it continue appearing the file I have deleted till I close dolphin and open it again File disappears from search result when I press F5 after deletion. Use del or shift+del to delete makes no difference. Tested on Arch Linux, plasma 5.12.4. The search results do update correctly after refreshing the view with Dolphin 18.04.2, but it'd probably be nice if we would automatically refresh after the deletion. I'll keep this report open, but re-word the title/tags. *** Bug 400095 has been marked as a duplicate of this bug. *** *** Bug 417269 has been marked as a duplicate of this bug. *** *** Bug 413184 has been marked as a duplicate of this bug. *** *** Bug 417501 has been marked as a duplicate of this bug. *** *** Bug 419727 has been marked as a duplicate of this bug. *** *** Bug 423549 has been marked as a duplicate of this bug. *** *** Bug 412980 has been marked as a duplicate of this bug. *** See also Bug 392793 There is a special case where baloo does not pick up on changes in a folder if a parent folder is renamed *** Bug 439517 has been marked as a duplicate of this bug. *** Dennis Schridde changed:
> What |Removed |Added
> ----------------------------------------------------------------------------
> See Also| |https://bugs.kde.org/show_bug.cgi?id=392793,
> | |https://bugs.kde.org/show_bug.cgi?id=429006
The issues of:
Baloo not noticing changes in the filesystem and/or not indexing the changed files
and:
Dolphin caching results and not showing changes.
are quite distinct. There is a command line test to check whether the issue is a "baloo thing" or not, try:
balooshow -x the-file-in-question.txt
or
baloosearch the-file-in-question
and see whether they give you details of the file.
If they do not then need to troubleshoot baloo. If baloosearch works and you don't see what you expect in Dolphin then need to check how dolphin is doing the search (Dolphin uses baloo when it can but this can get complicated) or whether there's an issue with caching.
*** Bug 475440 has been marked as a duplicate of this bug. *** Hi i found something funny why my Dolphin is not updating the view. I just found it comfy to put a shortcut of the PAPERBIN on my Desktop. After this Dolphin was not updating the view!!! After removing the PAPERBIN shortcut on my desktop (i put it in Paperbins ;-) ) Dolphin is working like normal and view is updated!!!!! As i am no expert to fix this problem or look at it its up to the professionals. In my case it was a "simple shortcut" like i was used to from windows. *** Bug 475440 has been marked as a duplicate of this bug. *** *** Bug 502238 has been marked as a duplicate of this bug. *** *** Bug 494298 has been marked as a duplicate of this bug. *** You can look at this question first. When a file is modified, the URL triggered by the modification fails to find the corresponding query cache, and the interface that provides modification functionality cannot meet the requirements for modifying the query cache. I can confirm this, on dolphin 25.08.0 from the Arch Linux repos. (In reply to Oliver Geer from comment #21) > I can confirm this, on dolphin 25.08.0 from the Arch Linux repos. Sorry; I do notice this wasn't a helpful thing to say. (In reply to liweinan@kylinos.cn from comment #20) > When a file is modified, the URL triggered by the modification fails to find > the corresponding query cache, and the interface that provides modification > functionality cannot meet the requirements for modifying the query cache. Thanks so much for looking into this! |