https://bugs.kde.org/show_bug.cgi?id=488178
Bug ID: 488178
Summary: Baloo file daemon started using outdated QProcess API
Classification: Frameworks and Libraries
Product: frameworks-baloo
Version: 6.3.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Baloo File Daemon
Assignee: baloo-bugs-n...@kde.org
Reporter: k...@davidedmundson.co.uk
Target Milestone: ---
Baloo is started manually in the following places with QProcess::startDetached
- balooctl
- qml monitor bindings
- kcm (plasma-desktop)
This is problematic as it skips all features systemctl --user kde-baloo.service
provides.
I strongly suspect this is how we end up with services not cleaned up properly.
This all needs porting to systemd startUnit/stopUnit with QProcess as a
fallback for legacy support.
relevant code will be:
```
auto msg =
QDBusMessage::createMethodCall(QStringLiteral("org.freedesktop.systemd1"),
QStringLiteral("/org/freedesktop/systemd1"),
QStringLiteral("org.freedesktop.systemd1.Manager"),
QStringLiteral("StartUnit"));
msg << "kde-baloo.service" << QStringLiteral("fail");
auto msg =
QDBusMessage::createMethodCall(QStringLiteral("org.freedesktop.systemd1"),
QStringLiteral("/org/freedesktop/systemd1"),
QStringLiteral("org.freedesktop.systemd1.Manager"),
QStringLiteral("StopUnit"));
msg << QStringLiteral("kde-baloo.service") << QStringLiteral("fail");
QDBusConnection::sessionBus().call(msg);
```
--
You are receiving this mail because:
You are watching all bug changes.
