Summary: | Balooctl enable revisited... | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-baloo | Reporter: | tagwerk19 |
Component: | balooctl | Assignee: | Stefan BrĂ¼ns <stefan.bruens> |
Status: | REPORTED --- | ||
Severity: | minor | CC: | baloo-bugs-null, nate |
Priority: | NOR | ||
Version: | 5.80.0 | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
tagwerk19
2021-04-03 16:27:19 UTC
Hmm, cannot reproduce. That's pretty strange. I see reproducable behaviour. I did have a surprise though when I stepped through the "Steps to Reproduce" on a Neon Testing "Live" edition. Neon Testing 20210330 Live (5.81.0) balooctl disable balooctl enable Worked as it ought to.... Neon Testing 20210330 Installed (5.81.0) balooctl disable balooctl enable balooctl enable That second "enable" is needed... I looked back though a collection of older Neon Testing ISO's, it was the same behaviour (5.80.0, 5.79.0, 5.76.0, 5.72.0). A "Live" install worked but as soon as I installed to disc the behaviour changed and I needed to "balooctl enable" twice. The behaviour was the same with Installed-to-disc Fedora 33 and 34 Beta Maybe interesting, on the "Live" image you don't get the "Baloo File Indexing has been disabled" message when enabling, it's just: $ balooctl disable Disabling and stopping the File Indexer $ balooctl enable Enabling and starting the File Indexer $ ps ax | grep baloo 1596 ? SNl 0:00 /usr/bin/baloo_file 1601 pts/1 S+ 0:00 grep --color=auto baloo |