[Stable Update] 2026-05-27 - Kernels, NVIDIA, Firefox, Thunderbird, Mesa, Blender

Hello Manjaro user community, here we have another set of package updates. We are continuing our development of the upcoming release of ‘Bian-May’ which can be expected end of June, beginning of July. Development speed may be a little slower the upcoming weeks. However, still let us know any issues you may found thus far.

Current Promotions

Recent News

New in Manjaro GNOME!

When choosing an accent color in Settings, the folder colors will now change automatically to match when using the Papirus Dark or Papirus Light icon theme.

To try it out, install gnome-shell-extension-papirus-folders-colorizer from Add/Remove Software, logout / login and enable Papirus Folder Colorizer from Extensions.

Or, if you prefer the command line:

Install:

sudo pacman -Syu gnome-shell-extension-papirus-folders-colorizer

Enable the extension:

 gnome-extensions enable papirus-folders-colorizer@NiffirgkcaJ.github.com

Logout:

gnome-session-quit --logout

Also, when applying accent colors from Layout Switcher settings, it will also set the matching folder color. Requires accent-color-change r172.c761c84-2 or newer.

KDE Plasma users with SDDM can now migrate to Plasma Login Manager

After ensuring plasma-login-manager 6.5.90-1 (or newer) is installed, run the following:

sudo pacman -Syu plasma-login-manager
systemctl disable sddm
systemctl enable plasmalogin
sudo pacman -R sddm-kcm sddm
NVIDIA 590 driver drops Pascal support

With the update to driver version 590, the NVIDIA driver no longer supports Pascal (GTX 10xx) GPUs or older.

Impact: Updating the NVIDIA packages on systems with Pascal, Maxwell, or older cards will fail to load the driver, which may result in a broken graphical environment.

Intervention required for Pascal/older users: Users with GTX 10xx series and older cards must switch to a legacy driver to maintain support:

  • Install the official linuxXXX-nvidia-575xx, linuxXXX-nvidia-570xx, or related DKMS packages.
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

  • Kernels got all updated
    • linux617-rt got removed
    • linux-firmware uses now zst compression
  • Firefox 151.0.1
  • Thunderbird 151.0
  • Fixes to gstreamer and pipewire
  • Blender 5.1.2
  • NVIDIA 580.159.04
  • Vivaldi 8.0
  • Mesa 26.1.1
  • Qt5 5.15.19
  • Updates to Deepin and Python

Install Medias

Bian-May 26.1.0-pre (2026-05-27)

Download XFCE

Full

https://download.manjaro.org/xfce/26.1.0-pre/manjaro-xfce-26.1.0-pre-260527-linux70.iso
https://download.manjaro.org/xfce/26.1.0-pre/manjaro-xfce-26.1.0-pre-260527-linux70.iso.sig
https://download.manjaro.org/xfce/26.1.0-pre/manjaro-xfce-26.1.0-pre-260527-linux70.iso.sha1
https://download.manjaro.org/xfce/26.1.0-pre/manjaro-xfce-26.1.0-pre-260527-linux70.iso.sha256
https://download.manjaro.org/xfce/26.1.0-pre/manjaro-xfce-26.1.0-pre-260527-linux70.iso.torrent
https://download.manjaro.org/xfce/26.1.0-pre/manjaro-xfce-26.1.0-pre-260527-linux70.iso.pkgs

Minimal

https://download.manjaro.org/xfce/26.1.0-pre/manjaro-xfce-26.1.0-pre-minimal-260527-linux70.iso
https://download.manjaro.org/xfce/26.1.0-pre/manjaro-xfce-26.1.0-pre-minimal-260527-linux70.iso.sig
https://download.manjaro.org/xfce/26.1.0-pre/manjaro-xfce-26.1.0-pre-minimal-260527-linux70.iso.sha1
https://download.manjaro.org/xfce/26.1.0-pre/manjaro-xfce-26.1.0-pre-minimal-260527-linux70.iso.sha256
https://download.manjaro.org/xfce/26.1.0-pre/manjaro-xfce-26.1.0-pre-minimal-260527-linux70.iso.torrent
https://download.manjaro.org/xfce/26.1.0-pre/manjaro-xfce-26.1.0-pre-minimal-260527-linux70.iso.pkgs

Minimal (linux618)

https://download.manjaro.org/xfce/26.1.0-pre/manjaro-xfce-26.1.0-pre-minimal-260527-linux618.iso
https://download.manjaro.org/xfce/26.1.0-pre/manjaro-xfce-26.1.0-pre-minimal-260527-linux618.iso.sig
https://download.manjaro.org/xfce/26.1.0-pre/manjaro-xfce-26.1.0-pre-minimal-260527-linux618.iso.sha1
https://download.manjaro.org/xfce/26.1.0-pre/manjaro-xfce-26.1.0-pre-minimal-260527-linux618.iso.sha256
https://download.manjaro.org/xfce/26.1.0-pre/manjaro-xfce-26.1.0-pre-minimal-260527-linux618.iso.torrent
https://download.manjaro.org/xfce/26.1.0-pre/manjaro-xfce-26.1.0-pre-minimal-260527-linux618.iso.pkgs

Minimal (linux612)

https://download.manjaro.org/xfce/26.1.0-pre/manjaro-xfce-26.1.0-pre-minimal-260527-linux612.iso
https://download.manjaro.org/xfce/26.1.0-pre/manjaro-xfce-26.1.0-pre-minimal-260527-linux612.iso.sig
https://download.manjaro.org/xfce/26.1.0-pre/manjaro-xfce-26.1.0-pre-minimal-260527-linux612.iso.sha1
https://download.manjaro.org/xfce/26.1.0-pre/manjaro-xfce-26.1.0-pre-minimal-260527-linux612.iso.sha256
https://download.manjaro.org/xfce/26.1.0-pre/manjaro-xfce-26.1.0-pre-minimal-260527-linux612.iso.torrent
https://download.manjaro.org/xfce/26.1.0-pre/manjaro-xfce-26.1.0-pre-minimal-260527-linux612.iso.pkgs

Download GNOME

Full

https://download.manjaro.org/gnome/26.1.0-pre/manjaro-gnome-26.1.0-pre-260527-linux70.iso
https://download.manjaro.org/gnome/26.1.0-pre/manjaro-gnome-26.1.0-pre-260527-linux70.iso.sig
https://download.manjaro.org/gnome/26.1.0-pre/manjaro-gnome-26.1.0-pre-260527-linux70.iso.sha1
https://download.manjaro.org/gnome/26.1.0-pre/manjaro-gnome-26.1.0-pre-260527-linux70.iso.sha256
https://download.manjaro.org/gnome/26.1.0-pre/manjaro-gnome-26.1.0-pre-260527-linux70.iso.torrent
https://download.manjaro.org/gnome/26.1.0-pre/manjaro-gnome-26.1.0-pre-260527-linux70.iso.pkgs

Minimal

https://download.manjaro.org/gnome/26.1.0-pre/manjaro-gnome-26.1.0-pre-minimal-260527-linux70.iso
https://download.manjaro.org/gnome/26.1.0-pre/manjaro-gnome-26.1.0-pre-minimal-260527-linux70.iso.sig
https://download.manjaro.org/gnome/26.1.0-pre/manjaro-gnome-26.1.0-pre-minimal-260527-linux70.iso.sha1
https://download.manjaro.org/gnome/26.1.0-pre/manjaro-gnome-26.1.0-pre-minimal-260527-linux70.iso.sha256
https://download.manjaro.org/gnome/26.1.0-pre/manjaro-gnome-26.1.0-pre-minimal-260527-linux70.iso.torrent
https://download.manjaro.org/gnome/26.1.0-pre/manjaro-gnome-26.1.0-pre-minimal-260527-linux70.iso.pkgs

Minimal (linux618)

https://download.manjaro.org/gnome/26.1.0-pre/manjaro-gnome-26.1.0-pre-minimal-260527-linux618.iso
https://download.manjaro.org/gnome/26.1.0-pre/manjaro-gnome-26.1.0-pre-minimal-260527-linux618.iso.sig
https://download.manjaro.org/gnome/26.1.0-pre/manjaro-gnome-26.1.0-pre-minimal-260527-linux618.iso.sha1
https://download.manjaro.org/gnome/26.1.0-pre/manjaro-gnome-26.1.0-pre-minimal-260527-linux618.iso.sha256
https://download.manjaro.org/gnome/26.1.0-pre/manjaro-gnome-26.1.0-pre-minimal-260527-linux618.iso.torrent
https://download.manjaro.org/gnome/26.1.0-pre/manjaro-gnome-26.1.0-pre-minimal-260527-linux618.iso.pkgs

Minimal (linux612)

https://download.manjaro.org/gnome/26.1.0-pre/manjaro-gnome-26.1.0-pre-minimal-260527-linux612.iso
https://download.manjaro.org/gnome/26.1.0-pre/manjaro-gnome-26.1.0-pre-minimal-260527-linux612.iso.sig
https://download.manjaro.org/gnome/26.1.0-pre/manjaro-gnome-26.1.0-pre-minimal-260527-linux612.iso.sha1
https://download.manjaro.org/gnome/26.1.0-pre/manjaro-gnome-26.1.0-pre-minimal-260527-linux612.iso.sha256
https://download.manjaro.org/gnome/26.1.0-pre/manjaro-gnome-26.1.0-pre-minimal-260527-linux612.iso.torrent
https://download.manjaro.org/gnome/26.1.0-pre/manjaro-gnome-26.1.0-pre-minimal-260527-linux612.iso.pkgs

Download KDE

Full

https://download.manjaro.org/kde/26.1.0-pre/manjaro-kde-26.1.0-pre-260527-linux70.iso
https://download.manjaro.org/kde/26.1.0-pre/manjaro-kde-26.1.0-pre-260527-linux70.iso.sig
https://download.manjaro.org/kde/26.1.0-pre/manjaro-kde-26.1.0-pre-260527-linux70.iso.sha1
https://download.manjaro.org/kde/26.1.0-pre/manjaro-kde-26.1.0-pre-260527-linux70.iso.sha256
https://download.manjaro.org/kde/26.1.0-pre/manjaro-kde-26.1.0-pre-260527-linux70.iso.torrent
https://download.manjaro.org/kde/26.1.0-pre/manjaro-kde-26.1.0-pre-260527-linux70.iso.pkgs

Minimal

https://download.manjaro.org/kde/26.1.0-pre/manjaro-kde-26.1.0-pre-minimal-260527-linux70.iso
https://download.manjaro.org/kde/26.1.0-pre/manjaro-kde-26.1.0-pre-minimal-260527-linux70.iso.sig
https://download.manjaro.org/kde/26.1.0-pre/manjaro-kde-26.1.0-pre-minimal-260527-linux70.iso.sha1
https://download.manjaro.org/kde/26.1.0-pre/manjaro-kde-26.1.0-pre-minimal-260527-linux70.iso.sha256
https://download.manjaro.org/kde/26.1.0-pre/manjaro-kde-26.1.0-pre-minimal-260527-linux70.iso.torrent
https://download.manjaro.org/kde/26.1.0-pre/manjaro-kde-26.1.0-pre-minimal-260527-linux70.iso.pkgs

Minimal (linux618)

https://download.manjaro.org/kde/26.1.0-pre/manjaro-kde-26.1.0-pre-minimal-260527-linux618.iso
https://download.manjaro.org/kde/26.1.0-pre/manjaro-kde-26.1.0-pre-minimal-260527-linux618.iso.sig
https://download.manjaro.org/kde/26.1.0-pre/manjaro-kde-26.1.0-pre-minimal-260527-linux618.iso.sha1
https://download.manjaro.org/kde/26.1.0-pre/manjaro-kde-26.1.0-pre-minimal-260527-linux618.iso.sha256
https://download.manjaro.org/kde/26.1.0-pre/manjaro-kde-26.1.0-pre-minimal-260527-linux618.iso.torrent
https://download.manjaro.org/kde/26.1.0-pre/manjaro-kde-26.1.0-pre-minimal-260527-linux618.iso.pkgs

Minimal (linux612)

https://download.manjaro.org/kde/26.1.0-pre/manjaro-kde-26.1.0-pre-minimal-260527-linux612.iso
https://download.manjaro.org/kde/26.1.0-pre/manjaro-kde-26.1.0-pre-minimal-260527-linux612.iso.sig
https://download.manjaro.org/kde/26.1.0-pre/manjaro-kde-26.1.0-pre-minimal-260527-linux612.iso.sha1
https://download.manjaro.org/kde/26.1.0-pre/manjaro-kde-26.1.0-pre-minimal-260527-linux612.iso.sha256
https://download.manjaro.org/kde/26.1.0-pre/manjaro-kde-26.1.0-pre-minimal-260527-linux612.iso.torrent
https://download.manjaro.org/kde/26.1.0-pre/manjaro-kde-26.1.0-pre-minimal-260527-linux612.iso.pkgs

Additional Info

Python 3.14 info

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

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

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

Rebuild them all at once:*

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

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 Support > 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

  • linux61 6.1.174
  • linux66 6.6.141
  • linux612 6.12.91
  • linux618 6.18.33
  • linux70 7.0.10
  • linux71 7.1.0-rc5
  • linux61-rt 6.1.167_rt62
  • linux66-rt 6.6.135_rt74
  • linux612-rt 6.12.89_rt18

Package Changes (5/26/26 07:53 CEST)

  • stable core x86_64: 46 new and 48 removed package(s)
  • stable extra x86_64: 2177 new and 2353 removed package(s)
  • stable multilib x86_64: 31 new and 31 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:


8 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:

:warning: Prepare the update beforehand

Preparation steps

From [INFO] Stable branch - BIG update BEST practice

If it has been a long time since your last update, you may want to refresh your pacman-keyring before running the actual update.

  1. Create a list of custom packages for later reference
    pamac list --foreign > ~/alien-pkgs.txt
    
  2. Remove all foreign packages
    pamac remove $(pamac list --foreign --quiet)
    
  3. Remove all orphans and other unneeded packages
    pamac remove --orphans --unneeded
    
  4. Optional: ensure the keyrings are up-to-date
    sudo pacman -Syy manjaro-keyring archlinux-keyring
    
  5. Optional: Run a simulated update
    pamac update --dry-run
    
  6. Looking good? Repeat the above without --dry-run
    reboot
    
  7. Consult the list of packages created in the first step and rebuild only those you really need

Important Note: Users of Plasma and GNOME may lose their X11 session support. Checkout our guides below before restarting your systems!

Important Note: Users of Pascal, Maxwell, or older cards will fail to load the NVIDIA driver when they were using 580xx series earlier, because the 590xx doesn’t support the older hardware anymore. Only Turing series and newer are still supported.

:arrow_right: 2026-05-27

Attention users with encryption - read before updating!

Several months ago upstream switched the mkinitcpio hooks from udev to systemd. There was a pacnew file which in theory everybody has seen and merged (right? Shame on you, yes you, who forgot :sweat_smile:). Until now it was kind of optional, because the udev hooks will not stop working overnight. Well, with this update it seems the new systemd hooks are forced upon at least on some users without them noticing. It should’t happen but in some cases it looks like it happened. The result is a system that throws a cryptic error about device not found on boot and nonbooting.
You either have to restore the udev hooks, or adapt the kernel boot line for the systemd.

The easiest is to not reboot after update (otherwise you will have to chroot). Check the hooks and cmdline:

grep HOOKS /etc/mkinitcpio.conf
cat /proc/cmdline

The right combination is either similar to the old one with udev

HOOKS=(base UDEV autodetect microcode kms modconf block keyboard keymap consolefont plymouth encrypt filesystems)

AND the following syntax on the boot line

cryptdevice=UUID=device

OR
the new systemd hooks, similar to

HOOKS=(SYSTEMD autodetect microcode modconf kms keyboard sd-vconsole block sd-encrypt filesystems fsck)

AND

rd.luks.uuid=XXXXXXXX-XXXX-XXXX

ANY MIX BETWEEN THE TWO WILL NOT BOOT!

The currently reported situation is usually systemd hook + cryptdevice= boot line.

If that happend, you have to change either one of those two places. Preferably go to systemd and rd.luks.uuid. The boot line is changed in /etc/default/grub
After that you need to sudo update-grub

Now you can reboot.

Some reading (pretty much obligatory)
mkinitcpio - ArchWiki
dm-crypt/System configuration - ArchWiki

Note: the hooks above are an example! Do not blindly replace your hooks with the examples above. Also, the capitalization of some hooks is to put a focus here, in reality all hooks are with small letters.

Mesa problems on some Intel GPUs (lines on screen, fuzzy fonts)

Intel ix-2xxx CPUs (Core i 2nd Generation aka Sandy Bridge, from 2011 and all earlier CPUs)

Either wait with the update, or downgrade mesa.
For some chome browsers a workaround can be to disable the hardware acceleration.

Alternative workarounds: manually upgrade to the patched version from unstable branch

sudo pacman -U https://mirrors2.manjaro.org/unstable/extra/x86_64/mesa-1:26.1.2-1-x86_64.pkg.tar.zst

Or install (replace) mesa with mesa-amber for those old gpus. Note that this is the only workaround which doesn’t put you in an unsupported state!

2026-05-19

Yet another vulnerability - local privilege escalation

TLDR: And yet another one
Until patches arrive (should be soon), a mitigation:

sudo sh -c "printf 'kernel.yama.ptrace_scope=2' > /etc/sysctl.d/10-ptrace.conf"
More vulnerabilities - Pintheft, Dirtydecrypt

More vulnerabilities were discovered. Until patches hit your mirror and update, the mitigation is as always to block the modules:

rmmod rds_tcp rds
sudo su -
printf 'install rds /bin/false\ninstall rds_tcp /bin/false\n' > /etc/modprobe.d/pintheft.conf
exit

Note that a good Samaritan created a script, proactively blocking all modules not currently loaded from automatic loading. Which mitigates all current and future vulnerabilities connected with modules. If you are interested - here is the script:
GitHub - jnuyens/modulejail: Proactively shrink a Linux host's kernel-module attack surface by blacklisting every module not currently in use. · GitHub
Please read the description and way of function carefully. If you decide to use that script, check if you have any of the vulnerable modules loaded first:

lsmod | grep -E "esp4|esp6|rxrpc|rds|rds_tcp|algif_aead"

If it returns nothing, you are all good, you can run modulejail with profile desktop.
You do not need to remove other blocking .conf files if you already installed something (unless you want the logging feature).

You might also be interested in the following tutorial which should proactively help:

[HowTo] modulejail

Kernels 5x removed - change kernel before updating!

Although kernel series 5x are still maintained upstream, they are pretty old. To simplify maintenance, Manjaro drops support for those kernels. Note that this change is still not updated in the graphical Manjaro-settings-manager (but mhwd-kernel shows the correct list). Please, if you are still running a 5x kernel, install a newer LTS one first, preferably the latest 6.18 before attempting to update. Then reboot and after that you can update. If linux-latest is blocking the update, remove it too.

2026-05-08

NTFS partitions or usb drives cannot be mounted anymore after update

The explanation:
Concerning NTFS3 and NTFS-3G - #15 by Ben

Note that forcing the system to use the old ntfs-3g driver to mount the drive/partition, although the dirty bit is set, means you will be mounting a potentially damaged filesystem. It is your decision and the responsibility for potential data loss is yours.
The only recommended solution is to check the filesystem from windows. If you don’t have windows anymore, you can get one designed for such repairs free and legal here:

https://www.hirensbootcd.org/

DIRTY FRAG VULNERABILITY (also read if scared from Fragnesia)

[ALERT] Dirty Frag (CVE-2026-43284, CVE-2026-43500) - Root Privilege Vulnerability

Note that the newly discovered vulnerability Fragnesia is still not patched, it is however in the same modules as Dirty frag and the described mitigation works for it too. Just apply the mitigation and you will be ok.

refind - booting problem

The currently shipped version of refind breaks booting on both ext4 and btrfs. Upstream cooks a fix, but until it comes there are several workarounds:

  • Downgrade refind before rebooting or from chroot with manjaro-downgrade
  • Make a backup of the refind_x64.efi file on the ESP partition and restore it after the update before rebooting or from chroot
  • Search for the hook that updates the .efi on package update and remove it
  • Remove the package refind before updating the system which will also remove the hook, but will leave the efi file on the ESP (not tested)

In any case be sure to have live usb at hand.

P.S. refind is alternative boot loader. It is not part of the default installation. If you don’t know what it is (you didn’t install it yourself) - you don’t have it and this doesn’t concern you.

2026-05-02

Issues with updating Kernels due to Nvidia drivers

We know that some of our users still use either 570xx or 575xx drivers from Nvidia. Both of these drivers are unsupported since several months: Current graphics driver releases - Linux - NVIDIA Developer Forums

The current legacy driver 580xx is still supporting older graphic cards by Nvidia, as in Maxwell, Pascal, and Volta GPUs. 470xx is unsupported by Nvidia, however the community is still patching that driver for newer kernels so GKxxx “Kepler” GPUs still work. Same goes for the 390xx driver series, which has the support of GF1xx “Fermi” GPUs.

With linux619+ there is no support for 570xx and 575xx. Our kernel-team had no time to look into this issue further, as backporting patches takes a lot of effort. Since we dropped driver support for these series in recent mhwd-db updates, you may still want to stay on linux618 kernel series, if you still need those drivers. To check if newer drivers support your hardware, please use 26.1x install medias and choose proprietary drivers on boot selection. No changes are performed on your installed system. It is a save environment to test new drivers before changing stuff on your OS.

It would be good to remove installed drivers by mhwd before using it to reinstall supported drivers for your system: Configure Graphics Cards - Manjaro

Also look for known issues within drivers at the Nvidia developer forum:

2026-05-01

COPY FAIL VULNERABILITY

On 29 April 2026, a high local privilege escalation vulnerability in the Linux kernel, tracked as CVE-2026-31431 and named “Copy Fail”, was publicly disclosed. The vulnerability affects Manjaro Linux since 2017. A public proof-of-concept exploit has been released.

We have patched most of our kernels and released them to our testing and unstable branches:

  • patched kernels are: 5.10.254+, 5.15.204+, 6.1.170+, 6.6.137+, 6.12.85+, 6.18.22+, 6.19.12+, 7.0-rc7+
  • affected kernels are: 6.1.167_rt62, 6.6.133_rt73, 6.12.79_rt17, 6.17.5_rt7 and lower

Temporary Mitigation for non-patched kernels/systems

Disable the algif_aead kernel module persistently on all affected systems until a patched kernel is available:

echo "install algif_aead /bin/false" > /etc/modprobe.d/disable-algif.conf
    rmmod algif_aead 2>/dev/null || true

More Information: CERT-EU - High Vulnerability in the Linux Kernel ("Copy Fail")

2026-03-23

pamac-manager gui (Add/Remove Programs) does not start or starts very slow

For now, disable flatpak support (you can just browse flathub.org and install and update from terminal)
sudo nano /etc/pamac.conf
scroll to the end and put # before EnableFlatpak
press ctrl+q , y to save and exit

`plasma-applet-window-buttons` is broken

The plasma-applet-window-buttons package included in this update is version 0.14.0-3, which looks for /usr/lib/libPlasma.so.7, but this library does not exist — the version of the library included in this Stable Update is /usr/lib/libPlasma.so.6.5.6.

The solution is to downgrade plasma-applet-window-buttons to version 0.14.0-2. You do this by way of manjaro-downgrade. :backhand_index_pointing_down:

sudo manjaro-downgrade plasma-applet-window-buttons

Update: In the meantime, the faulty package has been replaced in the repository by the working one already, but if you had updated your system and you have version 0.14.0-3 while you did not downgrade the package yet, run… :backhand_index_pointing_down:

sudo pacman -Syuu

… just once. It will downgrade the faulty package back to the working one.

2026-02-23

Possible signature validity issues with packages taken over from Arch

Do this before updating!

Edited by @linux-aarhus 2026-02-26T06:35:00Z
Before you jump to the big :hammer_and_wrench: and wipe the pacman gnupg folder

sudo pacman -Syy archlinux-keyring manjaro-keyring

Optionally

sudo pacman-key --populate archlinux manjaro
Original suggestion

The problem… :backhand_index_pointing_down:

https://www.reddit.com/r/archlinux/comments/1rafluf/pacman_and_keyring_issues/

The solution… :backhand_index_pointing_down:

 sudo rm -rf /etc/pacman.d/gnupg
 sudo pacman-key --init && sudo pacman-key --populate archlinux manjaro && sudo pacman -Syu
Unreliability of the `pamac` package manager

Rationale

There recently appears to be a high incidence of pamac crashing in the middle of a system update, be it only in the form of the pamac-manager crashing with the update process continuing in the background, or in the form of a complete crash of the pamac infrastructure, leading to a non-bootable system.

Advice

Until the Manjaro Team has managed to correct this issue, we would advise our users…

  • to either (install and) use octopi — see the screenshot below :backhand_index_pointing_down: — as a graphical package manager

  • …or to use the tried-and-trusted pacman from the command line for updating the repository packages, and to use the pamac command-line utility and flatpak command-line utility afterwards for updating the AUR packages and the FlatPaks, respectively, as follows… :backhand_index_pointing_down:
    sudo pacman-mirrors -f && sudo pacman -Syu && pamac update --aur --devel && flatpak update
    

Previous stable update threads:

Stable Updates

Qt5 apps (like smplayer) stopped working after QT5 packages upgrade, with following errors at launch:

Cannot mix incompatible Qt library (5.15.18) with this library (5.15.19)

I’m guessing that it has to be recompiled.

Edit:
I’m sorry - after further investigation it seems to be a problem with qt5gtk2 aur package (which needs to be recompiled). When forcing different platform theme (ie. env QT_QPA_PLATFORMTHEME=qt5ct smplayer) everything works.

1 Like

There is a strange title in the KWrite (kate) application in the Russian interface.
Everything is fine when opening the app:

but if you type some text, the title will change slightly:

This behavior is not observed in the English interface (it remains Untitled).

1 Like

Two years ago I asked the smplayer developer when he would switch the player to qt6, he replied that soon, another year had passed, he asked him again when, he replied that he had already done it, but so far in the test version for windows, another year has passed, but nothing has changed. Very sad, the player is actually very good, but stuck in the past. :frowning:

1 Like

Link is dead. Correct link is: Configure Graphics Cards - Manjaro

13 posts were split to a new topic: Issues with module blocks following 2026-05-27 update

Update went fine. So far no issues. Had linux-firmware-meta as a foreign package now so removed it and installed linux-firmware package. All seems to work with just minor testing. Nothing was left orphaned with doing the swap from linux-firmware-meta to linux-firmware.

All is in the picture, can’t read with Chromium - plasma6 update 2026-05-27.
On Firefox I can read
Rest seems ok so far, but system seems sluggish.

More convincing, may be this on Chromium:

I’ve got same issue on Gnome. All Chromium-based programs display glitched up fonts. I don’t even know what should I downgrade: mesa, compositors or Intel drivers.

I’ve tried different kernels, but older ones behave exactly the same.

Other thing is wallpaper. If I set it up a new, it seems fine.

But after I click program overview on favourites bar and get back to default desktop view, wallpaper is glitched with some strange raster.

imgur.c om/a/63WS6fv

I’ve tried my other Manjaro installation on USB stick maintained for other laptop, but once I booted it on my machine it behaves exactly the same.

Definetely, something in this update doesn’t like my low spec hardware.

1 Like

I haven’t had any issues myself. Perhaps try rebuilding your local font cache:

fc-cache -f

Which in particular?
Are you referring to programs that depend on electron?

Didn’t help, but I guess that can inspire some ficticious alien-made alphabet.

Different versions of Ungoogled Chromium, Thorium, RPG Maker games. There are glitches in Kodi GUI

imgur.c om/a/hY4T8IA

It’s system wide, gnome-shell is affected as well, albeit not so heavily. If I right-click to paste something in terminal, font display is also glitched.

imgur.c om/fAT3mIE

there was some issue with downloading linux618 kernel packages, but update went smooth on both computers
I can not find anything in logs from download period, but seems all works ok
uname -r => 6.18.33-1-MANJARO

1 Like

No Chromium font problem on XFCE, but well on KDE.

I confirm about possible Electon & Wayland, as Code OSS is also gibberish, even executing before launching code:

fc-cache -f

1 Like

xfce, x11 - no problems with fonts

1 Like

A post was split to a new topic: Can’t boot after stable update 2026-05-27

Firefox and Thunderbird appear two times with different versions.

This is rather sad, especially since 5.10 is a CIP kernel that will still get security updates till January 31.
When did supporting old hardware become an annoyance rather than a point of pride?

1 Like