As of Linux 6.13.12, the 6.13 series is now EOL (End Of Life). Please install 6.14 stable and/or 6.12 LTS (Long Term Support).
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.
Manjaro, like many other open-source projects, relies on the generosity of its community through donations and corporate sponsorships to support its growth and development. These donations are essential in covering the various expenses incurred in the operations of the project such as server costs, software development tools, infrastructure expenses, training, flying people to events or conferences and the salaries of key developers. With the help of these donations, Manjaro is able to secure the necessary financial stability that allows the project to continuously improve and remain active. If you love Manjaro, consider to donate!
As you might have seen some of our team were able to attend FOSDEM 2023 and the conference proved to be incredibly productive for us. See our blog post for more.
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
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
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.
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:
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.
Update regular repository packages first with
pamac update --no-aur or
sudo pacman -Syu
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:
hmmâŚwould it make sense to sort the list of supported kernels exclusively by version number?
I had just started whining before I realized that kernel 6.15 is included.
Although, now I know what to look out forâŚthe rt-kernels are at the end
Not sure if this matters or not, but after journalctl -rg nvidia is executed to view nvidia journal entries, the text in parentheses for a couple of entries changed from manjarolinux-builder@echo manjarolinux pre-update to root@ post-update :
Pre-update
Jun 02 21:35:03 REDACTED kernel: nvidia-modeset: Loading NVIDIA UNIX Open Kernel Mode Setting Driver for x86_64 570.153.02 Release Build (manjarolinux-builder@echo manjarolinux)
Jun 02 21:35:03 REDACTED kernel: NVRM: loading NVIDIA UNIX Open Kernel Module for x86_64 570.153.02 Release Build (manjarolinux-builder@echo manjarolinux)
Post-update
Jun 02 21:43:57 REDACTED kernel: nvidia-modeset: Loading NVIDIA UNIX Open Kernel Mode Setting Driver for x86_64 575.57.08 Release Build (root@)
Jun 02 21:43:57 REDACTED kernel: NVRM: loading NVIDIA UNIX Open Kernel Module for x86_64 575.57.08 Release Build (root@)
In any case, thanks for releasing the 575 nvidia drivers to testing
Been seeing something really odd since upgrading my Nvidia (1070) + Wayland + GNOME system⌠when I launch certain applications, the window just never appears. Their icon shows up in my dock (dash to dock), but a window canât be raised and seemingly doesnât exist.
Applications Iâve seen this with so far: Discord (from the repos) and Satisfactory Mod Manager (an AppImage, using GTK).
This does not seem to happen when I launch the same applications in XFCE + X11.
Running Discord in native Wayland mode with discord --enable-features=UseOzonePlatform --ozone-platform=wayland also seems to work around it.
I had some issues with the mesa update, some wine applications that used to run smoothly using the wayland driver started to look jittery, or crash on startup (Doom3 BFG Edition for example).
So I started to downgrate kernel, nvidia driver, wine and finally landed on mesa as the cause.
I tied to further pinpoint it by trying intermediate version from the upstream arch archive. Turns out it worked fine with mesa 1:25.1.1-1 but not with 1:25.1.1-2 - which really only differs by one single change, turing the bool zink from true to false.
So, from what I managed to understand it seems before zink must have been used, and now no longer is and that causes the issues. But I must say that I donât really understand exactly how all those things relate, even after lots of reading.
Anyway according to the arch wiki the zink driver can be forced to be used again by setting those environment variables:
A few more findings on this âwindow not showing upâ issue Iâm seeing:
Signal desktop client launches and the main window appears, but opening any other window with it - the Preferences window or the About window - doesnât show up. As with the other applications, it appears in the dock and in the alt-tab and gnome shell overviews, but canât be selected or interacted with.
Given how Discord always pops up an updater window before launching its main window, the behavior seems to be (for affected applications) âany window an application creates after the first one, gets this broken invisible un-interactable statusâ.
Also affected is the simple image viewer utility, âfehâ. The applications exhibiting this issue use a variety of toolkits, so this isnât just electron, or GTK, or what-have-you.
Can anyone else with an Nvidia + Wayland + Gnome system try launching Discord or Signal and see if this is happening for them?
Question: Isnât Thunderbird already at version 139.0 on stable? (here it says that the version is 138.0.2 which is an older version)
Suggestion: for Pipewire, version 1.4.5 was just released with a small but critical update which fixes a regression caused in 1.4.4 that breaks audio in many games. Please can you consider updating the package to 1.4.5?
If you installed Thunderbird from the AUR or as flatpak, the versions might differ.
Pipewire v1:1.4.4-1 is in both Unstable and Testing; v1:1.4.2-1 is in Stable. For v1.4.5, we would at least have to wait for it to reach Stable on Arch, and then pass through Unstable and Testing on Manjaro.
I am also seeing this behavior. It doesnât happen all the time. Applications on my side are Signal, Spotify and Jetbrains Toolbox. With Spotify I can still start playing music with the âplayâ key on my keyboard though. My system has an AMD Video Card. So it seems itâs not video card manufacturer related.
Hmm⌠In that case I think itâs better to just skip pipewire 1.4.4 and wait for 1.4.5 to be released since it fixes the game audio regression thingy.
You will need to rebuild any AUR Python packages that install files to site-packages or link to 
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.
2025-06-01
