[Testing Update] 2024-12-11 - Kernels, Cinnamon, GNOME, Powerstation, Cosmic, Mauikit, Mesa

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 4 months extra

Recent News

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: News – Manjaro

image

Notable Package Updates

  • Kernels
    • 4.19 and 6.11 are now marked as EOL
  • Cinamon and Deepin updates
  • Powerstation 0.3.1
  • Cosmic Alpha 4
  • Mauikit 4.0.1
  • Mesa 24.3.1

Additional Info

Nvidia driver downgrade

Nvidia drivers got downgraded to 550.100, therefore update with sudo pacman -Syuu. If you want to stay on the 555 driver series you may either switch to unstable or install nvidia-dkms via: sudo pacman -U https://mirror.easyname.at/manjaro/pool/overlay/nvidia-dkms-555.58.02-1-x86_64.pkg.tar.zst. More info about Nvidia drivers here:

555 release feedback & discussion - Linux - NVIDIA Developer Forums
550.78 release feedback & discussion thread - Linux - NVIDIA Developer Forums

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.325 [EOL]
  • linux54 5.4.286
  • linux510 5.10.230
  • linux515 5.15.173
  • linux61 6.1.119
  • linux66 6.6.64
  • linux611 6.11.11
  • linux612 6.12.4
  • linux613 6.13-rc2
  • linux61-rt 6.1.119_rt45
  • linux66-rt 6.6.63_rt46

Package Changes (Wed Dec 11 02:54:36 CET 2024)

  • testing core x86_64: 15 new and 15 removed package(s)
  • testing extra x86_64: 490 new and 484 removed package(s)
  • testing multilib x86_64: 22 new and 22 removed package(s)

Overlay Changes

  • testing core x86_64: 11 new and 11 removed package(s)
  • testing extra x86_64: 85 new and 96 removed package(s)
  • testing multilib x86_64: 0 new and 9 removed package(s)

A list of all 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:


2 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!

Note: Do not forget to review your .pacnew files:

:arrow_right: 2024-12-11

Kernel 6.11 has been marked End Of Life (EOL) on kernel.org

2024-11-27

Partial Cinnamon 6.4 updates

Linux Mint is currently preparing Cinnamon 6.4. The Arch Maintainers went ahead and released some Cinnamon packages which got already tagged 6.4. However, it seems this will break your installation of your Cinnamon desktop. We will monitor the situation and might downgrade to 6.2 packages if needed, before we do a stable branch update. Your feedback regarding Cinnamon overall is highly appreciated.

Known issues so far:

What you can do:

  • Ignore all cinnamon updates when updating.
  • You can try the newly added cinnamon-git package to see if it improves the situation.
  • Update: The issues are resolved with cinnamon >= 6.4.0-1. If you manually installed cinnamon-git, you may now install cinnamon again.

2024-11-13

v86d has been dropped from Manjaro repositories and is no longer required for mhwd

Re: Unstable Update MHWD disussion

If pamac GUI options Enable AUR support and Check for updates are enabled, users should check the package list before agreeing to update and un-check AUR packages

2024-11-01

KVM default behavior change on module loading in kernel 6.12

In kernel 6.12, KVM initializes virtualization on module loading by default. This prevents VirtualBox VMs from starting. In order to avoid this, either add kvm.enable_virt_at_load=0 parameter into kernel command line or unload the corresponding kvm_XXX module. Initial support for 6.12 kernel series was added with Virtualbox 7.1.4.

More info about that in the Linux mailing list

2024-10-20

Kernel 6.10 has been marked [EOL] on kernel.org

sddm login problems with multiple monitors
  • bug report
  • login only works on secondary monitor
  • switching sddm theme to maldives works around the issue

Previous testing threads:

The update went flawlessly.

Just an addition to Mesa 24.3.1, which I was already using.
Especially for AMD GPU users. The recent Linux firmware update 20241210, included numerous amdgpu fixes that addressed stability issues with 7800/7900 graphics cards amongst others, see kernel/git/firmware/linux-firmware.git - Repository of firmware blobs for use with the Linux kernel
Without it my system crashed randomly (amdgpu 0000:0d:00.0: [drm] ERROR flip_done timed out) on 24.3.1, no problems with 24.2.8.

Maybe helpful for other amdgpu users, to install linux-firmware-git if crashes happen.

2 Likes

@fraz0815 thx for letting us know. I will push the new firmware updates shortly.

3 Likes

After the update bluetooth error:

$ blueman-adapters
Traceback (most recent call last):
  File "/usr/bin/blueman-adapters", line 43, in <module>
    app = blueman_adapters = BluemanAdapters(args.adapter, args.socket_id)
                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/blueman/main/Adapter.py", line 57, in __init__
    check_bluetooth_status(_("Bluetooth needs to be turned on for the adapter manager to work"), bmexit)
  File "/usr/lib/python3.12/site-packages/blueman/Functions.py", line 67, in check_bluetooth_status
    if not applet.GetBluetoothStatus():
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/gi/overrides/Gio.py", line 374, in __call__
    result = self.dbus_proxy.call_sync(self.method_name, arg_variant,
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
gi.repository.GLib.GError: g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Remote peer disconnected (4)
$ 

I get a conflict when updating:

Fehler: Der Vorgang konnte nicht durchgeführt werden (In Konflikt stehende Dateien)
/usr/lib/modules/6.12.4-1-MANJARO/extramodules/Module.symvers existiert in »linux612-acpi_call« und »linux612-virtualbox-host-modules«
/usr/lib/modules/6.13.0-rc2-1-MANJARO/extramodules/Module.symvers existiert in »linux613-acpi_call« und »linux613-virtualbox-host-modules«

Ya, this one is odd. should not been there. Have to check why. Both are done via dkms packages.

Can confirm, same here.

blueman-applet[2586]: segfault at 7bed42ae7a29 ip 00007beb0aee8741 sp 00007ffd18455a98 error 4 in libgobject-2.0.so.0.8200.3[3a741,7beb0aeba000+38000] likely on CPU 10 (core 5, socket 0)

Seems Arch fixed it like this: 7.1.4-14: Remove Module.symvers (efeeccf1) · Commits · Arch Linux / Packaging / Packages / virtualbox-host-modules-arch · GitLab

@banjo @jimjones Which desktop environment you both use for blueman?

Cinnamon

Plasma Wayland
getting 2 orphans

liboxmil-bellagio
scons

NOTE, 6.11.11 is the last maintenance release of the 6.11 kernel series.
This kernel is now marked ‘End Of Life’ (EOL).

It is recommend to switch to the newer linux612 series:
‘sudo mhwd-kernel -i linux612’

Xfce, as always.

From journal:

Dez 12 07:34:43 systemd-coredump[1409]: [🡕] Process 1235 (blueman-applet) of user 1000 dumped core.
                                        
                                        Stack trace of thread 1235:
                                        #0  0x00007f5049da6741 g_type_check_instance_is_fundamentally_a (libgobject-2.0.so.0 + 0x3a741)
                                        #1  0x00007f5049d8cf20 g_object_unref (libgobject-2.0.so.0 + 0x20f20)
                                        #2  0x00007f504a07a555 n/a (libglib-2.0.so.0 + 0x53555)
                                        #3  0x00007f504a082cac n/a (libglib-2.0.so.0 + 0x5bcac)
                                        #4  0x00007f504a08466a n/a (libglib-2.0.so.0 + 0x5d66a)
                                        #5  0x00007f504a0e7257 n/a (libglib-2.0.so.0 + 0xc0257)
                                        #6  0x00007f504a083a55 g_main_context_iteration (libglib-2.0.so.0 + 0x5ca55)
                                        #7  0x00007f504924ecb6 g_application_run (libgio-2.0.so.0 + 0xdecb6)
                                        #8  0x00007f504af5f596 n/a (libffi.so.8 + 0x7596)
                                        #9  0x00007f504af5c00e n/a (libffi.so.8 + 0x400e)
                                        #10 0x00007f504af5ebd3 ffi_call (libffi.so.8 + 0x6bd3)
                                        #11 0x00007f5049e1df35 n/a (_gi.cpython-312-x86_64-linux-gnu.so + 0x2df35)
                                        #12 0x00007f5049e18a5b n/a (_gi.cpython-312-x86_64-linux-gnu.so + 0x28a5b)
                                        #13 0x00007f504b3c4c8a _PyObject_Call (libpython3.12.so.1.0 + 0x1c4c8a)
                                        #14 0x00007f504b3905ea _PyEval_EvalFrameDefault (libpython3.12.so.1.0 + 0x1905ea)
                                        #15 0x00007f504b44de35 PyEval_EvalCode (libpython3.12.so.1.0 + 0x24de35)
                                        #16 0x00007f504b4724aa n/a (libpython3.12.so.1.0 + 0x2724aa)
                                        #17 0x00007f504b46d24f n/a (libpython3.12.so.1.0 + 0x26d24f)
                                        #18 0x00007f504b4879d4 n/a (libpython3.12.so.1.0 + 0x2879d4)
                                        #19 0x00007f504b487261 _PyRun_SimpleFileObject (libpython3.12.so.1.0 + 0x287261)
                                        #20 0x00007f504b4869bf _PyRun_AnyFileObject (libpython3.12.so.1.0 + 0x2869bf)
                                        #21 0x00007f504b47f174 Py_RunMain (libpython3.12.so.1.0 + 0x27f174)
                                        #22 0x00007f504b43c5ec Py_BytesMain (libpython3.12.so.1.0 + 0x23c5ec)
                                        #23 0x00007f504b034e08 n/a (libc.so.6 + 0x25e08)
                                        #24 0x00007f504b034ecc __libc_start_main (libc.so.6 + 0x25ecc)
                                        #25 0x0000559747e95045 _start (python3.12 + 0x1045)
                                        
                                        Stack trace of thread 1338:
                                        #0  0x00007f504b11abb0 ppoll (libc.so.6 + 0x10bbb0)
                                        #1  0x00007f504a0e7327 n/a (libglib-2.0.so.0 + 0xc0327)
                                        #2  0x00007f504a085287 g_main_loop_run (libglib-2.0.so.0 + 0x5e287)
                                        #3  0x00007f5049283bc4 n/a (libgio-2.0.so.0 + 0x113bc4)
                                        #4  0x00007f504a0b9be6 n/a (libglib-2.0.so.0 + 0x92be6)
                                        #5  0x00007f504b0a339d n/a (libc.so.6 + 0x9439d)
                                        #6  0x00007f504b12849c n/a (libc.so.6 + 0x11949c)
                                        
                                        Stack trace of thread 1335:
                                        #0  0x00007f504b1261fd syscall (libc.so.6 + 0x1171fd)
                                        #1  0x00007f504a0b5be0 g_cond_wait (libglib-2.0.so.0 + 0x8ebe0)
                                        #2  0x00007f504a04c98c n/a (libglib-2.0.so.0 + 0x2598c)
                                        #3  0x00007f504a0bc237 n/a (libglib-2.0.so.0 + 0x95237)
                                        #4  0x00007f504a0b9be6 n/a (libglib-2.0.so.0 + 0x92be6)
                                        #5  0x00007f504b0a339d n/a (libc.so.6 + 0x9439d)
                                        #6  0x00007f504b12849c n/a (libc.so.6 + 0x11949c)
                                        
                                        Stack trace of thread 1336:
                                        #0  0x00007f504b11abb0 ppoll (libc.so.6 + 0x10bbb0)
                                        #1  0x00007f504a0e7327 n/a (libglib-2.0.so.0 + 0xc0327)
                                        #2  0x00007f504a083a55 g_main_context_iteration (libglib-2.0.so.0 + 0x5ca55)
                                        #3  0x00007f504a083ab2 n/a (libglib-2.0.so.0 + 0x5cab2)
                                        #4  0x00007f504a0b9be6 n/a (libglib-2.0.so.0 + 0x92be6)
                                        #5  0x00007f504b0a339d n/a (libc.so.6 + 0x9439d)
                                        #6  0x00007f504b12849c n/a (libc.so.6 + 0x11949c)
                                        
                                        Stack trace of thread 1356:
                                        #0  0x00007f504b1261fd syscall (libc.so.6 + 0x1171fd)
                                        #1  0x00007f504a0b68f7 g_cond_wait_until (libglib-2.0.so.0 + 0x8f8f7)
                                        #2  0x00007f504a04c955 n/a (libglib-2.0.so.0 + 0x25955)
                                        #3  0x00007f504a0bccfb n/a (libglib-2.0.so.0 + 0x95cfb)
                                        #4  0x00007f504a0b9be6 n/a (libglib-2.0.so.0 + 0x92be6)
                                        #5  0x00007f504b0a339d n/a (libc.so.6 + 0x9439d)
                                        #6  0x00007f504b12849c n/a (libc.so.6 + 0x11949c)
                                        
                                        Stack trace of thread 1402:
                                        #0  0x00007f504b1261fd syscall (libc.so.6 + 0x1171fd)
                                        #1  0x00007f504a0b68f7 g_cond_wait_until (libglib-2.0.so.0 + 0x8f8f7)
                                        #2  0x00007f504a04c955 n/a (libglib-2.0.so.0 + 0x25955)
                                        #3  0x00007f504a0bccfb n/a (libglib-2.0.so.0 + 0x95cfb)
                                        #4  0x00007f504a0b9be6 n/a (libglib-2.0.so.0 + 0x92be6)
                                        #5  0x00007f504b0a339d n/a (libc.so.6 + 0x9439d)
                                        #6  0x00007f504b12849c n/a (libc.so.6 + 0x11949c)
                                        
                                        Stack trace of thread 1358:
                                        #0  0x00007f504b11abb0 ppoll (libc.so.6 + 0x10bbb0)
                                        #1  0x00007f504a0e7327 n/a (libglib-2.0.so.0 + 0xc0327)
                                        #2  0x00007f504a083a55 g_main_context_iteration (libglib-2.0.so.0 + 0x5ca55)
                                        #3  0x00007f50459192fe n/a (libdconfsettings.so + 0x62fe)
                                        #4  0x00007f504a0b9be6 n/a (libglib-2.0.so.0 + 0x92be6)
                                        #5  0x00007f504b0a339d n/a (libc.so.6 + 0x9439d)
                                        #6  0x00007f504b12849c n/a (libc.so.6 + 0x11949c)
                                        ELF object binary architecture: AMD x86-64
░░ Subject: Speicherabbild für Prozess 1235 (blueman-applet) generiert
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ Documentation: man:core(5)
░░ 
░░ Prozess 1235 (blueman-applet) ist abgebrochen worden und
░░ ein Speicherabbild wurde generiert.
░░ 
░░ Üblicherweise ist dies ein Hinweis auf einen Programmfehler und sollte
░░ als Fehler dem jeweiligen Hersteller gemeldet werden.

I could recreate the flatpak problem. The 6.13rc1 and rc2 kernels break flatpak here:

6.13rc1 and rc2:

$ flatpak install com.visualstudio.code
Suchen nach Übereinstimmungen …

com.visualstudio.code Berechtigungen:
    ipc                   network               pulseaudio                   ssh-auth       x11       devices       devel
    file access [1]       dbus access [2]       system dbus access [3]       tags [4]

    [1] host
    [2] com.canonical.AppMenu.Registrar, com.canonical.AppMenu.Registrar.*, org.freedesktop.Flatpak, org.freedesktop.Notifications, org.freedesktop.secrets
    [3] org.freedesktop.login1
    [4] proprietary


        KENNUNG                         Zweig           Op          Gegenstelle          Herunterladen
 1. [✗] com.visualstudio.code           stable          i           flathub              107,9 MB / 109,6 MB

Error: Ungültige Prüfsumme für zusätzliche Daten
Fehler: Failed to install com.visualstudio.code: Ungültige Prüfsumme für zusätzliche Daten

6.12:

$ flatpak install com.visualstudio.code
Suchen nach Übereinstimmungen …

com.visualstudio.code Berechtigungen:
    ipc                   network               pulseaudio                   ssh-auth       x11       devices       devel
    file access [1]       dbus access [2]       system dbus access [3]       tags [4]

    [1] host
    [2] com.canonical.AppMenu.Registrar, com.canonical.AppMenu.Registrar.*, org.freedesktop.Flatpak, org.freedesktop.Notifications, org.freedesktop.secrets
    [3] org.freedesktop.login1
    [4] proprietary


        KENNUNG                         Zweig           Op          Gegenstelle          Herunterladen
 1. [✓] com.visualstudio.code           stable          i           flathub              107,9 MB / 109,6 MB

Installation abgeschlossen.

I see this on two different machines, one AMD one Intel.
But even more strange - it only happens with certain flatpaks like vscode or chrome. Their dependencies installed fine.

I read in the announcements here that the mesa driver v3.111 is included. Recently there was a serious problem in connection with mesa 3.11 and graphics cards from the RX 570 / 580 series. Is this also to be feared here and should I (RX 580 here) set the mesa 3.11 to ignore for now?

@Scruggs
If your card is running fine, I would skip 24.3.1, especially on KDE as you posted yourself. Actually three patches are in, but I still can manage to crash the gpu in complex scenarios on gnome (e.g. flatpaks which use ffmpeg)

0001-dri-don-t-fetch-X11-modifiers-if-we-don-t-support-th.patch
0002-egl-wayland-only-supply-LINEAR-modifier-when-support.patch
0003-egl-wayland-fallback-to-implicit-modifiers-if-advert.patch

@jimjones: confirming on 6.13.0-rc2-1-MANJARO

flatpak install com.visualstudio.code
Looking for matches…

com.visualstudio.code permissions:
    ipc                network                   pulseaudio    ssh-auth
    x11                devices                   devel         file access [1]
    dbus access [2]    system dbus access [3]    tags [4]

    [1] host
    [2] com.canonical.AppMenu.Registrar, com.canonical.AppMenu.Registrar.*,
        org.freedesktop.Flatpak, org.freedesktop.Notifications,
        org.freedesktop.secrets
    [3] org.freedesktop.login1
    [4] proprietary


        ID                       Branch    Op   Remote    Download
 1. [✗] com.visualstudio.code    stable    i    flathub   107,9 MB / 109,6 MB

Error: Extra data missing in detached metadata
error: Failed to install com.visualstudio.code: Extra data missing in detached metadata

    x11                devices                   devel         file access [1]
    dbus access [2]    system dbus access [3]    tags [4]

    [1] host
    [2] com.canonical.AppMenu.Registrar, com.canonical.AppMenu.Registrar.*,
        org.freedesktop.Flatpak, org.freedesktop.Notifications,
        org.freedesktop.secrets
    [3] org.freedesktop.login1
    [4] proprietary


        ID                       Branch    Op   Remote    Download
 1. [✗] com.visualstudio.code    stable    i    flathub   107,9 MB / 109,6 MB

Error: Extra data missing in detached metadata
error: Failed to install com.visualstudio.code: Extra data missing in detached metadata
1 Like

Thanks @fraz0815 , I expected that. As a precaution, I’ve set mesa to ignore, at least until a newer version is released.

I wonder if it’s in relation to the amdgpu firmware updates which philm immediately addressed.

1 Like

Let’s wait and see what @philm thinks about it.