Package Details: openrgb-git 0.9.1233.g1809c75-1

Git Clone URL: https://aur.archlinux.org/openrgb-git.git (read-only, click to copy)
Package Base: openrgb-git
Description: Configuration utility for RGB lights supporting motherboards, RAM, & peripherals
Upstream URL: https://gitlab.com/CalcProgrammer1/OpenRGB
Keywords: led
Licenses: GPL-2.0-only
Conflicts: openrgb
Provides: openrgb
Submitter: Myrddin
Maintainer: CalcProgrammer1
Last Packager: CalcProgrammer1
Votes: 34
Popularity: 0.023037
First Submitted: 2020-02-14 03:47 (UTC)
Last Updated: 2025-02-16 20:54 (UTC)

Dependencies (6)

Required by (15)

Sources (3)

Pinned Comments

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »

gardotd426 commented on 2020-07-06 18:41 (UTC)

@Myrddin, where did you see that i2c-piix4-aura-dkms was upstreamed?

Also, I have a humble suggestion about the included .desktop file. Change Exec=bash -c 'cd $HOME/.config/OpenRGB && openrgb' to Exec=bash -c 'cd ~/.config/OpenRGB && openrgb'.

Some desktop environments refuse to launch your version, such as Deepin (I guess because they have trouble getting the $HOME variable for some reason) and therefore WILL NOT launch OpenRGB (you have to launch it from the terminal). But using the tilde (~) is effectively the exact same thing (cd ~ and cd $HOME do the same thing) and it actually works on these desktop environments. Alternatively, just remove the cd part and just exec openrgb. The same config is loaded regardless, I just tested by launching from the terminal in a completely different directory, and my saved profiles were still present. So definitely either change the $HOME to a ~ or just remove that part and have it be Exec=openrgb

zoidby commented on 2020-07-04 23:14 (UTC) (edited on 2020-07-04 23:17 (UTC) by zoidby)

This is the output of uname -a

Linux arch 5.7.7-arch1-1 #1 SMP PREEMPT Wed, 01 Jul 2020 14:53:16 +0000 x86_64 GNU/Linux

If i don’t install i2c-piix4-aura-dkms, no hardware shows up at all. Not the board, not the ram.

Like i said, the issue with 99-openrgb.rules is fixed. The remaining problem is that i2c-piix4-aura-dkms has to be installed. And i am not even sure if that is a problem or related to this package.

Myrddin commented on 2020-07-04 23:06 (UTC)

zoidby, are you certain you're booting with the newer kernel version? Check with uname -a that you're using the newer kernel. Assuming you are booting the newer kernel, what hardware are you having difficulty with?

mmberlin, I speculate your issue could lie with newer Qt5 versions causing incompatibility with older gcc versions. Are you using an older gcc? I see errors regarding libQt5Widgets. I'm sorry I can't offer a definitive solution.

zoidby commented on 2020-07-03 19:34 (UTC)

Still doesn’t work like it should. Here is what i did:

  • Upgraded to 5.7.7
  • Removed i2c-piix4-aura-dkms
  • Did a clean reinstall of openrgb-git

But no devices are detected.

After i reinstalled i2c-piix4-aura-dkms, devices are detected again.

The issue with 99-openrgb.rules seems to be fixed, as that was renamed and doesn’t have to be deleted anymore.

mmberlin commented on 2020-06-25 17:21 (UTC)

Myrddin, yes the output does include GLIBCXX_3.4.26 as well as GLIBCXX_3.4 through GLIBCXX_3.4.28. I am running 64bit not 32bit. Also, I tried reinstalling my gcc-libs but no change.

Myrddin commented on 2020-06-25 17:02 (UTC) (edited on 2020-06-25 17:14 (UTC) by Myrddin)

zoidby, i2c-piix-aura-dkms is now deprecated as it has been merged upstream in Linux 5.8 & backported to Linux 5.7.6. It shouldn't be necessary any longer.

mmberlin, the issue could be an outdated gcc-libs package (are you on 32-bit?). Check to see if the output of strings /usr/lib/libstdc++.so.6 | grep GLIBCXX | head -n 30 includes GLIBCXX_3.4.26.

zoidby commented on 2020-06-23 17:17 (UTC) (edited on 2020-06-23 17:17 (UTC) by zoidby)

With /usr/lib/udev/rules.d/99-openrgb.rules no devices are found.

If i delete that file openrgb works as expected.

I am using i2c-piix4-aura-dkms, maybe that leads to conflicts?

Myrddin commented on 2020-06-22 00:04 (UTC)

mmberlin, that log is too brief to show the issue. It does seem like a linking issue. Perhaps a missing dependency, could you provide more lines from the output?

Edit your previous comment to add as much as you can.

mmberlin commented on 2020-06-21 19:49 (UTC) (edited on 2020-06-24 19:14 (UTC) by mmberlin)

build error

 collect2: error: ld returned 1 exit status
 make: *** [Makefile:912: OpenRGB] Error 1
 ==> ERROR: A failure occurred in build().
     Aborting...
 Error making: openrgb-git

EDIT: More output lines posted on pastbin: https://pastebin.com/UwWhGhmE

axelgenus commented on 2020-06-21 18:50 (UTC) (edited on 2020-06-21 18:51 (UTC) by axelgenus)

@Myrddin: I2C devices are not even tagged with "uaccess" in the first place. i2c-dev is a kernel driver, that's why giving access to those device nodes to any logged user is a really bad idea.

Again, 'i2c' and 'plugdev' groups DO NOT EXIST in ArchLinux and why should they? The UDEV rules should be adapted to ArchLinux since there is no "most compatible option for all distribution". Each distro has it's own perks.

G-Skill TRIDENT Z DRAM's are not enlisted in OpenRGB if 'i2c' group does not exist and/or the user is not assigned to that group. As a workaround, you can run it as root and it just works. Or just give access to an existing group.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »