I have seen the same, many users are still reporting this issue at the start of 2025.
While the 't' process does eventually close without having to kill it manually, it delays a clean shutdown significantly.
I can think of many situations where this is less than convenient, foremost when shutting down on a power plan when the battery level is low and this results in an unclean shutdown.
To be honest, why does this process take so long to close is the question we should be asking Logitech?
I have monitored the process activity and see it does perform a call home (observed in network activity and trace dumps from the router).
This means this process is for Logitech's benefit and not the owner of the device.
I have seen the same, many users are still reporting this issue at the start of 2025.
While the 't' process does eventually close without having to kill it manually, it delays a clean shutdown significantly.
I can think of many situations where this is less than convenient, foremost when shutting down on a power plan when the battery level is low and this results in an unclean shutdown.
To be honest, why does this process take so long to close is the question we should be asking Logitech?
I have monitored the process activity and see it does perform a call home (observed in network activity and trace dumps from the router).
This means this process is for Logitech's benefit and not the owner of the device.