is there any advantage over corectrl or is it simply another tool?
Linux
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
The big advantage for me is that lact runs as a (systemd) daemon. This is more convenient for me than having to autostart CoreCtrl.
A disadvantage of the daemon is that it can't be packaged on flathub.
Enable and start the service (otherwise you won't be able to change any settings):
sudo systemctl enable --now lactd
You can now use the GUI to change settings and view information.
LACT has an API over an unix socket.
I've been using this for a while now. It works great for me, basic fan control and temp info. I haven't used any of the overclocking features though.
Dope, thank you for posting. Been using 'Core CTRL' for quite awhile but Imma give this a rip. For some reason the former tool never could control the fan curve for my GPU (all the other fans in the box worked fine with it) so this might be profit.
CoreCTRL, but written in Rust? Based. I'll try it out when I have the time.
Saving this one. Thanks, man for the heads up
Sad to see that it's GTK-based. Cool concept overall though, I may give it a shot at some point to compare to CoreCTRL
As a GNOME user, I'm happy to see it's GTK, but idk why it's not Libadwaita.
We're never gonna get one cohesive UI on Linux, it's always gonna look out of place somewhere.
If the backend is not tied to the UI, it might be easy to reuse the work for a Qt6 front-end.