Other regular upstream updates including python and haskell
Get our latest daily developer images now from Github: Plasma, Gnome, XFCE. You can also help us with the Stable-Review images, so the upcoming installer ISOs are solid for Newcomers!
Our current supported kernels
linux44 4.4.258
linux49 4.9.258
linux414 4.14.222
linux419 4.19.177
linux54 5.4.101
linux59 5.9.16 [EOL]
linux510 5.10.19
linux511 5.11.2
linux512 5.12-rc1
linux54-rt 5.4.93_rt51
linux59-rt 5.9.1_rt19
Packages Changes (Wed Mar 3 10:49:15 CET 2021)
testing community x86_64: 1232 new and 1209 removed package(s)
testing core x86_64: 20 new and 18 removed package(s)
testing extra x86_64: 293 new and 344 removed package(s)
testing kde-unstable x86_64: 241 new and 240 removed package(s)
testing multilib x86_64: 25 new and 25 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)
This is a wiki post; please edit as necessary.
Please, consider subscribing to the Testing Updates Announcements RSS feed
Recent Arch Linux news:
PHP 8.0 and PHP 7 legacy packages are available
PHP 8.0 and PHP 7 legacy packages are available
2021-01-28 - Pierre Schmitz
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:
Note that support for php7 will be limited and likely be dropped in about a year depending on how soon the majority of applications will be compatible with version 8.
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.
We recommend to switch over to Nouveau drivers if your card is mentioned here and the feature you need is not in red TO DOhere for your particular card.
If you however still need proprietary drivers, you may want to execute the following to ensure all parts of the nVidia drivers get installed properly:
sudo mhwd -a pci nonfree 0300
If proprietary drivers don't fix everything, please click the âș at the beginning of this line to view more info
For AMD GPU users having a black screen with kernel 5.10
Please click the âș at the beginning of this line to view more info
Due to a bug in the AMD drivers, please try the following first:
For GRUB:
Open a terminal or a TTY
Open /etc/default/grub in your favourite CLI editor (nano vi, emacs`)
Find the line: GRUB_CMDLINE_LINUX_DEFAULT="
Add amdgpu.dc=0
Save
Execute sudo update-grub and reboot
For systemd-boot:
Open a terminal or a TTY
Open /boot/loader/entries/manjarolinux5.10.conf in your favourite CLI editor (nano vi, emacs`)
Add amdgpu.dc=0 to the end of the line options
Save & reboot
For rEFInd:
Open a terminal or a TTY
Open /boot/refind_linux.conf in your favourite CLI editor (nano vi, emacs`)
Find the line: "Boot using default options" "root=
Add amdgpu.dc=0
Save & reboot
Possible 2 Min delay on shutdown with Gnome
Please click the âș at the beginning of this line to view more info
If you got the problem with shutdown delay (about 2min) on Gnome, here is a workaround:
Edit /usr/lib/systemd/user/gnome-session-restart-dbus.service in your favourite editor as root and add Slice=-.slice as a line all by itself like this:
You get [PKGNAME] warning: directory permissions differ on [Directory name]
followed by:
Filesystem: NNN package MMM
Please click the âș at the beginning of this line to view this solution
The solution:
sudo chmod MMM DirectoryName
Where obviously MMM is the second number you see (the correct one)
The explanation:
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[1004]: -.slice: Failed to migrate controller cgroups from /user.slice/user-1000.slice/user@1000.service, 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.
Typical issue:
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[1453]: [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.
Rough translation: pipewire-pulse and pulseaudio are in conflict. I canât remove pipewire-pulse because it is not installed. Pipewire is, though.
Edit: Ok, pipewire aims to replace pulseaudio and pipewire-pulse has to be installed to provide access to pulseaudio. Got that. Iâm running Xfce, btw.
Newest powerdevil version 5.21.2 seems to have fixed the process not being able to terminate correctly at shutdown. Sadly it seems to have introduced another regression since i experienced a lot of warnings in the logs.
03.03.21 14:02 amdgpu 0000 3:00.0: amdgpu: Msg issuing pre-check failed and SMU may be not in the right state!
03.03.21 14:02 amdgpu 0000 3:00.0: amdgpu: Failed to export SMU metrics table!
03.03.21 14:02 amdgpu 0000 3:00.0: amdgpu: Msg issuing pre-check failed and SMU may be not in the right state!
03.03.21 14:02 amdgpu 0000 3:00.0: amdgpu: Failed to export SMU metrics table!
03.03.21 14:02 amdgpu 0000 3:00.0: amdgpu: Msg issuing pre-check failed and SMU may be not in the right state!
03.03.21 14:02 amdgpu 0000 3:00.0: amdgpu: Failed to enable gfxoff!
03.03.21 14:02 amdgpu 0000 3:00.0: amdgpu: Msg issuing pre-check failed and SMU may be not in the right state!
03.03.21 14:02 amdgpu 0000 3:00.0: amdgpu: Failed to export SMU metrics table!
It also disables all ability to read fanspeeds etc. After switching down to 5.20.5 no problems.
Edit: The bug had already been filed yesterday.
TL,DR: removing pulseeffects allows the update to go through. pulseeffects depends on pipewire-pulse, had to remove that. Replacing pulseaudio with pipewire breaks a lot of dependencies, among which is gnome-bluetooth. On the other hand, getting rid of pipewire ends up breaking flatpak.
is linux512 5.12-rc1 the kernel with the file system corruption issues? Iâll stay on 5.11 if thatâs the case and wait for a later release candidate.
I you want to continue to use PulseEffects, you require Pipewire indeed. On another side there is PulseEffects Legacy which uses PulseAudio.
I guess that depends on how you âreplaceâ things.
I donât believe so, Pipewire is not a Flatpak dependency.
TLDR: read PulseEffect development announces, especially the last one when they made their big move from Pulseaudio to PipeWire, and also the forum where this has been discussed a lot, and the simple solution back then was to not replace PulseAudio with the new, to me experimental, PipeWire thing, but using PulseEffects Legacy which was the previous version before the big change.
The mirrors with IPv6 canât sync anymore. I guess because AAAA DNS records were added to all manjaro servers. Now the IPv6 addresses of mirror servers are not whitelisted in the firewall of the repo server it seems.
GRUB-update ===> ERROR: Warnung: os-prober was executed to detect other bootable partitions.
As I start Wind**fs from /etc/grub.d/40_custom
AND have: GRUB_DISABLE_OS_PROBER=true in /etc/default/grub (wird missachtet!!!/ is disregarded !!!)
.
Solution: root-edit the file /usr/bin/os-prober and uncomment line 11: # ./usr/share/os-prober/common..sh
Well, Iâm just gonna put the first sentence of the post which you so thoroughly cite:
And indeed, afterwards, I installed pulseeffects-legacy (cosâ, you know, before posting, I try stuff, read here and there and so onâŠ).
If people want to install pamac-flatpak-plugin, they will end up having to install pipewire as a dependency. This being the testing branch, I thought it would be useful to let the devs know of that problem (pulseeffects requiring pipewire-pulse which conflicts with pulseaudio) when these packages get pushed to stable. But what do I know, right?
I can confirm here. As I only have one system to start on this computer, it is not necessary to run os-prober so I also had set GRUB_DISABLE_OS_PROBER=true in /etc/default/grub.
Nevertheless, os-prober is enabled by this update. I am sure that there are very sophisticated reasons for this decision. Hence, Iâd greatly appreciate some clarification why this step was necessary in order to allow me to understand.
For the time being, I have followed the advice and commented out ./usr/share/os-prober/common.sh in /usr/bin/os-prober on line 11.
@Berneri (and all): if you experience âcrackyâ sound when using pipewire (especially if you use pulseeffects), then try to play around with these parameters inside /etc/pipewire/pipwire.conf:
Great Job.