[ARM Stable Update] 2022-02-27 - Plasma 5.24, GCC Toolchain, Firefox 97, Gnome 41.4, PlaMo Gear 22.02 and Kernels

Hello ARM community.

This is a pretty big update as we are about to release 22.02 of Manjaro ARM!


Plasma 5.24 is here!


Some highlights:

  • Most of our kernels got updated
  • KDE Frameworks updated to 5.91
  • And Plasma itself is now at 5.24.2
  • GCC Toolchain got updated to the newest from Arch Linux
  • Also Firefox got updated to 97.0.1
  • Gnome updated to 41.4
  • And GStreamer got the long awaiting 1.20 update
  • Thunderbird update to 91.6.1
  • And Plasma Mobile Gear got updated to 22.02 (except dialer, because of a serious regression)
  • Lots of updated packages for our Mobile offerings
  • The regular Python updates
  • And regular updates from upstream

How to get Waydroid working

If you follow these steps, you should have Waydroid working fine.

Remember, Waydroid only works on wayland!

  • Install waydroid-image and all it’s dependencies.
  • Run pkexec setup-waydroid.
  • You should now be able to launch Waydroid. The first launch takes a while.
How to use Kodi RPI on Manjaro ARM

If anyone wants to test kodi on the rpi, install these packages:

sudo pacman -S kodi-rpi kodi-rpi-dev kodi-rpi-eventclients kodi-rpi-tools-texturepacker libcec-rpi linux-rpi4 xf86-video-fbdev

Have it set up is to boot straight in to kodi

This means the kodi.service file need to replace whatever login manager you have installed. In my case I would:

sudo systemctl disable lightdm.service
sudo systemctl enable kodi.service

They recommend removing custom configs in config.txt. We ran into an issue if a value was set with gpu_mem=.

My config.txt with a bit of overclocking:

over_voltage=5
arm_freq=2000
#gpu_mem=64     #disable this
initramfs initramfs-linux.img followkernel
kernel=kernel8.img
arm_64bit=1
disable_overscan=1

#enable sound
dtparam=audio=on
hdmi_drive=2

#enable vc4
dtoverlay=vc4-kms-v3d,cma-512
#max_framebuffers=2    #disable cause kodi uses more
dtoverlay=rpivid-v4l2
disable_fw_kms_setup=1

Some notes:

The default user will be kodi
kodi home directory will be /var/lib/kodi
So put test video in /var/lib/kodi/Videos so you can get to it
after setting up the video directory in kodi.


Upstream Notifications:

Older notifications

If you used the Manjaro ARM Installer or is using PinePhone or PineTab, you need to redo your passwords, because of an update to libxcrypt:
Arch Linux - News: Sorting out old password hashes

Chromium will loose sync support in early March:
Arch Linux - News: Chromium losing Sync support in early March

ghostpcl>=9.53.2-2 and ghostxps>=9.53.2-2 updates require manual intervention:
Arch Linux - News: ghostpcl>=9.53.2-2 and ghostxps>=9.53.2-2 updates require manual intervention

The nss and zn_poly packages requires manual intervention:
Arch Linux - News: nss>=3.51.1-1 and lib32-nss>=3.51.1-1 updates require manual intervention
Arch Linux - News: zn_poly 0.9.2-2 update requires manual intervention

The packages hplip and firewalld requires manual intervention:
Arch Linux - News: hplip 3.20.3-2 update requires manual intervention
Arch Linux - News: firewalld>=0.8.1-2 update requires manual intervention


Package changes:

(Sun Feb 27 12:01:23 CET 2022)

  • arm-stable community aarch64: 924 new and 875 removed package(s)
  • arm-stable core aarch64: 113 new and 111 removed package(s)
  • arm-stable extra aarch64: 760 new and 760 removed package(s)
  • arm-stable kde-unstable aarch64: 415 new and 415 removed package(s)

See the full package list here


Testers needed on arm-testing branch

We are in need of testers for our arm-testing and arm-unstable branches.
So if you are adventurous and want newer software quicker, we would love for you to help us test out the new packages in arm-testing branch.

All you have to do to switch to this branch is:

  • Run this command to switch branch: sudo pacman-mirrors -aS testing && sudo pacman -Syyu. This will generate a new mirrorlist for you, sync your databases with the new mirror and update your system using the arm-testing branch.

We would then love for you to give feedback in our update posts in #manjaro-arm:arm-testing-updates. That way we can better find and fix bugs, before they hit arm-stable branch. Thank you!


Donation

Please consider supporting Manjaro ARM directly via Patreon, Ko-Fi or Open Collective.
You can also donate to our upstream, which is Arch Linux ARM.

Poll

  • 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)

0 voters

Check if your mirror has already synced:

1 Like

Known Issues and Solutions

This is a wiki post, please edit it when you find a solution to an issue you encountered

Waydroid container cannot access internet

Cause: new default waydroid configuration issue, tracked here.

Short-term Solution:

  1. create /etc/nftables.d/waydroid.nft with the following contents:
#!/usr/sbin/nft -f
table inet filter {
    chain input {
        iifname "waydroid0" accept comment "Allow incoming network traffic from WayDroid"
    }
    chain forward {
        iifname "waydroid0" accept comment "Allow outgoing network traffic from WayDroid"
        ct state {established, related} counter accept comment "accept established connections"
    }
}
  1. any time you launch waydroid, run the following after it has started:
echo "ip route add default via 192.168.250.1" |sudo waydroid shell
Old Issues
Plasma Mobile - Black screen after update

We are seeing some reports about Plasma Mobile on the PinePhone only showing a black screen after entering the PIN after this update.
Workaround: Downgrade qt5-es2-wayland to 5.15.2+kde+r41 which is now back in Stable and Testing branch repositories.

New Breath theme not applying correctly

With the update to the new Breath theme, a migration package tries to apply the new theme correctly.
However this is not getting done for Plasma’s Lockscreen and the SDDM theme.
So please go through your settings after updating to make sure the themes are correctly applied.
Fix: manjaro-system should take care of this for you.

Plasma Mobile switch to ModemManager

With the PlaMo Gear 21.12 release, Plasma Mobile is now using ModemManager as the telephony stack. So in order to use SIM capabilities, you need to switch from using oFono to ModemManager.
Fix: Run sudo systemctl disable --now ofono ofonoctl && sudo systemctl enable --now ModemManager. You might have to reboot your phone for Plasma Mobile to pick up this change.

Plasma Mobile has does not launch after update
This was caused by an error in kwin 5.23.2 which only affects installs based on openGLES (qt5-es2).
Fix: Update to kwin 5.23.2-1.2 or above.

No ethernet on rk3399 boards
A recent kernel regression has resulted in built in ethernet on rk3399 based boards, such as RockPro64 and Rock Pi 4’s, no longer works on kernel 5.14. This is an upstream issue that has not been fixed yet.
Fix: Update to linux-5.14.1-2 or newer.

Vivaldi no longer working
The issue is present in all chrome based browser (except Chromium that got a patch for it).
It’s an issue with systemd-resolved and has been reported in the Arch Linux Bug Tracker.
Needs to be fixed by Vivaldi updates in the future.
Fix: Vivaldi 4.1.2369.21 fixed this issue.

Modemmanager-pp dependency issue
modemmanager-pp 1.16.10 depends on libqmi-pp and libmbim-pp, but they are no longer found in the repo.
Fixed by updated to modemmanager-pp 1.18rc1+2+ga20f2c05-2.

systemd-hook unsuccesful after pacman 6 update
After the pacman 6 update, updates will create this message in the post-transation hooks part:

Running the command manually works and there has been no issues reported as the result of this. This will either get fixed at some point in Pacman or SystemD.
Should be fixed with pacman-6.0.0-4

Keyring issues
If you have some gpg keyring issues, you can run sudo systemctl start pacman-init.service which will regenerate your keyring. Will take a few minutes to complete.
Should be fixed with manjaro-system-20210716-1

Plasma Mobile no longer boots
The current update to qt5-es2-base results in Plasma Mobile no longer booting, showing a screen that says to run a loginctl command to login.
Fixed by updating to qt5-es2-base-5.15.2+kde+r199-3.1 and qt5-es2-declarative-5.15.2+kde+r28-3.1.

Kwin crashes on startup on Pinebook Pro
This seems to be related to Mesa 20.3 and the Pinebook Pro support in kernel 5.10, as this does not seem to happen on other devices.
It does not impact 3d performance as far as I can tell. Just the OpenGL compositing in Kwin.
Fixed with mesa 20.3.2-2.

My VPN no longer connects
OpenVPN 2.5.0 changed how VPN routes work.
Workaround is to downgrade to previous version (2.4.9):

sudo pacman -U /var/cache/pacman/pkg/openvpn-2.4.9*

DP Alt Mode no longer works on Pinebook Pro
This is a known issue, the hacky patch we had to enable this has broken in recent kernels.
@tsys and Ayufan are looking into it.
As a workaround you can install linux-pinebookpro again.
FIXED with linux-5.9.12-4 and linux-rc-5.10-rc7-2 and above.

brcm-patchram-plus and pi-blueooth are in conflict
See this post for workaround:
[ARM Testing Update] 2020-11-16 - Bitwarden, Mesa-Git, Pacman and kernels - #10 by Darksky

Plasma Mobile Keyboard
The plasma mobile onscreen keyboard does not work with QT 5.15.0.
This is fixed by updating to kwin 5.19.3-1.1.

PinePhone uboot
This update to the PinePhone Uboot package (2020.04-2), changed how the DTS is loaded from the kernel, since the Kernel DTS for the Pinephone also changed. When doing this update on the PinePhone images from Alpha5 and back, please make this change to the /boot/extlinux/extlinux.conf before rebooting:

  • sun50i-a64-pinephone.dtb to sun50i-a64-pinephone-1.2.dtb
  • root=LABEL=ROOT to root=LABEL=ROOT_MNJRO

Manual interventions:
The nss and zn_poly packages prior to version 3.51.1-1 and version 0.9.2-2 respectively, were missing a soname link each. This has been fixed in 3.51.1-1 and 0.9.2-2 of these packages, so the upgrade will need to overwrite the untracked files created by ldconfig. If you get any of these errors

nss: /usr/lib/p11-kit-trust.so exists in filesystem
zn_poly: /usr/lib/libzn_poly-0.9.so  exists in filesystem

when updating, use

pacman -Syu --overwrite /usr/lib/p11-kit-trust.so --overwrite /usr/lib/libzn_poly-0.9.so

to perform the upgrade.

Device stopped booting after Uboot update
The uboot update included a change to the extlinux.conf file. This change will be incompatible with the old 1 partition layout of some devices.
So if you are updating installs made with images 20.02.1 or older, you need to apply this fix before rebooting!
To fix this please edit your /boot/extlinux/extlinux.conf file and add 2 periods in front of each first slash, like so:

KERNEL ../Image
FDT ../dtbs/ #etc.
APPEND initrd=../initramfs-linux.img #etc.

Save the file and reboot.

Update process didn’t happen as expected and In the end, my USB Penclic Mini Keyboard C3 Office behaves as if were broken. My mouse (connected on the keyboard) is frozen and the keyboard works sometimes, and sometimes not.

When pacman -Syyu, update process asked me to uninstall tlp. I took time to try to understand why tlp had to be removed but as I didn’t hit any yes/no key, the update process resumed.
It was real quick (3 steps only), ended with a

warning: lock file missing /var/lib/pacman/db.lck

To reboot I choose to ctrl-alt-del 7 times. Followed a kernel panic (if I remember well). Manually poweroff computer, no obvious error message at reboot, then had the issue with keyboard+mouse.

EDIT 2022-03-04: could now run pacman -Syyu with the expected update. One minor tweek before reboot. Same issue after. Have to connect mouse directly on the rpi usb, and use another usb keyboard.

Update went smoothly on RPi4 and Pinebook Pro. Pinebook Pro now makes “pop” sound after power down, but I can live with it.

kodi will not boot again.

error while loading shared libraries: libnfs.so.13: cannot open shared object file: No such file or directory

Need a rebuild. Hopefully tomorrow.

Thanks for reporting.

I updated my Rpi few minutes ago, i have a minimal installation without DE, just Kodi on it, the update appears to be fine, Kodi starts as it should.

2 Likes

Would the rebuild of kodi appear on test branch first?

Since the update I have a problem with Gnome Keyring and GOA.
In the logs I see that gnome-keyring-d is interrupted at startup.
I guess GOA doesn’t remember passwords anymore because of this.
In Seahorse the keys appear but the passwords only appear on a few startups.

An extract from the logs

mars 01 11:23:46 pbpro systemd-coredump[2707]: [🡕] Process 607 (gnome-keyring-d) of user 1000 dumped core.
                                               
                                               Module linux-vdso.so.1 with build-id 4f9136b827d0b2e9137b7cfb2fb0353898353baa
                                               Module librt.so.1 with build-id c929d8361c460ba82fa61ea1e0b4614df91744d7
                                               Module libblkid.so.1 with build-id 3d4c42385032a4286bad0a93bcc95c0dbae5ce6d
                                               Module libdl.so.2 with build-id 3d5771318379b07f0a5dda7613f76422aa7f6022
                                               Module libgpg-error.so.0 with build-id c21af18f2e32320cae7e1cc42a9e7dfa0f0ca02a
                                               Module libpcre.so.1 with build-id 75dc63d269e8b1acbd020273e4ada841b6217666
                                               Module libffi.so.8 with build-id 428dd8d9167ff2606b2f215c1450679f01c2db7a
                                               Module libresolv.so.2 with build-id 8864dfae5401109dbc3aa93749878536335a00ea
                                               Module libmount.so.1 with build-id e4ed585c555f9294d6fa83ef415b2444ea02cb60
                                               Module libz.so.1 with build-id c556c373ca4ff1466dbd5262e5436463757f8770
                                               Module libgmodule-2.0.so.0 with build-id 1fb0bd99a5ff893507680d4b0d3f1cbe5e17a83a
                                               Module libp11-kit.so.0 with build-id 5c3eefdf311483790b33a8f76dc45a87f6769ecf
                                               Module libc.so.6 with build-id 2858f54ba7c8eae476c62b8631c4feded56e9064
                                               Module libpthread.so.0 with build-id 2d7e5623023dc082483554f4447388c3a48a244b
                                               Module libgcrypt.so.20 with build-id 766e87748c92c8487a2dd42fe4cffc3c053e6036
                                               Module libglib-2.0.so.0 with build-id 9cf3e9a8f2895190b058e69a9610c1d7762c0a4f
                                               Module libgobject-2.0.so.0 with build-id 7a9b754f8a6c982140b9ac07c4813c65ddc1161e
                                               Module libgio-2.0.so.0 with build-id 448d032bfb7bcdc8b99f5204b97930a8586ba80f
                                               Module libgck-1.so.0 with build-id dce61092798b8d83dadd32f1b7a3df7ca89ff5e6
                                               Module libgcr-base-3.so.1 with build-id 56f6d65ea69788731e11dd72a1ea36c7afabef93
                                               Module gnome-keyring-daemon with build-id a7f9d2fce9e0050bfcc77f19163d65d1521ccba5
                                               Stack trace of thread 2704:
                                               #0  0x0000aaaad79153c0 n/a (gnome-keyring-daemon + 0xf53c0)
                                               #1  0x0000aaaad787c640 n/a (gnome-keyring-daemon + 0x5c640)
                                               #2  0x0000ffff7c003e10 n/a (n/a + 0x0)
                                               #3  0x0000ffff7c003e10 n/a (n/a + 0x0)
                                               ELF object binary architecture: AARCH64
mars 01 11:23:46 pbpro systemd[1]: systemd-coredump@0-2706-0.service: Deactivated successfully.

There is an issue with transmission-cli, which has been updated from 3.00-2 to 3.00-3.
It’s not possible to connect to the transmission server from a remote machine, you get “Unauthroized user”.
I downgraded to 3.00-2 version and i no longer have this issue anymore.

You can find a thread on that point on archlinuxarm forum transmission-cli 3.00-3 unauthroized user

1 Like

Thanks for the reminder. Completely forgot.

Will update it now.

thank you so much! It is working with the update now.

Display Settings (Ustawienia Wyświetlania) widget has wrong dimensions:


This is on the Pinebook Pro.

Remember

It’s is not display-mode-switcher from AUR:


because it isn’t installed on my system.
The only package with KDE Plasma addons installed in my system is kdeplasma-addons from the official repository extra:

But I don’t remember its English name, so if you know the package name, so I can remove the package, it would be helpful.
But if you just assumed it’s from AUR without knowing the package name, then thank you very much for your time, sir.

This is it:

$ pacman -F /usr/share/plasma/plasmoids/org.kde.kscreen/metadata.json
usr/share/plasma/plasmoids/org.kde.kscreen/metadata.json należy do extra/kscreen 5.24.2-1




It looks the same on the rpi4:

wireplumber 0.4.8 is broken on RPi4.
It is somehow fixed on upstream since compiling it from master branch it works.

1 Like

Unfortunately, when trying to upgrade my PinePhone from the ancient 2021-11-30 stable to this current one, Discover decided to not upgrade glibc! Needless to say, that leads to a very broken system (no Plasma Mobile, no NetworkManager, it’s a miracle I get to a shell with a working pacman at all). Thankfully, I have the USB dock and know how to fix things (plug in a USB keyboard and a USB stick with the missing glibc-2.35-2-aarch64.pkg.tar.xz), but I do not understand why Discover created such a broken state to begin with.

And it is not just glibc: the subsequent pacman -Su that I ran (after fixing glibc with pacman -U /mnt/glibc-2.35-2-aarch64.pkg.tar.xz from USB, which brought NetworkManager back) updates 97 more packages, bringing Plasma Mobile back to life (after reboot).

Autorotate stopped working after the update (and the quick toggle had no effect) because, for some reason, in the display configuration, “Only when in tablet mode” (under “Orientation” / “Automatic”) got checked. Unchecking that option fixed the issue, now autorotate works again (and can be toggled on/off through the quick toggle).