Error when running "sudo pacman -Syu"

I don’t know what exactly happened, but everything was working fine days ago before I left home. Today when I got back after a couple of days, I turned on the PC, and ran “sudo pacman -Syyu” Everything worked fine, update all the packages that it told me to update, and prompted me to reboot.

After the the reboot, I decided to run “yay -Syyu” as I always do after running pacman, I got prompted with this
yay -Syyu
:: 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)

I then tried pacman to see if maybe it was something with yay, but again, same error. I have been trying to search on how to fix it but I can’t find much, only way is to disable sandbox(which i never had to do before). Don’t know how that affects security, but if it does I would like to fix it, but I’m not educated enough on this matter to find a fix. Please help D:

What kernel are you running?

As a side note, don’t run yay -Syyu after running pacman -Syu. In that situation, just run yay -Sua. This is unrelated to your problem though.

Oh , didn’t know about -Sua, that great to know haha.

To answer your question, I am on Linux 6.17.9-arch1-1 kernel

I am not sure why that would be missing landlock support.

You can edit /etc/pacman.conf and disable the sandbox for now.

Set DisableSandboxFilesystem

Yeah I don’t know either. As far as I am aware, it does support landlock, and I have it on(if I did it right, not sure), but yeah I guess ill just disable sandbox for now. Is there any security issues with disabling the sandbox??

It is better to have it enabled than disabled but the sandbox was only added last year so we were all running pacman without a sandbox for years.

Sounds great! hopefully someone that has the same issue as me strolls by or makes a post about this haha, Thank you for your help! Have a good one :slight_smile:

Possibly related; getting a very similar error when trying to run pacseek -u: https://github.com/moson-mo/pacseek/issues/61

For reference, I’m on 6.18.1-1-cachyos kernel.

Yeah on my search i saw that packseek had the same issue. Im going to assume its possibly a bug or something that got introduced on some of the other packages, because I updated my system on dec a couple of times(last time being Dec-11th before I left home) and it was all working fine(linux 6.17.9 was published on Nov-30th) so i don’t think its the kernel itself causing the issue.

Reported fixed with 1.8.6 released today.

1 Like