[Unstable Update] 2022-05-23 - Systemd 251, Linux 5.18

Hello community,

Another unstable branch update with some usual updates for you.

In need an Office-ready MiniPC? Check out the UM350 shipping with KDE Plasma and OnlyOffice pre-installed!

  • Linux 5.18 is released. Not all modules are available yet.
  • Systemd 251 has been released with a lot of major changes. The minimum kernel version required has been bumped from 3.13 to 4.15. This of course means Manjaro will have to drop the 4.9 and 4.14 LTS kernels.

Additional Info

Info about AUR packages

:warning: AUR (Arch User Repository) packages are neither supported by Arch nor Manjaro. Posts about them in Annoucement topics are off-topic and will be flagged, moved or removed without warning.

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

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

  • linux419 4.19.244
  • linux54 5.4.195
  • linux510 5.10.117
  • linux515 5.15.41
  • linux517 5.17.9
  • linux518 5.18.0
  • linux515-rt 5.15.36_rt41
  • linux517-rt 5.17.1_rt17
  • 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:

[New Packages] core
[New Packages] extra

No module “linux518-virtualbox-host-modules”?

That’s common when a new kernel is released. It will take a little time for VirtualBox to add compatibility. Perhaps in the next point release or two.


Probably be a few days. When 5.17 was released March 20, 2022, VirtualBox added support 3 days later. Changelog – Oracle VM VirtualBox


Another option is to use the virtualbox-host-dkms package (remember kernel headers)

I have tried but it fails building the module for 5.18 (5.15 and 5.17 works).

Building module:
cleaning build area...
make -j8 KERNELRELEASE=5.18.0-1-MANJARO -C /usr/lib/modules/5.18.0-1-MANJARO/build M=/var/lib/dkms/vboxhost/6.1.34_OSE/build.......(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.18.0-1-MANJARO (x86_64)
Consult /var/lib/dkms/vboxhost/6.1.34_OSE/build/make.log for more information.

And the make.log doesn’t show a precise error, the last lines are

  LD [M]  /var/lib/dkms/vboxhost/6.1.34_OSE/build/vboxdrv/vboxdrv.o
make: *** [Makefile:1834: /var/lib/dkms/vboxhost/6.1.34_OSE/build] Error 2
make: Leaving directory '/usr/lib/modules/5.18.0-1-MANJARO/build'

I’ll wait for the modules to be precompiled.

I think this is a good choice, because some older Hardware run fine on newer LTS Kernel. My old ThinkPad T60 run on 5.18 (5.17 as fallback) no issues so far.

BTW for testing

only Kernel 5.18.0-1

systemd-udevd[449]: event3: Failed to call EVIOCSKEYCODE with scan code 0x7c, and key code 190: Invalid argument

Issue with Cherry-keyboard: Strait Black (corded keyboard). Keycode 190 = F22 does not exist
on that keyboard.
EDIT: issue has gone when downgrading to systemd 250

Timeshift was my friend again. ~The journald-handling was destroyed, too!~
No kernel 518 installed now - everything working as expected wanted.
Colonel 518 Wörks - Jess Sir!

Edit: Qjournalctl crashes using kernel 5.18.-1. (list all available boots)
EDIT2: reason is Systemd 251 - QJournalctl timestamp doesnot fit systemtime?!
reason for EVIOCSKEYCODE = Systemd 251 (tested)
Hopefull the “ARCHies” fix system 251?
@linux-aarhus open a thread "Systemd-251 issues?
Gnome-keyring issue: (in journald)
WARNING: Could not parse desktop file gnome-keyring-secrets.desktop or it references a not found TryExec binary
but: /etc/xdg/autostart/gnome-keyring-secrets.desktop EXISTS
(Cherry) wired keyboard is not in the /lib/udev/hwdb.d/60-keyboard

It is now. Arch just added a patch for 5.18 with 6.1.34-3.


Installing kernel 518 via “Manjaro Settings”
does not include my extra-modules (openrazer)
whereas instaling via Pamac does…

1 Like

It’s nothing I can’t live with and I don’t know which update or any caused it but when I restart or shutdown the computer it makes the same beep shutting down as when it’s starting up.

didnt notice it when starting, but happened after systemd 251 update

I installed today linux518 with virtualbox-host-modules. Thanks! :+1:t6:

1 Like

2 posts were split to a new topic: Some Systemd services are taking quite a bit longer to start

1 Like

i have vague memory of some old linux/unix systems having such beeps on shutdown of the server or terminals. maybe this is bringing some nostalgia back by systemd. unlike the second issue reported had no issues where system hung on shutdown/reboot.

@Yochanan apparmor package needs to be rebuilt with new perl build. presently get this warning due to it.

5/9) Warn about old perl modules
WARNING: '/usr/lib/perl5/5.34' contains data from at least 1 packages which will NOT be used by the installed perl interpreter.
 -> Run the following command to get a list of affected packages: pacman -Qqo '/usr/lib/perl5/5.34'



A post was split to a new topic: When will the final and stable 5.18 kernel appear in the stable branch updates?

Wow, the smoothest update of Plasma I’ve ever experienced! Literally nothing to complain so far, frankly, I am surprised :slight_smile: