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.

Latest python update has created a warning.

[2026-01-11T23:43:15Z WARN coolercontrold] Python Environment Error: Python liquidctl system package not detected

I will investigate how we can make this more reliable. In the meantime, makepkg's --nocheck flag can be used as a workaround (see --mflags arg if you're using helpers).

I have the same issue aequilibrium had, where the check fails.

I’ve tracked the build failure down to the AppStream validation step.

appstream-util validate-relax times out after 5 seconds when fetching the GitLab raw screenshot URL:

Resolving timed out after 5000 milliseconds

The URL itself is valid and loads fine in a browser, but GitLab’s raw CDN intermittently responds too slowly for AppStream’s strict timeout. This makes the build nondeterministic on both coolercontrol and coolercontrol-bin.

Since AppStream URL validation depends on external network conditions, would you consider making the check() step nonfatal or disabling the network-dependent validation (e.g., --nonet)? This would avoid transient CDN timeouts causing package build failures.

@slimljim192 libsodium is in CoolerControl's dependency tree. You may have a broken AUR package messing up the versions, probably an ffmpeg variant.

Hi, about make -C build -j8 please don't specify the number of the makejobs; that's up to the users makepkg.conf

Please add libsodium as a dependency. Coolercontrol does not launch or compile without it.

coolercontrol: error while loading shared libraries: libsodium.so.26: cannot open shared object file: No such file or directory

I tried again, still working on my end. Lets see if anyone else will have this issue over time.

Just to note: if you ran yay -Sc while coolercontrol was installed, then that wouldn't clear coolercontrol's cached packages. You should either run yay -Scc (this would clear all packages' cache, installed or not) or uninstall coolercontrol before running yay -Sc.

Also, it looks like your error is related to DNS resolution. If you can access gitlab.com on your browser, I suggest trying to curl it on the terminal. Your browser might be using a different DNS resolver.

@caferen Thank you for the extremely timely response. I am using an aur helper, i was using yay to install the package, and I just did yay -Sc and tried to rebuild it but it ended up in the same error. I really am not sure what the issue is, but as I previously mentioned I simply commented out the "appstream-util validate-relax "packaging/metadata/$_app_id.metainfo.xml"" check and it compiled and built fine. I guess its just one of those works for me, but not for you bits haha. In any case, I could just add this to ignorePkg and manually update it with new releases. Btw, props on the project guys, it really is a cool app, and the issue made me look at the gitlab, cctv seems like a very cute utility add to a rice!

hi @aequilibrium, the url is accessible on my end too and I can't reproduce the issue.

How are you installing the package? If you're using an AUR helper, it sometimes helps to clear the cache.

I suggest first trying to install the application manually and if that also does not work, opening an issue on the repository so we can have a look at the full output.