Jaroslav Škarvada

Interesting, it seems it's normally stopped. It should work without problem on python-3.10. Could you try running it in the debug mode and in the separate terminal? ``` # tuned...

You need to stop the tuned service before debugging: ``` # systemctl stop tuned ``` and then run `tuned -D`, it's for debugging purposes running on the foreground and logging...

The log seems OK, it seems you stopped TuneD with the Ctrl + C, so the problem is probably not related to the python. The question is why systemd stopped...

OK, I will try to reproduce it. You can also try running it for longer time in the terminal and check whether it keeps running.

Unfortunately, I am unable to reproduce the problem, I installed Manjaro 21.2.1, built and installed tuned-2.16.0-2 from the AUR, set the latency-performance TuneD profile: ``` # tuned-adm profile latency-performance ```...

It's running for me nearly two days without problem. I tried to logout/login several times, it's still OK. You could try editing the `/usr/lib/systemd/system/tuned.service`, changing the `Type` from the `dbus`...

Try the attached patch, then after the TuneD service is "magically" stopped observe the `/var/log/tuned/tuned.log`, there should be something like: ``` 2022-01-14 13:29:58,303 ERROR tuned.daemon.controller: Received SIGTERM from the: 8055,...

Yep, that's systemd. It's providing the /sbin/init. Unfortunately, I have no idea why systemd is stopping the TuneD service. Maybe there is something wrong with your systemd configuration. You could...

And maybe together with the debug journalctl output the following could be also useful: ``` # systemctl show tuned # systemctl is-enabled tuned ```

> (changed back to tuned 2.16.0 without the patch. Type and BusName are back to original. Don't know if it matters) > > ``` > # systemctl show tuned >...