[Testing Update] 2025-01-04 - Kernels, Plasma 6.2.5, LibreOffice, Qemu

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

Additional Info

Python 3.13 info

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

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

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

Rebuild them all at once:*

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

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

 checkrebuild

* It’s recommended to clean your build cache first with pamac clean --build-files

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

  • linux54 5.4.288
  • linux510 5.10.232
  • linux515 5.15.175
  • linux61 6.1.123
  • linux66 6.6.69
  • linux612 6.12.8
  • linux613 6.13-rc5
  • linux61-rt 6.1.120_rt47
  • linux66-rt 6.6.65_rt47

Package Changes (Sat Jan 4 09:50:04 CET 2025)

  • testing core x86_64: 12 new and 11 removed package(s)
  • testing extra x86_64: 1745 new and 1717 removed package(s)
  • testing multilib x86_64: 15 new and 15 removed package(s)

Overlay Changes

  • testing core x86_64: 14 new and 16 removed package(s)
  • testing extra x86_64: 108 new and 180 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:


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!

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

:arrow_right: 2025-01-04

2024-12-11

Kernel 6.11 and 4.19 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:

1 Like

Update :white_check_mark:
Installed easyeffects 7.2.1-2 from arch repo, easyeffects 7.2.1-1 was faulty.

1 Like

Fixed via another sync from Arch:

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

-------------------------------------------------------------------------------
                             PACKAGE           2024-12-23           2025-01-04
-------------------------------------------------------------------------------
                             libedit       20240517_3.1-1       20240808_3.1-1
                             libssh2             1.11.0-1             1.11.1-1


:: Different sync package(s) in repository extra x86_64

-------------------------------------------------------------------------------
                             PACKAGE           2024-12-23           2025-01-04
-------------------------------------------------------------------------------
                                 apt             2.9.21-1             2.9.21-2
                            apt-docs             2.9.21-1             2.9.21-2
                             asunder              3.0.1-2                    -
                         easyeffects              7.2.1-1              7.2.1-2
                                gegl             0.4.50-3             0.4.52-1
                             glances            4.3.0.7-1            4.3.0.8-1
                            libixion             0.19.0-5             0.19.0-6
                              ollama              0.5.4-1              0.5.4-2
                         ollama-cuda              0.5.4-1              0.5.4-2
                         ollama-docs              0.5.4-1              0.5.4-2
                         ollama-rocm              0.5.4-1              0.5.4-2
                    python-starlette             0.45.1-1             0.45.2-1
                            tenacity              1.3.3-4              1.3.4-2
                                 znc              1.9.1-4              1.9.1-5
1 Like

@cges30901, I think qemu-common has been upgraded too early by Archlinux (there is the same issue). I personally would downgrade it for the moment to 9.1.2-1.

qemu-system-cris still depends on qemu-common=9.1.2-1.

P.S.: Don’t use -Rdd here, it could break your system. Use -Rsn instead

… a good reason not to delete it! qemu-emulators-full is also already 9.2.0-1 in testing branch.

after update and rebooting it started with X11, have to manually revert to Wayland