Problem: just bar::launch (GUI default) requires a Beyond-All-Reason*.AppImage on Linux because _launch_uses_appimage() returns true for Chobby boots. Flatpak users don't have an AppImage — they launch via flatpak run info.beyondallreason.bar. The shell scripts have no awareness of Flatpak at all.
Changes needed:
-
scripts/setup.sh — ensure_bar_appimage_path_set(): After the existing ~/Applications/ auto-detect, run flatpak info info.beyondallreason.bar &>/dev/null and if found, offer the user an option to use Flatpak (or auto-detect it silently). Add new environment variable BAR_FLATPAK_PATH=flatpak:info.beyondallreason.bar to .env. (or possibly we need to emit the full application path)
-
scripts/setup.sh — bar_appimage_resolves(): Accept flatpak:* as a valid sentinel in addition to file/directory paths. (or have a separate function that checks for bar_flatpak_resolves() )
-
scripts/setup.sh — detect_game_dir(): Add auto-detection of the Flatpak data dir at ~/.var/app/info.beyondallreason.bar/data so linking and chobby-channel detection work out of the box.
-
scripts/launch.sh — run_linux(): When BAR_FLATPAK_PATH exists, inject --launcher-binary flatpak(or equivalent) into thebar-launch` args so the Python side knows which execution mode to use.
-
scripts/doctor.sh: Report Flatpak install alongside the AppImage status
(this issue was researched and written by Deepseek v4 flash, with an edit by NortySpock to focus on a new BAR_FLATPAK_PATH environment variable. It could easily contain errors)
Problem:
just bar::launch(GUI default) requires aBeyond-All-Reason*.AppImageon Linux because_launch_uses_appimage()returns true for Chobby boots. Flatpak users don't have an AppImage — they launch viaflatpak run info.beyondallreason.bar. The shell scripts have no awareness of Flatpak at all.Changes needed:
scripts/setup.sh—ensure_bar_appimage_path_set(): After the existing~/Applications/auto-detect, runflatpak info info.beyondallreason.bar &>/dev/nulland if found, offer the user an option to use Flatpak (or auto-detect it silently). Add new environment variableBAR_FLATPAK_PATH=flatpak:info.beyondallreason.barto.env. (or possibly we need to emit the full application path)scripts/setup.sh—bar_appimage_resolves(): Acceptflatpak:*as a valid sentinel in addition to file/directory paths. (or have a separate function that checks for bar_flatpak_resolves() )scripts/setup.sh—detect_game_dir(): Add auto-detection of the Flatpak data dir at~/.var/app/info.beyondallreason.bar/dataso linking and chobby-channel detection work out of the box.scripts/launch.sh—run_linux(): WhenBAR_FLATPAK_PATHexists, inject--launcher-binary flatpak(or equivalent) into thebar-launch` args so the Python side knows which execution mode to use.scripts/doctor.sh: Report Flatpak install alongside the AppImage status(this issue was researched and written by Deepseek v4 flash, with an edit by NortySpock to focus on a new BAR_FLATPAK_PATH environment variable. It could easily contain errors)