Unfortunately I can’t remember, as I said. The command appeared in the output when I ran pacman -Syyu, otherwise I wouldn’t have known it. Someone more expert in Manjaro may be able to help you there.
Check for perl packages (probably from AUR) which still use the old /usr/lib/perl5/5.32:
$ pacman -Qo /usr/lib/perl5/5.32
Re-install all of them.
1 Like
Thanks. I will do that. Thanks for all your help guys 
Upgrade fails for my system with the following messages related to libcanberra:
# pacman -Syyu
:: Synchronizing package databases...
core 169.4 KiB 2.36 MiB/s 00:00 [#####################################################################] 100%
extra 1903.8 KiB 2.82 MiB/s 00:01 [#####################################################################] 100%
community 6.6 MiB 2.87 MiB/s 00:02 [#####################################################################] 100%
multilib 177.7 KiB 3.27 MiB/s 00:00 [#####################################################################] 100%
:: Starting full system upgrade...
:: Replace lib32-libcanberra-pulse with multilib/lib32-libcanberra? [Y/n] Y
warning: lib32-systemd: local (248.2-1) is newer than multilib (247.7-1)
:: Replace libcanberra-pulse with extra/libcanberra? [Y/n] Y
warning: systemd: local (248.2-1.1) is newer than core (247.7-1)
warning: systemd-libs: local (248.2-1) is newer than core (247.7-1)
warning: systemd-sysvcompat: local (248.2-1) is newer than core (247.7-1)
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing lib32-libcanberra (0.30+2+gc0620e4-4) breaks dependency 'lib32-libcanberra=0.30+2+gc0620e4-3' required by lib32-libcanberra-gstreamer
:: installing libcanberra (0.30+2+gc0620e4-4) breaks dependency 'libcanberra=0.30+2+gc0620e4-3' required by libcanberra-gstreamer
Any info on how to resolve these would be appreciated!
Hey! I added export IGNORE_CC_MISMATCH=1 to /etc/environment, after that the driver was built and works on kernels 5.4 and 5.10.
the problem with the test branch still remains in the stable
Try a workaround
Chromium --high-dpi-support=1 --force-device-scale-factor=2
1 Like
Update worked but had to reboot before being able to connect USB drive.
Shouldn’t the command be …python3.9… not …python3.8…. under Older Issues, second post.
I use pacman and see these messages on the console, as well as grepping /var/log/pacman.log.
Where do pamac GUI users see these warning messages?
1 Like
No. The command targets packages built for the old version.
1 Like
But the title says, “Python 3.9 Requires Rebuilds”
Right. Whenever a new version is released, packages with files in the older version’s directory need to be rebuilt.
1 Like
Looks like the link is okay now.
What is the difference between, “Different overlay package(s)” vs “Different sync package(s)” for the various repositories?
On a side note, I uncommented VerbosePkgLists in /etc/pacman.conf to get a nice readable table of updates.
Ah got it. The python apps from AUR require the rebuild for the new python on the system.
I haven’t come across it myself, but I suppose it can happen that the AUR package isn’t ready for the new version of python?
I suppose that is when users start looking at python virtual environments?
Thank you banjo, that work-around works perfectly 
Overlay packages have been built by Manjaro Team.
Sync packages are taken as they were from Arch.
No.
ÀUR packages are built locally against the then installed versions of other packages/libs (python in this case) when installed.
They (oftentimes) need to be rebuilt, when those libs get updated.
Sometimes one gets away without rebuilding and the AUR package just seems to work - but if any “suspicious” malfunctioning starts happening it’s a good idea to first freshly rebuild the AUR package in question.
Sometimes these packages won’t work at all without rebuilding - as is the case with these python packages.
Everything seems to be fine on cinnamon.
It looks like you are on Testing branch?
But to answer your question, use Pamac to upgrade.
1 Like
Hello, I fixed my issue with nvidia 340-xx.
Tnx for the info, but I also had some error 2 thing 
Since I was on kernel 5.10.41-1 fallback initramfs wich was compiled with 11.1 gcc according to inxi -Sazy and kernel 5.4.123 was completely unusable, I decided to uninstall and install again.
So I uninstalled kernel 5.4.123 and the headers as well and installed it again.
linux54 and linux54-headers
It worked!! without any errors!! I did that through pamac its easier.
So first would be to try to boot to a fallback if it works or install another kernel through
tty CTRL + Alt + F3
If all goes well you boot to that kernel and again uninstall k 5.10.41-1 and install again.
linux510 and linux510-headers
If all goes well you can boot to k 5.10.41-1 and enjoy
This worked for me.
@6x12 tagging you in case you haven’t solved yet.
1 Like