v0.4.0 Launching doesn't launch in the correct directory at least on Linux drop desktop

[NicholasFlamy]

Without changing anything it attempts to launch and I see this log.
2026-06-27T14:28:29.706307601-04:00 | INFO | process/src/process_manager.rs:526 - launching (in /home/nicholas/.local/share/drop/games/SuperTuxKart): ParsedCommand { env: [], command: "run_game.sh", args: [] }

If I go into the game options and change the launch string to this it works.

Logs when it succeeds:
2026-06-27T14:40:40.392086804-04:00 | INFO | process/src/process_manager.rs:526 - launching (in /home/nicholas/.local/share/drop/games/SuperTuxKart): ParsedCommand { env: [], command: "/home/nicholas/.local/share/drop/games/SuperTuxKart/run_game.sh", args: [] }

@DecDuck this may be a release candidate bug so you may want to patch this before releasing.

[DecDuck]

Will look into it, looks like we should probably launch via the shell on Linux.

[NicholasFlamy]

I should add, I started looking at the code and realized I have no chance because it's rust. One day I'll learn it.

[jimmyhiggs337]

Logs when it succeeds:
2026-06-27T14:40:40.392086804-04:00 | INFO | process/src/process_manager.rs:526 - launching (in /home/nicholas/.local/share/drop/games/SuperTuxKart): ParsedCommand { env: [], command: "/home/nicholas/.local/share/drop/games/SuperTuxKart/run_game.sh", args: [] }

I'm also having this issue, but even changing the launch command to have the correct path doesn't work for me

[NicholasFlamy]

Logs when it succeeds:
2026-06-27T14:40:40.392086804-04:00 | INFO | process/src/process_manager.rs:526 - launching (in /home/nicholas/.local/share/drop/games/SuperTuxKart): ParsedCommand { env: [], command: "/home/nicholas/.local/share/drop/games/SuperTuxKart/run_game.sh", args: [] }

I'm also having this issue, but even changing the launch command to have the correct path doesn't work for me

Did you be sure to include the full path including the file (or having the slash and then curly brackets) as shown in my screenshot?

[jimmyhiggs337]

Logs when it succeeds:
2026-06-27T14:40:40.392086804-04:00 | INFO | process/src/process_manager.rs:526 - launching (in /home/nicholas/.local/share/drop/games/SuperTuxKart): ParsedCommand { env: [], command: "/home/nicholas/.local/share/drop/games/SuperTuxKart/run_game.sh", args: [] }

I'm also having this issue, but even changing the launch command to have the correct path doesn't work for me

Did you be sure to include the full path including the file (or having the slash and then curly brackets) as shown in my screenshot?

yes

[NicholasFlamy]

You should post your logs. I suspect your issue is slightly different.

[jimmyhiggs337]

You should post your logs. I suspect your issue is slightly different.

I opened the appimage via the shell to see the live output,

2026-06-29T13:38:43.607482116-05:00 | INFO | process/src/process_manager.rs:449 - launching (in /home/jhiggs/Drop/MeltysQuest): ParsedCommand { env: ["/home/jhiggs/Drop/MeltysQuest/GAMEID=d170c881-5ccf-43dd-bc07-dae2e5411d93", "PROTONPATH=/home/jhiggs/.steam/root/compatibilitytools.d/Proton-GE"], command: "Latest", args: ["WINEPREFIX=/home/jhiggs/.local/share/drop/pfx/eb65379f-8231-4934-9504-c62eb2c56e92", "umu-run", "Meltys's Quest.exe"] }

it displays this and I get the "no such file or directory" error in the gui

seems like pretty much the same issue to me

[jimmyhiggs337]

[jimmyhiggs337]

My best guess is because it's not a linux game

edit: tried the linux version, same issue.

[NicholasFlamy]

Yeah, I've never tried it with Proton and umu. I only just set up a test instance to see how it worked and ran into a bunch of things (including this) (if no one else steps up I'll have to learn Rust).

[declan-wtg]

When was the last time you re-downloaded the client? I patched a bunch of stuff last week, it might worth trying to re-install from the latest.

[jimmyhiggs337]

When was the last time you re-downloaded the client? I patched a bunch of stuff last week, it might worth trying to re-install from the latest.

Today, also this issue was created two days ago, so I would assume OP is also on the latest version, maybe the it was introduced with that update?

[NicholasFlamy]

When was the last time you re-downloaded the client? I patched a bunch of stuff last week, it might worth trying to re-install from the latest.

I downloaded it like a couple days ago from this release:
https://github.com/Drop-OSS/drop/releases/tag/v0.4.0

And yes, I see the assets say updated last week.

I have to comment that updating the assets in an existing release is awful practice. You should be making new releases. I tried to go back a few release candidates to try and see if the issue appeared in one of the bug fixes or changes between them, but I couldn't because of this.

[declan-wtg]

Yep, sorry, I know.

Looks like these issues come from Linux's PATH searching, where executables specifically need to start with ./ before it'll search the local directory.

You should post your logs. I suspect your issue is slightly different.

I opened the appimage via the shell to see the live output,

2026-06-29T13:38:43.607482116-05:00 | INFO | process/src/process_manager.rs:449 - launching (in /home/jhiggs/Drop/MeltysQuest): ParsedCommand { env: ["/home/jhiggs/Drop/MeltysQuest/GAMEID=d170c881-5ccf-43dd-bc07-dae2e5411d93", "PROTONPATH=/home/jhiggs/.steam/root/compatibilitytools.d/Proton-GE"], command: "Latest", args: ["WINEPREFIX=/home/jhiggs/.local/share/drop/pfx/eb65379f-8231-4934-9504-c62eb2c56e92", "umu-run", "Meltys's Quest.exe"] }

it displays this and I get the "no such file or directory" error in the gui

seems like pretty much the same issue to me

This is a little bit different, can you go into the log files for the specific game and get the error log?