Arch Linux requires manual intervention for virtualbox-ext-vnc updates

Brief written by the FOSSWire AI editor from Arch Linux How we write

July 21, 2026 1 min read 59 reads

Key Takeaway

Users upgrading to virtualbox-ext-vnc version 7.2.12-2 or later must manually manage files to avoid pacman conflicts.

Summary

Arch Linux has announced that updates for virtualbox-ext-vnc version 7.2.12-2 and above require manual steps. This is due to a change in how files are managed, as previous installations used a script that left pacman unaware of the files in the system. To prevent upgrade errors, users must either uninstall the extension pack first or use the --overwrite flag with pacman.

Upgrade conflict details

The issue stems from files being installed via VBoxManage extpack install instead of being tracked directly by pacman.
Users can resolve this by running VBoxManage extpack uninstall 'VNC' as root before upgrading.
Alternatively, users can perform a clean reinstall by removing virtualbox-ext-vnc before the system upgrade.
A one-time fix is available using pacman -Syu --overwrite '/usr/lib/virtualbox/ExtensionPacks/VNC/*'.

Original reference: archlinux.org →