Kronos icon indicating copy to clipboard operation
Kronos copied to clipboard

Experimental Flatpak - Config Folder Issues

Open BlueInterlude opened this issue 8 months ago • 0 comments

Hello, following up on this issue, https://github.com/FCare/Kronos/issues/967, from a couple of years ago.

I created an experimental Flatpak and I'm having some issues with the config folder. The flatpak saves its configurations in ~/.config/kronos. However, the typical Flatpak directory is ~/.var/$FLATPAK_ID or ~/.var/io.github.fcare.kronos.

The XDG Standards for Flatpaks can be found here, https://docs.flatpak.org/en/latest/conventions.html#xdg-base-directories.

To test the Flatpak (hosted here: https://github.com/BlueInterlude/flathub/tree/io.github.fcare.kronos), use the following steps:

  1. git clone --recurse-submodules https://github.com/BlueInterlude/flathub.git -b io.github.fcare.kronos io.github.fcare.kronos
  2. cd io.github.fcare.kronos
  3. flatpak remote-add --if-not-exists --user flathub https://dl.flathub.org/repo/flathub.flatpakrepo
  4. flatpak-builder --force-clean --user --install-deps-from=flathub --repo=repo --install builddir io.github.fcare.kronos.yaml

When the Flatpak is finished building, use flatpak run io.github.fcare.kronos to open the Flatpak. Make any setting changes and notice the settings are saved to ~/.config/kronos.

Is there any way this could be fixed upstream (in Kronos) for the Flatpak to properly respect the Flatpak XDG Base Directories?

BlueInterlude avatar Jun 05 '25 16:06 BlueInterlude