[ARM Stable Update] 2021-11-30 - Gnome 41, Pamac, LXQT 1.0, Firefox and Kernels

Hello ARM community.

Huge update. Between Plasma and Gnome it has everything!


Some highlights:

  • Most of our kernels got updated
  • Gnome got a new major release with 41.1
  • LXQT got it’s first major release of 1.0
  • Also Pamac got a new point release of 10.3.0
  • Thunderbird updated to 91.3.2
  • And Firefox is updated to 94.0.2
  • KDE Frameworks updated to 5.88
  • And KDE Gear updated to 21.08.3
  • LibreOffice-Still is now at 7.1.7
  • And Electron updated to 16.0.2
  • 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 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:

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:
https://archlinux.org/news/sorting-out-old-password-hashes/

Older notifications

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:

(Tue Nov 30 23:14:46 CET 2021)

  • arm-stable community aarch64: 891 new and 847 removed package(s)
  • arm-stable core aarch64: 60 new and 55 removed package(s)
  • arm-stable extra aarch64: 1006 new and 1004 removed package(s)
  • arm-stable kde-unstable aarch64: 407 new and 409 removed package(s)

To see the full package list, click 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

rpi4-post-install file conflict
Raspberry Pi 4 users might see an error like this:

error: failed to commit transaction (conflicting files)
rpi4-post-install: /etc/udev/rules.d/99-vcio-rewrite.rules exists in filesystem

The reason is that previously we added this file to fix a few issues, but it was not owned by any package. So with this update, we switched it to be owned by rpi4-post-install, which results in this file conflict.
Workaround: Run sudo pacman -Syu --overwrite /etc/udev/rules.d/99-vcio-rewrite.rules.

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 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.

Congratulations on the release!

My install failed cleanly (“no packages were upgraded”).
I got this error:

error: failed to commit transaction (conflicting files)
rpi4-post-install: /etc/udev/rules.d/99-vcio-rewrite.rules exists in filesystem

What should I do?

Hi,

the issue is looking this one, if I’m not wrong

Manjaro-Arm-Gnome-linux-5.15.1-3 GT King Pro, Kernel Panic/System Freeze during the last few stages of Update to Stable-Updates-2021-11-30 which render the USB Flash no longer able to boot up. Had to re-burn image using Manjaro-Arm-Gnome 21.10.

On first boot after new image installation Manjaro-Arm-Gnome-linux-5.14.12-1 (version 21.10), kernel panic during booting up process. Power cycle, it boot up fine.

Proceeded to update to latest Stable-Updates-2021-11-30 and updates successfully (download size: 809.37 MiB and Installed Size: 3249.74 MiB). Power cycle to Reboot. Booted up successfully to the latest Stable-Updates-2021-11-30 linux-kernel-5.15.5-1.

While editing this message, kernel panic strike again (uptime around 30 minutes). Power cycle, boot up successfully. Another kernel panic happened during editing a document (uptime around 20 minutes) this co-inside with the screen flash artifacts (default governor=schedutil and min_speed=100MHz if not mistaken). Remember that that the cpu frequency switch might cause stability issue.

Third power cycle, first thing “sudo cpupower frequency-set -g performance” to set governor to performance for the time being see whether stability improves (kernel .
panic).
Previously with Manjaro-Arm-Gnome mainline linux kernels with governor=performance or governor=schedutil but min_speed=1GHz did Not experience any kernel panic once successfully boot up since June 2021. Had three kernel panic during booting up process out of many boot ups since June.

By the way, firmware BCM4356A2.hcd is missing, this is required for Bluetooth to be activated on GT King Pro.

System still working with governor=performance current uptime of 2h48 minutes.

Somehow neofetch is reporting “Resolution: 720x576i” instead of “1920x1080p/60” according to Gnome Settings.

Edit: Just an update. With Governor set to “performance” (uptime around 4 hours with no kernel panic) or with governor set to “schedutil” and cpu min_speed=1GHz resolved the occasional “screen flashes artifacts”.

GT King Pro XFCE with cpu governor=performance updated to latest Stable successfully.

Run

sudo pacman -Syu --overwrite /etc/udev/rules.d/99-vcio-rewrite.rules

I have noticed one regression in Plasma Mobile: It now often resets the favorites (the shortcut bar on the bottom of the screen) on startup, putting only Phone and Phonebook there. (I normally have Spacebar and Angelfish added.)

Also, if you have noticed the eg25-manager hotfix that was issued separately, as far as I can tell, it has this fix for PinePhone Pro support. (So the eg25-manager hotfix should not make any difference for the regular PinePhone or for any other hardware.)

@Strit & @nl.smart: Thanks! That worked perfectly.

If anyone’s curious, this is the change. I haven’t researched yet to understand what it does, but what I’ve gathered so far is that the GPU subystem is changing somehow.

OLD:

❯ bat 99-vcio-rewrite.rules
───────┬───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
       │ File: 99-vcio-rewrite.rules
───────┼───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
   1   │ KERNEL=="vcio", GROUP="video", MODE="0660"
   2   │ KERNEL=="vchiq", GROUP="video", MODE="0660"

NEW:

❯ bat 99-vcio-rewrite.rules
───────┬───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
       │ File: 99-vcio-rewrite.rules
───────┼───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
   1   │ KERNEL=="vcio", GROUP="video", MODE="0660"
   2   │ KERNEL=="vchiq", GROUP="video", MODE="0660"
   3   │ SUBSYSTEM=="vc-sm", GROUP="video", MODE="0660"

All it does is allow for one to run certain things if you are a member of the group “video” without having to use sudo.

1 Like

Update went without problems. Issue of last month about xorg-xwayland regression is still there ([ARM Stable Update] 2021-11-06 - Firefox, Thunderbird, Plasma, LibreOffice and Kernels - #20 by appelgriebsch).

hmm no issue on my end. I’m on latest testing though, but my xwayland version still sticks to 21.1.2-1 (which is known to be the last working version)…

EDIT: ahhh I see the updated version of xwayland to 21.1.3 made it to the stable branch update :frowning:

It didn’t. Stable branch also has 21.1.2.
The problem might be that the user already has 21.1.3. The update does not automatically downgrade packages. To update and downgrade at the same time, run sudo pacman -Syuu.

Hmmm but its listed here: ARM Stable update 2021-11-30 ($708) · Snippets · Snippets · GitLab

xorg-xwayland 21.1.2.901-1 21.1.3-1

That’s just because we didn’t block the one from Arch ARM, but we added an overlay instead.

So what i have to do ?

Please run

yay -Syyuu

to make a whole system upgrade.

It should ask you if you want to downgrade xorg-xwayland. Please do so.

Do

But I can’t ever call

What’s the issue?

if you haven’t yay installed, you can replace it with sudo pacman instead