Tuxclocker starts with error and no sensors or values listed

[yreweb]

After the latest update batch on manjaro, tuxclocker starts with "Couldn't connect to TuxClocker daemon: Could not activate remote peer 'org.tuxclocker': unit failed" message and empty window.

It seems to be dbus related.

The logs

06/10/2024 08:33 systemd Started TuxClocker - Overclocking Tool. 06/10/2024 08:33 systemd Started dbus-:1.2-org.tuxclocker@2.service. 06/10/2024 08:33 tuxclockerd /usr/bin/tuxclockerd: symbol lookup error: /usr/lib/libtuxclocker.so: undefined symbol: _ZN5boost10filesystem6detail10equivalentERKNS0_4pathES4_PNS_6system10error_codeE 06/10/2024 08:33 systemd dbus-:1.2-org.tuxclocker@2.service: Main process exited, code=exited, status=127/n/a 06/10/2024 08:33 systemd dbus-:1.2-org.tuxclocker@2.service: Failed with result 'exit-code'.

Does someone experience the sames problem or has a solution ?

Thanks.

[brenoepics]

+1

[datante]

+1

Do you have a solution yet?

[yreweb]

No