As of Linux 6.15.11, the 6.15 series is now EOL (End Of Life). Please install 6.16 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.
pacman-mirrors version 5.1
Deprecation of --geoip in favor of -tz/--timezone.
This internal change make mirror-list generation use your system’s configured timezone - when applicable - without using an IP location provider.
More privacy…
2025-08-24
Graphical issues on older hardware (Black screen, Flickering) due to mesa 25.2.x update
It seems on older hardware the mesa 25.2.x update created some regressions which may result in black screens or flickering. Some older Nvidia cards with nouveau driver seem to be affected.
You can try to use the 25.1.x series of Mesa via this repo. Simply place it on top of [extra] in your /etc/pacman.conf file and use sudo pacman -Syuu to downgrade.
[mesa-251]
SigLevel = PackageRequired
Server = https://download.manjaro.org/pkgs/mesa
If you have no graphical session available you can access the bootloader by pressing ESC key during boot and select the bootloader entry. Press CTRL+E for edit and search for the words quiet and splash. Delete those and add 3 to the line. Then execute CTRL+x to start your session. You will land in a text console TTY. Login with your user.
Edit the /etc/pacman.conf with nano: sudo nano /etc/pacman.conf. Perform the downgrade and reboot.
2025-07-24
grub update - watch out
Before you reboot - ensure to run install-grub script to sync the efi-stubs and recreate the grub config.
Warning: ksystemstats: local (6.4.0-1) is newer than extra
If you get this warning, run the following command…
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.
After the update KDE refused to let me in: I had Auto Login with Plasma Wayland active. That did not work, the manually entered correct password was not accepted. In the terminal timeshift restore was succesfull.
What went wrong? I am running KDE Plasma 6.4.4. from the unstable channel and kernel 6.12.44-3. Maybe KDE crashed and returned to the login screen?
How can I find out what happened in the terminal if I ran the update again? Thanks. (BTW previous updates in Testing ran OK)
later: I ran the update again. In the terminal with journalctl -b many Qt6 errors turned up. Reverted with Timeshift. sudo pacman -Syu showed a long list of qt6 programs newer than the updates (and that is to be expected). The list of to be updated programs still has many qt6 updates:
Is it possible that these updated qt6 programs caused the problems?
later later: No hints / clues from anybody??
In the log 45 kde programs fail with:
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
and
sep 05 20:11:28 manja sddm-greeter-qt6[877]: Reading from "/usr/share/wayland-sessions/plasma.desktop"
sep 05 20:11:28 manja sddm-greeter-qt6[877]: Message received from daemon: LoginSucceeded
sep 05 20:11:30 manja kwin_wayland_wrapper[963]: /usr/bin/kwin_wayland: symbol lookup error: /usr/bin/kwin_wayland: undefined symbol: _ZN21QPlatformBackingStore8rhiFlushEP7QWindowdRK7QRegionRK6QPointP20QPlatformTextureListb, version Qt_6_PRIVATE_API
sep 05 20:11:30 manja kcminit_startup[967]: qt.qpa.wayland: Loading shell integration failed.
It isn’t clear how you came into the state you are in now.
How did you get this version? Did you switch to the unstable branch? If so, what did you do after switching to the unstable branch? On which branch are you currently?
The logs only show that the state your are in is somehow screwed up, as if you partially downgraded depending libraries while still running the latest kwin looking for the libs it was built against. I don’t have any clue how to accomplish this, though
To fix this you need to sync completely with one branch of your choice.
Thanks for your reply. I switched from testing to unstable to get kde 6.4.4. and then switched back to testing. I did not do anything more than that. After the switch back to testing I have followed 3 (I think) Testing updates without any problems. Until the 2025-09-03 update.
So it seems that process of swithing branches and back is not without risks. I had hoped that a systems maintainer would react (maybe they are out fishing. )
Yes, maybe I should switch back to unstable, sync there and see what happens. Thanks to Timeshift that is (almost) without risks!
This doesn’t make sense. If anything then the updated Qt 6.9.2 libs from
led to rebuilding Plasma 6.4.4. I mean rebuilding was done on unstable but since you were on testing your 6.4.4 wasn’t rebuilt against 6.9.2. That’s all i can imagine. So yes switching back to unstable and syncing should fix it. Moreover, the new 6.4.5 is released in three days and surely almost directly in Arch hence in the unstable branch.
Yep, and that is the risk nobody mentions! Now I understand what happened (or probably happened). Thanks!
btw I checked the timeshift snapshots: the last snapshot (created just before the update) was on 2025-08-29 and then on 2025-09-05. So I missed the Testing updates of 2025-08-31 and 2025-09-02 (I was out fishing!). So I hope that it now makes sense that my system was OK until yesterday.
Only if you don’t fully sync to the branch you are changing to. When you change back to testing from unstable it would be expected to downgrade all packages to testing again. (I know that would be against your interest to get Plasma 6.4.) Skipping the downgrade would work for many adjacent packages but is a bad idea for major system components being part of your DE. So you must decide either to use Plasma 6.4 and then stay sync’d in unstable branch or accept to wait for it and stay in testing branch.
The downgrading after changing branches is applied by:
The wiki does already in the note on the top of the page:
Please refer to System Maintenance Section for important maintenance information.
Since the user is the administrator of the system it is assumed that the user takes responsibility for partial updates as per the warning on that page:
Partial updates are not supported under any circumstances
My advice would be to stay on unstable and when the snap is made to testing with your preferred version switch back to testing and repeat to stable as needed. This way the system stay’s in sync with the correct versions for the branch.
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-09-02
)