You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The XDG base dir spec wants applications to first lookup XDG_DATA_HOME and only if that is not set, should applications assume its default value of $HOME/.local/share. Currently, Grayjay hardcodes $HOME/.local/share. Grayjay also attempts using $HOME/.config, which is not the right place for the kind of data Grayjay is storing there.
Per the comments in the issue i mentioned above, I believe this should be re-opened.
To summarize: The desktop app still contains file operations that dont fully respect/dont explicitly specify what directory they are meant to be in, leading the C# API's involved to make assumptions that break the app in the context of #14 .
Examples of file IO operations that i have seen that illustrate the problem:
the "launch" file - this is supposed to be in the user data directory
the wwwroot directory and grayjay.png file - these are part of the installation folder and (i assume) are okay to be read-only
all of these calls use APIs like GetFullPath, or WriteAllText, which seem to make assumptions that the current working directory should be used if a relative path or filename is given.
As you can see in the examples above, this assumption causes file access problems regardless of if the app is run from the installation directory (which is read only for flatpaks) or the user data directory.
What happened?
The XDG base dir spec wants applications to first lookup
XDG_DATA_HOME
and only if that is not set, should applications assume its default value of$HOME/.local/share
. Currently, Grayjay hardcodes$HOME/.local/share
. Grayjay also attempts using$HOME/.config
, which is not the right place for the kind of data Grayjay is storing there.Please have a look at https://specifications.freedesktop.org/basedir-spec/latest/
Grayjay Version
3
What plugins are you seeing the problem on?
Other
Plugin Version
No response
Which operating system are you using?
Linux
When do you experience the issue?
Are you using a VPN?
No
Relevant log output
No response
The text was updated successfully, but these errors were encountered: