@jwan then you installed the program twice
I'm not sure where you installed it by using the .run file, however you should make sure to have a single copy of davinci-resolve in your system.
Git Clone URL: | https://aur.archlinux.org/davinci-resolve.git (read-only, click to copy) |
---|---|
Package Base: | davinci-resolve |
Description: | Professional A/V post-production software suite from Blackmagic Design |
Upstream URL: | https://www.blackmagicdesign.com/support/family/davinci-resolve-and-fusion |
Keywords: | blackmagic davinci editor resolve video |
Licenses: | LicenseRef-Commercial |
Conflicts: | davinci-resolve-beta, davinci-resolve-studio, davinci-resolve-studio-beta |
Submitter: | jonathon |
Maintainer: | Muflone |
Last Packager: | Muflone |
Votes: | 162 |
Popularity: | 4.14 |
First Submitted: | 2017-04-19 20:57 (UTC) |
Last Updated: | 2025-08-28 17:19 (UTC) |
@jwan then you installed the program twice
I'm not sure where you installed it by using the .run file, however you should make sure to have a single copy of davinci-resolve in your system.
I downloaded the "DaVinci Resolve Studio 20.1" zip file from: https://www.blackmagicdesign.com/support/family/davinci-resolve-and-fusion
I then unzipped the file and followed the instructions:
cd ~/Downloads/
unzip ./DaVinci_Resolve_Studio_20.1_Linux.zip
chmod +x ./DaVinci_Resolve_Studio_20.1_Linux.run
sudo ./DaVinci_Resolve_Studio_20.1_Linux.run -i
I think that was a mistake, am I right? Cause I already had it installed via the AUR. How do I go about fixing this?
@Managor 20.0.1 and 20.1 are different versions. in a short period of time the newer package version will be released
The filename for this is wrong PKGBUILD expects DaVinci_Resolve_20.0.1_Linux.zip when the downloaded file is DaVinci_Resolve_20.1_Linux.zip. Also the file doesn't pass validity check
@filmroellchen
This is not true, as AUR helpers use specific directories that are not usually known to users.
Here's is how the wiki explains how to build packages from AUR https://wiki.archlinux.org/title/Arch_User_Repository#Build_the_package
If you prefer to use a different tool, it's your choice.
Apart from the bad taste pun, why exactly do extra curl options count as black magic in your book?
This giant mess in red counts like black magic, yes.
Ironically, people don't want to read simple instructions on the PKGBUILD explaining where to get the file and where to put it and then pretend to understand those +50 lines of awk/sed/bash escaping with no risks.
AUR package must be checked from both users and PMs for invalid, dangerous, obscure commands they could do to harm the users, so they have to be kept as simple as possible. Removing those +50 lines of black magic was a fundamental part to make sure the package would be simpler to inspect and check.
I read through the packaging guidelines and AUR submission guidelines and nothing to me indicates that prebuilt dependencies have to be provided manually by the user, as soon as the dependency is not just available from a trivial URL. Please source such claims accordingly, otherwise I’ll probably take this up with the mailing lists sometime soon if you don’t fix the package.
There's not a specific rule in the wiki about how to handle unpredictable source links but this approach was already backed by a lot of PMs keeping the things more simple as possible, without violating the author's website protection against the direct links.
You can propose anything you want but nothing changes the fact that circumventing the authors protections against direct links won't be applied by this package.
@rayne the PKGBUILD clearly explains where to download the file and where to put it
This is not true, as AUR helpers use specific directories that are not usually known to users. The only comment noting where these directories are for paru and yay has been buried on page 2 and is hard to find. If you’re unwilling to actually make this package usable again, you should at least pin that comment or copy its information into your pinned comment.
Packages must not contain black magic or unknown/hard to understand commands as users are required to check the PKGBUILDs before installing/updating from AUR.
Apart from the bad taste pun, why exactly do extra curl options count as black magic in your book? I find that some of the stuff this installer needs to do anyways is pretty hard to understand, and it only seems to grow every second release. This argument does not hold water.
This is the only valid way to use AUR
And that is plainly wrong. I read through the packaging guidelines and AUR submission guidelines and nothing to me indicates that prebuilt dependencies have to be provided manually by the user, as soon as the dependency is not just available from a trivial URL. Please source such claims accordingly, otherwise I’ll probably take this up with the mailing lists sometime soon if you don’t fix the package.
I believe pulseaudio-alsa should be added to optdepends for voiceover support. Even if you have pipewire-alsa installed, you still need pulseaudio-alsa installed for voiceover to work for whatever reason.
Download error ?
==> Création du paquet davinci-resolve 20.0-1 (ven. 13 juin 2025 03:06:54) ==> Vérification des dépendances pour l’exécution… ==> Vérification des dépendances pour la compilation… ==> Récupération des sources… -> Téléchargement de DaVinci_Resolve_20.0_Linux.zip… curl: (3) URL rejected: Bad file:// URL ==> ERREUR : Erreur lors du téléchargement de file://DaVinci_Resolve_20.0_Linux.zip Abandon… :: Unable to build davinci-resolve - makepkg exited with code: 1
DaVinci Resolve 20 was released a while ago. If you plan to use this package for installation, consider git cloning, changing the pkgver
to 20.0
and sha256sums
with your output of sha256sum DaVinci_Resolve_20.0_Linux.zip
and install it. Works for me out of the box. Hoping to see this updated in the future.
After using the official .run file, I was able to get version 20.0 working with LD_PRELOAD="/usr/lib/libgio-2.0.so /usr/lib/libgmodule-2.0.so /usr/lib/libglib-2.0.so" /opt/resolve/bin/resolve
. Commenting that here in case the information is useful to users or packagers.
UPDATE: Since the package updated to version 20.0, everything works as it should. Thank you Muflone!
Pinned Comments
Muflone commented on 2025-01-26 00:55 (UTC)
IMPORTANT!
Since version 19.1.3-2 this package will not download automatically the source file from the upstream site.
To build this package you will need to manually download the file from https://www.blackmagicdesign.com/support/family/davinci-resolve-and-fusion and place it in the same directory with the PKGBUILD.
This would reduce the mess in this package, making it more readable and clear. Also bypassing the required information from the upstream URL is not allowed in an automated way.
satriani commented on 2021-05-15 14:14 (UTC)
Issues and bugs, please report on the official forum here: https://forum.blackmagicdesign.com/viewforum.php?f=21&sid=239f0d5c49abe5d6a635b69638192e9a Thank you!
Visit DaVinci Resolve - ArchWiki before installing: https://wiki.archlinux.org/title/DaVinci_Resolve
ATTENTION: Please don't flag this package as out-of-date before beta version has been released as stable!
This is a current stable Package!
The current free beta is available here: https://aur.archlinux.org/packages/davinci-resolve-beta/
And for current studio beta here: https://aur.archlinux.org/packages/davinci-resolve-studio-beta/
Thanks.