[Bug]: /app/bin/easyterm.py: cannot execute: required file not found

[latin-1]

Describe the bug

"Run in Terminal" does not work properly. It works fine if the option is not checked.

To Reproduce

1. Create a new bottle
2. Check the "Run in Terminal" option in the gear icon
3. Click "Run Executable" and select an executable file to run

Package

Flatpak from Flathub

Distribution

Fedora 41

Debugging Information

Official Package: true
Version: '51.21'
DE/WM: gnome
Display:
    X.org: true
    X.org (port): :0
    Wayland: true
Graphics:
    vendors: {}
    prime:
        integrated: null
        discrete: null
Kernel:
    Type: Linux
    Version: 6.13.9-200.fc41.x86_64
Disk:
    Total: 14591766528
    Free: 14591602688
RAM:
    MemTotal: 27.2GiB
    MemAvailable: 24.0GiB
Bottles_envs: null

Troubleshooting Logs

22:51:13 (INFO) Launching an executable… 
22:51:14 (WARNING) No GPU vendor found, keep going without setting VK_ICD_FILENAMES… 
22:51:14 (INFO) Command: easyterm.py -d -p "#00ffff #2b2d2e" -c 'bash -c '"'"'/var/home/hikari/.var/app/com.usebottles.bottles/data/bottles/runners/soda-9.0-1/bin/wine64 /var/home/hikari/path/to/executable.exe'"'"'' 
/bin/sh: line 1: /app/bin/easyterm.py: cannot execute: required file not found

Additional context

No response

[Perkolator]

Yep, stopped working today right after installing these Flatpak updates:

com.usebottles.bottles.Locale
org.gnome.Platform.Compat.i386
com.usebottles.bottles

Which seems to point to about 2 weeks old (and last) commit (why it was offered as a Flatpak udpate only now?): 8875b2b

[TheEvilSkeleton]

Huh, I thought we canceled the build in https://buildbot.flathub.org/#/builders/6/builds/192819 - it was merged accidentally. I'll revert that right away.

[Perkolator]

@TheEvilSkeleton Just updated again, and it still doesn't work. Same error message as before.

[stashymane]

Same issue, installed the exact build in that PR, opening any terminal within Bottles results in /bin/sh: line 1: /app/bin/easyterm.py: cannot execute: required file not found

[MithicSpirit]

The file begins with a #!python, which seems incorrect. It should probably be #!/usr/bin/python instead.

[ChillyVanilly77]

yep, I managed to get it working again by modifying the actual file (wich would have the in-sandbox-specifiic path) /app/bin/easyterm.py script by swapping the original shebang line with the most preferred way to get the actual environment using #!/usr/bin/env python3. Namely, the exact file that I have modified on my host fs as the actual workaround was ~/.local/share/flatpak/app/com.usebottles.bottles/current/active/files/bin/easyterm.py (which is the 1-of-2 hard-linked files).

NOTE: I'm assuming here that Bottles was a user installation, not system one.

Cheers!

[NotAF0e]

@MithicSpirit solution fixed it for me :)

[kode54]

I do not have a ~/.local/share/flatpak/app folder on my system, but I do have a ~/.var/app. The directory you listed does not exist underneath the com.usebottles.bottles directory there.

[NotAF0e]

I do not have a ~/.local/share/flatpak/app folder on my system, but I do have a ~/.var/app. The directory you listed does not exist underneath the com.usebottles.bottles directory there.

I did a system wide search with sudo find / | grep easyterm.py, made sure that it was the correct file, then did the change stated above

[D0735]

I do not have a ~/.local/share/flatpak/app folder on my system, but I do have a ~/.var/app. The directory you listed does not exist underneath the com.usebottles.bottles directory there.

Then it will be in /var/lib/flatpak/.
~/.local/share/flatpak/ is the directory for user installations.