Hi, I’m trying the desktop Grayjay app and it seems to work fine.

I just have to keep locating the app in folder whenever I want to launch it so I found out how to make it appear in the GNOME Apps and launch it there.

However it requires me to copy 2 folders (cef,wwwroot) from the app folder into my “/home/werecat” folder and I don’t understand why when it can launch just fine from the executable without me having to do that.

Any idea on what I’m missing or doing wrong? The main goal is to add the app to my Dash to Dock.

  • Aiwendil@lemmy.ml
    13·
    8 days ago

    Try adding a PATH=/home/werecat/Grayjay line to your .desktop file. Without it the application will run with your home directory as your working-directory…and there the data files are missing (Why you need to copy them to your home). The path entry makes the program work in /home/werecat/Grayjay where the data directories actually are.

    Edit: That is assuming when you started it manually you did a cd Grayjay and a ./Grayjay or similar. So you changed your working directory there first before starting it. If that is not the case ignore my post ;)

    • BananaTrifleViolin@lemmy.worldEnglish
      5·
      8 days ago

      Yeah this looks right. The program is launching other tools, in this case when it gets to CEF (chromium embedded framework) it is looking in the default path it’s picked up when the .desktop file is launching it. So it’s essentially looking directly under /home/werecat/ instead of where the /Greyjay programme is running from.

      So if you specify the path in the .desktop file it should fix the problem.

      An alternative route of that doesn’t fix it might be to edit any config files (if it has them) to ensure they explicitly point to the correct Grayjay directory.

      • WereCat@lemmy.worldOP
        1·
        7 days ago

        Yeah, I’ve tried finding the config file to edit the path as the first thing but I could not find it. Adding the Path as was suggested worked after removing TryExec.

    • WereCat@lemmy.worldOP
      5·
      7 days ago

      Thanks, that actually worked even though it did not at first.

      I’ve tried to also do export PATH=/home/werecat/Grayjay:$PATH but that did not work either. And finally I had to remove the TryExec for some reason for the Path to start working.

      It launches now with Terminal even though I’ve set it to ‘false’ but at least it runs.

      • Aiwendil@lemmy.ml
        7·
        7 days ago

        Justr to make this clear (Sorry if it’s unnecessary, but maybe still useful info for others)…Path= lines in .desktop files are not related at all to the $PATH environment variables. They do something completely different (And yes, picking Path as key was a terrible choice in my view). Path= lines in .desktop files change the current working directory…they do about the same as a cd <directory> in a shell.

        They do not change where a .desktop file looks for executables…only indirectly if a executable runs another file relative to the current directory or looks for images/icons/audio/other data relative to the current working directory.

        And I have no clue why it doesn’t work with TryExec…the desktop file spec doesn’t mention anything about that :( ( https://specifications.freedesktop.org/desktop-entry-spec/latest/recognized-keys.html )