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:
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.
- Create a list of custom packages for later reference
pamac list --foreign > ~/alien-pkgs.txt
- Remove all foreign packages
pamac remove $(pamac list --foreign --quiet)
- Remove all orphans and other unneeded packages
pamac remove --orphans --unneeded
- Optional: ensure the keyrings are up-to-date
sudo pacman -Syy manjaro-keyring archlinux-keyring
- Optional: Run a simulated update
pamac update --dry-run
- Looking good? Repeat the above without
--dry-runreboot
- 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.
2026-05-19
2026-05-08
NTFS partitions or usb drives cannot be mounted anymore after update
Concerning NTFS3 and NTFS-3G - #15 by Ben
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 and btrfs - booting problem
The currently shipped version of refind breaks booting on btrfs. Upstream cooks a fix, but until it comes there are several workarounds:
- Downgrade refind before rebooring 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.
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: Welcome to Manjaro Wiki
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. 
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…
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 
and wipe the pacman gnupg folder
sudo pacman -Syy archlinux-keyring manjaro-keyring
Optionally
sudo pacman-key --populate archlinux manjaro
Original suggestion
The problem…
https://www.reddit.com/r/archlinux/comments/1rafluf/pacman_and_keyring_issues/
The solution…
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 — as a graphical package manager
2026-01-04
problems with polkit
After a change in polkit, some users report permission problems. Different solutions are suggested:
- rebooting
- reinstalling polkit (with
sudo pacman -S polkit, since pamac may not work in that case)
- fixing the suid permissions manually with
sudo chmod 4755 /usr/lib/polkit-1/polkit-agent-helper-1
- fixing the file permissions manually
The proper permissions are:
drwxr-xr-x (755) - root:root - Directory
-rwxr-xr-x (755) - root:root - Executables
-rw-r--r-- (644) - root:root - Rules files
so to fix you use
sudo chown -R root:root /usr/lib/polkit-1/
sudo chmod 755 /usr/lib/polkit-1/
sudo chmod 755 /usr/lib/polkit-1/polkitd /usr/lib/polkit-1/polkit-agent-helper-1
sudo chmod 644 /usr/lib/polkit-1/rules.d/*
Alternatively, running the full Manjaro packages update via pacman and rebooting before updating the AUR packages withpamac might circumvent the problem from occurring in the first place.
Some users report success with masking the helper service. Please use this as a temporary or last resort solution if everything else fails as this disables an important component and cannot be officially recommended:
sudo systemctl stop polkit-agent-helper.socket
sudo systemctl mask polkit-agent-helper.socket
Another solution for the Polkit issue is to switch Kernel to version 6.6 or above if all the above does not help.
NVIDIA 590 driver drops Pascal and Maxwell support
With the update to driver version 590, the NVIDIA driver no longer supports Pascal (GTX 10xx) or Maxwell (GTX 9xx) GPUs
Impact: Updating the NVIDIA packages on systems with Pascal or Maxwell cards will fail to load the driver, which may result in a broken graphical environment.
Intervention required: Switch to a legacy driver to maintain support:
Install the official linuxXXX-nvidia-575xx, linuxXXX-nvidia-570xx, or related DKMS packages. You can use nvidia-driver-assistant to figure out which driver would support your hardware best.
pacman-mirrors 5.3
Release Notes: https://gitlab.manjaro.org/applications/pacman-mirrors/-/releases/v5.3
error: pacman-mirrors: signature from “Frede Hundewadt”
The package is not corrupted - but for unknown reasons your system does not have the manjaro-keyring that was updated early October.
2025-12-22
Users with old Nvidia cards should change the driver first
Users with older cards should check if they have the proper drivers installed on their system:
$ sudo pacman -Sy nvidia-driver-assistant
$ nvidia-driver-assistant
Detected GPUs:
GeForce GT 740A - (pci_id 0x1292)
Detected system:
Manjaro Linux
Please copy and paste the following command to install the legacy kernel module flavour:
sudo pacman -S linux618-nvidia-470xx
2025-12-15
NVIDIA 580xx drivers might create issues with desktop environment
- Current 580xx driver seems to be super unstable. Users who face issues are recommended to report to NVIDIA
- For 580.119.02 the current workaround to avoid issues with flickering under XFCE is to disable compositing under Settings → Window Manager Tweaks → Compositor → Enable display compositing. NVIDIA is actively working on fixing this issue
- You may also want to consult the nvidia-open driver public bug tracker
Optional switch to older Nvidia driver
For a list of possible drivers for your hardware run
mhwd -l
If your system was automagically rolled to a supported kernel you may run into conflicts with the meta package(s).
Remove the meta packages
sudo pacman -R linux-nvidia-meta linux-meta
If you are using a desktop system and you are in doubt if you are affected
2025-12-08
Make sure to fully update grub also on MBR/EFI
On some UEFI systems the fallback EFI entry wont get updated. Hence either ignore the grub update completely and do a system reboot or make sure it got properly updated by running install-grub followed by update-grub after the system update and before a reboot to avoid issues like grub_memcpy not found.
For reinstallation the Anh-Linh ISOs are recommended, which can be found in the first post and include this update already.
Dark theming on XFCE for gtk4 apps and flatpaks (again)
The symlinking for the fixing of the dark theme for some flatpaks (which ignore the env variable) and parts of gtk4 apps might not be enough anymore. For example the graphs in gnome-system-monitor stay white.
So after
mkdir -p ~/.config/gtk-4.0/
ln -sf /usr/share/themes/Matcha-dark-sea/gtk-4.0/{assets,gtk.css,gtk-dark.css} ~/.config/gtk-4.0/
also do (it was not supposed to work anymore, but it does)
gsettings set org.gnome.desktop.interface gtk-theme Adwaita-dark
gsettings set org.gnome.desktop.interface color-scheme prefer-dark
After this you might have to go to the Appearence settings and set the theme back to Matcha dark sea to fix the xfce apps (but the gnome apps will stay dark).
mkinitcpio v40 disabled fallback image creation for new installs
mkinitcpio v40, packaging changes and kernel-install - Arch-dev-public - lists.archlinux.org
This is only affects new installs as we can’t change the hook files on existing installs.
To disable fallback image creation on older installed systems
- Change
PRESETS=('default' 'fallback') line to PRESETS=('default') in the respective .preset files in /etc/mkinitcpio.d/.
- Regenerate initramfs -
sudo mkinitcpio -P
- Update boot loader -
sudo update-grub
Warning
Disabling all fallback initramfs generation will deprive you of another option to boot into the system in case a default initramfs fails. Before proceeding, make sure you have a bootable installation medium for rescue purposes on hand.
waydroid >= 1.5.4-3 update may require manual intervention
The waydroid package prior to version 1.5.4-2 (including aur/waydroid) creates Python byte-code files (.pyc) at runtime which were untracked by pacman. This issue has been fixed in 1.5.4-3, where byte-compiling these files is now done during the packaging process.
As a result, the upgrade may conflict with the unowned files created in previous versions. If you encounter errors like the following during the update:
error: failed to commit transaction (conflicting files)
waydroid: /usr/lib/waydroid/tools/pycache/init.cpython-313.pyc exists in filesystem
waydroid: /usr/lib/waydroid/tools/actions/pycache/init.cpython-313.pyc exists in filesystem
waydroid: /usr/lib/waydroid/tools/actions/pycache/app_manager.cpython-313.pyc exists in filesystem
You can safely overwrite these files by running the following command:
pacman -Syu --overwrite /usr/lib/waydroid/tools/\*__pycache__/\*
dovecot >= 2.4 requires manual intervention
The dovecot 2.4 release branch has made breaking changes which result in it being incompatible with any <= 2.3 configuration file.
Thus, the dovecot service will no longer be able to start until the configuration file was migrated, requiring manual intervention.
For guidance on the 2.3-to-2.4 migration, please refer to the following upstream documentation: Upgrading Dovecot CE from 2.3 to 2.4
Furthermore, the dovecot 2.4 branch no longer supports their replication feature, it was removed.
For users relying on the replication feature or who are unable to perform the 2.4 migration right now, we provide alternative packages available in [extra]:
- dovecot23
- pigeonhole23
- dovecot23-fts-elastic
- dovecot23-fts-xapian
The dovecot 2.3 release branch is going to receive critical security fixes from upstream until stated otherwise.
zabbix >= 7.4.1-2 may require manual intervention
Starting with 7.4.1-2, the following Zabbix system user accounts (previously shipped by their related packages) will no longer be used. Instead, all Zabbix components will now rely on a shared zabbix user account (as originally intended by upstream and done by other distributions):
- zabbix-server
- zabbix-proxy
- zabbix-agent (also used by the
zabbix-agent2 package)
- zabbix-web-service
This shared zabbix user account is provided by the newly introduced zabbix-common split package, which is now a dependency for all relevant zabbix-* packages.
The switch to the new user account is handled automatically for the corresponding main configuration files and systemd service units.
However, manual intervention may be required if you created custom files or configurations referencing to and / or being owned by the above deprecated users accounts, for example:
PSK files used for encrypted communication- Custom scripts for metrics collections or report generations
sudoers rules for metrics requiring elevated privileges to be collected- …
Those should therefore be updated to refer to and / or be owned by the new zabbix user account, otherwise some services or user parameters may fail to work properly, or not at all.
Once migrated, you may remove the obsolete user accounts from your system.
Plasma 6.5 will need manual intervention if you are on X11
On Plasma 6.5 the wayland session will be the only one installed when the users does not manually specify kwin-x11.
With the recent split of kwin into kwin-wayland and kwin-x11, users running the old X11 session needs to manually install plasma-x11-session after the system update completed, or they will not be able to login. Currently pacman is not able to figure out your personal setup, and it wouldn’t be ok to install plasma-x11-session for every one using Plasma.
GNOME 49 is here and wayland is the default
With GNOME 49 there is no X11 session anymore. X11 support got disabled. It will get removed with GNOME 50 anyway. You still can use X11 applications via XWayland as usual, however running GNOME under X11 is not possible anymore.
.NET packages may require manual intervention
2025-12-11 - George Rawlinson
The following packages may require manual intervention due to the upgrade from 9.0 to 10.0:
- aspnet-runtime
- aspnet-targeting-pack
- dotnet-runtime
- dotnet-sdk
- dotnet-source-built-artifacts
- dotnet-targeting-pack
pacman may display the following error failed to prepare transaction (could not satisfy dependencies) for the affected packages.
If you are affected by this and require the 9.0 packages, the following commands will update e.g. aspnet-runtime to aspnet-runtime-9.0:
pacman -Syu aspnet-runtime-9.0
pacman -Rs aspnet-runtime
– Arch Linux - News: .NET packages may require manual intervention
Previous stable update threads:
You will need to rebuild any AUR Python packages that install files to site-packages or link to 
