Search Criteria
Package Details: linux-thermaltake-rgb 0.2.0-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/linux-thermaltake-rgb.git (read-only, click to copy) |
---|---|
Package Base: | linux-thermaltake-rgb |
Description: | Python usb daemon and controller for thermaltake rgb watercooling devices |
Upstream URL: | https://github.com/chestm007/linux_thermaltake_riing |
Licenses: | GPL2 |
Submitter: | chestm007 |
Maintainer: | chestm007 |
Last Packager: | chestm007 |
Votes: | 2 |
Popularity: | 0.000000 |
First Submitted: | 2018-12-02 10:42 (UTC) |
Last Updated: | 2019-03-06 11:03 (UTC) |
Dependencies (8)
- python (python37AUR, python311AUR, python310AUR)
- python-gobject (python-gobject-gitAUR)
- python-psutil
- python-pyusb (python-pyusb-gitAUR)
- python-yaml (python-yaml-gitAUR)
- python-nose (make)
- python-setuptools (make)
- tar (tar-gitAUR, busybox-coreutilsAUR) (make)
Latest Comments
mleivagomez commented on 2024-04-29 21:38 (UTC)
Amending my previous comment as Python 3.12 has since been released...
The file to edit now is in /usr/lib/python3.12/site-packages/linux_thermaltake_rgb/daemon/config.py
Line is line 42 at this point.
As before,
config = yaml.load(cfg)
must become
config = yaml.full_load(cfg)
mleivagomez commented on 2023-05-08 02:33 (UTC)
Since it's been a while since this package has been updated by the maintainer, I'd like to point out that yaml.load(cfg) no longer properly loads the configuration for the daemon. You may have had issues with this if you got the error:
TypeError: load() missing 1 required positional argument: 'Loader'
This can be rectified by simply editing /usr/lib/python3.11/linux_thermaltake_rgb/daemon/config.py on line 41 so that
config = yaml.load(cfg)
Becomes
config = yaml.full_load(cfg)
As of more recent versions of pyyaml, load() no longer takes one single argument.
The active version on the master branch last edited 9 months ago works just fine as he introduces two arguments (cfg, yaml.FullLoader) to yaml.load().
Either what the developer did or what I did is in essence fine.
insanemal commented on 2022-03-14 04:47 (UTC)
I've forked the repo and added the required YAML fix.
This fixes my issues with my hardware. Lighting and fan control now work
https://github.com/insanemal/linux_thermaltake_riing/releases/tag/0.2.1
Feel free to look at my fork. I've only one commit with the YAML fixes.
Probably time to switch to a fixed fork as it looks like the actual project is abandoned.
Ayy-Zee commented on 2020-06-09 13:39 (UTC) (edited on 2020-06-09 13:42 (UTC) by Ayy-Zee)
I assume I am using the G3 controller. I get this in dmesg when I unplug and replug it:
And I get a crap ton of these in demsg: They are still fillling up even after disabling the daemon.After installing numpy and gobject through either pacman or pip without root(first mistake), When trying to run the daemon through systemd using the command:
systemctl enable --now linux-thermaltake-rgb
as root
and checking with systemctl status linux-thermaltake-rgb
the following output is given:
When trying to run only the program regardless of root or not, this output is given: After editing the source and using the non-deprecated method of loading the yaml file, this output shows: ok. after fiddeling around a bit more, I installed numpy and gobject with pip as superuser (su) and I hardcoded the device product id and vendor id in the source(bad way to fix this because IDs might change.) in drivers.py(line 35 and 36). And oh my god. I finally got this running.this is the output of systemctl status:
The only package who can talk to this stupid controller on linux. Massive props chestm007. So far, only the speed control works. I can't be bothered to troubleshoot the RGB for now. Let me know if anyone got that running. It runs as a daemon and also a normal program as long as it has root.
Cheers.
rkmax commented on 2020-05-22 19:54 (UTC) (edited on 2020-05-22 19:54 (UTC) by rkmax)
after install python-numpy
python-gobject is present on my system
rkmax commented on 2020-05-22 19:52 (UTC) (edited on 2020-05-22 19:53 (UTC) by rkmax)
installed recently with the following problem
nicoulaj commented on 2019-02-21 14:08 (UTC)
Thanks, I don't think there are explicit rules about this. The Arch philosophy is to provide "vanilla" packages (as few modifications as possible), so this actually goes against my request. But this package already does this by deploying the config files to their intended locations in /etc anyway.
Maybe a cleaner solution would be that the upstream project provide a Makefile so that
package()
is reduced to just something likemake install PREFIX=$pkgdir
and packaging is straightforward for all distros.chestm007 commented on 2019-02-20 21:33 (UTC)
Hey, i've addressed everything except:
I'm still a little new to packaging and cant find any documentation stating the correct way of doing that - if you can point me somewhere that would be amazing!
nicoulaj commented on 2019-02-15 13:30 (UTC) (edited on 2019-02-15 13:32 (UTC) by nicoulaj)
Thanks for packaging !
I have a few requests:
backup=('etc/linux_thermaltake_rgb/config.yml')
? otherwise the config will be overwritten with every updatemakedepends
ongit
is needed, or it can't build in a clean chrootsource=('<https://github.com/chestm007/linux_thermaltake_riing/archive/>${pkgver}.tar.gz')
$pkgdir/usr/share
directory could be deleted from the package since files are deployed to their proper location anyway