Baloo file extractor linux

Saved searches

Use saved searches to filter your results more quickly

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Baloo is a framework for searching and managing metadata.

KDE/baloo

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Sign In Required

Please sign in to use Codespaces.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio Code

Your codespace will open once ready.

There was a problem preparing your codespace, please try again.

Latest commit

Git stats

Files

Failed to load latest commit information.

README.md

Baloo is the file indexing and file search framework for KDE Plasma. It focuses on speed and a very small memory footprint. It maintains an index of your files and optionally their contents which you can search.

Baloo is part of the KDE umbrella and relies on the KDE infrastructure.

Mailing List: kde-devel@kde.org (info page) Bug Tracker: http://bugs.kde.org (new bug) IRC Channel: #kde-baloo on Libera Chat

The recommended way of contributing patches is via KDE’s GitLab instance.

Baloo relies on KFileMetaData to extract content and metadata from files. KFileMetadata uses a number file type specific plugins. In case individual plugins are packaged separately, we recommend installing all plugins.

Without the indexer plugins, Baloo cannot function to its full potential.

Baloo is developed and tested exclusively for Linux. While it may run on other unix based systems. It is not recommended, and certainly not tested.

We do not recommend to package Baloo for Windows or OSX as both these operating systems offer their own file searching solutions which better integrate with the native system than Baloo ever will.

Baloo may run on 32-bit systems, but it has not been tested and may not work correctly. Please test and let us know by filing a bug.

Supported Kernels: Linux Supported Architectures: x86_64, aarch64 Supported Filesystems: ext3/4, Btrfs, XFS

Packaging the indexer service

The service is an autostarted, session wide background service. In case KF5 and KF6 versions of the Baloo libraries are installed, both will use the same service and database.

Only one version of the service autostart file and associated binaries should be installed at a time, i.e. the baloo_file.desktop service definition, the baloo_file service binary, the baloo_file_extractor helper, and the balooctl tool.

Building of the service can be disabled using the BUILD_INDEXER_SERVICE CMake option.

About

Baloo is a framework for searching and managing metadata.

Источник

Что делает экстрактор файлов baloo?

Как упоминалось в , этот вопрос и ответ, экстрактор файлов baloo часто случайным образом появляется в фоновом режиме в KDE Plasma и потребляет много циклов процессора. .

Ответ гласит, что отключить балу безопасно.

Что делает балу? Отключит ли он функции поиска / извлечения файлов в дельфине, если я отключу baloo?

1 ответ

Baloo является частью рабочего стола KDE Plasma. В частности, это фреймворк для индексации файлов и поиска файлов для KDE Plasma . Baloo — это не приложение, а демон для индексации файлов. Приложения могут использовать платформу Baloo для предоставления результатов поиска файлов. Вы можете узнать больше о Baloo в вики сообщества KDE .

Да, вы можете безопасно удалить или отключить Baloo, но если вы собираетесь искать с помощью инструментов KDE, вам, вероятно, не следует.

Я рад, что вы связались с этим вопросом, потому что, хотя на него есть хороший / принятый ответ, у меня есть проблема с самим вопросом. Вопрос подразумевает, что, поскольку демон использует фоновую оперативную память, система работает медленнее, и поэтому следует удалить. Это может стать скользкой дорожкой, когда кто-то может захотеть начать методически отключать процессы, чтобы снизить использование ОЗУ.

На самом деле это контрпродуктивно, потому что обычно верно обратное: демоны, которые выполняют такие задачи, как индексирование поиска и кеширование, могут значительно увеличиваться скорость результатов поиска, когда вы их запрашиваете. Есть поговорка: « Неиспользованная RAM — это потраченная впустую RAM ». Если ваша система не испытывает недостатка в оперативной памяти, я бы не стал беспокоиться о процессах, использующих ее, и посоветовал бы не отключать службы по причине уменьшения использования оперативной памяти. То же самое в целом справедливо и для использования ЦП, если это происходит в фоновом режиме и не мешает другим процессам.

Как упоминалось в комментариях,

Источник

Is it safe to disable baloo_file_extractor in KDE Plasma 5?

Today after upgrading to Ubuntu 18.04, I found baloo_file_extractor consuming too much RAM and causing my laptop to slow down. I can temporarily fix this by running balooctl disable . I did a little googling and found out that it related to KDE which is weird I am using GNOME. So is it safe to disable it or remove it altogether? If not, is there a way to make it not consume too much RAM?

Same problem. In my case it was installed when I tried digikam + piki-plugins. I purged both with apt + autoremove but a hell of libraries remained, including dolphin, konqueror and baloo…

It seems the problem was konqueror, automatically installed by apt because it is recommended by piki-plugins (and recommended packages are usually not removed by apt…). Had to manually remove it, and then autoremove took care of libkf5baloo* and many others. [I am still tracking other recommended libraries not removed by apt, such as libkf5configcore5…]. Use an AppImage! 🙁

2 Answers 2

It’s safe to use balooctl disable .

You need to be careful while installing software. Pay attention to what’s being installed and to what’s being pulled in by way of dependencies. For example, you may have installed dolphin , the file manager. That would pull in libkf5baloo5 and libkf5baloowidgets5 among other things. gwenview , an image viewer, would pull in libkf5baloo5 .

If you’re interested in chasing things down, run apt rdepends libkf5baloo5 and apt rdepends libkf5baloowidgets5 and examine the output for software packages you may have on your system.

Under normal circumstances in Kubuntu 18.04, which includes baloo by default, use of resources is minimal after the initial indexing process. RAM and CPU usage are not normally a concern. But there are reports of baloo running amok even on pure Kubuntu! I use it without problems for indexing both filenames and file contents.

Источник

What does baloo file extractor do?

As mentioned in this question and answer, baloo file extractor often randomly pops up in the background in KDE Plasma, and consumes a lot of CPU cycles. The answer says that it is safe to disable baloo. What does baloo do? Will it disable file search/extract features in dolphin if I disable baloo?

On a side note, it is not sufficient to kill baloo_file_extractor , it will spawn immediately again. The command to kill baloo seems to be: killall -9 baloo_file_extractor baloo_file baloorunner

1 Answer 1

Baloo is part of the KDE Plasma desktop. Specifically, it is the file indexing and file search framework for KDE Plasma. Baloo is not an application, but a daemon to index files. Applications can use the Baloo framework to provide file search results. You can learn more about Baloo in the KDE Community Wiki.

Yes, you can safely remove or disable Baloo, but if you intend to search using KDE tools, you probably shouldn’t.

As mentioned in the comments, it has been verified by OP that file search in Dolphin works after disabling Baloo, but file search in KRunner does not work anymore.

I’m glad that you linked to this question, because while it has a good top/accepted answer, I have issue with the question itself. The question implies that because the daemon uses background RAM, that the system runs slower, and therefore should be removed. This can become a slippery slope where one might want to start methodically disabling processes to get the RAM usage lower.

In fact, this is counterproductive because the opposite is usually true: daemons that perform tasks like search indexing and caching can dramatically increase the speed of search results when you call for them. There’s a saying: «Unused RAM is wasted RAM«. Unless your system is starved for RAM, I would not worry about processes using it, and would advise against disabling services for the reason of reducing RAM usage. The same is also generally true for CPU usage if it’s happening in the background and not interfering with other processes.

Источник