Fedora Silverblue - XDG_DATA_HOME is unset, causes applications to have bugs

Looking to have some discussion/thoughts on this. In a fresh installation of Fedora Silverblue (super easy to do via Boxes), running

echo $XDG_DATA_HOME

…Returns nothing. Applications that depend on writing info to xdg-data/an.app.name (i.e. usually .local/share/an.app.name seem to write into the void, and their info is not retrievable on next app launch.

Is this intentional behavior for Flatpak? As a user, I feel like it would better for xdg-data in Flatpak manifests to default to .local/share when XDG_DATA_HOME is unset.

If it’s unset, then it should default to what you write. I think you should give more information on these errors, since the cause might be something else.

Freedesktop spec says:

$XDG_DATA_HOME defines the base directory relative to which user-specific data files should be stored. If $XDG_DATA_HOME is either not set or empty, a default equal to $HOME/.local/share should be used.

1 Like

It might unset on the host, but it’s always set within the sandbox:

~ ❱ flatpak run --command=printenv org.telegram.desktop XDG_DATA_HOME
/var/home/bpiotrowski/.var/app/org.telegram.desktop/data
2 Likes