Summary: | Dolphins find function finds deleted file | ||
---|---|---|---|
Product: | [Applications] dolphin | Reporter: | ceolesen |
Component: | search | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | dap78, finex, frank78ac, justin.zobel, kde, nate, rockonthemoonfm, stu109382 |
Priority: | NOR | ||
Version First Reported In: | 2.2 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
ceolesen
2013-04-07 11:44:17 UTC
Thanks for the bug report! I assume that Nepomuk is enabled? In that case, it would probably be a Nepomuk issue. The "System Settings"->"Desktop Search - System Settings"->"Nepomuk Sematic Desktop" window says "Desktop search services are active" and "ps -ef" terminal output includes "/usr/bin/nepomukcontroller" ' On Mon, Apr 8, 2013 at 1:56 PM, Frank Reininghaus <frank78ac@googlemail.com>wrote: > https://bugs.kde.org/show_bug.cgi?id=317971 > > --- Comment #1 from Frank Reininghaus <frank78ac@googlemail.com> --- > Thanks for the bug report! I assume that Nepomuk is enabled? In that case, > it > would probably be a Nepomuk issue. > > -- > You are receiving this mail because: > You reported the bug. > Thanks, I guess it's a Nepomuk issue then. Could you please make paste the output of `ps aux | grep nepomuk`. I want to see which all Nepomuk processes are running. Also, can you find the file via - kioclient list 'nepomuksearch:/filename' ? I remember implementing filtering on the nepomuksearch kioslave that will never show files that cannot be statted. So, this is a little weird. If possible could you also try tagging the file, deleting the file and then searching for all files with that tag? (You can perform this search either via `nepomuksearch:/hasTag:TagName` or by clicking on that tag via the information panel or via tags:/TagName/) My previous entries were from a Fedora 17 system fully uptodate. That system may have been installed as an upgrade of a Fedora 16 system using Redhats OS upgrade procedure "preupgrade" - I dont remember. But on that F17 system I get $ ps aux | grep nepomuk xxxxxx 1267 0.0 0.4 89816 13360 ? S 10:41 0:00 /usr/bin/nepomukcontroller -session 10d3ce7a7a000132060974500000018810008_1365458409_712961 i.e. only 1 entry I also have access to a F18 system installed from scratch and also fully uptodate. On that I get $ ps aux | grep nepomuk xxxxxx 1302 0.0 0.6 77620 6632 ? Sl 10:42 0:00 /usr/bin/nepomukserver xxxxxx 1305 0.0 2.2 177100 22772 ? SNl 10:42 0:00 /usr/bin/nepomukservicestub nepomukstorage xxxxxx 1311 0.0 1.3 93112 13964 ? S 10:42 0:00 /usr/bin/nepomukcontroller -session 1028c1d320b210000136362031000000014500009_1365458375_864906 xxxxxx 1438 0.0 1.7 114744 18096 ? SNl 10:42 0:00 /usr/bin/nepomukservicestub nepomukfilewatch xxxxxx 1439 0.0 1.8 114840 18832 ? SNl 10:42 0:00 /usr/bin/nepomukservicestub nepomukfileindexer i.e. 5 entries -------------------------------------------------------------------------------------------------------------------------------------- The F18 system exhibits the same issue and what follows is from the F18 system only. -------------------------------------------------------------------------------------------------------------------------------------- $ kioclient list 'nepomuksearch:/a1.txt' in the home directory does not output anything even before deleting a1.txt in the home directory. -------------------------------------------------------------------------------------------------------------------------------------- $ kioclient list 'nepomuksearch:/hasTag:xyz' in the home directory finds the file in the home directory tagged with tag xyz before deletion but not after. On Tue, Apr 9, 2013 at 9:12 AM, Vishesh Handa <me@vhanda.in> wrote: > https://bugs.kde.org/show_bug.cgi?id=317971 > > Vishesh Handa <me@vhanda.in> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |me@vhanda.in > > --- Comment #4 from Vishesh Handa <me@vhanda.in> --- > Could you please make paste the output of `ps aux | grep nepomuk`. I want > to > see which all Nepomuk processes are running. > > Also, can you find the file via - kioclient list 'nepomuksearch:/filename' > ? I > remember implementing filtering on the nepomuksearch kioslave that will > never > show files that cannot be statted. So, this is a little weird. > > If possible could you also try tagging the file, deleting the file and then > searching for all files with that tag? (You can perform this search either > via > `nepomuksearch:/hasTag:TagName` or by clicking on that tag via the > information > panel or via tags:/TagName/) > > -- > You are receiving this mail because: > You reported the bug. > Thanks for the information. You F17 system is not running Nepomuk correctly. It's missing a number of Nepomuk components. Considering that hasTag:xyz failed to find the file after it was deleted. I'm fairly confident that Nepomuk does not find the file once it has been deleted. Maybe, this is a Dolphin file search thing. Could you try switching off nepomuk ( qdbus org.kde.NepomukServer /nepomukserver quit ) and then try this search process again? After qdbus org.kde.NepomukServer /nepomukserver quit then $ ps aux | grep nepomuk shows only 1 entry xxxxxx 1311 0.0 0.9 93112 10052 ? S 10:42 0:00 /usr/bin/nepomukcontroller -session 1028c1d320b210000136362031000000014500009_1365458375_864906 But the issue persists i.e. a found and deleted file is still found and that whether moved to the KDE trash with or without emptying the trash or deleted from the command line using 'rm filename'. On Tue, Apr 9, 2013 at 1:01 PM, Vishesh Handa <me@vhanda.in> wrote: > https://bugs.kde.org/show_bug.cgi?id=317971 > > --- Comment #6 from Vishesh Handa <me@vhanda.in> --- > Thanks for the information. You F17 system is not running Nepomuk > correctly. > It's missing a number of Nepomuk components. > > Considering that hasTag:xyz failed to find the file after it was deleted. > I'm > fairly confident that Nepomuk does not find the file once it has been > deleted. > > Maybe, this is a Dolphin file search thing. Could you try switching off > nepomuk > ( qdbus org.kde.NepomukServer /nepomukserver quit ) and then try this > search > process again? > > -- > You are receiving this mail because: > You reported the bug. > @Frank - If the file is still found even when Nepomuk is not running, then it's clearly not a Nepomuk problem. Anyway, I'll try to reproduce and see. @Vishesh: yes, you are right, sorry about that. *** Bug 319642 has been marked as a duplicate of this bug. *** I have the same issue with baloosearch. 1. Create a file. 2. Find the file in dolphin. 3. Delete the file. The file is still displayed although now deleted 4. Try to delete again Error message appears because file could not be found. It has been deleted already but is still displayed. Only after refreshing dolphin it seems to work. Confirmed, still a problem. *** Bug 364756 has been marked as a duplicate of this bug. *** *** Bug 203351 has been marked as a duplicate of this bug. *** *** Bug 320378 has been marked as a duplicate of this bug. *** Can you please confirm this still occurs in a recent version of Dolphin. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |