tuxclocker icon indicating copy to clipboard operation
tuxclocker copied to clipboard

Couldn't connect to TuxClocker daemon: Could not activate remote peer: unit failed.

Open mvrxxx opened this issue 11 months ago • 3 comments

I installed tuxclocker by cloning and installing the AUR package and i was getting the error "Couldn't connect to TuxClocker daemon: Not connected to D-Bus server" at start.

Now i have uninstalled tuxclocker and installed it following the instructions in the readme and adding -Dplugins=true as meson option but when i try to open the application from KDE's application list it does not open and when i try to open it with tuxclocker-qt command it opens with the error "Couldn't connect to TuxClocker daemon: Could not activate remote peer: unit failed."

I am on arch linux with kernel 6.7.8-arch1-1 and i have installed the qt5 dependencies

mvrxxx avatar Mar 06 '24 20:03 mvrxxx

"Couldn't connect to TuxClocker daemon: Not connected to D-Bus server"

This error likely means that the TuxClocker DBus service isn't running, or wasn't able to register. See what running tuxclockerd as root outputs.

Lurkki14 avatar Mar 06 '24 21:03 Lurkki14

"Couldn't connect to TuxClocker daemon: Not connected to D-Bus server"

This error likely means that the TuxClocker DBus service isn't running, or wasn't able to register. See what running tuxclockerd as root outputs.

Still getting the same error but now in the terminal i get this error: "QStandardPaths: runtime directory '/run/user/1000' is not owned by UID 0, but a directory permissions 0700 owned by UID 1000 GID 1000"

mvrxxx avatar Mar 07 '24 18:03 mvrxxx

I have the same issue on pop os 22.04, tuxclocker has never worked for me.

burd1 avatar Mar 23 '24 21:03 burd1