Arch Linux User Repository

First time I built the package it opened in browser, but every time I have tried to open it since I can't connect. Tried removing and rebuilding, but that didn't change anything.

output of systemctl status openlinkhub: × openlinkhub.service - Open source interface for iCUE LINK System Hub, Corsair AIOs and Hubs Loaded: loaded (/usr/lib/systemd/system/openlinkhub.service; enabled; preset: disabled) Active: failed (Result: exit-code) since Sat 2025-02-01 01:56:39 PST; 5s ago Duration: 52ms Invocation: d6b67e4f664c4f67ba8bf532356bd52c Process: 17104 ExecStart=/usr/bin/openlinkhub (code=exited, status=2) Main PID: 17104 (code=exited, status=2) Mem peak: 6M CPU: 6ms

openlinkhub[17104]: OpenLinkHub/src/config.upgradeFile({0xc000236000?, 0xc0002> openlinkhub[17104]: /var/tmp/pamac-build-stiffisharc/openlinkhub/src/openl> openlinkhub[17104]: OpenLinkHub/src/config.Init() openlinkhub[17104]: /var/tmp/pamac-build-stiffisharc/openlinkhub/src/openl> openlinkhub[17104]: OpenLinkHub/src/controller.Start() openlinkhub[17104]: /var/tmp/pamac-build-stiffisharc/openlinkhub/src/openl> openlinkhub[17104]: main.main() openlinkhub[17104]: /var/tmp/pamac-build-stiffisharc/openlinkhub/src/openl> systemd[1]: openlinkhub.service: Main process exited, code=exited, status=2/IN> systemd[1]: openlinkhub.service: Failed with result 'exit-code'.

@jrdn Thanks for the confirmation. I've investigated the integrated udev-rules and assumed that it should work out of the box. But in my case, the usb keyboard is not recognized. The udev-file contains the ID of my keyboard that is 1b1c:1b7c according to lsusb. Do you have any idea? Sorry if I hijack this thread for my personal issues.

@shizzle

This installs the required udev-rules. Upstream contains the udev-rules, and contains a running list of supported hardware. After the package is installed, you still need to start and enable the systemd service.

I'm a bit lost as the original sources are lacking some documentations: Is this a simple "install and go" regarding USB devices or do you have to modify permissions and udev-rules to get it working? I'm currently trying to use it with a K100 keyboard, but it seems not to be detected by openlinkhub.

So far this has worked really nice. A lot EASIER than messing with virtualbox with a Windows VM to mess with iCue. That said, I can't find an option to save the settings to the device (Corsair iCue H100i Elite Capellix XT). Is there an option for device mode like iCue has?

@martin-de

Agreed lsusb should be added as a dependency to the package as it currently is configured. I am waiting on upstream's 0.4.4 to do this more cleanly.

Please note the next PKGUILD will remove the generation script and install a predefined rule file provided upstream. Those rules will cover only intended and supported devices.

Updated PKGUILD will use gnu-install to install the aforementioned udev.rules so we won't generate them there, but we can perform a check for those devices with an install hook. The hook can provide a warning, and instead of utilizing lsusb, we can leverage /sys/bus/usb/devices/*/idVendor

(1) The package cannot be built because the dependency on the usbutils package, which is required for the lsusb call, is missing

(2) After correction, the package still cannot be built because an attempt is made to install files that could not be created in the prepare function: "install: cannot stat 'openlinkhub/openlinkhub.rules': No such file or directory"

Installation packages should always be built so that they can be installed on all systems. It makes little sense to include hardware-specific rules in an installation package that are only to be installed on one system, namely the one on which it was built. The package must therefore always be built on the system on which it is to be installed later. It would be better to create the rules in the .install file, and if the expected devices are not found, a warning can be issued to indicate this.

The dependency for the usbutils package should then be set in the depends array, since it is then only needed at runtime and not for building the package.

Installation user issue resolved. Package updated to v0.4.x. This package update should not require manual intervention for a fresh install, nor upgrading from 0.3.8.x.

Please report any issues.

Note and Changes(s):

1. The service no longer requires root privileges to run.
2. A service user openlinkhub has been created and assigned the uid:gid of 473:473. [1]
3. The systemd service is not automatically enabled. Users are required to manually enable and start the service (e.g. systemctl enable --now openlinkhub)
4. Update required package dependencies (lm_sensors, i2c-tools, systemd)

@orlfman Just noticed this. Was not happening while packaging v3.8.0 originally. I am working a fix now and will have it out shortly.