I’m trying to build a Flatpak of the Amulet Minecraft Map Editor, which runs fine when run directly through Python 3.11.9 (in a VENV) on Linux, Windows and MacOS, but on Linux, the Flatpak version crashes when loading the 3D Map window.

So, working from the source, using the Flatpak PIP Generator, I got all the dependencies pulled in, verified they in the correct install order, and ultimately, after some trial-and-error, built this Flatpak manifest.

Then I did the following:

flatpak-builder -v --install-deps-from=flathub --mirror-screenshots-url=https://dl.flathub.org/media/ --add-tag=0.10.35 --bundle-sources --repo=amulet_flatpak_repo amulet_build_dir amulet.yml --force-clean

It took a while, but we got through everything with no errors. Next, I did this:

flatpak install amulet.flatpak

This step too succeeded with no errors reported, so I moved to the final step:

flatpak run com.github.amulet_map_editor

The Flatpak version of the app actually loads initially, and I can select a Minecraft world to load, which it does without issue. However, when I go to the 3D map editor, that’s when everything falls apart with the afore-mentioned error, and yet, as stated previously, this doesn’t happen when running directly with Python through my terminal.

I just don’t understand why this isn’t working. Is the Flatpak sandbox blocking something? Do I need to add something to my manifest? It can’t be an issue with Amulet directly because it runs fine on its own, right?

I’ve tried the following:

• running the original project from it’s Python source
• rebuilding the flatpak manifest completely from scratch
• specifically adding and removing the org.freedesktop.Platform.GL.default extension in the manifest