This is a bug in version 1 of mediascanner. It has been fixed in version 2. Once we switch versions (hopefully soon, will definitely be in 14/04) then this issue will go away (assuming the Dash reacts correctly to invalidated result sets, which I think it already does).
We don't plan on fixing v1 as that would take quite a lot of effort and the real solution is moving to v2.
This is a bug in version 1 of mediascanner. It has been fixed in version 2. Once we switch versions (hopefully soon, will definitely be in 14/04) then this issue will go away (assuming the Dash reacts correctly to invalidated result sets, which I think it already does).
We don't plan on fixing v1 as that would take quite a lot of effort and the real solution is moving to v2.