On the 10th and 11th of October there is going to be an online edition of Arch
Conf. The conference is going to have presentations from the Arch team along
with community submitted presentations and lightning talks.
We are proud to announce the first revision of the schedule!
The conference timezone is CEST/UTC+2: https://everytimezone.com/s/40cc4784
Updates and additional information can be found on the conference page: https://conf.archlinux.org
See you there!
Cheers from the conference team.
We would like to hold a bug wrangling day on the 13th of September to reduce the large amount of open tickets.
If you cannot take part in the bug wrangling day, then feel free to help us any time before that event.
Please review all bugs that were reported by you and check if they are still
valid. Please request a task closure on the bug tracker if the task may be closed. Otherwise please provide further information so that we can continue to work on the bug.
We cannot fix bugs without your feedback.
Join us at #archlinux-bugs channel on irc.freenode.net during 13th of September. As we live in different timezones not all devs and bug wranglers will be available at the same time, but feel free to report your issues to any dev available.
Also please check your mailboxes that may contain notifications about comments made on your tickets.
libxcrypt provides /usr/lib/libcrypt.so.2, while glibc only has /usr/lib/libcrypt.so.1
Arch for x86_64 pulls in libxcrypt via dependency (e.g. of systemd), but I experienced it not being installed on i686 and i486 (and most probably also pentium4).
This leads to broken linking in e.g. sshd:
# ldd /usr/bin/sshd
libcrypt.so.2 => not found
If this is the case for you after an update, install libxcrypt manually
pacman -S --asdeps libxcrypt
I'm reluctant to force-move systemd to core, because this might break other stuff which I'm currently not aware of.
If you use pam 1.3 and pambase 20200721 you might not be able to login due to
a missing pam_faillock.so module. Make sure you are using pam 1.4 when using
If you upgrade to pam 1.4 you might experience all kind of weird login problems.
You might also get `pam_systemd(login:session): Failed to create session: Input/output error`
in your log and just hanging text console logins.
You can also get sporadic ssh logins with an sshd going 100% CPU and never letting
you log in.
Any manual configuration changes in the pam modules have to be checked
carefully before upgrading, some modules have gone (like pam_tally2, cracklib).
Also make sure to merge your .pacnew/.pacsave files.
In case you experience similar problems you can also downgrade to:
- pambase-20190105.1-2.0 and
- pam-1.3.1-2.0 (for pentium4) resp.
pam-1.3.1-2.0 (for i686) resp.
pam-1.3.1-2.0 (for i486).