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.

@codifryed upgrading from 1.70 to 1.77 fixed the issue. thank you

Hi @ggnoredo,

I'm unable to reproduce your error and none of our builds have had this issue.

Are you on the latest rust/cargo version of 1.77.1?

error: failed to select a version for `env_logger`.
    ... required by package `coolercontrold v1.2.1 (/home/USERNAME/.cache/yay/coolercontrol/src/coolercontrol-1.2.1/coolercontrold)`
versions that meet the requirements `^0.11.3` (locked to 0.11.3) are: 0.11.3

the package `coolercontrold` depends on `env_logger`, with features: `anstream` but `env_logger` does not have these features.
 It has an optional dependency with that name, but that dependency uses the "dep:" syntax in the features table, so it does not have an implicit feature with that name.


failed to select a version for `env_logger` which could resolve this conflict
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: coolercontrol-exit status 4

Hi @blackhole,
Hmm, I'm not sure where to start, other than this looks like a support issue and not an AUR package issue. Please create a ticket on the project page.

Some quick notes:
- All daemon configuration files are stored under /etc/coolercontrol/. If you haven't overwritten it, all your profiles are stored there.
- Login doesn't affect the daemon, only the UI connection.
- At first it sounds like the configuration got corrupted somehow, or something changed unexpectedly and the daemon doesn't know how to deal with it. Moving/deleting all your configuration files and starting fresh is an option, then copying over specific things like your profile if things work again. If there is a software issue then this needs some deeper debugging to find out what the issue is and it's not something that's happened in testing so far.

I cannot edit profiles any more. I have changed password and login is successful.

What I see in systemd status:

feb 23 08:58:15 archlinux coolercontrold[10215]: No Duty Set AND Safety latch triggered. This should not happen.

etc.

Before was working fine, reinstalled the package but still cannot edit or recover previous configuration for NZXT smart device v2

@texer22

If it says "Admin Access", then you're logged in as admin and should be able to create profiles. I see that IPv6 is blocked, but if "localhost" resolves only to your IPv4 address then there shouldn't be a problem. At this point I would suggest opening a proper bug ticket on the GitLab project page.

There are no openrc service files nor systemd service files for the Coolero Flatpak. Coolero was a completely different implementation without proper service daemons and the two phases of this project no longer share any code.

No, it says Admin Access and "Login" is inactive, only "Set New Password" is active. I have two errors

(WARN  coolercontrold::api] Failed to bind to loopback ipv6 address: Address family not supported by protocol (os error 97) because I blocked IPv6.

Second error

[2024-02-01T18:00:03Z ERROR coolercontrold::repositories::liquidctl::liqctld_client] Could not establish socket connection to coolercontrol-liqctld, retry #1 - No such file or directory (os error 2)
[2024-02-01T18:00:04Z ERROR coolercontrold::repositories::liquidctl::liqctld_client] Could not establish socket connection to coolercontrol-liqctld, retry #2 - No such file or directory (os error 2)
[2024-02-01T18:00:05Z ERROR coolercontrold::repositories::liquidctl::liqctld_client] Could not establish socket connection to coolercontrol-liqctld, retry #3 - No such file or directory (os error 2)
[2024-02-01T18:00:06Z ERROR coolercontrold::repositories::liquidctl::liqctld_client] Could not establish socket connection to coolercontrol-liqctld, retry #4 - No such file or directory (os error 2)
[2024-02-01T18:00:07Z ERROR coolercontrold::repositories::liquidctl::liqctld_client] Could not establish socket connection to coolercontrol-liqctld, retry #5 - No such file or directory (os error 2)
[2024-02-01T18:00:08Z ERROR coolercontrold] Error initializing LIQUIDCTL Repo: Failed to connect to coolercontrol-liqctld after 5 tries

I tried on VM and I get warning that connection to a CoolerControl daemon could not be established. Why there are openrc service files for Coolero on the flathub but not here?
Coolercontrold
Coolercontrol-liquidctl-daemon

I use portmaster so maybe there is some more security toward loopback but I haven't found any settings.

@texer22 Hmmm. If you open the Access Protection menu in the top right - and if it says "Guest" - try clicking on Log In to see if it then logs you in automatically.

Unfortunately, I can't reproduce your issue. I even fired up a fresh Artix install in a VM and both UIs connect and work fine. (Firefox for the Web UI) Do you have some extra security setup for your loopback interface by any chance?

@codifryed Ok, the alternative works for me! Thanks. Now, I cannot login and add any new profiles. It says "invalid credentials".

@texer22 That looks like the Desktop App coolercontrol isn't able to find a free port on your system to render the UI, and I'm not sure why.

As an alternative, once you have coolercontrol-liqctld and coolercontrold running on Artix you can open the daemon Web UI at http://localhost:11987/