A simple, lightweight distribution for 32-bit CPUs

You've reached the website for Arch Linux 32, the community maintained continuation of 32-bit support for Arch Linux, a lightweight and flexible Linux® distribution that tries to Keep It Simple.

Currently we have official packages optimized for the i686 and pentium4 architectures. Also most(ly) non-graphical packages are available for i486, too. Have a look at the required cpu flags to decide which architecture is the right one for you. Most packages from Arch Linux's community-operated package repository are also compatible with Arch Linux 32.

Installation media which boot on i686 can be found here.

Join us on #archlinux32 IRC channel on Libera, check out our forums or subscribe to the mailing list to get your feet wet. Also glance through the Arch Wiki if you want to learn more about upstream Arch.

Latest News

RSS Feed RSS Feed

Arch Linux 2024 Leader Election Results


Recently we held our leader election, and the previous Project Leader Levente "anthraxx" Polyák ran again while no other people were nominated for the role.

As per our election rules he is re-elected for a new term.

The role of of the project lead within Arch Linux is connected to a few responsibilities regarding decision making (when no consensus can be reached), handling financial matters with SPI and overall project management tasks.

Congratulations to Levente and all the best wishes for another successful term! 🥳

Increasing the default vm.max_map_count value


The vm.max_map_count parameter will be increased from the default 65530 value to 1048576.

This change should help address performance, crash or start-up issues for a number of memory intensive applications, particularly for (but not limited to) some Windows games played through Wine/Steam Proton. Overall, end users should have a smoother experience out of the box with no expressed concerns about potential downsides in the related proposal on arch-dev-public mailing list.

This vm.max_map_count increase is introduced in the 2024.04.07-1 release of the filesystem package and will be effective right after the upgrade.

Before upgrading, in case you are already setting your own value for that parameter in a sysctl.d configuration file, either remove it (to switch to the new default value) or make sure your configuration file will be read with a higher priority than the /usr/lib/sysctl.d/10-arch.conf file (to supersede the new default value).

xz backdoor in Archlinux32


The xz versions 5.6.0 and 5.6.1 should be considered harmful in Archlinux32,
especially the last versions installed:


Make sure that the following versions  or newer are installed:


The xz package has been backdoored


Update: To our knowledge the malicious code which was distributed via the release tarball never made it into the Arch Linux provided binaries, as the build script was configured to only inject the bad code in Debian/Fedora based package build environments. The news item below can therefore mostly be ignored.

We are closely monitoring the situation and will update the package and news as neccesary.

TL;DR: Upgrade your systems and container images now!

As many of you may have already read (one), the upstream release tarballs for xz in version 5.6.0 and 5.6.1 contain malicious code which adds a backdoor.

This vulnerability is tracked in the Arch Linux security tracker (two).

The xz packages prior to version 5.6.1-2 (specifically 5.6.0-1 and 5.6.1-1) contain this backdoor.

The following release artifacts contain the compromised xz:

  • installation medium 2024.03.01
  • virtual machine images 20240301.218094 and 20240315.221711
  • container images created between and including 2024-02-24 and 2024-03-28

The affected release artifacts have been removed from our mirrors.

We strongly advise against using affected release artifacts and instead downloading what is currently available as latest version!

Upgrading the system

It is strongly advised to do a full system upgrade right away if your system currently has xz version 5.6.0-1 or 5.6.1-1 installed:

pacman -Syu

Upgrading container images

To figure out if you are using an affected container image, use either

podman image history archlinux/archlinux


docker image history archlinux/archlinux

depending on whether you use podman or docker.

Any Arch Linux container image older than 2024-03-29 and younger than 2024-02-24 is affected.

Run either

podman image pull archlinux/archlinux


docker image pull archlinux/archlinux

to upgrade affected container images to the most recent version.

Afterwards make sure to rebuild any container images based on the affected versions and also inspect any running containers!

Regarding sshd authentication bypass/code execution

From the upstream report (one):

openssh does not directly use liblzma. However debian and several other distributions patch openssh to support systemd notification, and libsystemd does depend on lzma.

Arch does not directly link openssh to liblzma, and thus this attack vector is not possible. You can confirm this by issuing the following command:

ldd "$(command -v sshd)"

However, out of an abundance of caution, we advise users to remove the malicious code from their system by upgrading either way. This is because other yet-to-be discovered methods to exploit the backdoor could exist.

Older News

mkinitcpio hook migration and early microcode
Making dbus-broker our default D-Bus daemon
Bugtracker migration to GitLab completed
Incoming changes in JDK / JRE 21 packages may require manual intervention
Changes to default password hashing algorithm and umask settings
ansible-core >= 2.15.3-1 update may require manual intervention
budgie-desktop >= 10.7.2-6 update requires manual intervention
Shim packages required for 'icu'
New package signing keys
Git Migration
upstream git migration
In case of key problems
Dropping Haskell
OpenSSL 3.0.7
systemd 251.2 breaks logins
CA certificates file is empty
ISO 2022.02.01 available
error while loading shared libraries: libicui18n.so.68
Warning about upgrading to zstd 1.5.1
nss 3.73 crashes firefox
libffi.so.7: cannot open shared object file: No such file or directory

Recent Updates (more)

RSS Feed
icu 75.1-1.0 i486
libxml2 2.13.1-1.1 i486
libxml2-docs 2.13.1-1.1 i486
linux-api-headers 6.8-1.1 i486
libcap 2.70-1.0 i486
crypto++ 8.9.0-1.1 i486
mbedtls2 2.28.8-3.0 i486
libogg 1.3.5-2.0 i486
spglib 2.4.0-3.0 pentium4
havn 0.1.12-1.0 pentium4
cargo-semver-checks 0.32.0-1.0 pentium4
python-maxminddb 2.5.2-1.0 pentium4
lucene++ 3.0.9-1.0 pentium4
tickrs 2:0.14.10-1.0 pentium4
apptainer 1.3.2-1.0 pentium4