Arch Linux User Repository

Post-installation steps:

sudo systemctl enable --now coolercontrold

Then open the desktop application.

Check when installing fails:

    # ...
    Finished release [optimized] target(s) in 3m 28s
==> Starting check()...
packaging/metadata/org.coolercontrol.CoolerControl.metainfo.xml: OK
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/home/kainoa/.cache/yay/coolercontrol/src/coolercontrol-0.17.0/coolercontrol-gui/coolercontrol/__main__.py", line 18, in <module>
    from coolercontrol.coolercontrol import main
  File "/home/kainoa/.cache/yay/coolercontrol/src/coolercontrol-0.17.0/coolercontrol-gui/coolercontrol/coolercontrol.py", line 40, in <module>
    from coolercontrol.services.dynamic_buttons import DynamicButtons
  File "/home/kainoa/.cache/yay/coolercontrol/src/coolercontrol-0.17.0/coolercontrol-gui/coolercontrol/services/dynamic_buttons.py", line 27, in <module>
    from coolercontrol.models.device import Device, DeviceType
  File "/home/kainoa/.cache/yay/coolercontrol/src/coolercontrol-0.17.0/coolercontrol-gui/coolercontrol/models/device.py", line 23, in <module>
    from coolercontrol.models.status import Status
  File "/home/kainoa/.cache/yay/coolercontrol/src/coolercontrol-0.17.0/coolercontrol-gui/coolercontrol/models/status.py", line 22, in <module>
    from dataclass_wizard import LoadMixin, JSONWizard
ModuleNotFoundError: No module named 'dataclass_wizard'
==> ERROR: A failure occurred in check().
    Aborting...
 -> error making: coolercontrol-exit status 4

The GUI won't start. The rest seems to start fine, and I get no errors in the debug.

INFO     coolercontrol.coolercontrol - CoolerControl is initializing...
qt.core.qobject.connect: QObject::connect: No such signal QPlatformNativeInterface::systemTrayWindowChanged(QScreen*)
INFO     coolercontrol.services.notifications - Notification DBus Connection established
INFO     coolercontrol.services.sleep_listener - System DBus connection established: True
INFO     coolercontrol.repositories.daemon_repo - CoolerControl Daemon Repo Successfully initialized
INFO     coolercontrol.coolercontrol - Displaying Main UI Window...

And it just hangs there, no Gui shown.

Edit: nevermind! had a mistake in my makepkg.conf for rust flags.

Failing to build for me:

error: failed to run `rustc` to learn about target-specific information

Caused by:
  process didn't exit successfully: `rustc - --crate-name ___ --print=file-names -C opt-level=2 -C target -cpu=native --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=split-debuginfo --print=crate-name --print=cfg` (exit status: 1)
  --- stderr
  error: Unrecognized option: 'c'

==> ERROR: A failure occurred in build()

With the new icu 73.2-1 compilation is failing:

Traceback (most recent call last): File "<frozen runpy>", line 198, in _run_module_as_main File "<frozen runpy>", line 88, in _run_code File "/media/linux/yay/coolercontrol/src/coolercontrol-0.16.0/coolercontrol-gui/coolercontrol/main.py", line 18, in <module> from coolercontrol.coolercontrol import main File "/media/linux/yay/coolercontrol/src/coolercontrol-0.16.0/coolercontrol-gui/coolercontrol/coolercontrol.py", line 30, in <module> from PySide6 import QtCore ImportError: libicui18n.so.72: cannot open shared object file: No such file or directory

Hi @akiba and @sgtnasty,

There is an often overlooked settings option in both the UI and config file called: Startup Delay

This will add the specified number of seconds of delay to the startup procedure of the daemon(s) itself and should hopefully solve your startup issues.

I haven't run into this problem myself when testing a multitude of devices at the same time, but I have heard this from a few issues raised in GitLab: some devices (no clear culprit) not being completely "ready" to communicate when the service starts right after boot-up. That might be related to the motherboard/usb chip used rather than necessarily the devices themselves, but it's hard to say at this point.

@akiba I can confirm that I have the same issue: * ASUS Aura LED Controller * NZXT Kraken X

Every new startup I have to restart the services for coolercontrol to recognize both.

I noticed that if you have more than one device to control, sometimes an error occurs and coolercontrol not recognize one of devices. In my case, I have Corsair Commander Pro and Corsair Lighting Node Core.

A workaround that I have been testing and seems to have worked is delayed start service on boot.

coolercontrol-liqctld.service
coolercontrold.service

I don't know if it's an isolated case on my system.

Just a heads up, if you were previously holding back pyside6 and shiboken6, make sure you clean reinstall python-dataclass-wizard so that it recompiles against the new versions of these two packages - otherwise you wont pass the CoolerControl check() or package() with a module not found error.

Since python 3.11 I had to do remove and do a clean package build then reinstall python-dataclass-wizard when it fails. Run the install again and it should work this time.

@mrmackie: Thank you, solved my install problem. I also had to (daemon) reload the coolercontrold.service.