[Testing Update] 2025-05-15 - KDE Gear, KDE Frameworks, Firefox, GStreamer, LibreOffice

Hello community, here we have another set of package updates. Since I’m still recovering from my move back to Europe from Asia, I might be less responsive on the forum. So lets test these packages thoroughly so we can do another stable branch snap.

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: See current promotion

Recent News

Valkey to replace Redis in the [extra] Repository

2025-04-17 - Andrew Crerar

Valkey, a high-performance key/value datastore, will be replacing redis in the [extra] repository. This change is due to Redis modifying its license from BSD-3-Clause to RSALv2 and SSPLv1 on March 20th, 2024.

Arch Linux Package Maintainers intend to support the availability of the redis package for roughly 14 days from the day of this post, to enable a smooth transition to valkey. After the 14 day transition period has ended, the redis package will be moved to the AUR. Also, from this point forward, the redis package will not receive any additional updates and should be considered deprecated until it is removed.

Users are recommended to begin transitioning their use of Redis to Valkey as soon as possible to avoid possible complications after the 14 day transition window closes.

Arch Linux - News: Valkey to replace Redis in the [extra] Repository

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.293
  • linux510 5.10.237
  • linux515 5.15.182
  • linux61 6.1.138
  • linux66 6.6.90
  • linux612 6.12.28
  • linux613 6.13.12 [EOL]
  • linux614 6.14.6
  • linux615 6.15-rc5
  • linux61-rt 6.1.134_rt51
  • linux66-rt 6.6.87_rt54
  • linux612-rt 6.12.16_rt9
  • linux613-rt 6.13_rt5
  • linux614-rt 6.14.0_rt3

Package Changes (Thu May 15 09:37:03 CEST 2025)

  • testing core x86_64: 22 new and 22 removed package(s)
  • testing extra x86_64: 1903 new and 1879 removed package(s)
  • testing multilib x86_64: 15 new and 15 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:


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: 2025-05-15

2025-03-20

System may hang during splash screen when Nvidia 570 drivers are used

A lot of users with older Nvidia cards report system hanging on Plymouth splash screen after installing Nvidia 570 drivers. In the past we had issues with plymouth in general combined with Nvidia drivers. Therefore we didn’t update plymouth in our stable and testing branch.

As a workaround splash could be removed from /etc/default/grub file followed by a update-grub cmd to remove plymouth from starting. Another alternative is to test the newer plymouth and give feedback if that solves the issue:

sudo pacman -U https://mirrors.manjaro.org/repo/pool/overlay/plymouth-24.004.60-12-x86_64.pkg.tar.zst

2025-03-05

[community] repo removed from servers

Similar to Arch we removed our [community] repos from our mirrors and servers. You may want to check your pacnew files or manually remove [community] and [kde-unstable] when used in your /etc/pacman.conf file.

2025-02-16

Update only regular repository packages first, no AUR

Follow the best practice of first updating only regular repository packages, followed separately by AUR packages.

  1. Update regular repository packages first with
    • pamac update --no-aur
      or
    • sudo pacman -Syu
  2. Then, if needed, update AUR packages.

Failure to follow this practice may result in the installation of packages that you may not need, and may cause problems. For further details, see:

Keyboard layout issues / Update issues with fcitx5

If a system had sdl2 installed and AUR updates enabled, fcitx5 might be installed as a make dependency

It is recommended to remove fcitx5 and any other orphan packages following the update

pamac remove --orphans

Update issues with fcitx5

Previous testing threads:

There’s a problem with the KDE Frameworks update for me. Chromium is consistently taking 25 seconds to load, normally instant. I can solve it by running Chromium with:

env XDG_CURRENT_DESKTOP=chromium chromium

journalctl -f give any clues? Chromium launches instantly for me.

Yes, it’s KWallet causing it.

Is it disabled?

You’re right, the update has disabled it, re-enabling does solve the issue. Thanks for your help in further diagnosing it.

Known issue with kwallet and chromium: Please consider applying patch c9a9252d34a6 (KDE bug 504014) (#1) · Issues · Arch Linux / Packaging / Packages / kwallet · GitLab

1 Like

The issue with Kwallet should be fixed with 6.14.0-2.

Not sure about that. It asked me for a password when I started kmail. It normally never does that.

I’ve edited my above reply to link the upstream issue.

It seems what you’re referring to is not related to that issue / fix. Either way, Phil already linked to the Arch packaging issue that links to the same upstream issue.

Can confirm this new issue on manjaro stable with latest kwallet 6.14.0-2.

Now kwallet asks for my password on login, which never was the case before.

Edit: @Yochanan: It also dumped core, this is definitely related to recent updates from yesterday afternoon. The kwallet version distributed 2025-05-14 with all the other latest stable packages didn’t have this specific issue.

?!? Kwallet normaly got only updated in unstable branch for now.

I’ve now removed the forwarded kwallet from the branches. We will push it with a regular branch snap as needed. Users on stable branch should perform a downgrade to the working 6.13.0 version of kwallet via: sudo pacman -Syuu.

1 Like