[Stable Update] 2025-08-11 - Kernels, Mesa, KDE Frameworks, Systemd

Hello community, here we have another set of package updates. We are also happy to tell you about our latest Gaming Notebook from Slimbook.

Slimbook MANJARO III Specs

CPU: AMD Ryzen 7 8845HS
Graphics: Nvidia RTX 4070 8GB
Display: 15.3" WQHD 2560*1600p 120 Hz
Keyboard: RGB
Material: aluminum
Ports: 3x USB 3.2, 1x USB-C 3.2, HDMI 2.1, MiniDP
Connectivity: RJ45, Wifi 6, Bluetooth 5.2
RAM memory: up to 96GB DDR5
Storage: 2x SSD NVMe PCIe 4.0 M.2 up to 8TB
Keyboard: multiple languages
Operating System: Manjaro Gaming Plasma 6

More details

Current Promotions

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

Notable Package Updates

  • Most Kernels got updated
    • linux-firmware 20250808
    • this includes an initial release of 6.16 and first candidate of 6.17 kernel series
    • toolchain updates with gcc security fixes and glibc 2.42
  • Some Updates to GNOME
  • Blender 4.5.1
  • Mesa 25.1.7
  • Ollama 0.10.1
  • QEMU 10.0.3
  • Firefox 141.0.3 & 142.0b9
  • Tuxedo Drivers 4.14.4
  • Slimbook Service 0.8.5
  • GStreamer 1.26.5
  • KDE Frameworks 6.17.0
  • Systemd 257.8
  • Heroic Games Launcher 2.18.1
  • InputPlumber 0.62.0
  • OpenGamepadUI 0.41.0
  • Updates to Python and Haskell

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.296
  • linux510 5.10.240
  • linux515 5.15.189
  • linux61 6.1.147
  • linux66 6.6.101
  • linux612 6.12.41
  • linux615 6.15.9
  • linux616 6.16.0
  • linux617 6.17.0-rc1
  • linux61-rt 6.1.146_rt53
  • linux66-rt 6.6.99_rt58
  • linux612-rt 6.12.39_rt11
  • linux615-rt 6.15.0_rt2

Package Changes (Thu Aug 7 19:55:16 CEST 2025)

  • stable core x86_64: 99 new and 98 removed package(s)
  • stable extra x86_64: 3259 new and 3320 removed package(s)
  • stable multilib x86_64: 46 new and 45 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:


6 Likes

Known issues and solutions

This is a wiki post; please edit as necessary.
Please, consider subscribing to the Stable 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-08-11

Potential issues with toolchain update due to glibc 2.42

Whenever the toolchain gets updated, your system more or less switches to new versions of low level basic system package, which can soft-brick your system when not updated properly.

A more static release model of the likes of Debian or Ubuntu, only update the toolchain with major release updates. With Arch and Manjaro, this happens more often without a major release announcement.

Kernels and other system relevant parts need to been updated when that happens. glibc is used by more than 4955 packages.

To add a safety net to your system, you can install pacman-static:

sudo pacman -U https://mirrors.manjaro.org/repo/pool/overlay/pacman-static-7.0.0.r6.gc685ae6-8-x86_64.pkg.tar.xz

… and maintain the system as usual via sudo pacman-static -Syu, even when the regular pacman might trow glibc errors: With update I see glibc errors

phonon-qt5 and phonon-qt5-gstreamer packages got dropped to AUR

Those packages used to be in the repo, but they were dropped to the AUR because they’re still qt5-based and no longer required by any of the official packages — with the exception perhaps that they might be a dependency of something installed from the AUR.

2025-07-12

SDDM may crash with Nvidia drivers

In some case Nvidia drivers need the following workaround in /etc/environment to launch SDDM properly:

MESA_LOADER_DRIVER_OVERRIDE=zink
Warning: ksystemstats: local (6.4.0-1) is newer than extra

If you get this warning, run the following command in order to downgrade the installed package with the higher version to the version currently in the repository… :point_down:

 sudo pacman -Syuu
VLC does not play (certain) videos

For this update, the VLC packages were split up, and not all codecs may be installed on your system. You can install the additional codecs individually, or install the vlc-plugins-all meta-package, which will pull in all available plugins.

 sudo pacman -S vlc-plugins-all
linux-firmware-meta replaces linux-fimware

With the linux-firmware-meta package, all of the firmware is now split up into individual packages, which are all installed as dependencies of linux-firmware-meta.

If you wish to uninstall the firmware packages that you don’t need — e.g. linux-firmware-nvidia — including the meta package itself, then be sure to mark the firmware packages you wish to keep as explicitly installed, or else pacman will regard them as orphans, which would be dangerous when cleaning out your real orphans.

 sudo pacman -D --asexplicit <name-of-package(s)>

2025-06-23

Breaking changes to wine and wine-staging

Transition to the new WoW64 wine and wine-staging

2025-06-16

We are transitioning the wine and wine-staging package to a pure wow64 build. This change removes the dependency on the multilib repository for wine and wine-staging.

The main reason for this is to align with upstream Wine development, which simplifies packaging and the dependency chain.

Potential Issues:

  • OpenGL Performance: A known limitation of the new WoW64 mode is reduced performance for 32-bit applications that use OpenGL directly
  • Breaking Changes: Existing 32-bit prefixes needs to be recreated

If you are facing issues with 32 bit prefixes, please recreate these and reinstall the application.

Possible breaking changes to pacman-mirrors

:warning: With pacman-mirrors 5.0-1, the global mirrors.json data file has been moved from /usr/share/pacman-mirrors to /var/lib/pacman-mirrors.
:warning: This move introduces a possible breaking change if you have custom scripts relying on the mirrors data file. If this is the case, then simply create a symlink from the new location under /var/lib back to the old location, i.e. /usr/share.

ln -s /var/lib/pacman-mirrors /usr/share/

:information_source: The moving of the file is the only change and has been made to make it possible for users to have their /usr-tree on a separate read-only partition or btrfs subvolume.

xkeyboard-config 2.45 issue with symlinks

You may fail to upgrade from 2.44 to 2.45 due to some changes to symlinks. A discussion about it can be found here: Cannot update xkeyboard-config to 2.45 / Pacman & Package Upgrade Issues / Arch Linux Forums

The solution is to update the AUR packages depending on xkeyboard-config or move the files to the new folder /usr/share/xkeyboard-config-2.

More information about it here: xkeyboard-config 2.45 issue with symlinks (#1) · Issues · Arch Linux / Packaging / Packages / xkeyboard-config · GitLab

avahi-discover python script may fail to discover services

avahi-discover fails when attempting to write the discovered services to a sqlite database in /usr/lib/avahi due to lack of permissions.

The issue can be reproduced using a pristine Arch LInux system - it appears from the issues at GitHub - avahi/avahi: Avahi - Service Discovery for Linux using mDNS/DNS-SD -- compatible with Bonjour the issue is known - but not fixed.

Use of dbm causes problems with Python 3.13 · Issue #670 · avahi/avahi · GitHub
Fix issue with dbm.sqlite3 on readonly directories by mickael9 · Pull Request #698 · avahi/avahi · GitHub

Even though the issue has been known to upstream since december 2024, the behaviour on unstable branch has changed fairly recently - perhaps 4 weeks.

Temporary workaround
The workaround it is not optimal - but if you rely on avahi discover service - it will work

Move /usr/lib/avahi to /var/lib and symlink it back to /usr

sudo mv /usr/lib/avahi /var/lib/ && sudo ln -s /var/lib/avahi /usr/lib/

Change the ownership of the folder /var/lib/avahi including files

sudo chown root:avahi /var/lib/avahi -R

Change permissions to allow avahi group to write into the folder including the existing db file

sudo chmod g+w /var/lib/avahi -R

Finally add yourself to the avahi group

sudo gpasswd -a $USER avahi

Logoff and login to activate the new group.

Topic in German section
Avahi zeroconf browser zeigt nichts an

2025-04-12

Grub gained security fixes. Updating it may be risky

When Manjaro updates the grub package the actual installed binaries in master boot record (MBR) or UEFI won’t get updated. This is however needed to apply recent security fixes added to grub. Therefore we created Install-grub: a new way to keep your EFI/MBR in-sync with grub package to make it easier.

A more manual approach can be found here: [root tip] [How To] Primer on handling a grub package update

We also have it documented in our wiki on how to manually install grub when a disaster happens: GRUB/Restore the GRUB Bootloader - Manjaro. So if you are not experienced with it you can either ignore that extra step or have an install media at hand to recover as needed.

See also on how to create a boot media to install Manjaro fresh: Burn an ISO File - Manjaro. Those who want to get install medias having this update included may look for 25.0 ISOs when released or here: Releases · manjaro/release-review · GitHub

Remember, update-grub only updates the boot menu and install-grub is a script helper to install or reinstall grub on most case automatically via grub-install. All grub installations can be with a risk when not done properly as the user will change low level system parts and can easily break their systems.

Note: most likely grub was initially installed by an installer and therefore the user doesn’t know how grub got installed. So if you are unsure simply skip a reinstallation of grub.

2025-03-24

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

No sound from PulseAudio after PipeWire update

If PulseAudio audio playback is suspended after PipeWire update, unload module-suspend-on-idle

pactl unload-module module-suspend-on-idle

If that works, create a custom default.pa configuration for PulseAudio in home folder

cp /etc/pulse/default.pa ~/.config/pulse/default.pa

and comment out module-suspend-on-idle in custom configuration

sed -i '/load-module module-suspend-on-idle/s/^/#/' ~/.config/pulse/default.pa

2025-03-05

[community] repository 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-05-02
community has been re-created as an empty repository so that systems where package manager configuration /etc/pacman.conf has not been updated can still be used to update packages from other repositories

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

2025-02-04

Kernel 4,19 and 6.11 are EOL, 6.11 and 4.19 got removed from repos

Kernel 6.11 and 4.19 got marked [EOL] on kernel.org
Linux 6.11 and 4.19 have been removed from the repositories.
Please ensure your system use a supported kernel mhwd-kernel -l

PostgreSQL users should consider to prepare the change of major version 16→17

More info here and here

Update libpamac before installing the 2025-02-04 updates

Run sudo pacman -Sy libpamac in a terminal to make sure pamac-manager doesn’t crash during the update.

XFCE 4.20 may blank display after 5 mins idle time regardless of power management settings

Most likely this: Disable screen blanking

Call xfce4-screensaver-preferences and disable the screensaver.
xfce4-screensaver - Usage [Xfce Docs]

Previous stable update threads:

1 Like

Installed the core packages without any problems. When it finished, said a reboot was needed to complete the installation. I clicked OK and suddenly another window popped up asking me to install the phonon-qt5 and phonon-qt5-gstreamer packages from the AUR and that need to import the authors’ GPG keys. Can be legit, but seems a bit strange…

Those packages used to be in the repo, but they were dropped to the AUR because they’re still qt5-based and no longer required by any of the official packages — with the exception perhaps that they might be a dependency of something you’ve installed from the AUR.

4 Likes

A post was split to a new topic: With update I see glibc errors