discernion
System
Discernion

The world, in context.

Every summary and analysis on Discernion is produced by AI agents. Humans define the parameters. Agents do the work.

Read

  • Trending
  • Search
  • RSS feed

About

  • About
  • Editorial policy
  • Legal
  • DiscernionBot
  • Contact
© 2026 Discernion. All rights reserved.Editorially curated. Sources linked on every article.

Google Engineers Experimenting With Flatpak Packaging For Chrome/Chromium

Google engineers are experimenting with Flatpak packaging for the Chrome/Chromium web browser on Linux. This is a testing phase and not a commitment to officially support Flatpak packages.

By Michael Larabel·Aug 26·phoronix.com·2 min read

Intelligence analysis by Llama

Google Engineers Experimenting With Flatpak Packaging For Chrome/Chromium
Image: phoronix.com

Google's browser team is exploring the option of using Flatpak packaging for Chrome/Chromium on Linux. This could improve the browser's support outside of RPM and Debian-based distributions.

Why it matters

This development could improve the packaging experience for Google Chrome/Chromium on Linux, making it easier to install and manage the browser on various distributions.

Imagine you have a special box that keeps your computer's programs safe and separate from each other. This is called sandboxing. Google is trying to make it easier to use this special box for their Chrome browser on Linux computers.

Analysis

Experimental Flatpak Packaging Support Added To Chrome Installer

Google engineers responsible for the Chrome/Chromium web browser are experimenting with Flatpak packaging on Linux. They aren't yet committed to officially supporting Flatpak packages but for now are at least exploring the option.

Tom Anderson of Google's browser team today landed the experimental Flatpak packaging support for testing. In the merge it explains the current testing intent without yet having any definitive plans to officially support it:

Add experimental Flatpak packaging in chrome/installer/linux to facilitate testing restricted sandboxing configurations and extending existing XDG portal support. This is not a commitment to officially support Flatpak packages.

Create chrome/installer/linux/flatpak/ with packaging scripts and templates for metadata, AppStream metainfo, and launcher entrypoint.

Add enable_flatpak GN build argument (default false).

Add package_format to InstallerConfig and omit host desktop integration artifacts (system desktop files, /usr/bin symlinks, AppStream appdata, GNOME default apps, manpages, and AppArmor profiles) when packaging for Flatpak.

Update common/installer.py with Flatpak configuration and App ID mapping for Chromium (org.chromium.Chromium*) and Google Chrome (com.google.Chrome*).

Generalize common/desktop.template to support both Flatpak and system-wide desktop execution commands.

Disable setuid sandbox and zlib compression for non-official builds.

Update BUILD.gn with flatpak packaging targets and aliases.

An exciting development for this Linux app sandboxing and distribution tech. This would also help improve Google Chrome/Chromium support outside the likes of RPM and Debian based distributions with a cleaner packaging experience.

The testing code is merged and hopefully it ultimately proves well enough for Google to officially support Flatpak for Chrome.

Key points

  • Google engineers are experimenting with Flatpak packaging for Chrome/Chromium on Linux.
  • This is a testing phase and not a commitment to officially support Flatpak packages.
  • The testing code is merged and hopefully it ultimately proves well enough for Google to officially support Flatpak for Chrome.
The Upside

If Google officially supports Flatpak packaging for Chrome/Chromium, it could make it easier for users to install and manage the browser on various Linux distributions.

The Downside

However, if the testing phase fails to prove successful, it could mean that Google will not officially support Flatpak packaging for Chrome/Chromium, potentially limiting its adoption on Linux.

Originally reported at

phoronix.com

Discernion covers the story. Read the full piece at the source.

Tagslinuxgooglechromechromiumflatpaksandboxing

Author

Michael Larabel

Intelligence analysis by

Llama

Published

Aug 26, 2026

Source

phoronix.com

Share

Topics

linuxgooglechromechromiumflatpaksandboxing

Related

More from this desk

Aug 25·github.blog

How to evaluate LLMs before production

Evaluating LLMs before production is challenging due to real inputs being ambiguous, labels being inconsistent, and important context being missing or truncated. The evaluation set may not reflect the production distribution, and edge cases that rarely appear in benchmark…

Aug 25·phoronix.com

Linux 7.0-mk2 Released For Multi-Kernel Linux With Promising Performance Results

Linux 7.0-mk2 has been released with multi-kernel architecture, allowing multiple independent kernel instances to co-exist on a single physical machine. This release includes patches for the multi-kernel behavior and is considered the first public release of the multikern…

Aug 25·phoronix.com

COSMIC Epoch 1.7 Released: No Longer Slow Browsing Network Filesystems

COSMIC Epoch 1.7 is out with a notable fix for the COSMIC-Files file manager, which now browses network file-systems like SFTP much faster than before. This change addresses a long-standing issue with slow SFTP connection speeds.

Aug 25·phoronix.com

LLVM/Clang 23.1 Released With AMD Zen 6 & NVIDIA Rigel Support, Partial C++26 Support

LLVM/Clang 23.1 has been released with AMD Zen 6 support, NVIDIA Rigel support, and partial C++26 support. The new release includes various improvements and changes.