[Testing Update] 2024-07-01 - Kernels, Gstreamer, Thunderbird, Pipewire, Mesa, Firefox, Gnome, Phosh, Nvidia, Qt6

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 will be at Computex and show 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

image

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

checkrebuild
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.316
  • linux54 5.4.278
  • linux510 5.10.220
  • linux515 5.15.161
  • linux61 6.1.96
  • linux66 6.6.36
  • linux68 6.8.12 [EOL]
  • linux69 6.9.7
  • linux610 6.10-rc6
  • linux61-rt 6.1.83_rt28
  • linux66-rt 6.6.30_rt30
  • linux67-rt 6.7_rt6

Package changes (Mon Jul 1 05:13:25 CEST 2024)

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

Package Changes (Overlay)

  • testing core x86_64: 12 new and 12 removed package(s)
  • testing extra x86_64: 225 new and 279 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:

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


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

:arrow_right: 2024-07-01

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

2024-06-03

:warning: Linux 6.8 is EOL

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

:warning: Linux 6.7 is EOL
Linux 6.7 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

2024-05-18

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

2024-05-14

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.

2024-05-08

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.

2024-05-02

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:

can you check status for build nvidia lib32 modules ?

sudo pacman -Syyu
[sudo] 
:: Synchronisation des bases de données de paquets…
 core                  140,4 KiB  1003 KiB/s 00:00 [----------------------] 100%
 extra                   8,4 MiB  27,9 MiB/s 00:00 [----------------------] 100%
 multilib              145,5 KiB  1119 KiB/s 00:00 [----------------------] 100%
:: Début de la mise à jour complète du système…
résolution des dépendances…
avertissement : impossible de résoudre « nvidia-utils=555.58 », une dépendance de « lib32-nvidia-utils »
:: Le paquet suivant ne peut être mis à jour à cause de dépendances insolubles :
      lib32-nvidia-utils

:: Voulez-vous ignorer le paquet ci-dessus pour cette mise à jour ? [o/N] 
erreur : la préparation de la transaction a échoué (la satisfaction des dépendances a échoué)
:: impossible de satisfaire la dépendance « nvidia-utils=555.58 » requise par lib32-nvidia-utils

waiting when it all will be ok (no update to do for the moment )

Currently still pushing updates. You can see when it cools down here: The manjaro-packages Archives

2 Likes

Is this advice for Plasma users only? Can a Gnome user safely update?

1 Like

Why not just wait until the announcement that it’s there?

Or if you’re really, really, really that angsty, why not just give it a go and deal with thee consequences? Remember, always, before any upgrade: BACKUPS!

1 Like

We need Plasma 6.1 with Nvidia 555, not Plasma 6.0. You should wait some more few days before to update

1 Like

I’ve just asked a question. In the absence of an answer, obviously, I won’t update.

2 Likes

I just did prior to checking the forum. So far, so good…

1 Like

Why not Plasma 6.1? It runs better than 6.0 on my Arch and Manjaro unstable installations.

3 Likes

Because the fact that it might run better on YOUR installations is no guarantee - otherwise there’d be just one test laptop and it’d go straight to Stable :wink:

3 Likes

This is testing. The more people that test it, the sooner it can go to stable branch.

2 Likes

We won’t update to 6.1 Plasma any time soon. There are serious bugs which prevents that. You can find the Plasma 6 upstream release schedule and see when bug fixes are expected. Switch to unstable to help testing. Testing branch is a preparation branch for the Stable branch. So we will see when Plasma 6.1 is enough stable from our end to land here.

10 Likes

In addition to a considerable amount of bugs in 6.1, with NVIDIA 555.58 I have also had black screen problems when logging in and out in both Wayland and X11.

I have reverted to the stable branch.

1 Like

Known Issue regarding OpenSSH added above. :point_up:

4 Likes

Hi, thanks for the update.

Lutris was not behaving normal right now, so I checked the command line output. It seems it has to be recompiled with the pushed python updates.

The log:


2024-07-01 19:09:32,621: The Battle.net source is unavailable because Google protobuf could not be loaded: Descriptors cannot be created directly.
If this call came from a _pb2.py file, your generated code is out of date and must be regenerated with protoc >= 3.19.0.
If you cannot immediately regenerate your protos, some other possible workarounds are:
 1. Downgrade the protobuf package to 3.20.x or lower.
 2. Set PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=python (but this will use pure-Python parsing and will be much slower).

EDIT:

Another issue I face and cannot fully resolve is regarding gamscope-plus (and also gamescope (while using lutris). The error:

gamescope: children shut down!
(EE) failed to read Wayland events: Broken pipe
X connection to :2 broken (explicit kill or server shutdown).
X connection to :2 broken (explicit kill or server shutdown).
X connection to :2 broken (explicit kill or server shutdown).
X connection to :2 broken (explicit kill or server shutdown).
Initial process has exited (return code: 0)

(I am on gnome wayland with an AMD graphics card). I tried to downgrade to the previous gamescope version with manjaro-downgrade to resolve the issue, but this warning kept me from doing it to be honest.

Warning: Cannot resolve "libdisplay-info.so=1-64" (a dependency of "gamescope-plus")

Maybe this information helps :slight_smile:
(I am on Gnome Wayland)

I did a rebuild of that package. Let me know if that helps.

1 Like

Can not boot in plasma Wayland with NVIDIA 555, but can in X11. 550 are fine with both sessions. Hyprland is fine with 555

Journalctl states it is OpenGL error:

июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: OpenGL vendor string:                   NVIDIA Corporation
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: OpenGL renderer string:                 NVIDIA GeForce RTX 3060/PCIe/SSE2
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: OpenGL version string:                  3.1.0 NVIDIA 555.58
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: OpenGL shading language version string: 1.40 NVIDIA via Cg compiler
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: Driver:                                 NVIDIA
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: Driver version:                         555.58
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: GPU class:                              Unknown
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: OpenGL version:                         3.1
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: GLSL version:                           1.40
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: Requires strict binding:                no
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: Virtual Machine:                        no
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: Timer query support:                    yes
июл 02 10:48:21 dannkuntPC tailscaled[1159]: open-conn-track: timeout opening (TCP 100.115.35.14:51262 => 116.203.91.91:80); no associated peer node
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
июл 02 10:48:21 dannkuntPC kwin_wayland[1711]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"

Same with 6.9 xanmod and 6.6 lts from repos

And I have all recommended boot options:

GRUB_CMDLINE_LINUX_DEFAULT='apparmor=1 security=apparmor resume=UUID=9451eba8-7ab2-4f3a-8619-3a8c95b9ee84 udev.log_priority=3 nvidia-drm.modeset=1 nvidia_drm.fbdev=1 nvidia.NVreg_EnableGpuFirmware=0'
MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)

Did I miss something or this is bug somewhere

Hi. The update went almost OK. The only issue is missing krdp package that is listed as dependency of plasma-meta package:

:: Starting full system upgrade...
resolving dependencies...
warning: cannot resolve "krdp", a dependency of "plasma-meta"
:: The following package cannot be upgraded due to unresolvable dependencies:
      plasma-meta

P.S.
This package status on testing branch is marked yellow in Manjaro packages page:
https://packages.manjaro.org/?query=krdp