On Thu, 2024-12-19 at 09:09 +1100, Stephen Morris wrote: > > > Then anecdotally, I've just updated a system, restarted a service tracer > > > has identified (as you have), tracer still tells me that it needs > > > restarting because the calculated delta hasn't changed, despite the service > > > being restarted? > > It definitely does change tracer's output. I use this on a daily basis. > > Any time I restart something and check again with 'tracer' it notices > > and doesn't flag the service or app. I suspect a documentation bug. It > > doesn't seem to me that it's checking against boot time but against the > > last time the service or app was updated, which makes more sense. > > Yes, but why would it suggest restarting an applications that are > possibly not actually running, as the command shows akonadi wasn't > running, so why produce a message that it needs restarting? > > No idea. I haven't seen that myself. Possibly Akonadi was running when tracer checked, but then stopped for some reason, but I don't know. > Just on that front and slightly off topic to this question, I've had > tracer tell me I need to manually restart Plasma Shell, how does one > actually do that without rebooting the system or without the restart of > that forcing a reboot? You can just log out and in again. A reboot is not necessary and restarting plasmashell will not trigger it. Alternatively: $ systemctl restart --user plasma-plasmashell poc -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
