Linux GPU Control Application LACT: v0.8.0 released

Linux GPU Control Application LACT Screenshot

The Linux GPU Control Application LACT has been released in version 0.8.0.

[0.8.0] - 2025-06-28

Main changes:

More advanced profile management

You can now set multiple conditions to trigger profile activation, such as having any or all processes in a list running:

It is now also possible to export and import profiles to json files.

Process monitor

There is a new process monitor window (available from the dropdown menu on the top right) showing the list of processes that are using the GPU, with engine load and VRAM usage stats:

The monitor is supported on all 3 GPU vendors (using /proc fdinfo on AMD/Intel and NVML on Nvidia)

More Nvidia metrics

The following new readings are now available on Nvidia: GPU voltage, GPU hotspot temperature, VRAM temperature (GDDR6 only):

Power profiles daemon integration

Previously when running LACT together with power-profiles-daemon, ppd would override some settings as it has its own amdgpu management features. Now LACT detects if power-profiles-daemon is present on the system, and will automatically disable the conflicting functionality through ppd's dbus API (without affecting anything else that ppd manages).

Note: this needs power-profiles-daemon 0.30 or later to work.

Flatpak service improvements

The service in the Flatpak version of LACT has been updated to use flatbox. This makes it work more consistently across different system setups as it avoids the need for the system service to directly call flatpak as another user to run the service.

Note: after updating, you will be prompted to re-setup the service. This is normal, and is needed to update the systemd unit to the new format.

Important notes:

RDNA4 GPUs now require kernel 6.14 or later for overclocking to work. Older kernels had broken clockspeed control behaviour that LACT contained a workaround for, and this workaround has now been dropped. See #599 for more info.
There is a new workaround for RDNA3 constantly reporting thermal throttling, it should now be reported only when it's actually affecting performance.
If multiple Vulkan drivers are available (such as both RADV and AMDVLK), LACT will now let you select between them on the software page.

The full changelog is available on the release page.

Tags: