Bug 399365 - Notification when indexing is running
Summary: Notification when indexing is running
Status: RESOLVED DUPLICATE of bug 374474
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: baloo-bugs-null
: 409881 (view as bug list)
Depends on:
Reported: 2018-10-04 08:05 UTC by Martin Insulander
Modified: 2021-07-09 07:24 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description Martin Insulander 2018-10-04 08:05:53 UTC

When the indexing is running sometimes it will slow the desktop quite much. It is easy to see in the process overview that Baloo file extractors are running, but it would be great with some kind of notification or status icon when it is active.

I think this could lessen the number of angry comments about this cool indexer.


1. restart the baloo indexing (or add a lot of files to the indexed folder)
2. computer goes slow for a while


No indication on why the computer currently slows down for user.


Some kind of notification or icon, only showing when some indexing is done.
Suggested content would be index size, nr of files indexed, total nr of files to index, current indexing file(s).


A link to the settings page for excluding files.

A pause button on it (making it stay in the notifications), but if we assume it mostly works this shouldn't be needed.
Comment 1 Kai Uwe Broulik 2018-10-04 08:18:43 UTC
I think it should rather not slow down the computer. The user shouldn't be aware, let alone be explicitly told, that this is happening imho.
Comment 2 Nate Graham 2020-10-26 17:01:04 UTC
*** Bug 409881 has been marked as a duplicate of this bug. ***
Comment 3 tagwerk19 2021-07-09 07:24:00 UTC
There's a "Status" line and "Pause button" in
    System Settings -> Search -> File Search
In Neon User, 5.83.0.

Patch done in April, see Bug 374474

*** This bug has been marked as a duplicate of bug 374474 ***