Fix 'warning: directory permissions differ' during an upgrade
The openssl case holds. The EndeavourOS thread of 2026-06-09 shows the warning on openssl 3.6.2-2 to 3.6.3-1 and links the packaging commit. The Arch GitLab API shows commit b8cf05c2 'restrict /etc/ssl/private to 0700; closes #1' dated 2026-04-20, released in June 2026, so the cause's month is right for the shipped package. On this machine /etc/ssl/private is 700. libalpm.so.16 contains the two-line directory permissions differ on %s / filesystem: %o package: %o message as quoted. pacman.log shows /boot 700 against 755 and /var/log/swtpm/libvirt/qemu 730 against 755. pacman -Qkk prints (Permissions mismatch), and /boot is vfat mounted with dmask=0077. Thread 245014 supports /var/lib/AccountsService/users/. The one defect is in the symptom: it names /root/ as a common case, which neither source mentions. /root is 750 here and owned by filesystem 2025.10.12-1 with no mismatch, so that example is unsupported and is removed. Nothing was chmodded.
Tightening a directory that a service relies on reading as another user can stop that service. Use the mode the package itself declares, not a guess.
Symptom
An upgrade prints a warning and carries on:
(1/4) upgrading openssl
warning: directory permissions differ on /etc/ssl/private/
filesystem: 755 package: 700
Another reported case is /var/lib/AccountsService/users/ after an accountsservice upgrade. It repeats every time that package is upgraded. Users ask whether to fix it or ignore it.
Cause
pacman never changes the mode of a directory that already exists, so when a package changes the permissions it ships for a directory (or an admin or a program changed them on disk), pacman only reports the difference. The openssl case is a deliberate packaging change: Arch's openssl package restricted /etc/ssl/private to 0700 in June 2026, and existing systems keep their old 0755 directory until it is changed by hand. A wider mode on a private-key directory lets other local users list what it holds.
Fix
Set the directory named in the warning to the mode the package ships, which is the package: value:
sudo chmod 700 /etc/ssl/private
stat -c '%a %n' /etc/ssl/private
To see every permission mismatch pacman knows about, list them for review:
sudo pacman -Qkk 2>&1 | grep -i 'permissions mismatch'
Do not chmod everything that command prints. Change a path only when the package made it stricter and the warning appeared during an upgrade, as with /etc/ssl/private. Leave these alone:
- Mount points, whose mode comes from the mount options. On Omarchy 4,
/bootis a vfat ESP mounted withdmask=0077, so it always reads 700 against the package's 755, and chmod cannot change it. - Directories a service manages and resets itself, such as
/var/log/swtpm/libvirt/qemu(libvirt) or/var/cache/pacman/pkg. - Anything you widened or tightened on purpose. That warning then repeats on every upgrade of that package, which is harmless.
Verify
stat -c '%a %n' /etc/ssl/private prints 700 /etc/ssl/private, and the next upgrade of that package prints no warning.