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

ARM Stable Updates
,
21

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
22

xfce4-screensav is crippled on an rpi4 upgrade to this release or a new install using Manjaro ARM Flasher. Seems to be a gdk issue:

Jul 03 12:32:15 pi002.adbuco.com xfce4-screensav[621]: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed
Jul 03 12:32:15 pi002.adbuco.com xfce4-screensav[621]: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed
Jul 03 12:32:15 pi002.adbuco.com xfce4-screensav[621]: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed
Jul 03 12:32:15 pi002.adbuco.com xfce4-screensav[621]: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed
Jul 03 12:32:15 pi002.adbuco.com xfce4-screensav[621]: gdk_monitor_get_workarea: assertion 'GDK_IS_MONITOR (monitor)' failed
Jul 03 12:32:15 pi002.adbuco.com xfce4-screensav[621]: gdk_monitor_get_workarea: assertion 'GDK_IS_MONITOR (monitor)' failed
Jul 03 12:32:15 pi002.adbuco.com xfce4-screensav[621]: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed

Monitors go blank and activity pauses entering screen saver. For each workspace, all open windows are moved to one screen in a dual-monitor setup after resuming.DISPLAY is defined as :0.0

23

This log entry is new for this release:

Jul 04 05:26:07 pi002.adbuco.com lightdm[5048]: gkr-pam: unable to locate daemon control file

I think it is best to just live with it for now, since the same problem is logged for an Intel Fedora 36 install.