Skip to content

Godot executable fails to be recognized on atomic distros (flatpak) #981

@GreatGreenStar

Description

@GreatGreenStar

Godot version

4.6.1-stable (Flatpak)

VS Code version

Version: 1.107.18627 Commit: aafba0d66e7c8203c7e890a32383eecef870560c Date: 2025-12-25T12:20:53.256Z Electron: 39.2.7 ElectronBuildId: undefined Chromium: 142.0.7444.235 Node.js: 22.21.1 V8: 14.2.231.21-electron.0 OS: Linux x64 6.18.12-200.fc43.x86_64

Godot Tools VS Code extension version

2.6.1

System information

kinoite-main:latest

Issue description

Functionality related to godotTools.editorPath.godot4 and similar fails, as no executable is detected. When setting the executable path manually - in this case /var/lib/flatpak/exports/bin/org.godotengine.Godot for system and /home/greenstar/.local/share/flatpak/exports/bin/org.godotengine.Godot for user... it just fails to recognize it as such. System installation is A and user is B for further reference relative to this issue.

Steps to reproduce

  1. Use an atomic distro.
  2. Install godot
  3. Install vscode
  4. Install this extension
    5A. The specified Godot executable, '/var/lib/flatpak/exports/bin/org.godotengine.Godot' is invalid. Extension features will not work correctly unless this is fixed.
    5B. The specified Godot executable, '/home/greenstar/.local/share/flatpak/exports/bin/org.godotengine.Godot' is invalid. Extension features will not work correctly unless this is fixed.

Yes I am aware that /home is actually just /var/home on atomic systems, trying /var/home still causes these exact same issues.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions