[ARM Testing Update] 2023-05-04 - Kernels, Firmware, Firefox, Thunderbird, KDE Gear, Phosh, Pipewire

Hello ARM community.


Manjaro, like many other open-source projects, relies on the generosity of its community through donations and corporate sponsorships to support its growth and development. These donations are essential in covering the various expenses incurred in the operations of the project such as server costs, software development tools, infrastructure expenses, training, flying people to events or conferences and the salaries of key developers. With the help of these donations, Manjaro is able to secure the necessary financial stability that allows the project to continuously improve and remain active. If you love Manjaro, consider to donate!

Update Announcement

Some highlights:

  • Some Kernels got renewed
  • Linux-Firmware got its monthly update
  • Firefox got updated to 112.0.2 and Thunderbird to 102.10.1
  • Pipewire is at 0.3.70
  • Phoc and Phosh are now at 0.27.0
  • KDE Gear 23.04.0 includes now some Mobile Gear apps
  • QEmu is now at 8.0.0
  • Small updates to XFCE
  • The usual KDE-git and Python updates

End Of Life kernels (will be removed from repo soon):

  • linux60 (EOL on 2023-01-12) (removed from repository)

Tips And Tricks

Error about missing openssl 1.1 library

Since the update to the new OpenSSL 3.0, some applications might still be looking for version 1.1 og openssl.
Fortunately Arch Linux created a compatability package for such events called openssl-1.1.
So if you encounter any such errors, please install the above mentioned package.
Applications currently known to specifically look for 1.1 is silver. We have not been able to rebuild it yet. So if you are on our Gnome or Sway editions, please install openssl-1.1 as part of this update.

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

#gpu_mem=64     #disable this
initramfs initramfs-linux.img followkernel

#enable sound

#enable vc4
#max_framebuffers=2    #disable cause kodi uses more

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

The PHP package has been updated to 8.2. If you still need 8.1, use php-legacy packages.
Arch Linux - News: PHP 8.2 update and introduction of legacy branch

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

The ghostpcl and ghostxps requires manual intervention (if you have these installed):
Arch Linux - News: ghostpcl>=9.53.2-2 and ghostxps>=9.53.2-2 updates require manual intervention

The nss package requires manual intervention:
Arch Linux - News: nss>=3.51.1-1 and lib32-nss>=3.51.1-1 updates require 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 (Thu May 4 07:18:02 CEST 2023)

  • arm-testing community aarch64: 519 new and 508 removed package(s)
  • arm-testing core aarch64: 49 new and 49 removed package(s)
  • arm-testing extra aarch64: 683 new and 677 removed package(s)
  • arm-testing kde-unstable aarch64: 383 new and 383 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 Testing Updates. That way we can better find and fix bugs, before they hit arm-stable branch. Thank you!

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


Known Issues and Solutions

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

:arrow_right: 2023-05-04


Docker 23 not starting

Since the update to Docker 23, upstream is now inforcing new paths for apparmor related stuff. But there has been changes to dependencies yet. So Docker 23 will error on start.
Fix: Install apparmor from the repositories.


Ethernet and Wifi not working right on kernel 6.1.2+ on some devices

Some devices have been reported to not have properly working ethernet and wifi after the update to kernel 6.1.2 and above.
Fix: Kernel 6.1.5-2 and above should have working ethernet and wifi again.

Reduced video playback performance in mpv

There has been reports of video playback performance in mpv has regressed since an update to mpv.
Fix: MPV now needs a vd-lavc-dr=no parameter to play hw acceleration supported 1080p videos smoothly.

Touch input on Firefox with Phosh not working in Firefox 108

Since the update to Firefox 108, the touch input does not work. Seems to be an issue with a couple of the changes the mobile-config brings in.
Fix Fixed in version 4.0.0-1 of mobile-config-firefox released with Manjaro testing on April 14, 2023


OpenSSL 1.1 library not found

Some applications might still be looking for openssl 1.1.
Solution: Install openssl-1.1 package with sudo pacman -S openssl-1.1.


Firefox shows wrong colors when playing video on Raspberry Pi 4

Since Mesa 22.2, Firefox has been showing weird colors when playing video on the Raspberry Pi 4. This is caused by an issue in upstream mesa, which was recently fixed.
Fix: Update to mesa 22.2.3-0.1 in the repository, which includes this fix.

Chromium in Wayland crashes with --in-process-gpu

Since Mesa 22.2.0, Chromium running in wayland sessions seems to crash when running with the --in-process-gpu option. Running in X11 seems fine, although it’s slow.
Fix: Update to Mesa 22.3.2 was reported to work here.


Plasma Mobile Dialer seems to be unreliable

Plasma Dialer 22.09 seems to have issues switching audio profiles and as such might require manual switching. Sometimes audio is completely missing.

Reduced video performance on youtube

Some may encounter reduced video playback performance on YouTube in Firefox with the new Mesa 22.2 drivers.
No workaround at this time.

Old Issues

Phosh crashes when closing apps
An upstream issue results in the Phosh shell to crash when you close the app in the app switcher, with animations turned off.
Fix: Enable animations in Tweaks application

Mouse cursor is slow on Raspberry Pi
Due to a change in the Raspberry Pi kernels upstream, they no longer support FKMS. This can result in slow performance when using the FKMS drivers with the newer Raspberry Pi kernels.
Solution: Open /boot/config.txt, change fkms to kms in the dtoverlay line. Save the file and reboot.

[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" |sudo waydroid shell

Only issue so far:

/dev/ttyAMA0 is missing

was working with last month’s testing updates …

# ls -l /dev/ttyAMA0
ls: cannot access '/dev/ttyAMA0': No such file or directory
# systemctl status attach-bluetooth.service
× attach-bluetooth.service - Attach Bluetooth Adapter Raspberry Pi devices
     Loaded: loaded (/usr/lib/systemd/system/attach-bluetooth.service; enabled; preset: disabled)
     Active: failed (Result: exit-code) since Fri 2023-05-05 21:19:46 BST; 4min 56s ago
   Duration: 40ms
    Process: 2550 ExecStart=/usr/bin/patchram.sh (code=exited, status=2)
   Main PID: 2550 (code=exited, status=2)
        CPU: 57ms

May 05 21:19:45 manjaro-pi4-02.datachord.co.uk systemd[1]: Started Attach Bluetooth Adapter Raspberry Pi devices.
May 05 21:19:46 manjaro-pi4-02.datachord.co.uk patchram.sh[2555]: port /dev/ttyAMA0 could not be opened, error 2
May 05 21:19:46 manjaro-pi4-02.datachord.co.uk systemd[1]: attach-bluetooth.service: Main process exited, code=exited, status=2/INVALIDARGU>
May 05 21:19:46 manjaro-pi4-02.datachord.co.uk systemd[1]: attach-bluetooth.service: Failed with result 'exit-code'.```

I am getting the below on attempt at updating JRE
conflicting files:

  • /usr/lib/jvm/java-20-openjdk/lib/libattach.debuginfo exists in both jre-openjdk-headless and jdk-openjdk
  • /usr/lib/jvm/java-20-openjdk/lib/libdt_socket.debuginfo exists in both jre-openjdk-headless and jdk-openjdk
  • /usr/lib/jvm/java-20-openjdk/lib/libjdwp.debuginfo exists in both jre-openjdk-headless and jdk-openjdk
  • /usr/lib/jvm/java-20-openjdk/lib/libsaproc.debuginfo exists in both jre-openjdk-headless and jdk-openjdk
    …at work so have not dived into it more yet. Everything else seems to be running smoothly post update.
1 Like

Guessing you are using a image that is pretty old. We have not been using attach-bluetooth.service for a while in our images. There was a change in the kernel and the raspberrypi-bootloader package last week involving loading up the bluetooth. They are letting the kernel do it now:


In our recent images we have dtparam=krnbt=on set on /boot/config.txt and the attach-bluetooth.service disabled. With the new changes last week from reading in the links I got the impression that dtparam=krnbt=on may be the default now and may not be needed; I just have not tried it here yet to see as my bluetooth is working and forgot about testing by removing it.

sudo systemctl disable attach-bluetooth.service
sudo reboot

If you do not have bluetooth then add dtparam=krnbt=on to /boot/config.txt then reboot.


I removed dtparam=krnbt=on from my config.txt and rebooted and bluetooth loaded up so that is the default now. If one wants to disable it now they need to add dtoverlay=disable-bt to /boot/config.txt and disable bluetooth.service with the latest of these packages installed.

linux-rpi4 6.1.27-1
linux-rpi4-mainline 6.3.1-1
raspberrypi-bootloader 20230428-1
raspberrypi-bootloader-x 20230428-1
1 Like

i was just thinking that the kernel might be doing the job as disabling the 2 bluetooth services (bluetooth.service and attach-bluetooth.service) with reboot seems to still enable the bluetooth interface e.g. visible using rfkill etc.

I did not initially have kernel parameter dtparam=krnbt=on in /boot/cmdline.txt (correction!) and bluetooth was still visible.

# pacman -Ss linux-rpi4
core/linux-rpi4-mainline 6.3.1-1 [installed]
    The Linux Kernel and modules - Raspberry Pi 4 64-bit kernel
core/linux-rpi4-mainline-headers 6.3.1-1 [installed]
    Header files and scripts for building modules for linux kernel - Raspberry Pi 4 64-bit kernel
# pacman -Ss raspberrypi-bootloader
core/raspberrypi-bootloader 20230428-1 [installed]
    Bootloader files for Raspberry Pi
core/raspberrypi-bootloader-x 20230428-1 [installed]
    Bootloader with extra codecs for Raspberry Pi

Thanks for the details!

I may not understand what you said but I still have bluetooth.service running. Also dtparam=krnbt=on was initially in config.txt not cmdline.txt.

systemctl --status bluetooth.service:

● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
     Active: active (running) since Fri 2023-05-05 18:56:11 CDT; 2h 15min ago
       Docs: man:bluetoothd(8)
   Main PID: 335 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 3919)
        CPU: 487ms
     CGroup: /system.slice/bluetooth.service
             └─335 /usr/lib/bluetooth/bluetoothd

ah - ok - /boot/config.txt not /boot/cmdline.txt - was not expecting that!

I’ll keep the bluetooth.service enabled … thanks.

Is this ok?

● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
     Active: active (running) since Sat 2023-05-06 03:20:47 BST; 7s ago
       Docs: man:bluetoothd(8)
   Main PID: 3801 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 3934)
        CPU: 181ms
     CGroup: /system.slice/bluetooth.service
             └─3801 /usr/lib/bluetooth/bluetoothd

May 06 03:20:47 manjaro-pi4-02 systemd[1]: Started Bluetooth service.
May 06 03:20:47 manjaro-pi4-02 bluetoothd[3801]: Starting SDP server
May 06 03:20:47 manjaro-pi4-02 bluetoothd[3801]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled
May 06 03:20:47 manjaro-pi4-02 bluetoothd[3801]: src/plugin.c:plugin_init() Failed to init vcp plugin
May 06 03:20:47 manjaro-pi4-02 bluetoothd[3801]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled
May 06 03:20:47 manjaro-pi4-02 bluetoothd[3801]: src/plugin.c:plugin_init() Failed to init mcp plugin
May 06 03:20:47 manjaro-pi4-02 bluetoothd[3801]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled
May 06 03:20:47 manjaro-pi4-02 bluetoothd[3801]: src/plugin.c:plugin_init() Failed to init bap plugin
May 06 03:20:47 manjaro-pi4-02 bluetoothd[3801]: Bluetooth management interface 1.22 initialized
May 06 03:20:47 manjaro-pi4-02 bluetoothd[3801]: Failed to set mode: Failed (0x03)

dtoverlay=disable-bt & dtparam=krnbt=off, which better?
or, they are different thing?

Do not know for sure. Seems like I read some where in the links that they changed some things up with dtparam=krnbt= switches but I do know that they redid the dtoverlay=disable-bt overlay to accommodate the new kernel firmware changes.

Name:   disable-bt
Info:   Disable onboard Bluetooth on Pi 3B, 3B+, 3A+, 4B and Zero W, restoring
        UART0/ttyAMA0 over GPIOs 14 & 15.
        N.B. To disable the systemd service that initialises the modem so it
        doesn't use the UART, use 'sudo systemctl disable hciuart'.
Load:   dtoverlay=disable-bt
Params: <None>

For us it would be disable bluetooth.service instead

QT Apps(plasma) CJK fonts become blocks, no idea which is cause?

Beelink-GT-King-Pro Gnome-linux-aml-6.1.19-1 upgraded successfully to Arm-Testing-2023-05-04.

Firefox-112.0.2 with mesa-23.0.3 seems to off and on have some visual artifacts, like at times some of the text will flicker.

FYI, this is not specific to Manjaro-Arm-Gnome only. The Firefox and mesa visual artifacts also occurs in Ubuntu and Debian.

To stop the error/warnings - add “Experimental = true” to /etc/bluetooth/main.conf and restart bluetooth.service.

1 Like

Qemu 8 is released.
Any news about glibc without -fPIE not allowing to compile qemu-static for arm ?

Can’t update. I am getting the following error:

error: failed to commit transaction (conflicting files)
konsole: /etc/xdg/konsolerc exists in filesystem
Errors occurred, no packages were upgraded.
1 Like

I pushed a new manjaro-kde-settings package which should fix that issue for you @doug

The error that @doug mentioned still seems be be there.

Just now (~7h after your foum post)

error: failed to commit transaction (conflicting files)
konsole: /etc/xdg/konsolerc exists in filesystem
Errors occurred, no packages were upgraded.
 -> error installing repo packages

------------- EDIT ---------------

if you move the file out of the way it works. I don’t use konsole anyway

cd /etc/xdg
doas mv konsolerc konsolerc-old

I did this and everything seems to be working ok. Thank you!

I went ahead and deleted konsolerc already and everything is working ok. Thank you!

ok, ttf-jetbrains-mono break kde default font, removed.