[Testing Update] 2022-01-24 - OpenSearch, Kernels, VirtualBox, Systemd, Firefox, Linux-Firmware

Hello community,

Another testing branch update with some usual updates for you.

image

Don’t miss out on our current discounts on Manjaro Merch

  • Some of the Kernels got updated
  • linux514 got dropped, as well as all our 4.x kernels
  • linux-firmware got split up. More info here
  • OpenSearch is at 1.2.4
  • VirtualBox got updated to 6.1.32
  • Systemd is now at 250.3
  • Firefox got renewed to 96.0.2
  • AMDVLK is at 22.Q1.1
  • The usual upstream updates including Haskell and Python

:information_source: You may need to rebuild any AUR packages that install files to site-packages … :information_source:

You may need to rebuild any Python packages you’ve installed from the AUR. To get a list of them, you can run:

pacman -Qoq /usr/lib/python3.9

And to rebuild them all at once with an AUR helper such as yay, you can do:

yay -S $(pacman -Qoq /usr/lib/python3.9) --answerclean All

But if any of the packages don’t work with Python 3.10 yet, this might fail halfway through and you’ll have to do rebuild the remaining ones one or a few at a time.

Get our latest daily developer images now from Github: Plasma, Gnome, XFCE. You get the latest stable releases of Manjaro from CDN77.


Our current supported kernels

  • linux54 5.4.173
  • linux510 5.10.93
  • linux515 5.15.16
  • linux516 5.16.2
  • linux517 5.17-rc1
  • linux510-rt 5.10.90_rt60
  • linux515-rt 5.15.14_rt27
  • linux516-rt 5.16.2_rt18

Package Updates (Mon Jan 24 07:37:48 CET 2022)

  • testing community x86_64: 1319 new and 1283 removed package(s)
  • testing core x86_64: 27 new and 28 removed package(s)
  • testing extra x86_64: 211 new and 374 removed package(s)
  • testing kde-unstable x86_64: 245 new and 242 removed package(s)
  • testing multilib x86_64: 17 new and 18 removed package(s)

All package changes are listed here.

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

3 Likes

Known issues and solutions

This is a wiki post; please edit as necessary.
Please, consider subscribing to the Testing Updates Announcements RSS feed


New issues:

*Python packages from PIP and AUR* - how to upgrade them - detailed instructions

Read this post.

freetype2 update might result in font characters becoming squares

Don’t worry, a relogin to your UI should fix it. We recommend to do the update in a TTY. Affected UIs so far: Gnome, Phosh, Cinnamon.

compiz packages like compiz-easy-patch got dropped from our repositories.

compiz packages like compiz-easy-patch got dropped from our repositories. Due to protobuf update you may need to rebuild that package locally on your end. Compiz-easy-patch removed from repos

Announcement for PipeWire users

Re-enable any per-user enabled pipewire-media-session.service manually:

You should re-enable any per-user pipewire-media-session.service manually to establish a new service alias for pipewire-session-manager.service added with 0.3.38.

systemctl --user enable pipewire-media-session

See the PipeWire Release Notes for more info

New warnings when building the fallback initcpio - Possibly missing firmware for module: bfa, qed, qla1280, qla2xxx

That’s due to the recent changes to the linux-firmware package. You can install linux-firmware-qlogic to get rid of those errors.

pamac install linux-firmware-qlogic


Older Issues

OS prober does not run and add other operating systems*

To restore, please execute: echo GRUB_DISABLE_OS_PROBER=false|sudo tee -a /etc/default/grub && sudo update-grub

For more information, see opening post in [Stable Update] 2021-03-08.

Nvidia card owners
  • We simplified nVidia driver installation. This means we dropped legacy drivers.
    • We recommend to switch over to Nouveau drivers if your card is mentioned here and the feature you need is not in red TO DO here for your particular card.

    • If you however still need proprietary drivers, you may want to execute the following to ensure all parts of the nVidia drivers get installed properly:

      sudo mhwd -a pci nonfree 0300
      
      If proprietary drivers don't fix everything, please click the ► at the beginning of this line to view more info
      1. try installing kernel 5.4 LTS (Long Term Support)
      2. If that doesn’t fix it, take a full system backup, go to a console using Ctrl+Alt+F2 and:
      • Backup /etc/X11/mhwd.d/nvidia.conf if you ever edited that manually
      • remove all nVidia related drivers and applications:
        pacman --remove nvidia*
        
      • Note which applications are being removed and keep them handy in a list
      • Install the driver first:
        mhwd --install video-hybrid-XXX-nvidia-prime
        
        (Where XXX is amd or intel if you have hybrid graphics or the whole thing is video-nvidia if you’re on an nVidia-only system)
      • reboot and see if you at least get a screen.
      • Install all the other applications from your handy list that you still need one by one.
      • Restore /etc/X11/mhwd.d/nvidia.conf if you ever edited that manually
      • If that wouldn’t solve the issue open a new issue here referring to this update and posting at a minimum the full output of:
        inxi --admin --verbosity=7 --filter --no-host --width
        

      If you however still have issues with your Nvidia card, you may open a new thread in our forum: Graphics & Display - Manjaro Linux Forum or look at our tutorial on compiling old Nvidia drivers.

For AMD GPU users having a black screen with kernel 5.10

Due to a bug in the AMD drivers, please try the following first:

For GRUB:

  1. Open a terminal or a TTY
  2. Open /etc/default/grub in your favourite CLI editor (nano vi, emacs`)
  3. Find the line: GRUB_CMDLINE_LINUX_DEFAULT="
  4. Add amdgpu.dc=0
  5. Save
  6. Execute sudo update-grub and reboot

For systemd-boot:

  1. Open a terminal or a TTY
  2. Open /boot/loader/entries/manjarolinux5.10.conf in your favourite CLI editor (nano vi, emacs`)
  3. Add amdgpu.dc=0 to the end of the line options
  4. Save & reboot

For rEFInd:

  1. Open a terminal or a TTY
  2. Open /boot/refind_linux.conf in your favourite CLI editor (nano vi, emacs`)
  3. Find the line: "Boot using default options" "root=
  4. Add amdgpu.dc=0
  5. Save & reboot
Possible 2 Min delay on shutdown with Gnome
  • If you got the problem with shutdown delay (about 2min) on Gnome, here is a workaround:
    • Edit /usr/lib/systemd/user/gnome-session-restart-dbus.service in your favourite editor as root and add Slice=-.slice as a line all by itself like this:

      [Service]
      Type=notify
      Slice=-.slice
      ExecStart=/usr/lib/gnome-session-ctl --restart-dbus
      
    • Click this link For more information

Touchpad on a ThinkPad stops working

Restart again, please.

$PKGNAME warning: directory permissions differ on $Directoryname

followed by:

Filesystem: NNN package MMM

  • The solution:

    sudo chmod MMM DirectoryName
    

    Where obviously MMM is the second number you see (the correct one)

  • The explanation:
    Your package expects the security permissions to be MMM but your system is set to NNN. This is just a warning (today) but to ensure you remain up-to-date with the latest and greatest security rules it’s advised to execute the above command.

Systemd error message: .slice: Failed to migrate controller cgroups

If you have a similar error message like this:

systemd[1004]: -.slice: Failed to migrate controller cgroups from /user.slice/user-1000.slice/user@1000.service, ignoring: Permission denied

… you may need to add this Grub parameter to your /etc/default/grub file in line GRUB_CMDLINE_LINUX_DEFAULT: systemd.unified_cgroup_hierarchy=true. To update your grub menu, call: sudo update-grub. For more information on that issue, see also Arch Forum.

Python 3.9 Requires Rebuilds

Instructions for quickly and easily rebuilding affected AUR packages:

# Install yay
sudo pacman -S --needed --noconfirm yay

# Rebuild AUR python packages
yay -S --noconfirm $(pacman -Qqo "/usr/lib/python3.8/site-packages")
libtraceevent>=5.9-1 update requires manual intervention

2020-10-23 - Sébastien Luttringer

The libtraceevent package prior to version 5.9-1 was missing a soname link. This has been fixed in 5.9-1, so the upgrade will need to overwrite the untracked files created by ldconfig. If you get any of these errors

libtraceevent: /usr/lib/libtraceevent.so.1 exists in filesystem

when updating, use

pacman -Syu --overwrite /usr/lib/libtraceevent.so.1

to perform the upgrade.

Arch Linux - News: libtraceevent>=5.9-1 update requires manual intervention

OpenVPN connection times out

Workaround: downgrade openvpn (2.5.0-1 => 2.4.9-2).
For a proper solution follow this bug report on Arch Linux: FS#68480 : [openvpn] running unprivileged with iproute no longer working

PAM and PAMBASE got updated, which might prevent you from login

Due to updates from pambase and pam you might take care about any .pacnew files in /etc/pam.d as for example pam_tally, pam_tally2 and pam_cracklib got deprecated. Read in the ArchWiki about managing those files.

Typical issue:

For recovery, it is enough to boot with kernel option “systemd.unit=rescue.target”, then proceed into /etc/pam.d and merge “system-auth” and “system-auth.pacnew”

System takes a long time to boot

If you’ve got errors like Failed to start Network Manager Wait Online. you can try removing systemd from passwd and group in /etc/nsswitch.conf as described here
Update: If you can see the line
dbus-daemon[1453]: [system] Connection has not authenticated soon enough, closing it (auth_timeout=30000ms, elapsed: 45146ms)
in in your dbus log ( journalctl -b -u dbus ), the new/better workaround is to switch cups from service to socket as described here:
systemctl disable cups.service
systemctl enable cups.socket

I think I've some font problems

With the update of fontconfig some major rules how fonts get applied changed. Make sure that your system has ttf-dejavu installed. A more in depth explanation can be found here.

Please RTFT (Read This Fine Thread) first before reporting the same issues over and over again!

A post was split to a new topic: Is the amd-pstate driver included in 5.17-rc1 kernel?

This update introduces a few new “missing firmware” warnings when running mkinitcpio -P:

Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux510.preset: 'default'
  -> -k /boot/vmlinuz-5.10-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.10-x86_64.img
==> Starting build: 5.10.93-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [systemd]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.10-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux510.preset: 'fallback'
  -> -k /boot/vmlinuz-5.10-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.10-x86_64-fallback.img -S autodetect
==> Starting build: 5.10.93-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [systemd]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: qla1280
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: qla2xxx
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.10-x86_64-fallback.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'default'
  -> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64.img
==> Starting build: 5.15.16-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [systemd]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.15-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'fallback'
  -> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64-fallback.img -S autodetect
==> Starting build: 5.15.16-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [systemd]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: qla1280
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: qla2xxx
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.15-x86_64-fallback.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux516.preset: 'default'
  -> -k /boot/vmlinuz-5.16-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.16-x86_64.img
==> Starting build: 5.16.2-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [systemd]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.16-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux516.preset: 'fallback'
  -> -k /boot/vmlinuz-5.16-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.16-x86_64-fallback.img -S autodetect
==> Starting build: 5.16.2-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [systemd]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: qla1280
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: qla2xxx
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.16-x86_64-fallback.img
==> Image generation successful

Interestingly, these warnings only occur on creation of the fallback initcpios.

1 Like

I’m having troubles with JACK and Pipewire:

:: pipewire-jack and jack2 are in conflict (jack). Remove jack2? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: removing jack2 breaks dependency 'jack2=1.9.20' required by lib32-jack2

Removing jack2 and lib32-jack2 seems to be impossible due to multiple dependencies:

error: failed to prepare transaction (could not satisfy dependencies)
:: removing jack2 breaks dependency 'jack' required by audacious-plugins
:: removing jack2 breaks dependency 'libjack.so=0-64' required by audacity
:: removing jack2 breaks dependency 'jack' required by ffmpeg
...
3 Likes

install lib32-pipewire-jack

7 Likes

New warnings when building the fallback initcpio:

  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: qla1280
==> WARNING: Possibly missing firmware for module: qla2xxx
1 Like

You can install linux-firmware-qlogic to get rid of those errors, but unless you actually have qlogic stuff, you shouldn’t be worried about those warnings.

4 Likes

Neither my keyboard nor my trackpad are working after the update.
Used Timeshift from a live USB to restore. Will check logs soon.

I also can reproduce that. Interesting though: These warnings only occur with the fallback initcpios not the regular ones. Shouldn’t the fallbacks include less stuff than the regular initcpios?

1 Like

nope, fallback skips autodetect hook (which only loads detected modules) and proceeds to load all modules, hence why you get these drivers as missing.

1 Like

Thanks a lot for clarification.

Meanwhile, I did some research and found a way to get rid of these warnings altogether: Arch Linux mkinitcpio: Possibly missing firmware for module · GitHub

Of course, this will only work if you are not using any SCSI hardware on your rig (which, probably, will be true for most of us here).

Small advantage: Leaving out all the SCSI drivers in the initcpio build process, will speed things up a little bit when running mkinitcpio -P.

For convenience, here’s a patch doing the changes discussed.

--- /usr/lib/initcpio/install/block	2021-12-03 16:06:50.000000000 +0100
+++ /usr/lib/initcpio/install/block	2022-01-24 12:55:17.792192681 +0100
@@ -5,8 +5,10 @@
 
     map add_module sd_mod? sr_mod? usb_storage? mmc_block? firewire-sbp2? virtio_blk?
 
-    # pata, sata, scsi, nvme
-    for filter in 'scsi/.*ata' '/(block|scsi|fusion|nvme)/' 'ata/[ps]ata_' \
+    # pata, sata, nvme
+    # scsi removed to avoid unnecessary missing firmware warnings
+    # on systems not using scsi
+    for filter in '/(block|fusion|nvme)/' 'ata/[ps]ata_' \
             'ata/(ahci|pdc_adma|ata_piix|ata_generic)'; do
         add_checked_modules "$filter"
     done
@@ -34,8 +36,11 @@
 help() {
     cat <<HELPEOF
 This hook loads the necessary modules for most block devices using pata, sata,
-scsi, firewire, usb, or mmc. Detection will take place at runtime. To minimize
+firewire, usb, or mmc. Detection will take place at runtime. To minimize
 the modules in the image, add the autodetect hook too.
+In this version of the hook, the scsi drivers have been omitted to avoid
+missing firmware warnings when running mkinitcpio -P.
+Hence, DO NOT use this hook if you are using SCSI in your system.
 HELPEOF
 }
 
3 Likes

FYI, older kernels were dropped because of

I have a 1660 and would ;like to know if need to be concerned about this right now, right? Thanks

I had to install the Renesas firmware in my case. → Renesas firmware for xhci_pci
The firmware is in the AUR.

What are your concerns? What is your issue?

in addition to the changes mentioned i also saw, “sd_mod? sr_mod?” being omitted in the SCSI-less configuration.

decided to keep things as is, building fallback-initramfs with less drivers will indeed take slightly less time and will make it smaller. however considering the frequency it takes place and meddling with driver configuration (applies globally) that i have no idea about, I’ll pass on this. great work finding this BTW

Please let me kindly ask you for your assistance. Where was “sd_mod? sr_mod” omitted in the SCSI-less config?
At least, all I wanted to do is remove

'scsi/.*ata'

entirely, as well as

scsi

from the second filter in that line, like below:

for filter in ‘scsi/.*ata’ ‘/(block|scsi|fusion|nvme)/’ ‘ata/[ps]ata_’ \

The line above that saying

map add_module sd_mod? sr_mod? usb_storage? mmc_block? firewire-sbp2? virtio_blk?

will be left unchanged; it is only there for patch to identify its entry point in the block file.

The kernel runs well here - only drawback is that the Nvidia driver 495 is not compatible with it:

In file included from /home/gerd/Downloads/nvidia-495xx/dkms/src/NVIDIA-Linux-x86_64-495.46-no-compat32/kernel/common/inc/nv-procfs.h:26,
                 from /home/gerd/Downloads/nvidia-495xx/dkms/src/NVIDIA-Linux-x86_64-495.46-no-compat32/kernel/nvidia/nv-procfs.c:31:
/home/gerd/Downloads/nvidia-495xx/dkms/src/NVIDIA-Linux-x86_64-495.46-no-compat32/kernel/nvidia/nv-procfs.c: In function 'nv_procfs_open_gpu_info':
/home/gerd/Downloads/nvidia-495xx/dkms/src/NVIDIA-Linux-x86_64-495.46-no-compat32/kernel/common/inc/nv-procfs-utils.h:106:28: error: implicit declaration of function 'PDE' [-Werror=implicit-function-declaration]
  106 | #define NV_PDE_DATA(inode) PDE(inode)->data
      |                            ^~~
/home/gerd/Downloads/nvidia-495xx/dkms/src/NVIDIA-Linux-x86_64-495.46-no-compat32/kernel/common/inc/nv-procfs-utils.h:127:27: note: in expansion of macro 'NV_PDE_DATA'
  127 |                           NV_PDE_DATA(inode));                              \
      |                           ^~~~~~~~~~~

Looks like in this driver, some #includes are missing or set incorrectly.
The Nvidia beta driver 510.39.01 runs with kernel 5.17-rc1, without visible problems so far.

For driver 495.46, I have prepared a tentative patch and uploaded it here: Patch for compiling driver 495.46 for kernel... - 40848cd3
Feel free to test it and kindly provide feedback.

Fix my post. Just wanting to know if any of that affects the 1660 series?