Upstream software project

pop-launcher

Modular IPC-based desktop launcher service

About pop-launcher

Modular IPC-based desktop launcher service

This project links 3 native package records across 3 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

pop-launcher repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Fedora 43: 1 package records; Fedora 44: 1 package records; openSUSE Tumbleweed: 1 package records. Catalog coverage diagram, not an application screenshot.pop-launcher: recorded package coverageFedora 431 recordsFedora 441 recordsopenSUSE Tumbleweed1 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
pop-launcher
Publisher
Not authoritatively mapped
Native package records
3
Operating systems
fedora-43, fedora-44, opensuse-tumbleweed
License expression
MPL-2.0
Source repository
Open source repository

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

Modular IPC-based desktop launcher service, written in Rust. Desktop launchers may interface with this service via spawning the pop-launcher process and communicating to it via JSON IPC over the stdin and stdout pipes. The launcher service will also spawn plugins found in plugin directories on demand, based on the queries sent to the service. Using IPC enables each plugin to isolate their data from other plugin processes and frontends that are interacting with them. If a plugin crashes, the launcher will continue functioning normally, gracefully cleaning up after the crashed process. Frontends and plugins may also be written in any language. The pop-launcher will do its part to schedule the execution of these plugins in parallel, on demand.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Fedora 43

  1. Package pop-launcher

    43 (Fedora 43) (Unspecified): Modular IPC-based desktop launcher service

    1:1.6.0-2.fc43: aarch64 x86_64

    Source: pop-launcher

Fedora 44

  1. Package pop-launcher

    44 (Fedora 44) (Unspecified): Modular IPC-based desktop launcher service

    1:1.6.0-2.fc44: aarch64 x86_64

    Source: pop-launcher

openSUSE Tumbleweed

  1. Package pop-launcher

    tumbleweed (openSUSE Tumbleweed) (Unspecified): Modular IPC-based desktop launcher service

    1.0.8-1.4: x86_64

    Source: pop-launcher

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.