[Testing Update] 2024-07-07 - Kernels, Mesa, Systemd, hhd, adjustor

Hello community, here we have another set of package updates.

Current Promotions

  • Find out all about our current Gaming Laptop the Hero with Manjaro pre-installed from Spain!
  • Protect your personal data, keep yourself safe with Surfshark VPN: Get 3 months extra

Recent News

  • Philip was at Computex and showed off the OrangePi Neo
  • Manjaro Team member @romangg has a new library project with a guest post on Phoronix.
Previous News
Finding information easier about Manjaro

Finding information easier about Manjaro always has been a topic that needed to be solved. With our new search we have put all Manjaro data accessible in one place and divided by sections so it makes it easier to digest: New Manjaro search engine is available | Blog


Notable Package Updates

  • Some Kernels got updated
  • Systemd 256.2
  • Updates to hhd, hhd-ui and adjustor
  • Mesa 24.1.3
  • regular Haskell and python updates

Additional Info

Python 3.12 info

:information_source: You will need to rebuild any AUR Python packages that install files to site-packages or link to libpython3.11.so. :information_source:

Print a list of of packages that have files in /usr/lib/python3.11/ :

pacman -Qoq /usr/lib/python3.11/

Rebuild them all at once:*

pamac build $(pacman -Qoq /usr/lib/python3.11)

* Note that if any fail to build, you’ll have to rebuild what’s remaining one or a few at a time.

Use rebuild-detector to see if anything else needs to be rebuilt:

Info about AUR packages

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

For help with AUR packages, please create a new topic in AUR and a helpful volunteer may be able to assist you.

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

Our current supported kernels

  • linux419 4.19.317
  • linux54 5.4.279
  • linux510 5.10.221
  • linux515 5.15.162
  • linux61 6.1.97
  • linux66 6.6.37
  • linux68 6.8.12 [EOL]
  • linux69 6.9.8
  • linux610 6.10-rc6
  • linux61-rt 6.1.83_rt28
  • linux66-rt 6.6.30_rt30
  • linux67-rt 6.7_rt6

Package changes (Sun Jul 7 05:59:49 CEST 2024)

  • testing core x86_64: 6 new and 6 removed package(s)
  • testing extra x86_64: 228 new and 226 removed package(s)
  • testing multilib x86_64: 12 new and 12 removed package(s)

Package Changes (Overlay)

  • testing core x86_64: 19 new and 19 removed package(s)
  • testing extra x86_64: 107 new and 107 removed package(s)
  • testing multilib x86_64: 12 new and 12 removed package(s)

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

1 Like

Known issues and solutions

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

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

:arrow_right: 2024-07-07


The sshd service needs to be restarted after upgrading to openssh-9.8p1

2024-07-01 - Robin Candau

After upgrading to openssh-9.8p1, the existing SSH daemon will be unable to accept new connections (see Can't login after openssh 9.8p1-1 upgrade, MUST restart sshd (#5) · Issues · Arch Linux / Packaging / Packages / openssh · GitLab).
When upgrading remote hosts, please make sure to restart the sshd service using systemctl try-restart sshd right after upgrading.

We are evaluating the possibility to automatically apply a restart of the sshd service on upgrade in a future release of the openssh-9.8p1 package.

Arch Linux - News: The sshd service needs to be restarted after upgrading to openssh-9.8p1


:warning: Linux 6.8 is EOL

Linux 6.8 is EOL and will - at some point - be removed from the repo.

Suggestion is to install latest LTS to be sure

sudo mhwd-kernel -i linux66


Shutdown Issues on some AMD systems (fixed in latest kernels)
  • Problem: Kernel updates 6.1.91-1 and 6.6.31-1 break shutdown and suspend/resume on the Framework 16 (Ryzen 7 7840HS, no GPU).
  • Solution: kernels were patched - please update to 6.1.92 / 6.6.32 / 6.8.11 / 6.9.2
  • Issue tracking: framework forums


No plasma interface with kernel 6.9 + Nvidia gpu + Wayland

If you encouter a black screen with no inteface after login in, it’s probably a problem with simpledrm loading.

To solve it add nvidia_drm.fbdev=1 to /etc/default/grub
in the line begining with GRUB_CMDLINE_LINUX=" .
Verify that you also have nvidia_drm.modeset=1 in the same line.
Then exec sudo update-grub

Also, verify that you have nvidia_drm in /etc/mkinitcpio.conf in the MODULES= or HOOKS= line.
Exemple :

MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)

If it was not present, then run sudo mkinitcpio -P after adding it.


Qemu: MacOS is not bootable with 9.0

Due to a bug MacOS is not bootable with 9.0: [9.0.0] qemu breaks mac os vm (#2334) · Issues · QEMU / QEMU · GitLab
Workaround: remove virtio-serial and org.qemu.guest_agent.0 from libvirt XML until bug will be fixed.


The default KDE Plasma session has been changed to X11

As of Plasma 6, KDE decided to make Wayland the default. However, since issues were discovered, we have reverted the default to X11. Users are free to choose whichever works best for them.

Previous testing threads:

LLVM + Clang etc also got updated to 18.
So be prepared in case of using mesa-git etc to recompile and solve some dependencies (e.g. ‘yay -d’ and build mesa afterwards)

1 Like

with kernel 6.9.8-1 & nvidia 555.58.02 for GTX 970 series

i have in red this two line

juil. 07 11:33:42 kernel: [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000700] Failed to grab modeset ownership
juil. 07 11:33:42 kernel: [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000700] Failed to grab modeset ownership

this is this point

that reappears

Thread cleaned. :broom:

Manjaro has three branches. If you require newer packages, switch to the appropriate branch.

1 Like

Did you read that from Nvidia developer?

You can avoid the problem by loading nvidia-drm with the fbdev=1 parameter. But like I mentioned in my earlier reply, this message is usually harmless and expected. You can just ignore it if you’re not having any functional problems regarding applications using DRM just for rendering.

this is only remove the two red lines , nothing else …
a little change on boot screen

before : grub ( text ) > systemd text > UEFI logo motherboard > left corner (nvidia ) more than 3sec (TTY1) > Xfce login

grub ( text ) > left corner (nvidia ) more than 3sec (TTY1) > Xfce login

that do not solve locking screen endin on login with black screen and mouse that you can move ( Ctrl + Alt + F7 returns same ) in both cases

@stephane check which plymouth version is installed on your end. Newer versions than 22 series might have issues with Nvidia drivers.

i have removed plymouth form a long time


Read the Nvidia driver discussion thread if you think it is the driver: 555 release feedback & discussion - Linux - NVIDIA Developer Forums

I can confirm that DVI output is not working with Nvidia 555 driver. Tested on my dual monitor setup. 550 working super fine.

DVI-D and DVI-I?