Flatpak

Zed v1.17.1-pre fixes an issue in Flatpak packaging environments where a defect in argument construction during command-line startup could accidentally open unrelated files (#62958).

Flatpak was led by the GNOME community (formerly known as xdg-app); it isolates application permissions through a Bubblewrap sandbox (based on Linux kernel namespaces and seccomp mechanisms), applications must request resource access through the Portal API, and updates use OSTree incremental update technology.

Flatpak bundles its dependencies internally, is sandboxed by default, and can be installed on almost any Linux distribution.

When assessing the security of a Flatpak application, one should focus on checking the permission declarations in the application manifest, prefer fine-grained paths such as --filesystem=xdg-download, and use tools such as Flatseal to audit the permissions of installed applications.

A widely circulated article criticizes Flatpak's sandbox and security model, arguing that its actual protective capability is lower than users assume.

Flatpak's sandbox model is built on Bubblewrap, isolating filesystem, network and device access through namespaces, with permissions declared via finish-args in the application manifest and additional authorizations requested through the portal mechanism.

Bubblewrap constrains the filesystem, network, and devices a process can see through namespaces and seccomp filters, and is often used by Flatpak as an underlying isolation layer.

Seatbelt is macOS's sandboxing framework, and bwrap (Bubblewrap) is a lightweight container tool on Linux based on user namespaces, which is used as the underlying mechanism by application sandboxes such as Flatpak

The portal-based file chooser (org.freedesktop.portal.FileChooser) is part of the XDG Desktop Portal specification and is one of the core design elements of Flatpak's least-privilege principle.

Using a pure-Python conversion library causes all conversion logic to be completed within the application process without invoking external executables, enabling operation in a closed sandbox without additional permission declarations.

Flatpak applications calling LibreOffice (soffice) must request the flatpak-spawn permission to break out of the sandbox boundary, which creates tension with Flathub security review requirements.

Bwrap (Bubblewrap) restricts process access via Linux namespaces and seccomp filters, and is one of the underlying mechanisms for Flatpak application isolation.

Bubblewrap is a low-privilege container tool on Linux, originally derived from the Flatpak project, that can create isolated namespaces without root privileges.

Flatpak and Snap applications bundle their own runtimes, which are large in size (easily hundreds of MB), have slow first launches, and suffer from friction in integrating with GTK/Qt theme engines.

Linux distribution packaging mechanisms vary, and distribution options include universal binary packages, Flatpak, Snap, or collaboration with distribution package maintainers, each with its own trade-offs.

Flatpak is led by Red Hat; applications run in a sandbox with dependencies shared through runtimes, and Flathub is its main application repository.

Zed v1.16.2 fixes an argument construction defect when launching Zed via Flatpak from the command line (#62959), a bug that caused Zed to accidentally open unrelated or nonexistent files.

Flatpak packages an application and all its dependencies into a standalone runtime container, implements process-level sandbox isolation via technologies such as Bubblewrap, and provides a unified distribution channel through Flathub.

When a Flatpak application calls command-line arguments, they must be forwarded through the flatpak run wrapper layer, making the argument-passing chain longer than with a native installation.

Flatpak appeared in 2015 and Snap appeared in 2016, providing user-friendly sandboxing solutions for desktop applications.