[Testing Update] 2020-10-19 - Kernels, Alsa, Haskell, Pamac, Calamares

Hello community,

Another testing branch update with some interesting updates for you!

Need a phone? We got you covered! PinePhone will ship with Manjaro #stayhome, #staysafe, #stayhealthy

  • We updated most of our Kernels
  • Pamac got another point-release with needed fixes
  • Calamares supports now Swap-files
  • Alsa stack got renewed
  • Usual Python and Haskell package updates and rebuilds

If you like following latest Plasma development you may also like to check out our current version of manjaro-kde-dev, which we build on a regular basis against kde-git master packages. Also check out our latest Manjaro Nibia 20.2 preview release! KDE and Gnome

Our current supported kernels

  • linux44 4.4.240
  • linux49 4.9.240
  • linux414 4.14.202
  • linux419 4.19.152
  • linux54 5.4.72
  • linux57 5.7.19 [EOL]
  • linux58 5.8.16
  • linux59 5.9.1
  • linux54-rt 5.4.66_rt38
  • linux56-rt 5.6.19_rt12

Packages Changes (Mon Oct 19 11:22:26 CEST 2020)

  • testing community x86_64: 834 new and 824 removed package(s)
  • testing core x86_64: 16 new and 16 removed package(s)
  • testing extra x86_64: 170 new and 170 removed package(s)
  • testing multilib x86_64: 5 new and 5 removed package(s)

A detailed list of all package changes can be found 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:


Known issues and solutions

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

nvidia 455.28 is incompatible with linux >= 5.9

2020-10-21 - Sven-Hendrik Haase

nvidia is currently partially incompatible with linux >= 5.9 [1] [2]. While graphics should work fine, CUDA, OpenCL, and likely other features are broken. Users who’ve already upgraded and need those features are advised to switch to the linux-lts kernel for the time being until a fix for nvidia is available.


Older Issues

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 org.cups.cupsd.service
systemctl enable org.cups.cupsd.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.

Gnome-shell-extension-pop-shell is currently incompatible with wayland

… and causes the system to freeze when the first window is tiled and can render it unbootable. Solution is a hard reset and disabling either pop shell or wayland. If the system becomes unbootable, use a live USB to edit /etc/gdm/custom.conf to disable wayland and reboot.

Trying to run corectrl: corectrl: error while loading shared libraries: libbotan-2.so.15: cannot open shared object file: No such file or directory

I think you need to rebuild the package to look for libbotan-2.so.16 (or maybe just the libbotan-2.so symlink?).

I think this issue was present in the previous release as well.

Not sure if its related to the latest update or not but I’m having issues with screenshot now. If I take a screenshot I only get the top left hand quarter of the screen, the other 3/4 are just blank.

Edit. It’s only gnome screenshot, pantheon screenshot works fine.

added new packages:

:: Different overlay package(s) in repository community x86_64

                             PACKAGE           2020-10-16           2020-10-19
           kaccounts-integration-git    .r1162.gaf7e5d0-1    .r1163.gc64e373-1
                      kio-extras-git    r6886.gc2e576ab-1    r6887.gef76b22b-1

:: Different overlay package(s) in repository core x86_64

                             PACKAGE           2020-10-16           2020-10-19
                             linux58             5.8.16-1             5.8.16-2
                     linux58-headers             5.8.16-1             5.8.16-2

that is an AUR package. Pls do a rebuild of it.

It’s actually a repo package, that @schinfo added (last packager).

Rebuilding from source fixes that, of course. But it has (relatively recently) became an official repo package.

I can also see that @schinfo bumped the pkgrel version yesterday, so I guess 1.1.1-3 just didn’t make it to the update for some reason…

( 8/37) mise Ă  jour de grub-theme-manjaro                                                          [----------------------------------------------------------] 100%
Création du fichier de configuration GRUB…
Thème trouvé : /usr/share/grub/themes/manjaro/theme.txt
Windows Boot Manager trouvé sur /dev/sdc1@/efi/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings ...
==> Installation: Theme is added to your /etc/default/grub: GRUB_THEME="/usr/share/grub/themes/manjaro/theme.txt"
==> Default resolution "auto"
==> If an OS icon doesn't appear probably not present in /usr/share/grub/themes/manjaro/icons simply add it or merge in
==> https://gitlab.manjaro.org/artwork/branding/grub-theme

Everything seems OK (//EDIT: kernel 5.8, Nvidia 455), but it is the second consecutive update erasing my custom GRUB theme GRUB_THEME="/boot/grub/themes/pacbang/theme.txt", is this something I’ll have to revert regularly now? Maybe if it can be possible, do not override this line if it is not the default Manjaro theme already?


Pamac threw this error (and put up an error window):

Detecting snapshots ...
Info: Separate boot partition not detected 
No snapshots found.
If you think an error has occurred , please file a bug report at " https://github.com/Antynea/grub-btrfs "
Error while configuring 
Nothing to do. Abort.
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.

Will send bug report to btrfs at github (IF there is a bug) as it recommends.

I just rebooted, everything seems to be OK, so I guess this error was nothing to worry about.

octopi reacting very slow when pressing Apply
not yet update to freeoffice 978?

Info Center -> SMART still has the non sense French translation saying THE EXACT OPPOSITE of the original English version… It is telling me all my peripherals seem to not work properly, when in the original version it is telling me the opposite, all me peripherals seem to work as intended.

17 posts were merged into an existing topic: Update error - unsure of update cycles/consequences

No issues, I can see so far.: XFCE + linux58 + BTRFS
I can safely turn on Bluetooth again :slight_smile:

A post was split to a new topic: Update error - unsure of update cicles/consequences

Hope I can install Manjaro with linux59 isos…might not happen but hope for the best :grinning::grinning::pensive:

Running Arch with 5.9.1 for a Day without any kind of issue…but really want to use Manjaro with new kernels

A post was merged into an existing topic: Update error - unsure of update cycles/consequences

It happens all the time that there are updates without announcement, Manjaro team doesn’t create a new thread when some packages got updated, and again, you’re twisting the chronology, the information of the issue being about Stable branch was not there at all, when I started trying to figure it out, when a user posted information about an issue in the Testing branch thread. I don’t have a crystal ball.

I lost my audio, probably due to the ALSA update. I just have a “dummy output” that doesn’t play any sound. Ideas?

I temporarily solved by downgrading alsa-ucm-conf as suggested here.