Where Does TuxClocker Store Config on Linux?
TuxClocker keeps device profiles and view state in Qt config paths on Linux. Fix driver flags before blaming profiles.
Last updated
TuxClocker stores device profiles and interface state through Qt settings paths on Linux. The DBus daemon plus GUI share them. Sort order and collapsed nodes persist between restarts.
Back up the config tree to move overclocking setups. Exact filenames vary by release, so confirm inside the app when paths differ. Fix driver flags before blaming saved profiles.
Where TuxClocker stores this, by platform
~/.config (TuxClocker profiles and view state, Qt settings)
Profiles and view state in Qt config paths. Daemon plus GUI share them. Copy with both stopped; confirm names per release.
Frequently asked questions
How do I move TuxClocker profiles?
Copy the TuxClocker config with the app and daemon stopped to the same path. Profiles plus view state travel together. Restart the daemon after restoring.
No devices show up. Why?
Check the daemon connection plus driver flags first. Missing devices usually mean Coolbits or ppfeaturemask gaps. GUI copies cannot fix driver setup.
Notice an outdated path? Let us know.