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-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: v5.3 · Applications / pacman-mirrors · GitLab
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
2025-10-06
Apache - hardening override configuration
/etc/systemd/system/httpd.service.d/hardening.conf
Change the values to suit your use case
To disable a hardening change a value to either off or false and restart the service
[Service]
# These are the settings from service file `httpd.service`, providing some extra
# hardening and security. If this conflicts with your use case uncomment below and
# configure as required.
#NoNewPrivileges=on
#PrivateDevices=on
#PrivateTmp=on
#ProtectHome=on
Also see → Apache HTTP Server - ArchWiki
2025-08-30
Libreoffice 25.8.0.4 crashes on opening files
In case you experience immediate crash of Libreoffice Writer ver 25.8.0.4 (or other office apps and versions too?) on opening every already saved .docx file (or other formats too?), the workaround may be to switch from the Microsoft Tabbed toolbar to the standard old look. View -> User interface... until the bug is fixed.
This might or might not be fixed in 25.8.1 since there are several similar bugs in the bugtracker, one is fixed and one not until ver. 26. I guess some input from test or unstable branch users will help here.
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-08-11
Wrong default action removing phonon-qt6-vlc
looking for conflicting packages...
:: phonon-qt6-vlc-0.12.0-5 and phonon-qt5-vlc-0.12.0-3 are in conflict. Remove phonon-qt5-vlc? [y/N] y
The default is No, which will leave the old and deprecated package. This is obviously not what we want, so answer Y here.
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.
Additional information can be found here.
Grub - Error: grub_is_using_legacy_shim_lock_protocol not found
The issue Error: grub_is_using_legacy_shim_lock_protocol not found is caused when the EFI firmware is pointing to the fallback /EFI/boot/bootx64.efi which is not updated automatically.
When it happens the efi-stub /EFI/Manjaro/grubx64.efi must be copied to /EFI/boot/ as bootx64.efi and this is what the install-grub script is designed for: Install-grub: a new way to keep your EFI/MBR in-sync with grub package
Booting from a live ISO running install-grub in chroot I may result in
WARNING: EFI directory not found! Grub couldn't be installed.
You can verified your mounts for $esp and check the /sys/firmware/efi/efivars.
efibootmgr can be used to create an efi entry pointing to the efi-stub in /EFI/Manjaro/grubx64.efi and manually generated grub.cfg using grub-mkconfig.
Example run of install-grub
[manjaro user]# install-grub
[D] GRUB 2 EFI-x64 found
[D] Checking EFI-Directory: /boot/efi
[D] Found EFI Bootloader: /boot/efi/EFI/Manjaro/grubx64.efi
[D] Found EFI Fallback: /boot/efi/EFI/boot/bootx64.efi
Install command will be: grub-install --no-nvram --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=Manjaro --recheck --force
Do you want to proceed? (yes/no) yes
ok, we will proceed
Grub will be installed on: EFI
Installing for x86_64-efi platform.
Installation finished. No error reported.
Update Grub Menu
Do you want to proceed? (yes/no) yes
ok, we will proceed
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-6.15-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-6.15-x86_64.img
Found initrd fallback image: /boot/initramfs-6.15-x86_64-fallback.img
Found linux image: /boot/vmlinuz-6.12-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-6.12-x86_64.img
Found initrd fallback image: /boot/initramfs-6.12-x86_64-fallback.img
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme1n1.
Found memtest86+ EFI image: /boot/memtest86+/memtest.efi
/usr/bin/grub-probe: warning: unknown device type nvme1n1.
done
Warning: GRUB bootloader at /boot/efi/EFI/Manjaro was updated,
but it seems like you are not using it by default.
Please check your EFI boot priorities!
Example
[manjaro user]# efibootmgr
BootCurrent: 000A
Timeout: 1 seconds
BootOrder: 000A,0001,0003,0008,0009,0002,0004,0000,0007,0006,0005
Boot0000 Lenovo Cloud PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/MAC(047bcba9026a,0)/IPv4(0.0.0.0,0,DHCP,0.0.0.0,0.0.0.0,0.0.0.0)/Uri(https://download.lenovo.com/pccbbs/cdeploy/efi/boot.efi)
Boot0001* UEFI OS HD(1,GPT,519fa53d-c862-4efb-948b-eee1a5d9c584,0x1000,0x96000)/\EFI\BOOT\BOOTX64.EFI0000424f
Boot0002 UEFI: HTTP IPv4 Marvell AQtion 10Gbit Network Adapter PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/MAC(047bcba9026a,0)/IPv4(0.0.0.0,0,DHCP,0.0.0.0,0.0.0.0,0.0.0.0)/Uri()0000424f
Boot0003* UEFI: PXE IPv4 Marvell AQtion 10Gbit Network Adapter PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/MAC(047bcba9026a,0)/IPv4(0.0.0.0,0,DHCP,0.0.0.0,0.0.0.0,0.0.0.0)0000424f
Boot0004 UEFI: HTTP IPv6 Marvell AQtion 10Gbit Network Adapter PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/MAC(047bcba9026a,0)/IPv6([::],0,Static,[::],[::],64)/Uri()0000424f
Boot0005* Generic Usb Device VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0006* CD/DVD Device VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0007 Win VDI Boot PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/MAC(047bcba9026a,0)/IPv4(0.0.0.0,0,DHCP,0.0.0.0,0.0.0.0,0.0.0.0)/Uri(https://download.lenovo.com/pccbbs/cdeploy/vdiboot/efi/vdi.efi)
Boot0008* UEFI: PXE IPv6 Marvell AQtion 10Gbit Network Adapter PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/MAC(047bcba9026a,0)/IPv6([::],0,Static,[::],[::],64)0000424f
Boot0009* UEFI: KingstonDataTraveler 3.0PMAP, Partition 2 PciRoot(0x0)/Pci(0x3,0x1)/Pci(0x0,0x0)/Pci(0x8,0x0)/Pci(0x0,0x1)/USB(7,0)/HD(2,GPT,9bea21dc-4f71-6934-996a-cdea67030e7b,0x6f6ffd8,0x10000)0000424f
Boot000A* Manjaro Linux HD(1,GPT,519fa53d-c862-4efb-948b-eee1a5d9c584,0x1000,0x96000)/\EFI\MANJARO\GRUBX64.EFI
Set boot order (example)
[manjaro user]# efibootmgr --bootorder 000A,0001,0000
BootCurrent: 000A
Timeout: 1 seconds
BootOrder: 000A,0001,0000
Boot0000 Lenovo Cloud PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/MAC(047bcba9026a,0)/IPv4(0.0.0.0,0,DHCP,0.0.0.0,0.0.0.0,0.0.0.0)/Uri(https://download.lenovo.com/pccbbs/cdeploy/efi/boot.efi)
Boot0001* UEFI OS HD(1,GPT,519fa53d-c862-4efb-948b-eee1a5d9c584,0x1000,0x96000)/\EFI\BOOT\BOOTX64.EFI0000424f
Boot0002 UEFI: HTTP IPv4 Marvell AQtion 10Gbit Network Adapter PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/MAC(047bcba9026a,0)/IPv4(0.0.0.0,0,DHCP,0.0.0.0,0.0.0.0,0.0.0.0)/Uri()0000424f
Boot0003* UEFI: PXE IPv4 Marvell AQtion 10Gbit Network Adapter PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/MAC(047bcba9026a,0)/IPv4(0.0.0.0,0,DHCP,0.0.0.0,0.0.0.0,0.0.0.0)0000424f
Boot0004 UEFI: HTTP IPv6 Marvell AQtion 10Gbit Network Adapter PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/MAC(047bcba9026a,0)/IPv6([::],0,Static,[::],[::],64)/Uri()0000424f
Boot0005* Generic Usb Device VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0006* CD/DVD Device VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0007 Win VDI Boot PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/MAC(047bcba9026a,0)/IPv4(0.0.0.0,0,DHCP,0.0.0.0,0.0.0.0,0.0.0.0)/Uri(https://download.lenovo.com/pccbbs/cdeploy/vdiboot/efi/vdi.efi)
Boot0008* UEFI: PXE IPv6 Marvell AQtion 10Gbit Network Adapter PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/MAC(047bcba9026a,0)/IPv6([::],0,Static,[::],[::],64)0000424f
Boot0009* UEFI: KingstonDataTraveler 3.0PMAP, Partition 2 PciRoot(0x0)/Pci(0x3,0x1)/Pci(0x0,0x0)/Pci(0x8,0x0)/Pci(0x0,0x1)/USB(7,0)/HD(2,GPT,9bea21dc-4f71-6934-996a-cdea67030e7b,0x6f6ffd8,0x10000)0000424f
Boot000A* Manjaro Linux HD(1,GPT,519fa53d-c862-4efb-948b-eee1a5d9c584,0x1000,0x96000)/\EFI\MANJARO\GRUBX64.EFI
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… 
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
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
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.
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/
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
Previous stable update threads:
