Where Does KStars Store Config and Data?
KStars keeps its main config in kstarsrc under .config on Linux, with data under local share and device access through .indi. No single Ekos file exists.
Last updated
KStars follows KDE storage law. One rc file in .config carries the main settings, proven by its kcfg binding upstream. A data tree under local share carries everything else. Device access flows through a separate dot directory.
Ekos refuses a single-file answer. Profiles and queues distribute across the rc file and data tree with no dedicated path verified. Flatpak twins both locations under var-app with documented migration commands. Copy config with data or copy neither.
Where KStars stores this, by platform
~/.config/kstarsrc
Main settings file proven by upstream kcfg binding. Flatpak twin lives under the app var tree with documented migration. Ekos state splits between here and the data tree.
~/.local/share/kstars
Supporting data tree for the Linux build with the Flatpak data twin beside it. Device access additionally touches the dot-indi folder. No single Ekos profile file is verified inside.
Frequently asked questions
How do I back up KStars settings?
Copy ~/.config/kstarsrc with ~/.local/share/kstars while KStars is closed. The rc file is proven by the upstream kcfg binding, and the data tree holds the rest. Flatpak builds use var-app twins of both paths.
Where are my Ekos profiles?
They split across the rc file and the data tree with no dedicated profile file verified. Sequence queues and device setups live in that combination. Anyone naming one Ekos file is guessing, so back up both locations.
How do I move KStars into Flatpak?
Copy the native paths into the Flatpak config and data twins. The download page documents that migration pair explicitly with matching permissions for device access. Native and sandboxed installs otherwise diverge.
Notice an outdated path? Let us know.