953972 – kde-frameworks/baloo not enough memory using systemd

Bug 953972 - kde-frameworks/baloo not enough memory using systemd

Summary: kde-frameworks/baloo not enough memory using systemd

Status:	UNCONFIRMED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	Normal normal
Assignee:	Gentoo KDE team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2025-04-17 20:27 UTC by Dr. Peer Griebel
Modified:	2025-04-17 20:31 UTC (History)
CC List:	0 users

See Also:	https://bugs.kde.org/show_bug.cgi?id=502641
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Dr. Peer Griebel 2025-04-17 20:27:44 UTC

baloo hangs because it does not get enough memory by systemd.
The supplied value is 512M.  This is far to low (at least for my system).

Reproducible: Always

Steps to Reproduce:
1. restart baloo via systemd
2. baloo hangs
3. restart
Actual Results:  
baloo hangs during indexing the files.

Expected Results:  
baloo should finish until state idle.

I reported this bug to kde. See: https://bugs.kde.org/show_bug.cgi?id=502641
There I gut the crucial hint.

Comment 1 Sam James archtester

2025-04-17 20:31:32 UTC

Thanks for the report.

I don't think you should close the upstream bug. That limit isn't set by us -- we don't modify the systemd unit at all. We *could* start modifying it as a workaround but it still needs to be resolved properly upstream.