Proprietary nvidia drivers cause "conflicting files" error

When installing proprietary drivers using their install script, it overwrites some package files. Consequently whenever I perform a system update I get the following error:

error: failed to commit transaction (conflicting files)
lib32-nvidia-450xx-utils: /usr/lib32/libEGL_nvidia.so.450.80.02 exists in filesystem
lib32-nvidia-450xx-utils: /usr/lib32/libGLESv1_CM_nvidia.so.450.80.02 exists in filesystem
lib32-nvidia-450xx-utils: /usr/lib32/libGLESv2_nvidia.so.450.80.02 exists in filesystem
lib32-nvidia-450xx-utils: /usr/lib32/libGLX_nvidia.so.450.80.02 exists in filesystem
lib32-nvidia-450xx-utils: /usr/lib32/libcuda.so.450.80.02 exists in filesystem
lib32-nvidia-450xx-utils: /usr/lib32/libnvcuvid.so.450.80.02 exists in filesystem
lib32-nvidia-450xx-utils: /usr/lib32/libnvidia-eglcore.so.450.80.02 exists in filesystem
lib32-nvidia-450xx-utils: /usr/lib32/libnvidia-encode.so.450.80.02 exists in filesystem
lib32-nvidia-450xx-utils: /usr/lib32/libnvidia-fbc.so.450.80.02 exists in filesystem
lib32-nvidia-450xx-utils: /usr/lib32/libnvidia-glcore.so.450.80.02 exists in filesystem
lib32-nvidia-450xx-utils: /usr/lib32/libnvidia-glsi.so.450.80.02 exists in filesystem
lib32-nvidia-450xx-utils: /usr/lib32/libnvidia-glvkspirv.so.450.80.02 exists in filesystem
lib32-nvidia-450xx-utils: /usr/lib32/libnvidia-ifr.so.450.80.02 exists in filesystem
lib32-nvidia-450xx-utils: /usr/lib32/libnvidia-ml.so.450.80.02 exists in filesystem
lib32-nvidia-450xx-utils: /usr/lib32/libnvidia-opticalflow.so.450.80.02 exists in filesystem
lib32-nvidia-450xx-utils: /usr/lib32/libnvidia-ptxjitcompiler.so.450.80.02 exists in filesystem
lib32-nvidia-450xx-utils: /usr/lib32/libnvidia-tls.so.450.80.02 exists in filesystem
lib32-nvidia-450xx-utils: /usr/lib32/vdpau/libvdpau_nvidia.so.450.80.02 exists in filesystem
opencl-nvidia-450xx: /usr/lib/libnvidia-compiler.so.450.80.02 exists in filesystem
opencl-nvidia-450xx: /usr/lib/libnvidia-opencl.so.450.80.02 exists in filesystem

Now moving and backing up these files allows the system update to proceed, but after rebooting LigthDM fails to start. The only way I found to fix that issue is by reinstalling the proprietary drivers, but then the next time I want to perform a system update I get the same conflict.

My pacman logs: Pastebin.com - Potentially offensive content ahead!

Output of pacman -Qs nvidia:

local/cuda-10.1 10.1.243-1
    NVIDIA's GPU programming toolkit
local/lib32-libvdpau 1.4-1
    Nvidia VDPAU library
local/lib32-nvidia-450xx-utils 450.80.02-1
    NVIDIA drivers utilities (32-bit)
local/libvdpau 1.4-1
    Nvidia VDPAU library
local/mhwd-nvidia-340xx 340.108-1
    MHWD module-ids for nvidia 340.108
local/mhwd-nvidia-390xx 390.132-1
    MHWD module-ids for nvidia 390.132
local/mhwd-nvidia-418xx 418.113-1
    MHWD module-ids for nvidia-418xx 418.113
local/mhwd-nvidia-430xx 430.64-1.0
    MHWD module-ids for nvidia-430xx 430.64
local/mhwd-nvidia-435xx 435.21-1.0
    MHWD module-ids for nvidia 435.21

I asked the same question on the Arch forums, where I was directed here.

Welcome to the forum! :slight_smile:

You’re not supposed to do that. Manjaro has mhwd for installing anything to do with the hardware.

I would recommend rolling back your installation by way of your backup and then using mhwd to install the required proprietary Nvidia drivers.

:arrow_down:

Configure NVIDIA (non-free) settings and load them on Startup - Manjaro

1 Like

Lesson learnt - don’t use proprietary install scripts on Manjaro (or any Arch based distro for that matter).

If you are sure you don’t make a mess you can use --overwrite '*' with pacman - this will make your Manjaro install even more unsupported.

2 Likes