When i download Updates with Software i get the message Sorry, something went wrong with the following content:
Error running transaction: file /opt/amdgpu/lib64/libdrm.so.2.4.0 from install of libdrm-amdgpu-1:2.4.106-1290604.el8.x86_64 conflicts with file from package amdgpu-pro-shims-1.1.1-1.fc35.x86_64
file /opt/amdgpu/lib64/libdrm_amdgpu.so.1.0.0 from install of libdrm-amdgpu-1:2.4.106-1290604.el8.x86_64 conflicts with file from package amdgpu-pro-shims-1.1.1-1.fc35.x86_64
file /opt/amdgpu/lib64/libdrm_radeon.so.1.0.1 from install of libdrm-amdgpu-1:2.4.106-1290604.el8.x86_64 conflicts with file from package amdgpu-pro-shims-1.1.1-1.fc35.x86_64
file /opt/amdgpu/lib64/libkms.so.1.0.0 from install of libdrm-amdgpu-1:2.4.106-1290604.el8.x86_64 conflicts with file from package amdgpu-pro-shims-1.1.1-1.fc35.x86_64
file /opt/amdgpu/share/doc/libdrm-amdgpu/README.rst from install of libdrm-amdgpu-1:2.4.106-1290604.el8.x86_64 conflicts with file from package amdgpu-pro-shims-1.1.1-1.fc35.x86_64
file /lib/udev/rules.d/91-amdgpu-pro-modeset.rules from install of libdrm-amdgpu-1:2.4.106-1290604.el8.x86_64 conflicts with file from package amdgpu-pro-shims-1.1.1-1.fc35.x86_64
It seems that you are mixing packages from enterprise linux here, which one shouldn’t generally use on Fedora. Could you tell us more about where you installed these from?
Could you also please share the output of this command with us?
fpaste --sysinfo-short --printonly
(Please sudo dnf install fpaste if it isn’t already installed on your system).
The command dnf list installed <package name> should show which repo that package was installed from.
The packages that are conflicting seem to be
libdrm-amdgpu which appears to be for el8
and
amdgpu-pro-shims which appears to be a package for fedora 35.
To me it seems that there is an attempt to install one that is conflicting with the one already installed. Either do not install the one that is complaining or remove the one that is already installed first.
This can also occur when a package content is changed and now causes the conflict during an update.
Conflicts often happen when using 3rd party repos for similar packages.