Arch Linux User Repository

With the release of 1.4.1 CoolerControl has now been spit up into several packages. This requires users to uninstall and then reinstall the application.

See: https://gitlab.com/coolercontrol/coolercontrol/-/issues/347

There's an upside, there's now a binary AUR package coolercontrol-bin for less compile time!

Post-installation steps:

sudo systemctl enable --now coolercontrold

Then open the desktop application.

One additional issue though: This PKGBUILD should not use the any CPU architecture, but rather the x86_64 architecture, because /usr/bin/coolercontrold is an actual ELF binary and not just a python script.

Also, it might make sense to depend not simply on python, but rather on python>=3.11 and python<3.12, because the built package would clearly break if the python package was to be upgraded to a non-3.11.x version.

codifryed: Oh sorry, you're absolutely right about python-pyqt6 not being used/necessary because pyside6 is used instead. I had misinterpreted the output of the tooling that I was using (basically https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot#Convenience_way, but modified such that than an additional custom repo of mine is used to allow for building AUR packages that depend upon other AUR packages).

Thanks, I'll update those @hardfalcon.

One I question though is python-pyqt6. pyside6 and pyqt6 are completely separate implementations and there should be no dependency there. There's definitely no direct dependency from this package at least.

As of coolercontrol 0.17.1-1, this PKGBUILD lacks the following packages in its depends array:

gcc-libs
glibc
python-colorlog
python-dateutil
python-pillow
python-pydantic
python-pyqt6
python-urllib3

Also, the polkit dependency can probably be removed because the coolercontrol package doesn't contain any files within the /usr/share/polkit-1 directory tree.

@That1Calculator

Try doing a clean and then reinstalling python-dataclass-wizard. Then install CoolerControl again. That worked for others who faced the ModuleNotFoundError: No module named 'dataclass_wizard' issue in the past.

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.