Summary: | After making changes, restart Baloo in the background instead of asking the user to reboot | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | Ben Daines <benjamindaines> |
Component: | kcm_baloo | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | wishlist | CC: | baloo-bugs-null, benjamindaines, nate, tagwerk19 |
Priority: | NOR | Keywords: | usability |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Ben Daines
2024-03-14 01:49:52 UTC
> work will be lost when the session is ended Only if you have "confirm logout turned off, which is a non-default setting. > Supposedly this is fixed with Plasma 6 It's fixed for Qt6 apps at least. > I can confirm that merely restarting the user service for kde-baloo is plenty to what needs to be done. That's fine, we can do that instead, but what about people not using Systemd? That use case needs to be considered too. We also may need to kill the worker processes as IIRC at least at some point in the past that didn't happen automatically. If we can handle all those subtleties then it's feasible to remove the message and kust restart the service in the background. (In reply to Nate Graham from comment #1) > ... but what about people not using > Systemd? That use case needs to be considered too. We also may need to kill > the worker processes as IIRC at least at some point in the past that didn't > happen automatically ... On systems with systemd, baloo is started using it (it gets the unit file contraints on the use of RAM). It does seem though that if you stop and restart with with "balooctl disable" and "balooctl enable", it is started as a background process (not controlled by systemd). It's probably worthwhile to give this process management more love: Use systemd functions whereever possible, fall back to old school methods where not. In that case a "systemctl --user restart kde-baloo" (equivalent) ought to do the job... There seems to be a Bug 467531 with some discussion already covering this... ... Marking as duplicate *** This bug has been marked as a duplicate of bug 467531 *** (In reply to tagwerk19 from comment #2) > It's probably worthwhile to give this process management more love: Use > systemd functions whereever possible, fall back to old school methods where > not. In that case a "systemctl --user restart kde-baloo" (equivalent) ought > to do the job... Ref: Bug 488178 |