New to EndeavourOS, liking it alot coming from mint. Installing Davinci Resolve gives me some pain but i will learn to build pkgs eventually.
I have a problem with blender, one that i had encountered in mint too, and could not find any answers as to why it happens, or how to fix it.
Randomly (i think) shortcuts will stop working. Not all of them, but most. Across different modes. Ctrl+Z will stop working for example. Sculpt mode shortcuts, extrude commands in edit mode, you name it. Happens both to new and existing files. I plug in through USB a Wacom Intuos tablet to sculpt but it happens without the tablet plugged in, not sure if that has anything to do with it.
The problem will randomly resolve itself, and will reappear at a later time.
Any one has any idea why this happens and what can be done about it?
If you need any specification on versions or diagnostics in order to help please ask.
Let us know if you need some help getting Davinci Resolve setup.
The basic approach is to grab the PKGBUILD like this:
yay -G davinci-resolve
Or if using the Studio version:
yay -G davinci-resolve-studio
That’ll create a directory, that you should then put your downloaded Davinci Resolve install file into, having downloaded that direct from the Davinci Resolve website.
Once the install file’s there, enter that directory and run this to build and install the package:
makepkg -sri
It’s a bit of a pain, but there’s a good reason it has to be done this way.
I’m less experienced with Blender, but I can’t say I’ve noticed the issue you’ve described. In Blender, what have you got here?
Turns out i am slightly dumb. I have English and another keyboard language installed, shortcuts do not work with the other language. Problem solved (once again probably, i think i had figured that out and with time i forgot).
As far as Resolve goes, i tried to use yay -s to install it and it did not go well (could not download the installer), later found out i had to manually download the installer, which i have done. Read on the AUR page that it should go to the build directory, but as i understand what your wrote i should yay -g first so the directory gets created, move the installer there and then makepkg -sri, right?
If you’ve used yay -S davinci-resolve to start the installer, it’s likely made the directory for you in ~/.cache/yay/davinci-resolve.
So one way is to drop the install file into that directory, then re-run yay -S davinci-resolve.
The method I gave is just another way of approaching it, where you download the directory first in a place of your choosing, then run makepkg -sri inside that directory after you’d put the install file in it.
In the end, with either method, the installed version will be exactly the same, and interacting with it after its install with package management tools, will also be exactly the same (if you wanted to remove it, for example). It just comes down to preference.
Could not find the directory the yay -S command made, does it automatically delete it if enough time passes?
Run yay -G, it made a directory, i put the zip install file in that directory, opened the terminal there and run makepkg -sri but there was still an error where it could not download the DaVinci_Resolve_20.3.3_Linux.zip, and the installation failed.
I have downloaded 30.3.2, is there a chance that the version difference is what blocks the install?
