Welcome (linxira-welcome)
Why it exists
The first screen after boot should not be an empty desktop. linxira-welcome is a
Plasma-native status and routing surface: on the Live ISO it puts installation first;
on an installed system it reports whether the machine is ready and which first-run
steps are still pending, then offers a fixed allowlist of Linxira tools.
It only reads the versioned software catalog and the installer receipt. It does not
list installable software, and it never builds or executes shell strings, package
transactions, sudo or pkexec.
Responsibility boundaries
It owns: the five pages (Home, Status, Terminal, System, Help), Live vs installed
detection, health and first-completion state, language selection, the show-at-login
preference, the fixed launcher allowlist, and handing linxira-config subcommands to
a terminal.
It does not own:
- Software installation. Applications belong to Package Center; runtimes and components belong to Component Manager.
- Privilege escalation. Every tile launches a fixed program with fixed arguments;
there is no
sudoand nopkexec. - Catalog content. Applications, categories and component subcommands stay with their own products.
- Configuration. The System page only opens
linxira-configsubcommands in a terminal; the settings live in Config.
How to use
linxira-welcome # from the application menu or a terminal
linxira-welcome --autostart # what the login entry runs
The menu entry is /usr/bin/linxira-welcome; the autostart entry appends
--autostart. With --autostart, Welcome exits immediately if you cleared
Show Welcome at login on the Help page.
The five pages:
- Home. Live shows the install banner; clicking install writes the selected UI
language to
/tmp/linxira-installer-langand starts/usr/local/bin/linxira-installer-shell, so the installer continues in the same language. Installed shows health and first-completion tiles. If installation left deferred software or components behind, continuation banners open Package Center or Component Manager respectively. Below that is the launcher grid: Software Center (Shelly), Quick System Software Setup, Quick System Runtime Setup, Config CLI in a terminal, System Settings and Terminal; an installed system also gets System Update, Gaming Manager, Hardware and Drivers and Recovery Diagnostics, plus a driver quick-setup banner that also opens Hardware and Drivers. - Status. Release, kernel, network, catalog availability and review, installer receipt status, available updates, last check, reboot flag, and the profiles and applications chosen during installation.
- Terminal. bash is the system default and always installed. For fish, nushell or
zsh the button opens Quick System Runtime Setup with
--select; the transaction stays there. If the shell is already installed but is not your login shell, the button only copieschsh -s /usr/bin/fish(with the chosen path) to the clipboard. - System. Reads the capability manifest installed by
linxira-config-huband renders only commands carryingwelcomemetadata. Each tile opens the matchinglinxira-configsubcommand in a terminal. Mutating entries are skipped unless they opt in; laptop-only entries are hidden when the chassis is not portable and noBAT*device exists. - Help. Links to Arch Linux News, the Linxira Wiki, ArchWiki, the project site, the repository and the issue tracker, plus the show-at-login checkbox.
The language selector offers English, Simplified Chinese, Traditional Chinese, German, Spanish, French, Japanese, Korean, Brazilian Portuguese and Russian. The choice is persisted; unsupported locales fall back to English.
When root is needed
Never. Welcome has no elevation path: launchers use fixed executables and fixed
argument vectors, Config CLI is opened in the session's terminal (KDE runs
konsole --hold -e; on COSMIC the terminal starts with SHELL pointing at
linxira-config, which works on cosmic-term 1.10 and 1.11), and the System page
entries, which carry arguments, use cosmic-term -e on COSMIC. The Terminal page
copies chsh to the clipboard for you to run.
Anything requiring root goes through the owning tool and its own authorization model.
Launchers only start fixed programs: linxira-update --launch (System Update),
linxira-recovery-diagnostics-gui (Recovery Diagnostics) and
/usr/local/bin/linxira-installer-shell (Live install). A tile whose executable is
missing is disabled.
Known limitations
- It is an entry and status surface, not a live monitor of the other tools.
- The System page depends on
/usr/share/linxira/agent/capabilities.jsonfromlinxira-config-hub; when it is missing the page is empty. - Terminal dispatch is session-aware: COSMIC prefers
cosmic-term, KDE preferskonsole --hold -e, thenalacritty -eandxterm -hold -e. A single command (Config CLI) usesSHELLinjection on COSMIC so it also works on cosmic-term 1.10; other commands use the terminal's exec flag. Only when no terminal is usable does Welcome write a temporaryTerminal=trueentry forgtk-launch. - The System page shows only commands carrying
welcomemetadata;mutatingentries stay hidden unless the manifest opts in explicitly. A missing command removes one tile rather than raising an error. - The Live ISO uses an ephemeral profile, so Welcome opens on every fresh Live boot and the login preference does not persist across boots.
- Ten UI languages are shipped; everything else falls back to English.
Further reading
Implementation lives in the
linxira-welcome repository. Catalog
and receipt contracts are described under Catalog and
Package Center.