LACT is available as a Flatpak package. However, due to sandbox restrictions, there are some extra steps needed to achieve full functionality.
LACT uses a system daemon to interact with the GPU and manage configuration. For access to hardware and system settings the daemon needs to run as root.
When you run the flatpak and the daemon is not detected, you will get a prompt to install it outside of the sandbox.
This will automatically set up and start the system service. It is installed at /etc/systemd/system/lactd.service.
If the setup was successful, you will now be able to use all of the functionality.
Service status can be checked with systemctl status lactd.
It is also possible to skip the service setup if you want to use LACT only for information and monitoring. This can work entirely in the Flatpak sandbox and does not require extra permissions.
Note: the setup script requires Polkit to be functional.
If you wish to set up the service automatically in a script (without graphical prompts), you can run the Flatpak with the LACT_UNATTENDED_SETUP=true environment variable.
The setup script will automatically configure the daemon in such a way that the user who ran the setup has access to it. It will not happen if you had an existing LACT config before setting up the Flatpak.
In this scenario you have to manually edit /etc/lact/config.yaml and set admin_user in the daemon section.
See this README section for more information.
Flatpak specifically requires admin_user to be set (and it is configured by default in the setup). Simply being part of a group like wheel does not grant the UI access to the daemon from Flatpak.
To uninstall the flatpak-created service run the following commands:
sudo systemctl disable --now lactd
sudo rm /etc/systemd/system/lactd.serviceThe service uses flatbox in order to create a flatpak-like environment for the service that still has the permissions it needs to function (such as write access to various sysfs paths). Flatbox itself is shipped as a static binary with the flatpak and is executed on the host, which then discovers flatpak application/runtime/extension paths and sets them up for the service.
This approach allows the service to avoid any dependence on system libraries and commands for its functionality. The only exception are distro-specific commands for AMD overdrive setup.