I think I got it almost! It was a mixture of things: As you pointed out I had to start with the prime-run command.
Then I used the non-studio version of davinci resolve, where .mp4 and .mts codecs and others are not supported. I now have some braw video played back correctly in davinci resolve. Only thing now I would need to upgrade to
resolve studio to get my projects running on manjaro. Problem is when trying to install via yay I get this, but this is already a different problem:
Making package: davinci-resolve-studio 19.1.3-2 (Thu 30 Jan 2025 01:41:44 CET)
==> Retrieving sources…
→ Downloading DaVinci_Resolve_Studio_19.1.3_Linux.zip…
curl: (3) URL rejected: Bad file:// URL
==> ERROR: Failure while downloading file://DaVinci_Resolve_Studio_19.1.3_Linux.zip
Aborting…
→ error downloading sources: /home/kalimerox/.cache/yay/davinci-resolve-studio
context: exit status 1
:: (1/1) Parsing SRCINFO: davinci-resolve-studio
==> Making package: davinci-resolve-studio 19.1.3-2 (Thu 30 Jan 2025 01:41:45 CET)
==> Checking runtime dependencies…
==> Checking buildtime dependencies…
==> Retrieving sources…
→ Downloading DaVinci_Resolve_Studio_19.1.3_Linux.zip…
curl: (3) URL rejected: Bad file:// URL
==> ERROR: Failure while downloading file://DaVinci_Resolve_Studio_19.1.3_Linux.zip
Aborting…
→ error making: davinci-resolve-studio-exit status 1
→ Failed to install the following packages. Manual intervention is required:
davinci-resolve-studio - exit status 1
wonderful, this all went well. I got davinci resolve studio installed and can start it with the prime-run command. Last obstacle is an error I when I try to activate the license. I am trying some things now and let you know
Ok , this seems to be the last step but I m a bit out of luck: The typical license activation. From what I read the problem could have various sources. The License file is in /opt/resolve/.license and it is there.
I tried to change the rights of the file with
sudo chmod -R 7777 .license
but no luck.
One suggestion was also , in case it is a bug in Resolve, to downgrade to the Base version of Resolve, activate, and then upgrade.
But I have no idea how to do that. I tried to do the procedure you outlined above and do it with Resolve19.0 and change the PKGBUILD file to pkgver=19.0, but then it tries to download the package which fails. So something I am missing here…
Blockquote
( including the manual makepkg approach )…
I think I am doing a mistake there: I am trying to install now an older version of Resolve to solve the activation problem. With your method I could easily install the recent version, but for downgrading, I do not know how to edit the PKGUILD or something else to be able to install it. I downloaded Resolve 19, then I changed the Version in the PKGBUILD to 19.0 but this did not do the trick.
line 14 is: pkgver=19.1.3
→ adapt this for the version you want or already have
line 27 - the sha256sums= ...
will now, of course, be wrong - it is a different file now
To “fix” this, run: udpkgsums
then build it (makepkg …)
This should fetch the file if it is still available -
or use the one you have and have put in the appropriate place -
and then build and install it.
I cannot test any of this - I don’t know the program or how to use it, probably don’t have any of the needed drivers, only have Manjaro in a VM, and I don’t have a licence/activation key.
I know nothing of the activation - but when that is (likely) done by running the program in your user account, the configuration also takes place and is stored within your user account.
I don’t know where - likely under ~/.config.
Look through your hidden directories for something pertaining to davinci
and delete it - to start the procedure from scratch.
Probably no need to bother with changing the PKGBUILD to install an older version.
What you did here:
is almost definitely wrong and even counterproductive.
The license comes with the program.
The activation is a different matter.
I am trying to edit the PKGBUILD file : I changed the version Number to 19.0 and Downloaded that version and put it in the same folder than the PKGBUILD file. I tried running
updpkgsums PKGBUILD
but I get
==> Retrieving sources…
→ Downloading DaVinci_Resolve_Studio_19_Linux.zip…
curl: (3) URL rejected: Bad file:// URL
==> ERROR: Failure while downloading file://DaVinci_Resolve_Studio_19_Linux.zip
Aborting…
==> ERROR: Failed to generate new checksums
I wonder how I can edit the PKGBUILD file that it does not point to the url but to the actual directory? can I exchange the url for /home/username/davinci-resolve-studio in some way?
I am pretty sure that when I can install that base level Version, I can finally activate. Looks like a lot of people were struggling with that recently…
If so, all you need to do is drop that file in the same directory as the PKGBUILD and change the pkgver=19.1.3 line to whatever that number is in that file between the _ characters. if it is 19 then pkgver=19, is it is 19.0 then pkgver=19.0.
When this is finished you can run (from within that directory);
yeah I definitely will! I even installed 18.5.6 and have the same issue. It is really strange and they should really do something about their compatibility on linux systems…
After trying really everything to get the license recognised I tried (maybe a dirty thing i should not do? ) run the program with sudo twice, as I found somewhere on the internet, and it worked! finally a .license file was written and all is perfect. Thank you so much for your help!!
That actually looks much more like black magic than a real solution - with the two times starting it as root
… and the “info” being on or from the blackmagic design forum as well …
When the thing is run as root, the files it writes are also owned by root - and may not be any good to an “ordinary” user …
It’s unfortunate the original poster at the BlackMagic forum didn’t bother to add a link when they claimed:
I mean, that’s what User forums are supposed to be about; Users helping Users; but some Users don’t seem too interested in anything beyond helping themselves.
It’s heartening when a Member here at least makes an attempt at helping others.
This can then help you figure out what the issue is. However, you will get issues with various libraries which then turn out to actually be issues with libraries that library uses etc. I figured out one of these libs, then searched about that library + DR and found Arch Wiki Davinci Resolve which contains lots of information including:
cd /opt/resolve/libs/
mkdir ./disabled_libs
mv libglib-2.0.so* libgio-2.0.so* libgmodule-2.0.so* disabled_libs/
Moving the above libraries is the ONLY thing i actually need to do after installing.
My one issue is not being able to record from my mic directly into resolve (and probably can’t do it from other sources either), so I’m just using Audacity to record and initially process audio, then exporting a track as separate files and then dumping those into DR. I might bother to solve that too sometime.
Lastly: If you install DR as root by accident, you need to remove root/root/.local/Shared/Davinci and reinstall. Note you may have important DR stuff in there if you were actually using it as root! Make sure you back things up.