Explore the field guideDocumentationField guidesCommunitySearchStoreJournal

2026-01-27

Linyaps support in xdg-desktop-portal 1.21.0: the announcement and its scope

The January 2026 community announcement alongside the actual upstream release note, with a practical portal check that does not mistake support for universal certification.

On this pageThe announcement’s project contextThe implications described for three audiencesWhat was reported at the timeThe precise upstream evidenceCheck one portal-dependent task

Original publication: 2026-01-27. English edition and practical reading notes: Linglong editorial, 18 October 2026. Chinese original.

On 27 January 2026 the community published an announcement headed “XDG officially supports Linyaps”. It introduced freedesktop.org’s XDG work as a common basis for Linux desktop interoperability, from icons and menus to notifications and file selection.

The announcement’s project context

The article described Linyaps as a cross-distribution application format originating in the deepin community and donated to the OpenAtom Foundation. It emphasized isolation, dependency management and the “one architecture, one build” objective as ways to reduce repeated packaging work.

It presented XDG integration as an important upstream collaboration and argued that common interfaces could make resource access and application development more consistent across desktops. It also made broad claims about compliance, security, least privilege and equivalence to Flatpak. Those are claims in the historical announcement; the upstream evidence below supports a narrower, specific statement.

The implications described for three audiences

  • Users: the article envisaged explicit control over access to selected files, cameras and other resources, instead of broad exposure of personal directories.
  • Developers: it argued that reusable desktop interfaces could reduce per-distribution permission-integration work.
  • The desktop ecosystem: it presented shared resource-access interfaces as a way to reduce fragmentation between application formats.

What was reported at the time

The article reported more than 6,000 adapted applications and support across more than ten distributions, naming deepin, UOS, Ubuntu, Debian and Fedora. These are January 2026 statements from that announcement, not this website’s current compatibility count. Its closing invitation called for collaboration on application distribution and linked to the Linyaps project, community website and forum.

The project description reiterated goals of reducing dependency conflicts, maintenance work and environment-related compatibility problems through an isolated application environment. Those goals do not replace application-level testing.

The precise upstream evidence

The linked xdg-desktop-portal 1.21.0 release, published on 21 January 2026, lists “Support linyaps applications” under new features and references change #1846. That confirms support in this named component and release. It is not a certification of every XDG specification, a security audit of every Linyaps package, or proof that every resource access on every desktop prompts the user.

The original announcement also linked to the community website, the project organization and the Linyaps forum section.

Check one portal-dependent task

  1. Record the application, Linyaps version, portal service version and desktop backend.
  2. Choose one task, such as opening a user-selected test file, rather than assuming all permissions work alike.
  3. Record what request or dialog actually appears, and test both cancellation and a permitted selection.
  4. Check that the application handles the result correctly. Keep unrelated personal files out of the test.
Application / Linyaps:
xdg-desktop-portal version / backend:
Desktop / task:
Observed dialog:
Cancel result:
Selected test-file result:
Unexpected access or failure:

The diagram is a conceptual request path. The application’s integration and the installed backend determine actual behavior.

A conceptual portal request travels from an application through xdg-desktop-portal to a desktop backend and a user choice; support is not universal certification.
A conceptual portal request travels from an application through xdg-desktop-portal to a desktop backend and a user choice; support is not universal certification. Diagram: Linglong editorial; based on the original publication linked below.