[ARM Stable Update] 2022-06-19 - Toolchain, Perl, Calamares, Firefox, Gnome and Kernels

Known Issues and Solutions

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

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 192.168.250.1" |sudo waydroid shell
Old Issues
Plasma Dialer cannot answer calls

Sadly Plasma Dialer 22.02 has a serious regression with no known workaround. It’s not possible to accept incoming calls. Very sorry about this. Follow the upstream bug report. We will patch the package as soon as a solution is found.

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.

1 Like
(1/1) removing uboot-pinebookpro-bsp                [##########################] 100%
warning: /boot/extlinux/extlinux.conf saved as /boot/extlinux/extlinux.conf.pacsave
(248/276) upgrading pulseaudio                      [##########################] 100%
warning: /etc/pulse/default.pa installed as /etc/pulse/default.pa.pacnew
(273/276) installing uboot-pinebookpro              [##########################] 100%
New version of U-Boot firmware can be flashed to your microSD card (mmcblk1)
or eMMC module (mmcblk2).  You can do that by running:
# dd if=/boot/idbloader.img of=/dev/mmcblkX seek=64 conv=notrunc,fsync
# dd if=/boot/u-boot.itb of=/dev/mmcblkX seek=16384 conv=notrunc,fsync
Keeping old extlinux.conf file...

(15/27) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k 5.18.5-1-MANJARO-ARM -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 5.18.5-1-MANJARO-ARM
  -> Running build hook: [base]
  -> Running build hook: [udev]
==> ERROR: Hook 'plymouth' cannot be found
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> WARNING: errors were encountered during the build. The image may not be complete.
error: command failed to execute correctly
(16/27) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k 5.18.5-1-MANJARO-ARM -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 5.18.5-1-MANJARO-ARM
  -> Running build hook: [base]
  -> Running build hook: [udev]
==> ERROR: Hook 'plymouth' cannot be found
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> WARNING: errors were encountered during the build. The image may not be complete.
error: command failed to execute correctly

Considering the last time I tried to update uboot it bricked my PBP, I’m nervous to try to figure out what’s going here. I can still boot, so I’m reluctant to “fix” this. Is there something in the above I should be concerned with?

Installed this update. Reboot went fine. Installed u-boot to EMMC. Reboot locked with failed script.
(Running the Manjaro plasma desktop on x-org)

Installed old uboot code to EMMC, this did not fix the issue. PBP no longer boots form EMMC, but will boot form SD card running an older version.
Open to suggestions.

Update: next day attempt at reboot really bricked. Power button does not even bring the light up. May have to open her up and disconnect the EMMC. This could be hardware, and the upgrade timing a coincidence.

Thank you. GT King Pro updated successfully to Arm-Stable-2022-06-19 on second try.

But something doesn’t seems right in the sense than in Firefox or Chromium streaming Youtube video, whenever you move the mouse cursor or arrow and it encounter the “Window Border” or crosses a “Window Border” it will momentarily freeze the video. Same if you are on “webglesamples.org Aquarium”. Repeatable in both.

I notice upgrading from linux-khadas-5.17.6-1 to linux-khadas-5.18.1-1 in Gnome Desktop whenever you move the mouse pointer/cursor a cross a “Window Border” it will momentarily freeze. Could this be the cause of video freeze momentarily when the mouse pointer/cursor crosses the “Window Border”?

Pulse sink name changes again. Custom modifications using sink names in /etc/pulse/default.pa prevented pulse from starting before new names were in use. See [ARM Stable Update] 2022-05-31 - Electron, SystemD, QT5 and Kernels - #25 by dbeach

Using XFCE, gnome-keyring not installed, getting messages about gnome keyring errors:

Jun 20 11:00:17 pi002.adbuco.com xfce4-screensaver-dialog[3959]: PAM unable to dlopen(/usr/lib/security/pam_gnome_keyring.so): /usr/lib/security/pam_gnome_keyring.so: cannot open shared obj>
Jun 20 11:00:17 pi002.adbuco.com xfce4-screensaver-dialog[3959]: PAM adding faulty module: /usr/lib/security/pam_gnome_keyring.so
Jun 20 11:06:51 pi002.adbuco.com xfce4-screensaver-dialog[4044]: PAM unable to dlopen(/usr/lib/security/pam_gnome_keyring.so): /usr/lib/security/pam_gnome_keyring.so: cannot open shared obj>
Jun 20 11:06:51 pi002.adbuco.com xfce4-screensaver-dialog[4044]: PAM adding faulty module: /usr/lib/security/pam_gnome_keyring.so

Installing gnome-keyring is the fix. This is new for this release upgrade. It is also a problem for a new install using Manjaro ARM Flasher which also does not install gnome-keyring.

Another smooth update. Working well on my Pinephone.

After update on pinebook 1080p with swaywm, waybar doesn’t start.

When running waybar from terminal, I’ve got this result:

jezek@pinjezbook ~ 
$ waybar                                                                                                                                                                                                 [00:31:12]
[2022-06-21 00:31:13.690] [info] Using configuration file /home/jezek/.config/waybar/config
[2022-06-21 00:31:13.692] [info] Using CSS file /home/jezek/.config/waybar/style.css
[2022-06-21 00:31:13.837] [warning] For a functional tray you must have libappindicator-* installed and export XDG_CURRENT_DESKTOP=Unity

** (waybar:1952): WARNING **: 00:31:14.038: gtk-layer-shell v0.7.0 may not work on GTK v3.24.34. If you experience crashes, check https://github.com/wmww/gtk-layer-shell/blob/master/compatibility.md

** (waybar:1952): ERROR **: 00:31:14.093: 
unhandled exception (type std::exception) in signal handler:
what: argument not found

[1]    1952 trace trap (core dumped)  waybar
133 ↵                              

Hi,

Device: GT King Pro
Manjaro-Edition: Manjaro-Arm-Gnome
Kernel: linux-khadas-5.17.6-1 to linux-khadas-5.18.1-1

Need assistance. After Upgrading to the latest Arm-Stable-2022-06-19. I noticed that the mouse cursor movement momentarily freeze (jerk) whenever it crosses a Window Border. And it also causes Firefox or Chromium streaming video to momentarily freeze (jerk) when mouse cursor movement crosses a Window Border.

This lead me to try out linux-5.18.5-2 from Unstable Repo. Installation of linux-5.18.2-2 was successful.

(1/1) removing linux-khadas                        [######################] 100%
(1/1) installing linux                             [######################] 100%
Optional dependencies for linux
    crda: to set the correct wireless channels of your country [installed]
:: Running post-transaction hooks...
(1/6) Arming ConditionNeedsUpdate...
(2/6) Updating module dependencies...
(3/6) Updating linux module dependencies...
(4/6) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k 5.18.5-2-MANJARO-ARM -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 5.18.5-2-MANJARO-ARM
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [plymouth]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> Image generation successful
(5/6) Updating uInitrd...
Image Name:   uInitrd Image
Created:      Tue Jun 21 10:22:42 2022
Image Type:   AArch64 Linux RAMDisk Image (uncompressed)
Data Size:    8386363 Bytes = 8189.81 KiB = 8.00 MiB
Load Address: 00000000
Entry Point:  00000000
(6/6) Updating uImage...
Image Name:   uImage
Created:      Tue Jun 21 10:22:48 2022
Image Type:   AArch64 Linux Kernel Image (uncompressed)
Data Size:    24388096 Bytes = 23816.50 KiB = 23.26 MiB
Load Address: 01080000
Entry Point:  01080000
 jflim@jflim-gtkpro   

But after installing linux-5.18.5-2 from Unstable Repo, it cannot boot anymore. Stuck at:

uEnv.ini
dtb_name=/dtbs/amlogic/meson-g12b-gtking-pro.dtb
bootargs=root=PARTUUID=f46886d7-02 rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 audit=0
/etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
PARTUUID=f46886d7-01  /boot   vfat    defaults        0       0
PARTUUID=f46886d7-02   /   ext4     defaults    0   1

I notice /dev is EMPTY. Is this normal?

Appreciate guidance on how to get Manjaro-Arm-Gnome to boot again is much appreciated.

/dev/ is empty if the system is not booted. That’s normal.

Tried a few times to boot. It is stuck at the same point try to mount: PARTUUID=f46886d7-02

Any suggestion how to resolve this and get it to boot again?

Check your /etc/fstab file. See if anything looks wrong/off.

/etc/fstab

# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
PARTUUID=f46886d7-01  /boot   vfat    defaults        0       0
PARTUUID=f46886d7-02   /   ext4     defaults    0   1

Hm, maybe the mainline kernel is missing something for the SD/eMMC controller. @spikerguy, you know anything about that?

1 Like

Let me look at mainline kernel as I have been concentrating on amlogic specific kernel only.

ibus doesn’t start at startup .

Reinstalled plymouth. (Did I remove it? :thinking:) Updating initcpios worked. Still reboots.

I had a similar problem. After removing the back, you can disable the eMMC with a hardware switch. (Not the one for switching from audio to console out.) Keep the back off, and reboot on the SD card. About two or three seconds after booting, turn the switch back on. The SD-card booted operating system will then be able to mount the eMMC after bootup, and you can reinstall uboot on it.

Manjaro ARM Flasher: rpi4 gnome 22.06 mmcblk0 new installation. After setup, keyboard @ and " transposed on the mapping. From the journal:

Jun 22 19:47:18 pi002 gnome-session-binary[480]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Jun 22 19:47:18 pi002 gnome-session-binary[480]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Jun 22 19:47:25 pi002 pipewire[525]: spa.v4l2: '/dev/video14' VIDIOC_QUERYCTRL: Inappropriate ioctl for device
Jun 22 19:47:25 pi002 pipewire[525]: spa.v4l2: '/dev/video14' VIDIOC_ENUM_FRAMEINTERVALS: Inappropriate ioctl for device
Jun 22 19:47:25 pi002 pipewire[525]: spa.v4l2: '/dev/video15' VIDIOC_QUERYCTRL: Inappropriate ioctl for device
Jun 22 19:47:25 pi002 pipewire[525]: spa.v4l2: '/dev/video15' VIDIOC_ENUM_FRAMEINTERVALS: Inappropriate ioctl for device
Jun 22 19:47:25 pi002 pipewire[525]: spa.v4l2: '/dev/video21' VIDIOC_QUERYCTRL: Inappropriate ioctl for device
Jun 22 19:47:25 pi002 pipewire[525]: spa.v4l2: '/dev/video21' VIDIOC_ENUM_FRAMEINTERVALS: Inappropriate ioctl for device
Jun 22 19:47:25 pi002 pipewire[525]: spa.v4l2: '/dev/video22' VIDIOC_QUERYCTRL: Inappropriate ioctl for device
Jun 22 19:47:25 pi002 pipewire[525]: spa.v4l2: '/dev/video22' VIDIOC_ENUM_FRAMEINTERVALS: Inappropriate ioctl for device
Jun 22 19:47:35 pi002 gdm-password][704]: gkr-pam: unable to locate daemon control file
Jun 22 19:47:46 pi002 pipewire[822]: spa.v4l2: '/dev/video14' VIDIOC_QUERYCTRL: Inappropriate ioctl for device
Jun 22 19:47:46 pi002 pipewire[822]: spa.v4l2: '/dev/video14' VIDIOC_ENUM_FRAMEINTERVALS: Inappropriate ioctl for device
Jun 22 19:47:46 pi002 pipewire[822]: spa.v4l2: '/dev/video15' VIDIOC_QUERYCTRL: Inappropriate ioctl for device
Jun 22 19:47:46 pi002 pipewire[822]: spa.v4l2: '/dev/video15' VIDIOC_ENUM_FRAMEINTERVALS: Inappropriate ioctl for device
Jun 22 19:47:46 pi002 pipewire[822]: spa.v4l2: '/dev/video21' VIDIOC_QUERYCTRL: Inappropriate ioctl for device
Jun 22 19:47:46 pi002 pipewire[822]: spa.v4l2: '/dev/video21' VIDIOC_ENUM_FRAMEINTERVALS: Inappropriate ioctl for device
Jun 22 19:47:46 pi002 pipewire[822]: spa.v4l2: '/dev/video22' VIDIOC_QUERYCTRL: Inappropriate ioctl for device
Jun 22 19:47:46 pi002 pipewire[822]: spa.v4l2: '/dev/video22' VIDIOC_ENUM_FRAMEINTERVALS: Inappropriate ioctl for device
Jun 22 19:47:51 pi002 gdm-launch-environment][454]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 23 16:16:35 pi002 kernel: v3d fec00000.v3d: MMU error from client L2T (0) at 0x78c1000, pte invalid