| Summary: | Baloo crashes despite being disabled | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-baloo | Reporter: | Lukas Kucharczyk <lukas> |
| Component: | Baloo File Daemon | Assignee: | baloo-bugs-null |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | crash | CC: | tagwerk19 |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 6.3.0 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Lukas Kucharczyk
2024-07-19 06:05:16 UTC
> ... I have Baloo disabled ...
It'd be worth checking to see if Baloo is really disabled and staying disabled... Look at the config file:
~/.config/baloofilerc
If disabled, that should include lines:
[Basic Settings]
Indexing-Enabled=false
Check for a process, "pgrep -l baloo". If you are on system is based round systemd, you can also try "systemctl --user status kde-baloo".
Doublecheck after a reboot (or a software update), just in case the settings have been reverted. If you are on an immutable distribution (?), life may be more complicated...
Maybe some overlap with Bug 481101 I have checked and it seems disabled and not running:
grep Indexing ~/.config/baloofilerc
Indexing-Enabled=false
systemctl --user status kde-baloo.service
○ kde-baloo.service - Baloo File Indexer Daemon
Loaded: loaded (/usr/lib/systemd/user/kde-baloo.service; disabled; preset: disabled)
Drop-In: /usr/lib/systemd/user/service.d
└─10-timeout-abort.conf
Active: inactive (dead) (Result: exec-condition) since Fri 2024-07-19 07:53:54 CEST; 1h 27min ago
Condition: start condition unmet at Fri 2024-07-19 07:53:54 CEST; 1h 27min ago
Process: 2243 ExecCondition=/usr/bin/kde-systemd-start-condition --condition baloofilerc:Basic Settings:Indexing-Enabled:true (code=exited, status=1/FAILURE)
CPU: 5ms
čec 19 07:53:54 nobara-pc systemd[1860]: Starting kde-baloo.service - Baloo File Indexer Daemon...
čec 19 07:53:54 nobara-pc systemd[1860]: kde-baloo.service: Skipped due to 'exec-condition'.
čec 19 07:53:54 nobara-pc systemd[1860]: Condition check resulted in kde-baloo.service - Baloo File Indexer Daemon being skipped.
pgrep -l baloo reports nothing running.
(In reply to Lukas Kucharczyk from comment #3) > ... I have checked and it seems disabled and not running ... That sounds good then... What you might have had is the system catching up with reporting "old" crash dumps (not sure what process does the reporting, but you can look at the dumps with coredumpctl). We can close this then? In coredumctl I see the latest crashes from 2024-07-18 even though they were reported to me yesterday and today as well so I think you're right, we can close this. (In reply to Lukas Kucharczyk from comment #5) > In coredumctl I see the latest crashes from 2024-07-18 even though they were > reported to me yesterday and today as well so I think you're right, we can > close this. Will do ... Thank you for the report and putting in the time to troubleshoot. |