Description of problem: kf5-baloo doesn't depend on kf5-baloo-file, which makes balooctl give useless messages about "baloo index could not be opened" and desktop search be broken. Installing KDE after installing the normal fedora workstation with GNOME does not install kf5-baloo-file (only kf5-baloo is installed) and this happens. Steps to Reproduce: · Try to search · Try to do anything with balooctl Actual results: borked Expected results: working baloo Additional info: Installing KDE after installing the normal fedora workstation with GNOME does not install kf5-baloo-file (only kf5-baloo is installed) and this happens.
It is intentional that kf5-baloo-file can be not installed. That said, perhaps the best course is to move balooctl to the -file sub-package as well.
Boy, too early and not enough coffee. I meant "intentional that kf5-baloo-file can be uninstalled"
And, when you say "Installing KDE after installing the normal fedora workstation with GNOME does not install kf5-baloo-file". How did you install KDE exactly? kf5-baloo-file is present in the comps 'kde-desktop' group, https://pagure.io/fedora-comps/blob/master/f/comps-f28.xml.in#_3608
Looking closer, it appears other binary tools in kf5-baloo main package, baloosearch balooshow have similar issues, in that they don't make much sense without -baloo-file either. Moving those to -file as well means the main package will end up essentially empty. If that's the path we want to take, then it probably makes sense to get rid of -libs subpkg and consolidate it's content into main.
(In reply to Rex Dieter from comment #3) > And, when you say "Installing KDE after installing the normal fedora > workstation with GNOME does not install kf5-baloo-file". How did you > install KDE exactly? > > kf5-baloo-file is present in the comps 'kde-desktop' group, > https://pagure.io/fedora-comps/blob/master/f/comps-f28.xml.in#_3608 sorry I don't remember but I probably screwed up then! but anyways the things you say in #4 are true so just one kf5-baloo package makes sense.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.