OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
pacman-aur medium occasional DISPUTE

Stop pacman aborting downloads with 'Operation too slow'

archomarchyendeavouroscachyosmanjarodesktoplaptop
AUDITED Audited against its sources and confirmed accurate. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

Thread 173909 shows the exact symptom including the byte-range message and a security gateway at work, but it predates and does not mention DisableDownloadTimeout, so the pacman.conf(5) man page is added as the source for the fix. man pacman.conf and man pacman on this machine (pacman 7.1.0) document DisableDownloadTimeout and --disable-download-timeout for proxy and security gateway problems. pacman-conf Color prints Color, consistent with the verify step. Read on 4.0.4-1: omarchy-update-system-pkgs calls pacman with fixed arguments, so extra flags cannot be passed. Omarchy-refresh-pacman overwrites /etc/pacman.conf then runs omarchy-hook pre-refresh-pacman, and omarchy-hook runs every non-.sample file in ~/.config/omarchy/hooks/pre-refresh-pacman.d with bash. Omarchy-channel-set calls omarchy-refresh-pacman. The mirrorlist has one server. Not exercised: no download was made and no hook was installed.

Symptom

Downloads die after a few seconds even though the connection is fine, often on a large package:


error: failed retrieving file 'foo-1.2-1-x86_64.pkg.tar.zst' from mirror.example.org : Operation too slow. Less than 1 bytes/sec transferred the last 10 seconds
warning: failed to retrieve some files
error: failed to commit transaction (failed to retrieve some files)

Sometimes followed by HTTP server doesn't seem to support byte ranges. Cannot resume. as it moves to the next mirror.

Cause

pacman's built-in downloader applies a low-speed limit: a transfer that moves less than 1 byte per second for 10 seconds is aborted. A server or proxy that is slow to start sending (a cold cache, a security gateway scanning the file, a congested mirror, a VM NAT) trips it while the real throughput would have been fine. With several mirrors pacman retries the next one. On Omarchy 4 the mirrorlist holds exactly one server, so one stalled transfer fails the whole download step.

Fix

Delete any partial file for the failing package first, then retry:


sudo find /var/cache/pacman/pkg -name '*.part' -delete

**Plain Arch, one transaction:**


sudo pacman -Syu --disable-download-timeout

**Permanently, any distro.** Add the option under [options] in /etc/pacman.conf:


[options]
DisableDownloadTimeout

**Omarchy 4.** omarchy update does not pass extra flags to pacman, so use the config option above and then run omarchy update. omarchy refresh pacman and omarchy channel set overwrite /etc/pacman.conf, so re-apply it from the hook Omarchy runs right after that copy:


mkdir -p ~/.config/omarchy/hooks/pre-refresh-pacman.d
cat > ~/.config/omarchy/hooks/pre-refresh-pacman.d/50-download-timeout <<'EOF'
grep -q '^DisableDownloadTimeout' /etc/pacman.conf || sudo sed -i '/^\[options\]/a DisableDownloadTimeout' /etc/pacman.conf
EOF

If transfers are genuinely slow rather than slow to start, rank mirrors (plain Arch) instead of only lifting the timeout.

Verify

pacman-conf DisableDownloadTimeout prints the option name when it is set, and the next upgrade downloads the package that previously aborted.

Sources

download-operation-too-slow-timeout