Fedora 40 installation issues due change of zlib to zlib-ng

I know this might be little off topic and might be not resolved here but Davinci resolve is working fine and can be installed on Fedora 39 since the distri still uses zlib, but issue comes on new Fedora version 40 where zlib is not anymore available on distro since system wide change has been done to use zlib-ng-compat libraries. I was testing DaVinci Resolve on my Fedora 40 to see if I can get it working nicely and if so I would buy Pro and since I don't have Pro yet only support I could get for now is the forums here.

Possible workarounds is to use distrobox method where I use centOS or Fedora 39 where DaVinci works but that is not as easy or not so ling term and I'm suspicious how good GPU passthrough is on those so I would prefer Native installation

Well this just saved me a few more hours of searching reasons why things weren't working
Thanks

i got Davinci working on Fedora 40 workstation i found good guide and it always had issues for depencies before and after installation i iwll post here how i got it working easy and upgrading to Fedora 40 didint broke anything

Code: Select all

sudo dnf install libxcrypt-compat libcurl libcurl-devel mesa-libGLU

These commands will help resolve compatibility issues and prepare your system for the installation process.
After successfully installing DaVinci Resolve, there are a few additional steps to optimize compatibility. Follow these commands:

Code: Select all

cd /opt/resolve/libs
sudo mkdir disabled-libraries
sudo mv libglib* disabled-libraries
sudo mv libgio* disabled-libraries
sudo mv libgmodule* disabled-libraries

These commands will further enhance the compatibility of DaVinci Resolve with your Fedora 39 system, ensuring a smooth editing experience. Whether you're a beginner or an experienced user, our detailed instructions and tips will help you unleash the full potential of DaVinci Resolve on Fedora 39. Watch now and start creating stunning videos with ease!

Fedora 40. libxcrypt-compat libcurl libcurl-devel mesa-libGLU installed. But:
Missing or outdated system packages detected.
Please install the following missing packages:
zlib

i got Davinci working on Fedora 40 workstation i found good guide and it always had issues for depencies before and after installation i iwll post here how i got it working easy and upgrading to Fedora 40 didint broke anything

Code: Select all

sudo dnf install libxcrypt-compat libcurl libcurl-devel mesa-libGLU

These commands will help resolve compatibility issues and prepare your system for the installation process.
After successfully installing DaVinci Resolve, there are a few additional steps to optimize compatibility. Follow these commands:

Code: Select all

cd /opt/resolve/libs
sudo mkdir disabled-libraries
sudo mv libglib* disabled-libraries
sudo mv libgio* disabled-libraries
sudo mv libgmodule* disabled-libraries

These commands will further enhance the compatibility of DaVinci Resolve with your Fedora 39 system, ensuring a smooth editing experience. Whether you're a beginner or an experienced user, our detailed instructions and tips will help you unleash the full potential of DaVinci Resolve on Fedora 39. Watch now and start creating stunning videos with ease!

This indicates that you already have resolve installed (from an upgrade)? The resolve installer halts at the zlib issue on a fresh fedora 40 install, can`t get passed it..

Hi! A can install Davinchi resolve 19 beta on Fedora 40.
Use: sudo SKIP_PACKAGE_CHECK=1 ./DaVinci_Resolve_19.0b1_Linux.run

Hi,

Just in case it helps work around the zlib issue: on Fedora at least, the installer apparently egrep's the output of rpm, so aliasing rpm to a script that would replace zlib-ng with zlib and running the installer from the command line might work:

Code: Select all

$ cat foo.sh
#!/bin/sh
PACKAGES=$(rpm $@ | sed s/zlib-ng/zlib/)
echo "${PACKAGES}"
exit 0

$ alias rpm=./foo.sh
$ ./DaVinciInstaller # sorry, forgot the actual file name

Another option -- that worked for me -- is to move egrep out of the way by renaming it for the duration of the installation. The installer will then ignore the check altogether (including the check for other libraries, so this is by no means the preferred way).

After that, you'll still have to move the libs around like previously. This merely addresses the installer not running because of the switch to zlib-ng.

Hope this helps.

i got Davinci working on Fedora 40 workstation i found good guide and it always had issues for depencies before and after installation i iwll post here how i got it working easy and upgrading to Fedora 40 didint broke anything

Code: Select all

sudo dnf install libxcrypt-compat libcurl libcurl-devel mesa-libGLU

These commands will help resolve compatibility issues and prepare your system for the installation process.
After successfully installing DaVinci Resolve, there are a few additional steps to optimize compatibility. Follow these commands:

Code: Select all

cd /opt/resolve/libs
sudo mkdir disabled-libraries
sudo mv libglib* disabled-libraries
sudo mv libgio* disabled-libraries
sudo mv libgmodule* disabled-libraries

These commands will further enhance the compatibility of DaVinci Resolve with your Fedora 39 system, ensuring a smooth editing experience. Whether you're a beginner or an experienced user, our detailed instructions and tips will help you unleash the full potential of DaVinci Resolve on Fedora 39. Watch now and start creating stunning videos with ease!

This indicates that you already have resolve installed (from an upgrade)? The resolve installer halts at the zlib issue on a fresh fedora 40 install, can`t get passed it..

yes best option for me was to install F39 do all this to verify DaVinci is running on it then i just did Distro upgrade and everything was still working because the zlib issue if you run on Fresh F40 installation. on that i found best way to go around is creating distrobox and install DaVinci on there

i actually tested fresh F40 Workstation installation with this method and it is still working all pre installation depencies working libcurl might give fedora errorr

Code: Select all

Last metadata expiration check: 0:14:21 ago on Fri 03 May 2024 07:52:04 PM +07.
Error:
 Problem: problem with installed package libcurl-minimal-8.6.0-8.fc40.i686
  - package libcurl-minimal-8.6.0-8.fc40.i686 from @System conflicts with libcurl(x86-32) provided by libcurl-8.6.0-7.fc40.i686 from fedora
  - package libcurl-minimal-8.6.0-7.fc40.i686 from fedora conflicts with libcurl(x86-32) provided by libcurl-8.6.0-7.fc40.i686 from fedora
  - package libcurl-minimal-8.6.0-8.fc40.i686 from updates conflicts with libcurl(x86-32) provided by libcurl-8.6.0-7.fc40.i686 from fedora
  - conflicting requests
  - package libcurl-minimal-8.6.0-8.fc40.i686 from @System conflicts with libcurl(x86-32) provided by libcurl-8.6.0-8.fc40.i686 from updates
  - package libcurl-minimal-8.6.0-7.fc40.i686 from fedora conflicts with libcurl(x86-32) provided by libcurl-8.6.0-8.fc40.i686 from updates
  - package libcurl-minimal-8.6.0-8.fc40.i686 from updates conflicts with libcurl(x86-32) provided by libcurl-8.6.0-8.fc40.i686 from updates
  - problem with installed package libcurl-minimal-8.6.0-8.fc40.x86_64
  - package libcurl-minimal-8.6.0-8.fc40.x86_64 from @System conflicts with libcurl(x86-64) provided by libcurl-8.6.0-7.fc40.x86_64 from fedora
  - package libcurl-minimal-8.6.0-7.fc40.x86_64 from fedora conflicts with libcurl(x86-64) provided by libcurl-8.6.0-7.fc40.x86_64 from fedora
  - package libcurl-minimal-8.6.0-8.fc40.x86_64 from updates conflicts with libcurl(x86-64) provided by libcurl-8.6.0-7.fc40.x86_64 from fedora
  - package libcurl-minimal-8.6.0-8.fc40.x86_64 from @System conflicts with libcurl(x86-64) provided by libcurl-8.6.0-8.fc40.x86_64 from updates
  - package libcurl-minimal-8.6.0-7.fc40.x86_64 from fedora conflicts with libcurl(x86-64) provided by libcurl-8.6.0-8.fc40.x86_64 from updates
  - package libcurl-minimal-8.6.0-8.fc40.x86_64 from updates conflicts with libcurl(x86-64) provided by libcurl-8.6.0-8.fc40.x86_64 from updates
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages)

so skip that install rest and after those done just use

Code: Select all

sudo SKIP_PACKAGE_CHECK=1 ./DaVinci.ResolveXYZ

after installation is done create the folder and move the libs there on the post and it works and run as nothing

So I just installed Fedora KDE 40 and followed the steps to install all the dependencies and then SKIP_PACKAGE... and then move the libraries. Resolve installed successfully and then successfully ran and opened a new project. HOWEVER, when I try to add clips, I get an error (see screenshot).

Additionally, I work off our org's NAS (I have a 10gb connection to it), but Resolve seems to not be able to access network shares at all. Any help on that? But especially on the GPU error.

This workaround does get Resolve installed. But the resulting installation still has issue with NVIDIA CUDA drivers. All drivers and repositories loaded successfully without errors. And installing Resolve from the command line, though clunky, also completed without issues. Resolve does launch and my GPU is recognized, but the interface flickers horribly when moving or hovering the pointer. It's so bad that it effectively renders the install unusable.

This is the process I used:

NVIDIA Drivers

Load Repos
sudo dnf install https://download1.rpmfusion.org/free/fe ... ease-$(rpm -E %fedora).noarch.rpm
sudo dnf install https://download1.rpmfusion.org/nonfree ... ease-$(rpm -E %fedora).noarch.rpm

Load NVIDIA Drivers
sudo dnf install akmod-nvidia

Load CUDA Drivers
sudo dnf install xorg-x11-drv-nvidia-cuda


Divinci Resolve

Install From Konsol
sudo SKIP_PACKAGE_CHECK=1 ./DaVinci_Resolve_[VERSION_NUMBER_Linux.run

Install Libraries
sudo dnf install libxcrypt-compat libcurl libcurl-devel mesa-libGLU

Disable Incompatible Libraries
cd /opt/resolve/libs
sudo mkdir disabled-libraries
sudo mv libglib* disabled-libraries
sudo mv libgio* disabled-libraries
sudo mv libgmodule* disabled-libraries

So I tried Distrobox as a solution. But, after installing and configuring several distros including multple versions of Fedora, Debian, Ubuntu, CentOS (the only distro officially supported by BlackMagic) Rocky and even a custom distro made specifically for Distrobox called Davincibox which included a handy bash install script that even exported Davinci Resolve as an app into my Applications Menu. The closest I was able to get to a running install was with the latter but I get the dreaded 'Unable to Intitialize GPU' when Resolve is launched. The weird thing about this last attempt was that if I selected the 'Update Configuration' option, my NVIDIA GeForce GTX 1070 is listed and selected. But Resolve can't use it. WTH?

I feel like I've tried everything at this point; used the --nvidia switch when creating the containers, loaded the nvidia-container-toolkit on the host, tried using the Container Device Interface (CDI) switche as an environment variable. But nothing has worked. I'm at my wits end. I'm not sure Resolve is worth this effort since the BETA I use doesn't even support mpg anymore and there are other alternatives that will suite my needs.

I've done so many searches, read so many posts of users having success with other GPUs like AMD and Intel. But I have yet to find anyone who has gotten a GeForce working in Fedora 40 host or any container.

Sorry, I should have clarified, I'm running a 7900x and an Rx 6650xt. Opencl seems to be installed correctly and both the igpu and the 6650xt are detected. At first launch the igpu was selected by DR, but even after manually selecting the 6650xt I still get the same error. I recall on Windows one time having trouble in Resolve because I had used a USB DisplayLink device once and for some reason DR couldn't just ignore it and use the discreet gpu. Had to uninstall it in Device Manager before Resolve would work correctly again. I wonder if there is a way to disable the igpu in Fedora in case Resolve is having some kind of conflict?

Sorry, I should have clarified, I'm running a 7900x and an Rx 6650xt. Opencl seems to be installed correctly and both the igpu and the 6650xt are detected. At first launch the igpu was selected by DR, but even after manually selecting the 6650xt I still get the same error. I recall on Windows one time having trouble in Resolve because I had used a USB DisplayLink device once and for some reason DR couldn't just ignore it and use the discreet gpu. Had to uninstall it in Device Manager before Resolve would work correctly again. I wonder if there is a way to disable the igpu in Fedora in case Resolve is having some kind of conflict?

I'm having the exact same issue, I'm using Nobara 40, based en Fedora 40, and i have an amd gpu, Davinci Resolve doesn't work on my distro, i can't switch to x11 because it has graphic glitches, and i don't know what to do.
Do you already solve your problem with Davinci?

Sorry, I should have clarified, I'm running a 7900x and an Rx 6650xt. Opencl seems to be installed correctly and both the igpu and the 6650xt are detected. At first launch the igpu was selected by DR, but even after manually selecting the 6650xt I still get the same error. I recall on Windows one time having trouble in Resolve because I had used a USB DisplayLink device once and for some reason DR couldn't just ignore it and use the discreet gpu. Had to uninstall it in Device Manager before Resolve would work correctly again. I wonder if there is a way to disable the igpu in Fedora in case Resolve is having some kind of conflict?

I'm having the exact same issue, I'm using Nobara 40, based en Fedora 40, and i have an amd gpu, Davinci Resolve doesn't work on my distro, i can't switch to x11 because it has graphic glitches, and i don't know what to do.
Do you already solve your problem with Davinci?

I just registered for this post, I hope it's not too late
I was able to make it work on Fedora 40 under Wayland by forcing it to run under XWayland, like so:

Code: Select all

env -u WAYLAND_DISPLAY env XDG_SESSION_TYPE=x11 /opt/resolve/bin/resolve

I hope this helps!

Hi,

Actually this did not work, however given a good idea.
Doing a strace it looks like the DaVinci installer use full path when checking rpm: /usr/bin/rpm
So the steps:
1) sudo su -
2) mv /usr/bin/rpm /usr/bin/rpm_tmp
3) Create the file bellow as rpm:
vi /usr/bin/rpm
Then add these lines and also make sure the rpm will be rpm_tmp in the 2nd line:

Code: Select all

#!/bin/sh
PACKAGES=$(rpm_tmp $@ | sed s/zlib-ng/zlib/)
echo "${PACKAGES}"
exit 0


4) If you use selinux you may need to change security label:
chcon --reference=/usr/bin/rpm_tmp /usr/bin/rpm
5) exit (leave root)
6) sudo ./DaVinci_Resolve_Studio_19.0.2_Linux.run
7) Install Libraries
sudo dnf install libxcrypt-compat libcurl libcurl-devel mesa-libGLU
8)
Disable Incompatible Libraries
cd /opt/resolve/libs
sudo mkdir disabled-libraries
sudo mv libglib* disabled-libraries
sudo mv libgio* disabled-libraries
sudo mv libgmodule* disabled-libraries

However that would be useful if BMD would be so kind and make a little change on the install at least on Studio (payed) version to avoid experimental workaround by customers. Just because I got ~15 empty lines at the very beginning of the install and not sure why...

Last but not least I would not suggest force skipping checks due to other possible missing dependence that may or may not cause issue in the future.

Good luck. For me this worked and already the neural engine optimization is running...

Hi,

Just in case it helps work around the zlib issue: on Fedora at least, the installer apparently egrep's the output of rpm, so aliasing rpm to a script that would replace zlib-ng with zlib and running the installer from the command line might work:

Code: Select all

$ cat foo.sh
#!/bin/sh
PACKAGES=$(rpm $@ | sed s/zlib-ng/zlib/)
echo "${PACKAGES}"
exit 0

$ alias rpm=./foo.sh
$ ./DaVinciInstaller # sorry, forgot the actual file name

Another option -- that worked for me -- is to move egrep out of the way by renaming it for the duration of the installation. The installer will then ignore the check altogether (including the check for other libraries, so this is by no means the preferred way).

After that, you'll still have to move the libs around like previously. This merely addresses the installer not running because of the switch to zlib-ng.

Hope this helps.

All these work arounds..for many years.. Blackmagic, we need this linux install process to be cleaned up once and for all.