[Testing Update] 2021-11-27 - Kernels, ICU 70.1, Virtualbox 6.1.30, LibreOffice 7.2.3

Hello community,

Another testing branch update with some usual updates for you. This is more a rebuild against icu 70.1.

  • Most of our Kernels got updated. Note that 5.14 is marked EOL and 5.13 removed from our servers …
  • Most of our packages got rebuilt against icu 70.1. Let us know if we missed any!
  • VirtualBox got updated to 6.1.30
  • LibreOffice 7.2.3 is now available
  • Other regular upstream updates

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

  • linux44 4.4.293
  • linux49 4.9.291
  • linux414 4.14.256
  • linux419 4.19.218
  • linux54 5.4.162
  • linux510 5.10.82
  • linux514 5.14.21 [EOL]
  • linux515 5.15.5
  • linux516 5.16-rc2
  • linux510-rt 5.10.78_rt55
  • linux515-rt 5.15.3_rt21

Package Updates (Sat Nov 27 15:57:41 CET 2021)

For a detailed list of update changes see 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:

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

nvidia-390xx is not compatible to Xorg-Server 21.1.1 yet

For all those with that Xorg ABI error and having no /etc/X11/xorg.conf: Search for a file called /etc/X11/xorg.conf.d/20-server_flags.conf. If it does not exist yet, create it. Amend the file and paste the well-known contents there:

Section "ServerFlags"
  Option "IgnoreABI" "1"
EndSection
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


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!

1 Like

Detected a dependency cycle, otherwise the update went completely smoothly and also restarting the virtual machine went quite normally. I hope you can see something in the screenshot.

it’s usual in updates :wink:

3 Likes

Ah ok, I thought I’d help out a bit. Thanks for the info! :slightly_smiling_face:

Excuse me, I don’t get it: pipewire-media-session.service is just a sample session service, isn’t it? Wireplumber is the way as far as I remember.

Wireplumber is providing media-session and the next step of the evolution. However not all applications work great with it yet. Hence the recommendation to use media-session still.

2 Likes

Yes, but an alias needs to be created. See the pipewire-media-session and wireplumber post_upgrade() messages.

Please do not post screenshots of text:

you can check your caches drives ( kernel 5.15.5 )

nov. 27 22:22:20 mjro kernel: ata3.00: ATA Identify Device Log not supported
nov. 27 22:22:20 mjro kernel: ata16.00: supports DRM functions and may not be fully accessible
nov. 27 22:22:20 mjro kernel: ata9.00: supports DRM functions and may not be fully accessible
nov. 27 22:22:20 mjro kernel: ata3.00: ATA Identify Device Log not supported
nov. 27 22:22:20 mjro kernel: sd 2:0:0:0: [sda] Asking for cache data failed
nov. 27 22:22:20 mjro kernel: sd 2:0:0:0: [sda] Assuming drive cache: write through
nov. 27 22:22:20 mjro kernel: ata5.00: supports DRM functions and may not be fully accessible
nov. 27 22:22:20 mjro kernel: ata4.00: supports DRM functions and may not be fully accessible
nov. 27 22:22:20 mjro kernel: ata6.00: supports DRM functions and may not be fully accessible
nov. 27 22:22:20 mjro kernel: ata16.00: supports DRM functions and may not be fully accessible
nov. 27 22:22:20 mjro kernel: ata9.00: supports DRM functions and may not be fully accessible
nov. 27 22:22:20 mjro kernel: ata5.00: supports DRM functions and may not be fully accessible
nov. 27 22:22:20 mjro kernel: ata4.00: supports DRM functions and may not be fully accessible
nov. 27 22:22:20 mjro kernel: ata6.00: supports DRM functions and may not be fully accessible
nov. 27 22:22:20 mjro kernel: sd 3:0:0:0: [sdb] Asking for cache data failed
nov. 27 22:22:20 mjro kernel: sd 3:0:0:0: [sdb] Assuming drive cache: write through
nov. 27 22:22:20 mjro kernel: sd 4:0:0:0: [sdc] Asking for cache data failed
nov. 27 22:22:20 mjro kernel: sd 4:0:0:0: [sdc] Assuming drive cache: write through
nov. 27 22:22:20 mjro kernel: sd 5:0:0:0: [sdd] Asking for cache data failed
nov. 27 22:22:20 mjro kernel: sd 5:0:0:0: [sdd] Assuming drive cache: write through
nov. 27 22:22:20 mjro kernel: sd 8:0:0:0: [sde] Asking for cache data failed
nov. 27 22:22:20 mjro kernel: sd 8:0:0:0: [sde] Assuming drive cache: write through
nov. 27 22:22:20 mjro kernel: sd 15:0:0:0: [sdf] Asking for cache data failed
nov. 27 22:22:20 mjro kernel: sd 15:0:0:0: [sdf] Assuming drive cache: write through
1 Like

Hello,

I*m missing the linux510-r8168 kernel.module for the 5.10.82-kernel. Its also not on the list of the new packages. I need that, maybe others too.

Thanks Girk

Hello.

just lead:

sudo pacman -S linux510-r8168

In the terminal off.

Previous issue in kernel 5.15 has been fixed

[omano@omano-nvme ~]$ sudo journalctl -p 3 -xb-1
-- Journal begins at Fri 2021-11-26 23:51:40 CET, ends at Sun 2021-11-28 07:11:46 CET. --
nov. 28 05:45:22 omano-nvme kernel: ata2.00: Read log page 0x08 failed, Emask 0x1
nov. 28 05:45:22 omano-nvme kernel: ata2.00: Read log page 0x08 failed, Emask 0x1
nov. 28 05:45:23 omano-nvme kernel: 

But I also see new warnings now

[omano@omano-nvme ~]$ sudo journalctl -p 3 -xb
-- Journal begins at Fri 2021-11-26 23:51:40 CET, ends at Sun 2021-11-28 07:11:36 CET. --
nov. 28 06:17:19 omano-nvme kernel: sd 0:0:0:0: [sda] Asking for cache data failed
nov. 28 06:17:19 omano-nvme kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
nov. 28 06:17:19 omano-nvme kernel: sd 1:0:0:0: [sdb] Asking for cache data failed
nov. 28 06:17:19 omano-nvme kernel: sd 1:0:0:0: [sdb] Assuming drive cache: write through
nov. 28 06:17:19 omano-nvme kernel: sd 5:0:0:0: [sdc] Asking for cache data failed
nov. 28 06:17:19 omano-nvme kernel: sd 5:0:0:0: [sdc] Assuming drive cache: write through
nov. 28 06:17:20 omano-nvme kernel: 

Probably no big deal and it will be fixed in future kernel update. It doesn’t seem to break anything.

Happy to report that Brightness Controls for OLED Screens (which wasn’t working on 5.15.4-2) is working on 5.15.5-2

It is showing this error message when updating.

==> ERROR: module not found: ...' ==> ERROR: module not found: …’
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.15-x86_64-fallback.img
==> WARNING: errors were encountered during the build. The image may not be complete.
erro: comando não executado corretamente

Update went fine.
Just one curious question: Is there some way to prevent pamac from trying to downgrade packages if the version number in the repository is lower than the version number of locally installed package?

Fortunately, sudo pacman -Syyu in the terminal only warns in this situation but does not actually downgrade the packages installed locally.

If I understand what you are asking:
In pamac-preferences-advanced uncheck “Enable Downgrade”.

Do you have by any chance kernel-alive package installed? If so, remove it and reinstall your kernels.

Thanks a lot! Indeed, that setting does the job.

I got a GPGME error today, I searched for some solutions on the forum but none of them work.

Packages (3) archlinux-keyring-20211028-1  gnupg-2.2.32-2  manjaro-keyring-20210910-2

Total Download Size:    3.47 MiB
Total Installed Size:  11.49 MiB
Net Upgrade Size:       0.00 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
gnupg-2.2.32-2-x86_64                          2.4 MiB  21.6 MiB/s 00:00 [------------------------------------------] 100%
archlinux-keyring-20211028-1-any             979.1 KiB  9.56 MiB/s 00:00 [------------------------------------------] 100%
manjaro-keyring-20210910-2-any               141.6 KiB  2.20 MiB/s 00:00 [------------------------------------------] 100%
Total (3/3)                                    3.5 MiB  12.7 MiB/s 00:00 [------------------------------------------] 100%
(3/3) checking keys in keyring                                            [------------------------------------------] 100%
(3/3) checking package integrity                                          [------------------------------------------] 100%
(3/3) loading package files                                               [------------------------------------------] 100%
(3/3) checking for file conflicts                                         [------------------------------------------] 100%
(3/3) checking available disk space                                       [------------------------------------------] 100%
:: Running pre-transaction hooks...
(1/1) Creating Timeshift snapshot before upgrade...
==> skipping timeshift-autosnap due skipRsyncAutosnap in /etc/timeshift-autosnap.conf set to TRUE.
:: Processing package changes...
(1/3) reinstalling gnupg                                                  [------------------------------------------] 100%
(2/3) reinstalling archlinux-keyring                                      [------------------------------------------] 100%
==> Appending keys from archlinux.gpg...
gpg: public key DB323392796CA067 is 3037 days newer than the signature
==> Updating trust database...
gpg: next trustdb check due at 2022-01-20
==> Updating trust database...
gpg: next trustdb check due at 2022-01-20
(3/3) reinstalling manjaro-keyring                                        [------------------------------------------] 100%
==> Appending keys from manjaro.gpg...
gpg: public key DB323392796CA067 is 3037 days newer than the signature
gpg: error reading key: No public key
gpg: error reading key: No public key
==> Disabling revoked keys in keyring...
-> Disabled 2 keys.
==> Updating trust database...
gpg: next trustdb check due at 2022-01-20
:: Running post-transaction hooks...
(1/3) Arming ConditionNeedsUpdate...
(2/3) Refreshing PackageKit...
(3/3) Updating the info directory file...
(base) [firestar@ThinkPad ~]$ sudo pacman -Syu  
error: GPGME error: No data
error: GPGME error: No data
error: GPGME error: No data
error: GPGME error: No data
:: Synchronizing package databases...
core                                         169.1 KiB   502 KiB/s 00:00 [------------------------------------------] 100%
extra                                       1957.2 KiB  11.9 MiB/s 00:00 [------------------------------------------] 100%
community                                      6.8 MiB  36.9 MiB/s 00:00 [------------------------------------------] 100%
multilib                                     176.1 KiB  3.02 MiB/s 00:00 [------------------------------------------] 100%
archlinuxcn is up to date
error: GPGME error: No data
error: GPGME error: No data
error: GPGME error: No data
error: GPGME error: No data
error: failed to synchronize all databases (unexpected error)