Manjaro, like many other open-source projects, relies on the generosity of its community through donations and corporate sponsorships to support its growth and development. These donations are essential in covering the various expenses incurred in the operations of the project such as server costs, software development tools, infrastructure expenses, training, flying people to events or conferences and the salaries of key developers. With the help of these donations, Manjaro is able to secure the necessary financial stability that allows the project to continuously improve and remain active. If you love Manjaro, consider to donate!
Previous News
As you might have seen some of our team were able to attend FOSDEM 2023 and the conference proved to be incredibly productive for us. See our blog post for more.
Protect your personal data, keep yourself safe (unlimited devices): 82% off + 2 mo. FREE
Finding information easier about Manjaro
Finding information easier about Manjaro always has been a topic that needed to be solved. With our new search we have put all Manjaro data accessible in one place and divided by sections so it makes it easier to digest: New Manjaro search engine is available | Blog
You will need to rebuild any AUR Python packages that install files to site-packages or link to libpython3.10.so.
Print a list of of packages that have files in /usr/lib/python3.10/ :
pacman -Qoq /usr/lib/python3.10/
Rebuild them all at once:*
pamac build $(pacman -Qoq /usr/lib/python3.10)
* Note that if any fail to build, you’ll have to rebuild what’s remaining one or a few at a time.
Use rebuild-detector to see if anything else needs to be rebuilt:
checkrebuild
Info about AUR packages
AUR (Arch User Repository) packages are neither supported by Arch nor Manjaro. Posts about them in Announcement topics are off-topic and will be flagged, moved or removed without warning.
Changes to default password hashing algorithm and umask settings
2023-09-22 - David Runge
With shadow >= 4.14.0, Arch Linux’s default password hashing algorithm changed from SHA512 to yescrypt [1].
Furthermore, the umask [2] settings are now configured in /etc/login.defs instead of /etc/profile.
This should not require any manual intervention.
Reasons for Yescrypt
The password-based key derivation function (KDF) and password hashing scheme yescrypt has been chosen due to its adoption (readily available in libxcrypt, which is used by pam [3]) and its stronger resilience towards password cracking attempts over SHA512.
Although the winner of the Password Hashing Competition [4] has been argon2, this even more resilient algorithm is not yet available in libxcrypt [5][6].
Configuring yescrypt
The YESCRYPT_COST_FACTOR setting in /etc/login.defs is currently without effect, until pam implements reading its value [7]. If a YESCRYPT_COST_FACTOR higher (or lower) than the default (5) is needed, it can be set using the rounds option of the pam_unix [8] module (i.e. in /etc/pam.d/system-auth).
General list of changes
yescrypt is used as default password hashing algorithm, instead of SHA512
pam honors the chosen ENCRYPT_METHOD in /etc/login.defs and does not override the chosen method anymore
changes in the filesystem (>= 2023.09.18) and pambase (>= 20230918) packages ensure, that umask is set centrally in /etc/login.defs instead of /etc/profile
ansible-core >= 2.15.3-1 update may require manual intervention
2023-08-19 - Robin Candau
As of ansible-core 2.15.3, upstream moved documentation and examples to a separate dedicated repository (see the related changelogs).
This means that, starting from version 2.15.3 the ansible-core package will stop shipping documentation and a default configuration example under /etc/ansible/ansible.cfg.
Regarding the documentation, it is available online: https://docs.ansible.com/
As for the configuration file, as explained in the wiki, a base config can be generated with the following command:
ansible-config init --disabled > ansible.cfg
After updating from ansible-core <= 2.15.2-1 to >= 2.15.3-1, everyone using a custom global Ansible configuration file stored under /etc/ansible/ansible.cfg will have their configuration saved as a pacsave file.
To restore it, run the following command:
When upgrading from budgie-desktop 10.7.2-5 to 10.7.2-6, the package mutter43 must be replaced with magpie-wm, which currently depends on mutter. As mutter43 conflicts with mutter, manual intervention is required to complete the upgrade.
First remove mutter43, then immediately perform the upgrade. Do not relog or reboot between these steps.
pacman -Rdd mutter43
pacman -Syu
2023-07-28
Grub conflicting files
Error: Failed to commit transaction:
conflicting files:
grub: /usr/bin/update-grub already exists in filesystem (owned by grub-update)
Steam crashes on startup with lib32-libgudev installed
The latest lib32-libgudev update does not cooperate with the version of the same package provided by steam, and steam seems to attempt making calls to both leading to the crash.
:: Vollständige Systemaktualisierung wird gestartet …
:: plasma-framework durch extra/plasma-framework5 ersetzen? [J/n] j
Abhängigkeiten werden aufgelöst …
Warnung: Kann "libdav1d.so=7-64" nicht auflösen (eine Abhängigkeit von "ffmpeg")
Warnung: Kann "libdav1d.so=7-64" nicht auflösen (eine Abhängigkeit von "ffmpeg4.4")
Warnung: Kann "libdav1d.so=7-64" nicht auflösen (eine Abhängigkeit von "ffmpeg")
Warnung: Kann "libdav1d.so=7-64" nicht auflösen (eine Abhängigkeit von "ffmpeg4.4")
:: Die folgenden Pakete können aufgrund nicht auflösbarer Abhängigkeiten nicht aktualisiert werden:
ffmpeg ffmpeg4.4
:: Möchten Sie die oben genannten Pakete bei dieser Aktualisierung überspringen? [j/N] n
Fehler: Vorgang konnte nicht vorbereitet werden (Kann Abhängigkeiten nicht erfüllen)
:: Unerfüllbare Abhängigkeit »libdav1d.so=7-64«, benötigt von ffmpeg
:: Unerfüllbare Abhängigkeit »libdav1d.so=7-64«, benötigt von ffmpeg4.4
:: Unerfüllbare Abhängigkeit »libdav1d.so=7-64«, benötigt von ffmpeg
:: Unerfüllbare Abhängigkeit »libdav1d.so=7-64«, benötigt von ffmpeg4.4
ffmpeg is required by firefox, ffmeg4.4 is required by vlc.
dav1d version 1.2.1-1 is currently installed, so for @Hanzel’s proposal it’s too late already.
Have a look here as well:
Update:
After updating again, everything is fine now.