Someone have a solution for this problem?
Hi @RayonRa I solved the issue all I did was disabling the baloo, purge all the the indexed data and the enable it again.
balooctl disable
balooctl purge
and for safety I removed also the index-lock file in .local/share/baloo
balooctl enable
The files now are indexed and the ghost document is gone
Hi @sergiupopescu, when i execute balooclt enable, i have this error:
“Error (2448): No current point in closepath”
“Error (2571): No current point in closepath”
“Error (2671): No current point in closepath”
“Error (2731): No current point in closepath”
“Error (2802): No current point in closepath”
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x556883787680] st: 0 edit list: 1 Missing key frame while searching for timestamp: 0
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x556883787680] st: 0 edit list 1 Cannot find an index entry before timestamp: 0.
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x556883787680] st: 0 edit list: 2 Missing key frame while searching for timestamp: 1000
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x556883787680] st: 0 edit list 2 Cannot find an index entry before timestamp: 1000.
And the ghost file is always here.
@RayonRa I talked to a KDE contributor, the 5.77 version of baloo in broken, the 5.78 will be fixed
2 Likes
@sergiupopescu Thank you so much. I will wait for the new version. Thanks again.
1 Like
I am still having this issue too, even with version 5.78 of baloo and following the above steps.
EDIT: I found on the Arch wiki that one needs to logout and login again after disabling baloo. Maybe that is the trick to be rid of this ghost document? I will try to remember to report back once I’m convinced this procedure worked.
Yes, I am still having this issue too.
I’ll wait for your test. 
I can say that I am cautiously optimistic that it worked. Logging out after disabling baloo I think was the missing step to fix this issue. So log back in and enable, and hopefully that ghost file will be gone for good for both of us. 
