Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tuxclocker starts with error and no sensors or values listed #100

Open
yreweb opened this issue Oct 6, 2024 · 0 comments
Open

Tuxclocker starts with error and no sensors or values listed #100

yreweb opened this issue Oct 6, 2024 · 0 comments

Comments

@yreweb
Copy link

yreweb commented Oct 6, 2024

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-:[email protected]. 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-:[email protected]: Main process exited, code=exited, status=127/n/a 06/10/2024 08:33 systemd dbus-:[email protected]: Failed with result 'exit-code'.

Does someone experience the sames problem or has a solution ?

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant