Here same problem on my wife pc. It doesn’t boot with kernel 419 anymore, as I experienced on my pc when testing updated to systemd 248, reported here.
I tried many kernel versions and, on my pc, the 419 was the only one affected by this problem,
The issue seems to be not solved, yet.
Hm, I used the mirrors that were picked by pacman-mirrors. I do not remember and did not check if they were all trusted https mirrors.
Yes, it’s been resolved, but is it known if that issue was actually exploited?
I know this is a highly theoretical question, albeit an interesting one, isn’t it?
My understanding of it is that if you had http mirrors up until the keyring refresh, you were vulnerable. So any package installed/updated from now on is safe. I’m not sure about the ones currently installed that weren’t updated yet. My hunch is they’re unsafe, but this needs to be clarified.
I’ve noticed many of you had issues with this update and I wonder if sudo pamac upgrade should resolve most of the issues, then I’d suggest the following tutorial should be updated accordingly, to reflect such important change:
Currently it still recommends using sudo pacman -Syyu.
Thanks for the hint about the systemd version, hopefully they will fix it soon.
I only kept that old kernel , because I tested how that uses swap, compared to 5.x.
I wish the stable branch should have more quality testing before releasing updates.
No way back to Ubuntu for me
sudo pacman -Syyu (here returned errors) has been deemed fool-proof or at least it led me to believe it had always been like that till I read the suggestion:
XFCE user here. I looked through the comments on this post, and found that going through the update was not so good when using pacman. So I used pamac update instead. Apparently, it’s safe to run with kernel > 5.10 and the update removed libcanberra. Successfully updated with no major hiccups so far.