You are not logged in.
$ pacman -Syuor using pacman with any other arguments, indeed, fails after:
:: Synchronizing package databases...
error: restricting filesystem access failed because Landlock is not supported by the kernel!
error: switching to sandbox user 'alpm' failed!
error: failed to synchronize all databases (failed to retrieve some files)
-> error refreshing databases - exit status 1The second error is what my question is about. I've tried:
$ id alpm
uid=935(alpm) gid=935(alpm) groups=935(alpm)$ sudo su - alpm
This account is currently not available.$ cat /etc/passwd | grep alpm
alpm:x:935:935:Arch Linux Package Management:/:/usr/bin/nologinWhat is this user alpm supposed to do and how do I fix this?
Last edited by diederick76 (2025-12-18 06:44:18)
Offline
What kernel are you using?
Online
What kernel are you using?
Nothing special.
$ uname -a
Linux zaphod 6.18.1-arch1-2 #1 SMP PREEMPT_DYNAMIC Sat, 13 Dec 2025 18:23:21 +0000 x86_64 GNU/LinuxOffline
Mod note: Moving to Pacman issues.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Online
Does the version reported `pacman -Q linux` match the uname output? If it does, do you pass the security option to the kernel to change the default LSM use?
Offline
Does the version reported `pacman -Q linux` match the uname output?
It does:
$ pacman -Q linux
linux 6.18.1.arch1-2If it does, do you pass the security option to the kernel to change the default LSM use?
I'm passing on apparmor. Could that be it?
Last edited by diederick76 (2025-12-17 18:20:09)
Offline
This is odd, though. My current lsm config appears:
$ cat /sys/kernel/security/lsm
capability,apparmorBut if I understand it correctly, this is configured:
$ grep CONFIG_LSM= /proc/config.gz
CONFIG_LSM="landlock,lockdown,yama,integrity,bpf"Also:
grep GRUB_CMDLINE_LINUX_DEFAULT /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet lsm=apparmor"I did not alter these options during last boot. What does this apparent inconsistency mean?
Last edited by diederick76 (2025-12-17 18:27:18)
Offline
I did not alter these options during last boot. What does this apparent inconsistency mean?
lsm=apparmorDisables all the default LSM landlock,lockdown,yama,integrity,bpf.
Offline
And that was the issue. Adding
lsm=landlock,lockdown,yama,integrity,apparmor,bpfto the kernel command line made pacman work as expected again. Thanks for pointing me in that direction.
Offline