[APP BUG]: Game Desktop File Creation points to Incorrect Executable (Linux)

[BlueInterlude]

Checklist

• I have searched for a similar issue in this repository and did not find one.
• I am using an official build obtained from releases or updated one of those builds using its in-app updater.

Describe the Bug

When creating game desktop files, the Exec= line points to the incorrect executable causing the desktop file to not launch the game properly.

In the AppImage, the Exec= line points to /tmp/.mount_ShadpsNIHcfh/usr/bin/shadps4. In the Flatpak, the Exec= line points to /app/bin/shadps4.

For the AppImage desktop file, that should likely point to the AppImage. For the Flatpak, I'm not sure but typically it's flatpak run net.shadps4.shadPS4 but it may differ in desktop files.

I am not using a front-end to launch these desktop files, I am not using a package distributor like EmuDeck or RetroDECK. I am using the official AppImage and Flatpak directly from ShadPS4's repo and Flathub respectively along with double clicking the desktop file to test. In addition, copying the output of the Exec= line to a terminal also does not work.

Reproduction Steps

On Linux, download the AppImage or Flatpak. Right click a game in the GUI, click Create Shortcut, test launching shortcut.

Can also test copying the output of the Exec= line to a terminal to see if it works.

Expected Behavior

For the desktop file to properly launch the game.

Specify OS Version

Tested on two distros, EndeavourOS and SteamOS

[jardon]

a couple of things:

1. the desktop shortcut should be created under ~/.local/share/applications/
2. the exec line needs to point to the correct executable per the installation method