https://bugs.kde.org/show_bug.cgi?id=511123
Bug ID: 511123
Summary: KDE File Search dialog shows incorrect status of
baloo__file_ext
Classification: Frameworks and Libraries
Product: frameworks-baloo
Version First unspecified
Reported In:
Platform: KDE Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
SUMMARY
The "System Settings" -> Search -> "File Search" dialog status shows
"Not running, 0% complete" at the bottom status line, but simultaneously shows
"Pause Indexer" with the double bar pause icon at the top right.
At the same time, "top" from the bash command line shows that both the
"baloo_file_ext" and "baloo_file" are in fact running and using CPU.
STEPS TO REPRODUCE
1. Open the System Settings -> Search -> "File Search" dialog
2. If file indexing is not running, start it via the "Resume Indexing" button
at the top right.
3. Let run for some period of time (how much time required is unknown)
4. Return to search dialog window.
5. Observe the discrepancy in the status of the file indexing.
OBSERVED RESULT
System Settings -> Search -> "File Search" dialog shows that file indexing is
_not_ running, but the top right of the dialog displays the "Pause Indexer"
button, implying that file indexing _is_ running.
And, in fact, file indexing _is_ running per the output of "top" in a bash
shell window.
EXPECTED RESULT
The System Settings -> Search -> "File Search" dialog should show consistent
state of file indexing activity.
SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 42
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.19.0
Qt Version: 6.9.2
Kernel Version: 6.17.4-200.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7840HS w/ Radeon 780M Graphics
Memory: 32 GiB of RAM (27.1 GiB usable)
Graphics Processor: AMD Radeon 780M Graphics
ADDITIONAL INFORMATION
The "Locations" pane in the "System Settings" -> Search -> "File Search" dialog
shows the following locations:
/home/rhimbo Indexed
/home/rhimbo Not indexed
I don't know why it appears twice. And I don't know if this is the cause of
any problems.
I have two external HDD that I use for back up (via rsync) and swap partitions.
I _believe_ these are not (should not) be indexed as the partitions on those
drives are all mounted on mount points that begin with the prefix
"/mnt/disk..." so /home/rhimbo should not be indexing the external drives.
However, when the output of "top" indicates that "baloo_file_ext" and
"baloo_file" are running, the access lights are blinking on the external drives
even though the progress status line is not updating on the "System Settings"
-> Search -> "File Search" dialog.
I was not sure under which Product to file this bug:
Baloo File Daemon
balooctl
general
I filed under "general" following other bugs that I searched on baloo_file_ext
before filing this bug.
--
You are receiving this mail because:
You are watching all bug changes.
