Long story short, this error popped up when I was running an update in Manjaro using the Add/Remove Software program. As a result, the in-progress update failed, and I wasn’t able to get past it. Even after restarting my computer, restarting Add/Remove Software, I still ran into the same error. After some research, I discovered that apparently, somewhere along the way, one of my updates had gotten interrupted. (Which makes sense when your two year old son just goes around pushing the hard reset button (conveniently?) located on the front of my tower… or the glowing blue power button on my UPS… you get the idea.) So yeah, there was a solid chance a process or two was interrupted. Because of that interruption, there was a temporary file left in my pacman cache. Removing this incomplete temp file was solved as soon as that file was removed and the update was restarted.
Solved error with sudo rm /var/cache/pacman/pkg/*.part
Hey guys, I was trying to build a copy of Local by Flywheel on Manjaro Linux, but ran into this error… ‘ Failed to build nettle6 ‘
failed to build nettle6
nettle6 is a dependency of Local, but after the attempted build of the package, I got the error failed to build nettle6 :
==> Verifying source file signatures with gpg...
nettle-3.4.1.tar.gz ... FAILED (unknown public key F3599FF828C67298)
==> ERROR: One or more PGP signatures could not be verified!
Failed to build nettle6
If you happen to come across this error, just double check the key by running
gpg --recv-key F3599FF828C67298
Just plug in the gpg key from the error at the end of your gpg --recv-key call.
In my case, that didn’t work. The resulting output was:
In my case, it shows that the new key was successfully imported.
~ >>> gpg --keyserver pool.sks-keyservers.net --recv-key F3599FF828C67298 [2]
gpg: key F3599FF828C67298: public key "Niels Möller <[email protected]>" imported
gpg: Total number processed: 1
gpg: imported: 1
~ >>>
Now, when I run the nettle6 package build again… it works! Hope this helps. There’s a great resource on this on the Manjaro forums.
Again, this is a very specific error and solution, and it just so happened that I was having trouble with my gpg keys. This may not be the case for everyone, but I hope this article is helpful to you.
I’m trying to download some assets from the Unity Asset Store, but clicking ‘open in Unity’ is not working. Chrome prompts me with an “XDG-Open” dialogue. Even after selecting “ok”, nothing happens.
So far, there are lots of complaints about the Unity Asset Store and how the only way to download some simple PDFs is via a giant, several GB Unity Editor.
Regardless, if you just want to download some assets for learning like I do, I found a simple workaround:
Open up the Unity Hub:
Click Learn:
Then Select the project you’d like to check out, and hit “Download”:
The biggest problem with this workaround is that it only works for learning assets. I can’t seem to find a way to download assets that wouldn’t typically be categorized under ‘learn’. If anyone has any suggestions or ideas, feel free to let me know!
By default, the project landed in my /tmp/ folder. Simply save the project to any location you like from inside the Unity Editor, or copy the contents of /tmp manually. Here’s some more information on how to copy projects. Hope this helps!
It appears that this issue is fixable. There’s a solid chance my xdg-open tool is not configured to open Unity when I click the “Open In Unity” link. I’m investigating further via these resources:
How to fix Failed to Commit Transaction (Conflicting Files) Error in Manjaro Linux
This error is usually thrown after an attempted package upgrade using either pacman, the GUI, or another package manager. Below is an example of the error:
This can happen with pretty much any package, depending on what else you’ve got installed on your system. Basically, pacman is saying it can’t go through with the upgrade because there are some conflicting files that exist on your machine that is preventing the upgrade from progressing any farther. Here’s what you can do to solve this.
Step 1
Check to see which package owns the file in question. You can do this by running pacman -Qo /path/to/the/file. If that prints out the name of a package, then you will have to decide whether or not to uninstall the package with the conflicting package by using sudo pacman -R nameOfThePackage.
Step 2
If the file in question is not owned by any package (as was the case for my situation), you can simply delete the file in conflict. You can do this by running sudo rm /path/to/the/file. Once the file has been removed, you’ll need to run the update process again to confirm that all the conflicting files in question have been resolved.
When I try to update my machine by running sudo pacman -Syyu I get an error saying it’s unable to lock the database. Below is an example:
But as you may have noticed, by removing a special database lock file, I was able to solve the issue. You can do this with sudo privileges by running:
sudo rm /var/lib/pacman/db.lck
The above method is dangerous
I’ve done this before, and it’s worked perfectly fine with no issues. But the reason the db.lck file exists is to ensure that only one program can run updates at a time. This prevents partial updates, or interrupted updates, or conflicts, or any other problems that can occur when two programs try to do the same update at the same time.
So before you go deleting your db.lck file like I did, do yourself a favor and make absolute certain that there are no other programs trying to update anything. You can use the lsof command to check what other programs are using the db.lck file. lsof is short for “list open files”.
The lsof command will either return nothing or a single number. If it returns nothing, that means that no process is currently using that file. If it does return a number, then that is the ID of the process currently using that file. In order to delete the file safely, you’ll need to kill that process first. You can do that by running sudo kill -9 <process_id>
Hope that helps! Please leave a comment below if you have any questions. You can find more information on using the command line, check out this awesome book called The Linux Command Line. It’s free!
Hey guys! If you’re hear, you probably already know what RAM is and you’re excited to learn how to add swap in Manjaro. If not, this is sort of a follow-up post to how to download more RAM. Anyway, let’s get started!
Using a Swap File
There’s a ton of different ways to add swap to your system, some more advantageous than others. In my experience, it’s always been easier to add swap to an existing install by using a swap file. First, just confirm that you don’t already have swap enabled. To do this, just run sudo swapon. If that command does not return any output, then you don’t have swap enabled. Also, if you have and/or use htop, it will actually display your swap status right below your RAM usage bar. if it reads empty and 0/0kb, then you don’t have swap enabled. Great! Now we can add a swap file.
Creating and initializing a new swap file
To create an initialize a new swap file, we’ll be using the fallocate command. To initialize a 16GB swap file just run the following in a terminal:
sudo fallocate -l 16G /swapfile
then run: sudo mkswap /swapfile
Setting permissions for your new swap file
Manjaro will likely give you a warning about changing the permissions of your swap file. You can change permissions using the chmod command. The swap file should only be readable and writable by the root.
sudo chmod 0600 /swapfile
Enabling your new swap file
Enable your new swap file by running the following:
sudo swapon /swapfile
Make your changes permanent
Make sure Manjaro knows to use your swap file every single time it boots up. Do this by running:
And that’s it! The only thing left to do is reboot and just double check to see if your swap is up and running. Again, you can just run those commands from the beginning of the tutorial swapon or htop and you should be good to go! Happy blending!
The simplest and quickest way to get up and running with DaVinci Resolve on Manjaro is to simply open the default package manager that comes with Manjaro and searching for davinci-resolve. This will give you a few results, because Resolve comes in free and paid versions. If you want to install and use the paid version, search davinci-resolve. If you have an activation key or USB key for the paid version of Resolve, then just search for davinci-resolve-studio. Click on the package you want, click “Build”, type in your password, and you’re good to go!
Method 1:
This is likely the more common way to install Davinci Resolve 16.1 on Manjaro. Just head over to the official Blackmagic site to guarantee yourself the latest and greatest version of DaVinci Resolve. From there, you can register and download the latest .zip file. Once you unzip, the installation is pretty easy, just execute the file named “DaVinci_Resolve_{yourVersionNumber}_Linux.run”. That’ll launch an installation wizard that will walk you through the terms and conditions, licensing agreements, and installation process.
The only catch with this method is that there’s a chance you might not have all the required dependencies in order to run Resolve on your machine. In order to avoid this… I’d recommend the second method.
Method 2:
Use the user-created AUR package. This can’t be found inside the “Add/Remove Software” program that comes with Manjaro, as it’s not an officially supported repository. However, as of the writing of this post, it’s up-to-date and appears to be pretty well maintained. To install DaVinci Resolve 16.1 on Manjaro using this method, there is one prerequisite. You’ll need a group of packages called base-devel and git. To install these, just run:
sudo pacman -Syu base-devel git
You’ll be prompted for your password, and pacman will automatically go and grab all the required packages you need. Once that’s done, go to the official AUR package page and find the GIT Clone URL (usually linked at near the top of the page on the left).
Copy that link, because you’ll need it in just a second. Next, create a new folder in your home directory called Programs, and inside Programs, create a new folder called DavinciResolve. Next, open a terminal window in your newly created DavinciResolve folder, and type git clone and paste that URL you copied earlier like so:
Once you hit enter, you’ll create a copy of the AUR repository on your machine. Inside your folder, there should be a file called PKGBUILD just for peace of mind, you can optionally run less PKGBUILD to take a look at the script, just to make sure that you’re pulling official copies of Davinci Resolve 16.1 from Blackmagic’s official website. Once you see the official URL in the code, you’re ready for the final step!
To build and install DiVinci Resolve 16.1 on Manjaro, all you need to do now is run makepkg -si. That will begin building resolve, -s to sync your local repositories with the remote ones, and -i to install the packages once you’ve built them. And that’s it! You’re now running Davinci Resolve 16.1 on Manjaro. Have fun!
Earlier this week I decided to run DaVinci Resolve on Ubuntu 18.04. This was a terrible idea. I spent the last 3 days banging my head against a wall and scouring countless forums, blogs, articles, and all for nothing. Here’s my situation. I have an AMD Threadripper with a pair of RTX 2080TIs that I was trying to use with Ubutnu and Davinci Resolve.
Of course, if you plan to run Davinci Resolve on Ubuntu 18.04, the default Ubuntu install pretty much gives you the generic graphics drivers and it’s up to you to install the ones you need. Since I want to run Resolve, I’ll be needing the latest Nvidia drivers for Linux. Downloaded and installed from the website, but it didn’t work. Installed CUDA, but it didn’t work.
I tried so many different drivers that they started conflicting with each other and it became an even bigger mess than what I started with. I rebooted a ton of times and sometimes the drivers would work, and other times they wouldn’t even switch from the old driver. I tried with and without CUDA and with and without OpenCL, but nothing worked. I couldn’t get anywhere beyond the opening splash page.
TL;DR
Guys, just save yourself the trouble. Seriously. If you’re wanting to run Davinci Resolve on Linux, but you don’t want the official CentOS build… Do yourself a huge favor, avoid the headache and just install Manjaro. Seriously. I was up and running in Davinci Resolve cutting 5K RED footage in 15 minutes. It’s the easiest Linux video workstation setup ever. I’m never going back.
Full disclosure: I’m not being paid to write this. Opinions are my own. This is just my experience. As always, keep your passwords secure, and your sources open. Cheers.
Let’s locate files using the terminal! This is just a cool little trick you can use if you’re doing a bunch of stuff in the terminal, and you don’t want to leave, or you’re just interested in cool terminal tricks. Let’s say you’re looking for a file, anywhere on your machine, but you don’t know exactly where it is. You can install a very cool search package called mlocate (or merging locate).
Install
On Ubuntu/Debian you can run:
sudo apt-get install mlocate
Or if you’re on that Manjaro/Arch life:
sudo pacman -S mlocate
Syntax
To locate files in the terminal by using mlocate, just type:
locate [name of the file] [directory in which you want to start recursively searching]
If you’re using mlocate for the first time, it’s not gonna work just yet. mlocate is actually a pair of tool bundled into one. The other half of mlocate is called updatedb. So by running updatedb, you’re essentially creating/updating an index so that you can run your search. So any time you want to run a locate command and it’s not giving you the results you are expecting, there’s a good chance your index is outdated, so you can just run updatedb, then run your locate search again, and you should be good to go.
Update your junk by running updatedb then run locate [file] to get your mind blown!
Bonus Tip
If the results of your locate command are crazy long, like… CRAZY long…. too long to view everything in the terminal because your terminal only has a finite history, here’s a tip: You can print the results of ANY command to a text file and save it anywhere by using >. For example:
The above command will run a system-wide search for anything matching myfile.txt recursively from the root directory / and print the results to searchresults.txt on the Desktop.
Good luck and have fun! Now that you’ve found the file you’re looking for, perhaps you want to do something cool with it! If you wanna learn more cool stuff you can do in the terminal, check this out.
I use Adobe CC on a Windows machine for my video production pipeline at work. I do video side work on the weekends, and have used Windows and Adobe for those projects as well, but I’ve always felt trapped. Like I’m a slave to Adobe or something. I’ve spent most of my professional career learning and using software like Premiere Pro, After Effects, and Photoshop.
Making the Switch
I’ve used Ubuntu a TON, as it’s a super popular distro, and it was my introduction to Linux. A few months back, I was checking out https://opendata.blender.org/ and noticed that a good chunk of data was coming from a distro called Manjaro, but I’d never heard of it. Shortly after seeing all that performance data, I decided to give Manjaro a shot. After some basic research, I discovered Manjaro is actually based on Arch (unlike Ubuntu, based on Debian).
I gotta say, installing Manjaro was a breeze (cursor theme). I will admit however, I have never known the pain of installing Arch. Like actual Arch. But I’m aware of the memes. So I’m sure it’s pretty involved. While I can’t exactly go around trolling like, “btw I use arch”, I was seriously surprised at the installation and how much was up and running right out of the box! Ubuntu is pretty straightforward, but depending on the hardware, you may need to find a few hacks or packages to get everything full up and running. For example, I couldn’t get the wifi working when I put Ubuntu on my 10 year old Macbook until I installed a special package that didn’t come with the default install.
Everything Works.
Immediately… Very first boot up. Everything works. Hardline network connection works. Wifi card works. GRAPHICS look great. Manjaro automatically grabs graphics drivers for you upon install! And I was actually impressed with the pre-installed software collection. Most of the time, in Ubuntu, I have to delete a bunch of crap software I’ll never use. But Manjaro… Like, I use Steam all the time. It’s pre-installed. Libre Office pre-installed. Tweaks pre-installed. Gparted pre-installed (this might be normal). But I was really surprised how little I actually had to do post-installation.
Smooth UI Experience
It’s a bunch of little things that add up to a massive amount of time saved. One of my pet peeves in Windows is switching apps on the task bar. If your app has multiple windows (like Blender, and a render window), you have to click once to reveal thumbnails, then click the thumbnail of the window you want. If they’re small or detailed windows like terminals, good luck. I love the single hot corner in the upper left to give you an expose-like look of all your running apps. I love the best-of-both worlds option to launch a full-screen app tray from the bottom left, or tap the drop-down xcfe-like ‘start menu’ from the upper left. It’s pretty awesome. Just gotta get used to typing pacman -S instead of apt-get
Haven’t logged a ton of hours on Manjaro just yet, still very much in the “moving in” phase. Feeling great so far. Looking forward to diving into my brand new postproduction workflow in Manjaro using Blender, Resolve, Gimp, Inkscape, and Ardour. More on that in the coming weeks! Peace
