If you like following latest Plasma development you may also like to check out our current version of manjaro-kde-dev, which we build on a regular basis against kde-git master packages. Also check out our latest Manjaro Ornara 21.0 preview release! KDE, XFCE and Gnome
Our current supported kernels
linux59 5.9.16 [EOL]
Packages Changes (Thu Jan 14 03:18:58 CET 2021)
testing community x86_64: 1105 new and 1115 removed package(s)
testing core x86_64: 27 new and 28 removed package(s)
testing extra x86_64: 371 new and 432 removed package(s)
testing multilib x86_64: 10 new and 10 removed package(s)
A detailed list of all package changes can be found here.
No issue, everything went smoothly
Yes there was an issue. I was able to resolve it myself.(Please post your solution)
Yes i am currently experiencing an issue due to the update. (Please post about it)
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 /email@example.com, 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.
[ 3.159344] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20200925/utaddress-204)
[ 3.159352] ACPI: This conflict may cause random problems and system instability
[ 3.159353] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 3.159360] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20200925/utaddress-204)
[ 3.159365] ACPI: This conflict may cause random problems and system instability
[ 3.159366] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 3.159368] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20200925/utaddress-204)
[ 3.159372] ACPI: This conflict may cause random problems and system instability
[ 3.159373] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 3.159374] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20200925/utaddress-204)
[ 3.159378] ACPI: This conflict may cause random problems and system instability
[ 3.159379] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Linux 5.10 still seems to be heavily buggy, causing everything to load slowly, for example gnome takes like 10s to load and my terminal takes a couple of seconds (instead of instantly). Can’t see anything different in journal, just the time to launch taking alot more time.
I have my KDE showing me thumbnails when I switch between open programs (ALT+TAB), and after the update and reboot the thumbnails are almost triple in size from before. Not really liking that visual change.
mytake on this, while updates in testing branch are deemed less stable they are more granular thanks to having more frequent update cycles. the updates only change small subsets of software at a time. whereas updates in stable branch pack updates to many more software at time increasing the probability of breakage.
i dont have stats, but i’m also assuming there are larger number of people using the staging branch than there are the testing branch, which also exposes the possible issues with larger number of niche configurations (mostly hardware) also exacerbated by many software changes.
IMHO i think testing branch is best play-safe branch you could be in from my experience in the two. you get sane granular batch updates, whilst also standing behind unstable branch. i’m not meaning to say it is insane to be on the unstable branch. afterall only things that have made it into arch-stable makes its way there. just that i found updates keep coming endlessly a bit too much to manage.
That certainly makes sense. My worries are: why the latest “stable” updates appear to be more buggie than those stable updates, let’s say a few months ago. I’ve never experienced any issues with older stable updates. I may have been just lucky (and I use manjaro for over 2 years now), but my guess is that the latest updates come with more bugs from upstream and I mean not only Arch but also the kernel itself…