Shelly 2.3.2 GUI Package Manager for Arch Linux Gets Downgrade UI, Flatpak Repair

Shelly 2.3.2, the latest stable release of the open-source graphical package manager for Arch Linux-based distributions, arrived on 30 May 2026 with several highly anticipated features. Developed by Zoey Bauer and released just one week after Shelly 2.3.1, this rapid follow-up delivers a brand-new downgrade UI, the long-requested Flatpak repair workflow, a fully-featured ignore command group for managing IgnorePkg entries, and tooltip support across the entire GUI.

Shelly fills an important gap in the Arch Linux ecosystem: a polished, GTK-based graphical frontend for pacman and Flatpak that makes package management accessible to users who prefer a point-and-click interface over terminal commands, without sacrificing the power and transparency that Arch users expect. Version 2.3.2 pushes Shelly closer to feature parity with dedicated GUI package managers from other distributions while maintaining the speed and direct pacman integration that sets it apart.

1. What Is Shelly?

Shelly is a free, open-source graphical package manager designed specifically for Arch Linux and Arch-based distributions (Manjaro, EndeavourOS, Garuda Linux, and others). It provides a clean, modern GTK interface for pacman operations — installing, removing, updating, searching packages — as well as Flatpak management through a unified interface.

Unlike Pamac (the other major GUI package manager in the Arch ecosystem), Shelly is developed independently and focuses on directness and transparency: you see exactly what pacman commands will be run, the output is displayed in real-time during operations, and the interface mirrors pacman’s conceptual model rather than abstracting it away. For users who learned Arch Linux via the terminal and want a GUI that respects that foundation, Shelly is the natural choice.

Shelly’s Design Philosophy

Bauer has described Shelly’s design philosophy as “the pacman you know, with a face.” The interface is organised around the same operations that terminal users perform: install, remove, update, search, query — with the GUI adding discoverability, package detail views with dependency graphs, and the ability to manage multiple packages in a single transaction without building long pacman command strings manually.

The GTK 4 interface (Shelly has used GTK 4 from early in its development) provides crisp rendering on both X11 and Wayland, good HiDPI support, and native integration with GNOME and other GTK-based desktop environments. It also works well with Xfce and other environments that can run GTK 4 applications.

2. New Downgrade UI: Package Version Rollback

The headline feature of Shelly 2.3.2 is a brand-new downgrade UI that allows users to roll back any installed package to a previous version. This capability has been requested by Arch users since the project’s early days and was previously only available through manual terminal operations involving the pacman cache or the AUR’s downgrade package.

Why Package Downgrading Matters on Arch

Arch Linux is a rolling release distribution — packages are updated continuously rather than in discrete release batches. This means that breaking changes in a new package version can affect users immediately when they update. Common scenarios requiring a downgrade include:

• A new GPU driver update that breaks display output or gaming performance
• A kernel update that causes a compatibility issue with proprietary hardware
• An application update that removes a feature you depend on or introduces a bug
• A library update that breaks dependent applications before those applications can update
• A browser update that changes behaviour in ways that affect your workflow

Terminal-savvy Arch users handle this by installing the downgrade AUR package or by manually reinstalling from the pacman cache (/var/cache/pacman/pkg/). Shelly 2.3.2 brings this to the GUI.

How the Downgrade UI Works

The new downgrade interface is accessible from the package detail view for any installed package. It shows:

• The currently installed version with installation date
• A list of previous versions available in the local pacman cache (/var/cache/pacman/pkg/)
• Optionally, previous versions from the Arch Linux Archive (ALA) — a snapshot repository that maintains older package versions
• Dependency conflict warnings if downgrading to a specific version would break other installed packages
• A “Downgrade” button that executes the reinstallation with confirmation

The interface integrates with pacman’s dependency resolver to identify and warn about conflicts before executing the downgrade, reducing the risk of breaking the system in the process of rolling back a single package.

3. Flatpak Repair Workflow

The Flatpak repair workflow is the second major feature addition in Shelly 2.3.2, described in the release notes as “long-requested.” Flatpak installations can become corrupted or inconsistent through partial installs, storage issues, or interrupted update processes. The standard fix requires running flatpak repair from the terminal — a command that many GUI-focused users are not aware of or comfortable with.

Shelly 2.3.2 exposes this workflow through the GUI under the Flatpak management section. The repair operation can be triggered in two ways:

1. Manual repair — accessible from the Flatpak settings or a right-click context menu on the Flatpak section, allowing users to trigger a repair at any time
2. Automatic detection — Shelly monitors for symptoms of Flatpak database inconsistency (failed installs, missing runtimes, checksum errors) and surfaces a “Repair Flatpak Installation” prompt when these conditions are detected

The repair workflow shows real-time progress as flatpak repair scans and fixes the installation, and displays a summary of what was repaired or what could not be automatically fixed. For unfixable situations, Shelly provides guidance on manual remediation steps.

4. IgnorePkg Management: The Ignore Command Group

Pacman’s IgnorePkg and IgnoreGroup directives in /etc/pacman.conf allow users to prevent specific packages from being updated during pacman -Syu system updates. This is commonly used to hold back packages that are intentionally pinned to an older version — for compatibility reasons, stability requirements, or because a newer version has a known bug.

Previously, managing IgnorePkg entries required manually editing /etc/pacman.conf in a text editor. Shelly 2.3.2 introduces a complete ignore command group that surfaces this management in the GUI:

• View ignored packages — a dedicated “Ignored Packages” panel showing all currently ignored packages and groups, pulled from the live pacman.conf
• Add to ignore list — right-click on any installed package and select “Add to IgnorePkg” to prevent it from future updates
• Remove from ignore list — remove a package from the ignore list to allow future updates again
• IgnoreGroup support — manage package groups (e.g., ignore the entire base or gnome group) in addition to individual packages
• Update indicator — ignored packages that have available updates are shown with a distinct indicator (a lock icon), so users know that updates are available but held back intentionally

This feature brings Shelly in line with package managers on other distributions (APT’s “hold” mechanism, dnf versionlock, zypper locks) that have had GUI-accessible package pinning for years.

5. Tooltip Support Across the GUI

Shelly 2.3.2 adds tooltip support across all major GUI elements. While this is a smaller quality-of-life improvement compared to the headline features, it significantly improves discoverability — particularly for new users who are learning what each button, icon, and control does.

Tooltips appear on hover after a short delay and include:

• Button function descriptions (e.g., “Install selected packages,” “Refresh package database”)
• Package flag explanations (what “explicitly installed,” “dependency,” “orphan,” and “ignored” mean)
• Package size information when hovering over size indicators in the package list
• Repository badge descriptions

6. CLI Event-Driven Rewrite

Shelly includes a command-line interface (CLI) version — shelly-cli — that provides the same package management operations as the GUI but from the terminal, useful for scripting or for users who want Shelly’s higher-level abstractions in a terminal context. Version 2.3.2 rewrites the CLI with a proper event-driven architecture.

The previous CLI implementation polled for state changes rather than subscribing to events, which caused issues with operation sequencing and could result in the CLI displaying stale information during long-running operations. The event-driven rewrite ensures that the CLI responds to state changes in real-time and that operation sequences (e.g., database refresh → update → install) execute correctly without race conditions.

7. Package Detail View Enhancements

The package detail view — shown when you click on any package in Shelly — receives three new information fields in Shelly 2.3.2:

• Build Date — the date the package was compiled and added to the repository. Useful for identifying how recent a package version is and correlating with upstream release dates.
• Install As — indicates whether the package was installed explicitly (you directly installed it) or as a dependency (installed automatically because another package required it). This information was previously only visible through pacman -Qi output; Shelly now surfaces it visually.
• Required By — the list of currently installed packages that depend on this package. This information is critical before removing a package, as it shows the cascade of other packages that would also need to be removed. Previously available only through pacman -Qi or reverse-dependency queries.

The “Required By” field is particularly valuable for preventing accidental system breakage — understanding the full dependency tree before removing a library, runtime, or shared component is essential for maintaining a working Arch installation.

Additionally, a “Remove” button is added to the Recommendations section — the panel that shows optional dependencies and suggested companion packages. Previously, recommendations could be installed from this panel but not removed; the new Remove button provides symmetry.

8. New Translation Support

Shelly 2.3.2 adds translations for four new languages: Catalan, Portuguese, Turkish, and Brazilian Portuguese. This expands the application’s reach to significant user communities in Catalonia, Portugal, Turkey, and Brazil — regions where Arch-based distributions have substantial followings.

The Shelly translation project uses GNU gettext and is hosted on Hosted Weblate, allowing community contributors to add and improve translations without requiring development environment setup. If your language is not yet supported, the project welcomes translation contributions.

9. Installation and Upgrade Guide

# Install Shelly on Arch Linux from AUR
yay -S shelly
# or with paru:
paru -S shelly

# If already installed, update to 2.3.2
yay -Syu shelly
# or:
paru -Syu shelly

# Verify installed version
shelly --version
# Should output: Shelly 2.3.2

# Alternative: install from source
git clone https://github.com/zoeybauer/shelly.git
cd shelly
git checkout v2.3.2
meson setup build
ninja -C build
sudo ninja -C build install

10. Shelly in the Arch Linux GUI Tool Landscape

Conclusion

Shelly 2.3.2 is a meaningful update that adds three substantive features — the downgrade UI, Flatpak repair workflow, and IgnorePkg management — that address real pain points in the Arch Linux package management experience. Combined with the tooltip improvements, CLI rewrite, and expanded package detail information, this release noticeably improves Shelly’s utility as a daily-driver package manager for Arch-based Linux users who prefer a graphical interface.