The php package has been updated to version 8.0. Please refer to the upstream migration guide. As some applications are not compatible with PHP 8 yet we provide a php7 package which can be installed alongside version 8. Packages that depend on PHP reflect this update and will require php7 if needed. You might need to update your configuration accordingly. PHP 7 binaries and configuration have the “7” suffix:
Google has announced that they are going to block everything but Chrome from accessing certain Google features (like Chrome sync) starting on March 15. This decision by Google is going to affect Arch’s chromium package a bit earlier, on March 2, when Chromium 89 gets released.
We know for sure that data syncing will stop working (passwords, bookmarks, etc.). Other features such as geolocation or enhanced spell check might continue to function for a bit longer. Extensions integrating with Google Drive might misbehave and LibreOffice will lose access to documents stored there.
Other distros such as openSUSE and Fedora have already removed the soon-to-be-limited API keys from their Chromium 88 packages. Fedora’s advisory provides a great deal of perspective on this and I also found this Hackaday post to be quite informative.
You get [PKGNAME] warning: directory permissions differ on [Directory name]
Filesystem: NNN package MMM
Please click the ► at the beginning of this line to view this solution
sudo chmod MMM DirectoryName
Where obviously MMM is the second number you see (the correct one)
Your package expects the security permissions to be MMM but your system is set to NNN. This is just a warning (today) but to ensure you remain up-to-date with the latest and greatest security rules it’s advised to execute the above command.
Systemd error message: .slice: Failed to migrate controller cgroups
If you have a similar error message like this:
systemd: -.slice: Failed to migrate controller cgroups from /firstname.lastname@example.org, ignoring: Permission denied
… you may need to add this Grub parameter to your /etc/default/grub file in line GRUB_CMDLINE_LINUX_DEFAULT: systemd.unified_cgroup_hierarchy=true. To update your grub menu, call: sudo update-grub. For more information on that issue, see also Arch Forum.
Python 3.9 Requires Rebuilds
Instructions for quickly and easily rebuilding affected AUR packages:
# Install yay
sudo pacman -S --needed --noconfirm yay
# Rebuild AUR python packages
yay -S --noconfirm $(pacman -Qqo "/usr/lib/python3.8/site-packages")
The libtraceevent package prior to version 5.9-1 was missing a soname link. This has been fixed in 5.9-1, so the upgrade will need to overwrite the untracked files created by ldconfig. If you get any of these errors
libtraceevent: /usr/lib/libtraceevent.so.1 exists in filesystem
PAM and PAMBASE got updated, which might prevent you from login
Due to updates from pambase and pam you might take care about any .pacnew files in /etc/pam.d as for example pam_tally, pam_tally2 and pam_cracklib got deprecated. Read in the ArchWiki about managing those files.
For recovery, it is enough to boot with kernel option “systemd.unit=rescue.target”, then proceed into /etc/pam.d and merge “system-auth” and “system-auth.pacnew”
System takes a long time to boot
If you’ve got errors like Failed to start Network Manager Wait Online. you can try removing systemd from passwd and group in /etc/nsswitch.conf as described here Update: If you can see the line dbus-daemon: [system] Connection has not authenticated soon enough, closing it (auth_timeout=30000ms, elapsed: 45146ms)
in in your dbus log ( journalctl -b -u dbus ), the new/better workaround is to switch cups from service to socket as described here: systemctl disable cups.service systemctl enable cups.socket
I think I’ve some font problems
With the update of fontconfig some major rules how fonts get applied changed. Make sure that your system has ttf-dejavu installed. A more in depth explanation can be found here.
Gnome-shell-extension-pop-shell is currently incompatible with wayland
… and causes the system to freeze when the first window is tiled and can render it unbootable. Solution is a hard reset and disabling either pop shell or wayland. If the system becomes unbootable, use a live USB to edit /etc/gdm/custom.conf to disable wayland and reboot.
and the graphical desktop could not be loaded.
In Xorg.0.log, I had the following errors:
[ 168.106] (II) Loading sub module "ramdac"
[ 168.106] (II) LoadModule: "ramdac"
[ 168.106] (II) Module "ramdac" already built-in
[ 168.108] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the
[ 168.108] (EE) NVIDIA: system's kernel log for additional error messages and
[ 168.108] (EE) NVIDIA: consult the NVIDIA README for details.
[ 168.108] (EE) No devices detected.
[ 168.108] (EE)
Fatal server error:
[ 168.108] (EE) no screens found(EE)
[ 168.108] (EE)
dmesg showed the following errors:
[ 1.159347] nvidia: version magic '5.11.2-1-MANJARO SMP preempt mod_unload ' should be '5.11.4-1-MANJARO SMP preempt mod_unload '
[ 1.168887] nvidia: version magic '5.11.2-1-MANJARO SMP preempt mod_unload ' should be '5.11.4-1-MANJARO SMP preempt mod_unload '
[ 1.177875] nvidia: version magic '5.11.2-1-MANJARO SMP preempt mod_unload ' should be '5.11.4-1-MANJARO SMP preempt mod_unload '
[ 1.231638] nvidia: version magic '5.11.2-1-MANJARO SMP preempt mod_unload ' should be '5.11.4-1-MANJARO SMP preempt mod_unload '
[ 1.284749] nvidia: version magic '5.11.2-1-MANJARO SMP preempt mod_unload ' should be '5.11.4-1-MANJARO SMP preempt mod_unload '
[ 1.296969] nvidia: version magic '5.11.2-1-MANJARO SMP preempt mod_unload ' should be '5.11.4-1-MANJARO SMP preempt mod_unload '
Apparently, simply reinstalling the linux511-nvidia390xx package is not enough - the driver needs to be compiled against the new kernel.
After I re-created the linux511-nvidia390xx package from the PKGBUILD on GitLab (Packages / Extra / linux511-extramodules / nvidia-390xx · GitLab), re-installed it and also did sudo mkinitcpio -P, I was able to load the graphical desktop again after another reboot.
What remains interesting:
After cd /lib/modules/5.11.4-1-MANJARO/extramodules and sudo modinfo * | grep -E "filename|vermagic" I could verify that the version magic seems to be correct:
This will be a huge change for people who wants to have dual booting, like the classic Manjaro/Windows dual boot. This is not really a bug in itself, as it is intentionally disabled and not by accident because of a programming error, but this choice means that people won’t be able to boot Windows from GRUB, which is something that we were usually able to do on Manjaro and with Linux OS in general and somehow has become the “de facto” standard in term of behavior.
Manjaro will most likely suffer from this choice for a time, and I do expect a lot of complains from the users, outcrying that “MY DUAL BOOT IS BROKEN CAN’T BOOT TO WINDOWS” or even worse, “OH MY GOD MANJARO DELETED WINDOWS HOLY CRAP” simply because they can’t see Windows in GRUB anymore.
Plus, any new user trying to do a dual boot will have an unpleasant surprise that they have to change the configuration of GRUB in order to have access to GRUB inside Windows, and I am afraid that Manjaro will be compared to Ubuntu, Linux Mint, etc., where it still works as it used to be (although there is no guarantee that it won’t change in the future).
For people that use UEFI, you can still boot Windows manually by selecting it in the boot override menu or whatever, although it is much less convenient than selecting it from GRUB I suppose.
I know it has been disabled for security reasons. But disabling it is not without consequence. Hopefully users will be able to accept this new reality. I would understand if Manjaro devs revert their decision for the sake of convenience and user-friendliness though.
Of course, people that use Manjaro as their only operating system has nothing to fear from this change, obviously.