mirror of
https://github.com/Droid-Deck/DroidDeck.git
synced 2026-11-18 12:28:40 +00:00
feat: Flatpak apps and a Flathub store (#77)
* feat: run Flatpak apps through a proot bwrap stand-in and add a Flathub store * feat: give Flatpak apps the KGSL GPU, the controllers and a CPU LLVM can target * feat: Flatpak games on the desktop, Store apps on the Desktop page, safer remove * test: cover the sandbox planner and store helpers; docs: explain Flatpak on DroidDeck * fix: keep controller focus through Store tabs and app pages; show progress per Flatpak step * fix: let Chromium, Electron and Firefox Flatpaks start without their own sandboxes * fix: fetch Flatpak's supporting libraries when the runtime lacks them * fix: add Flathub without a download, log store commands, keep Electron apps on X11 under gamescope * feat: import ARM64 AppImages from storage and run them from the Desktop page * fix: report failed Flatpak installs as failures and deploy runtimes that ship a resolv.conf link * fix: let Flatpak create its repo where Android denies hard links * fix: point store commands at the current network's DNS * fix: keep failed Flatpak extensions non-fatal, give Electron AppImages a bus, X11 and time to relaunch * docs: AppImage import and what x86 apps would take * feat: put the Flathub Store and AppImage import behind beta toggles in Setup --------- Co-authored-by: MaxsTechReview <maxjividen@gmail.com>
This commit is contained in:
1 parent
970fc3a946
commit
4a234b2824
38 files changed
+3293
-20
No files matched your search
@@ -0,0 +1,118 @@
|
||||
# Flatpak and the Store
|
||||
|
||||
Both features are beta and off by default. Setup → Launcher → "Linux apps (beta)" has one toggle for the
|
||||
Flathub Store, which shows the Store rail item and the Store's apps on the Desktop page, and one for
|
||||
AppImages, which shows the AppImages section. Turning either off hides it; installed apps stay installed
|
||||
and remain in the Linux desktop's menu.
|
||||
|
||||
The Store rail section installs apps from Flathub into the Linux runtime with Flatpak. Only
|
||||
ARM64 builds are listed. Everything lives in one per-user installation at
|
||||
`/root/.local/share/flatpak`, so nothing needs Flatpak's system helper or polkit.
|
||||
|
||||
## Putting Flatpak in the runtime
|
||||
|
||||
`bannerlator-flatpak-setup` runs under proot's fake root (`-0`), because pacman and pacman-key
|
||||
refuse any other uid. The runtime's pacman database lists only the base image. The desktop
|
||||
and emulator packages were unpacked over it without registering. A plain `pacman -S flatpak`
|
||||
would therefore reinstall about a hundred packages, Mesa among them, over the runtime's KGSL
|
||||
Turnip build, and run every hook in the image, mkinitcpio included. So pacman, with a
|
||||
database of its own under `/var/cache/droiddeck-flatpak`, only downloads the nine packages
|
||||
Flatpak adds to this image and checks their signatures against the Arch Linux ARM keyring.
|
||||
The script then unpacks them without hooks and checks what the binaries link. Libraries that
|
||||
the Desktop package normally brings (PyGObject, json-glib, fuse3 and others) are fetched too,
|
||||
but only when their files are missing. Flathub is added as a per-user remote from a copy of
|
||||
its `.flatpakrepo` carried in the script, so that step needs no network. Every store command
|
||||
writes its output to `Download/DroidDeck/flatpak-<verb>.log`, next to the session logs. The
|
||||
setup script also puts Flatpak's own error text in the failure message the app shows.
|
||||
|
||||
## bubblewrap without namespaces
|
||||
|
||||
Android gives apps no user namespaces, so `bwrap` cannot work. Flatpak is pointed at
|
||||
`bannerlator-bwrap` instead (`FLATPAK_BWRAP`, exported by `bannerlator-session` and by the
|
||||
store's commands). It reads bwrap's command line, including `--args` fds and the `--file` and
|
||||
`--bind-data` payloads, and then does one of two things:
|
||||
|
||||
- A sandbox that remaps nothing runs directly. Flatpak's install triggers (`--ro-bind / /`) and
|
||||
the D-Bus proxy (every top-level directory bound onto itself) are the cases, and they keep the
|
||||
file descriptors Flatpak handed them.
|
||||
- Anything else is described to the app over the abstract socket
|
||||
`com.droiddeck.launcher.bwrap`, which serves only the app's own uid. `BwrapSpawner` builds the
|
||||
tree under `cache/bwrap/<n>`: a root directory for top-level links, directories and files,
|
||||
scratch directories for `--tmpfs` inside a bind, and every `--bind` translated from guest
|
||||
to host paths through the session's own binds. It then starts it as a proot of its own
|
||||
beside the session's. Output, the pid (for `--info-fd`) and the exit status flow back, and
|
||||
the stand-in exiting kills the sandbox.
|
||||
|
||||
A proot nested in the session's proot would also work, but every system call then goes
|
||||
through two tracers, about thirty times slower at a program's start.
|
||||
|
||||
The spawner also adds what the rootfs gives its own programs:
|
||||
|
||||
- **GPU.** Flathub's Mesa has Turnip only for DRM, and Adreno on Android is KGSL. The runtime's
|
||||
own `libvulkan_freedreno.so` is bound in with the three libraries the Freedesktop runtime
|
||||
lacks (`libdisplay-info`, SPIRV-Tools). Vulkan uses it, and Mesa's GL runs on it through Zink
|
||||
(`MESA_LOADER_DRIVER_OVERRIDE=zink`). This is skipped for an app drawing into a desktop
|
||||
composited by pixman, where Zink cannot present.
|
||||
- **Controllers.** The libraries in the rootfs's `/etc/ld.so.preload` (the session shim and the
|
||||
fake evdev reader) go in through `LD_PRELOAD`, with the session's `dev` directory.
|
||||
- **Browsers.** Firefox's child sandboxes are switched off (`MOZ_DISABLE_*_SANDBOX`), and
|
||||
Chromium and Electron apps use zypak's mimic strategy (`ZYPAK_ZYGOTE_STRATEGY_SPAWN=0`). The
|
||||
Flatpak portal's Spawn refuses a caller whose `/proc/<pid>/root` holds no `.flatpak-info`,
|
||||
and a proot sandbox's root is the host's.
|
||||
- **CPU.** `/proc/cpuinfo` without the cores' part numbers. Snapdragon's ARMv9 cores imply SVE2
|
||||
to LLVM, Qualcomm leaves SVE off, and llvmpipe's first shader died with SIGILL.
|
||||
|
||||
## Running apps
|
||||
|
||||
The front end starts an app as a run-mode session of `bannerlator-flatpak-run <app-id>`, full
|
||||
screen under gamescope. Under gamescope it passes `--nosocket=wayland --socket=x11` and sets
|
||||
`XDG_SESSION_TYPE=x11`. Otherwise Flatpak finds the app compositor's `wayland-0` and the window
|
||||
opens behind gamescope. gamescope's own Wayland socket is no alternative: Chromium on Wayland
|
||||
asks the render node it names for a DRM version, which KGSL cannot give, and aborts. The
|
||||
launcher also starts a session bus when there is none. On the Linux desktop, the apps' exported
|
||||
menu entries appear in the LXQt menu. While the desktop is composited by pixman, games are
|
||||
wrapped through `droiddeck-gpu` like the rootfs's own.
|
||||
|
||||
## The store
|
||||
|
||||
`FlathubApi` reads flathub.org's public API: collections, search filtered to `aarch64`, and
|
||||
AppStream details. `bannerlator-flatpak` drives libflatpak through PyGObject and prints one
|
||||
JSON object per line (`op`, `progress`, `error`, `done`). `FlatpakManager` turns those lines
|
||||
into the store's progress bar. Store commands run in a proot of their own, and
|
||||
`OrphanReaper` spares them when a session starts.
|
||||
|
||||
## AppImages
|
||||
|
||||
"Add AppImage" on the Desktop page imports an ARM64, type 2 AppImage from storage. `AppImageManager`
|
||||
checks its ELF header first, so an x86_64 image is refused with a message saying so. It then copies the
|
||||
image in, because shared storage is noexec, and extracts it once to `/opt/appimages/user/<id>/app`.
|
||||
proot has no FUSE, and extracting at every start would cost the whole image each time. The name,
|
||||
comment and icon come from the image's own desktop entry. A menu entry goes to
|
||||
`/usr/local/share/applications`, where the desktop's GPU wrapper picks it up.
|
||||
|
||||
`bannerlator-appimage-run` starts it:
|
||||
|
||||
- `APPIMAGE` stays unset, so apps don't offer to add themselves to the menu or update in place.
|
||||
- Firefox forks get the same sandbox switches as Flatpaks.
|
||||
- Electron apps (a `chrome-sandbox` beside them) get `--no-sandbox` and X11.
|
||||
- A session bus is started when the session has none.
|
||||
- The launcher waits while anything from the image still runs, because Electron apps relaunch themselves.
|
||||
|
||||
Known to fail:
|
||||
|
||||
- Obsidian's own AppImage traps (SIGTRAP) after startup. Its Flatpak works.
|
||||
- Zen's AppImage hangs in Firefox's startup GPU probe. The Firefox Flatpak works.
|
||||
|
||||
## x86_64 apps
|
||||
|
||||
Flathub lists x86_64-only apps (Heroic, Discord, Spotify, Steam), and the store hides them. Running them
|
||||
would need an x86 emulator in the sandbox. There's no FEX or box64 package in Arch Linux ARM; Valve's
|
||||
ARM64 Steam can install its FEX compatibility tool, but only through the Steam client. With a FEX binary
|
||||
available, the path would be:
|
||||
|
||||
1. `flatpak install --arch=x86_64`. Flatpak accepts it, and the x86 runtime is also the x86 root FEX needs.
|
||||
2. `BwrapSpawner` starts those sandboxes with `proot -q`, through a small wrapper that runs FEXInterpreter.
|
||||
`-q` passes QEMU-style arguments.
|
||||
3. GPU drivers would need FEX's thunks, or Mesa runs emulated on the CPU.
|
||||
|
||||
x86 AppImages would also need an x86 rootfs for the libraries they don't bundle.
|
||||
Reference in new issue
Block a user