Automate Updates In Linux Mint

Today’s article will be a fairly simple one and is limited to Linux Mint users as we learn how to automate updates in Linux Mint. That seems like a good idea to me. Ideally, this will continue working without any intervention, but we’ll see…

So, I’m not sure how long this has been an option. I only noticed it fairly recently. If you’re not already aware, you can automate updates in Linux Mint. It’s a pretty simple task and won’t require much more than a mouse – or maybe a terminal and then a mouse.

This can be a touchy subject. I’m firmly in the camp of immediately installing all updates. I want my system to be as secure as possible, which means applying the updates as soon as they are available. So far, this mostly appears to work.

Updates often come right before public disclosure and proof-of-concept samples. While it’s true that an update can bork your system, that’s easily fixed and such a rare thing that I don’t even consider it as a reasonable reason not to apply updates.

I also consider it my duty, my obligation, to keep my systems secure. An insecure system doesn’t just impact you. An unsecured computer can be used as a proxy, a command center, a spam relay, or a node in a DDoS attack, among other things. As a good netizen, I keep my systems updated.

So, why not automate that stuff when I can? 

Automate Updates In Linux Mint:

In your system tray, down on the right, look to see if you have an icon that looks like a shield. If you do not see the icon, press CTRL + ALT + T and type in mintupdate. Both of those things will open the Update Manager in Linux Mint.

At some point along this path, you’ll be asked to enter your password. Do so.

That will open this window:

to automate updates in Linux Mint, start with opening up the update manager
Your theme may mean this has different colors or whatnot, but it should look like this.

Next, you’ll click on ‘Edit’.

You need to click on the Edit button to move to the next step of automating updates in Linus Mint
This is a pretty easy step. Heck, they’re all easy steps! You’ve got this! I’m sure of it!

You next want to open Preferences and click on Automation.

You'll need to edit the preferences to automate Linux Mint Updates.
Just in case you’re confused, I added an arrow for you! (My CDN is going to hate me.)

When you’ve done all of this, you’ll face a new screen.

This new screen is where you edit your automation settings. This new screen is where you enable automatic updates in Linux Mint. It looks like this when I’ve configured it to my liking:

Enabling automatic updates in Linux Mint via the Update Manager preferences.
You can configure those however you like, but I enable all of them. You do you, I guess.

Make sure you have a viable backup process.

As you can see, I’ve chosen all the things. I’ve chosen to automate all the updating that I can do. If anything, I wish I could increase the frequency. I suppose I could set up a cron job for this, but a handy GUI is fine for this task. This way will also update Spices and Flatpaks. So, there’s that.

I’ve had this setting enabled for a little while now and I’ve verified that it has been working as expected. If you want to automate updates in Linux Mint, you can do that – and it’s not even difficult.

Update:

No, it doesn’t appear to update Flatpaks. I’ve given it a few tries and it does not.

flatpaks are not automatically updated
I’ve waited and waited a few times. You have to update Flatpaks manually. So, there’s that…

Closure:

I like automatic updates. I use that sort of feature online with my various websites. Scheduled updates performing themselves is a good thing to me. You may be more cautious, but I throw caution to the wind. I haven’t had an update nuke my system beyond a 2-minute repair job in forever. I haven’t even had a 2-minute repair job in years. That’s good enough for me. You can make your own choices. Regardless of your choices, be sure to backup your system regularly.

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

Meta: The State Of Linux Tips #15

Today’s article is just a meta article, one where we cover the state of Linux Tips (this site). It’s just a chance to sit down and share what’s going on with the site, a chance to not write something technical. So, for another meta article, read on!

This will be mostly about the month of February. See, I didn’t write any meta article(s) in February. It just didn’t cross my mind and it was a shorter month than the months surrounding it. So, I suppose, this will be about February.

I try to write these meta articles once a month, but they’re never really formally scheduled. They just get written when I remember to write one and when I have the urge to do so. I should probably pick a specific day of the month and write them on that day, but where’s the fun in that?

So, about February…

The State of Linux Tips:

February only has 28 days. Because of this, Linux Tips did not have more traffic than the month before. If February had been 29 days, I’d have had slightly more traffic than was had in the month of January – which has 31 days. (Traffic for this month appears to be breaking all sorts of records.)

Like always, the vast majority of my traffic came from Google. However, that number has jumped a great deal. I had about 6200 visitors from Google in the month of February. The site’s getting more and more popular, or so it seems.

In February, I had 12,655 unique visitors. In January, that number was 12,885 unique visitors. So, if February had been just a few hours longer it’d have had more unique visitors than the month prior. I’m going to put that one in the ‘win’ column!

Google’s definitely taken me out of the doghouse, but the ad clicks are worth less than they used to be before they put me in the dog house. Amusingly, this coincides with my CDN deciding the amount I had been paying is an ‘introductory rate’ and will be doubling the cost. I bought a bunch of credits, hoping that they’ll still be worth the same as they are now.

That’s not actually a complaint. They provide a great service and the cost isn’t that much. I know, I ask for donations and I have ads, but the reality is that the site will remain online for the foreseeable future.

The expenses aren’t so great that I can’t handle them. If they ever do become more than I’m willing to pay, I’ll be sure to let folks know and let folks decide how much they value the site. But, really, don’t worry about it all that much. We’re good!

Some Linux-Tips Numbers:

Hmm… How about the three articles AWstats tells me had the greatest traffic numbers?

Find Out Which Display-Manager You’re Using
Screenfetch vs. Neofetch, You Decide!
How To: Restart TeamViewer From The Terminal

That’s a bit interesting, as here’s what Google says were my top 3 pages:

It agrees with the #1 slot.
The #2 slot (according to Google) is the TeamViewer article.
How To: Stop, Pause, and Resume Processes Running in Your Term

But, Google’s not very good with counting traffic. Google seems to me to not count anyone that doesn’t allow the Google cookie. So, if you’re blocking ads appropriately, you are also probably blocking the cookies from the blocked sites. That means Google isn’t very good at counting traffic.

For example…

According to Google Analytics, my monthly visitors for February was a total of ~4800 people. (That’s pretty amazing, as the previous month was like ~4200.) It does say that I was in the search engine results some 365k times. But…

In reality, I had almost 13k unique visitors and a total of ~17.5k total visits.

So, for all the complaints about Google tracking people, they’re not very good at it. Also, they really suck at figuring out what kind of ads I’d like. I’m not allowed to click on them, but I do see them. They’re seldom for anything I’m interested in.

Still, you should whitelist this site and Google wants you to only click on ads that are of legitimate interest to you. Don’t just click ads to be nice. I appreciate that, but it’ll just screw me over in the end. As it is, Google loves to call clicks invalid for reasons I do not know.

Closure:

There’s still a lot going on here. There’s still more articles to write. I could use a bit of a break now and again, so speak up if you’re wanting to write an article for the site. (And you’re not looking to use my site to boost the ratings of unrelated sites, of course…) 

We’ll see when the next meta article comes along, but it probably won’t be in the month of March. It could be, I dunno… Oh, and I chewed through about 20 GB of bandwidth with 5 of those GBs being gratis.

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your own site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

How To: Find Linux News

Today’s article will be really easy for anyone to follow, as I share how it is I find Linux news. It’s amazing how many people don’t keep up with any Linux news. Read on, as this is sure to be a fairly short article. 

I might even speculate that most Linux users don’t keep up with Linux news. I’d speculate that it’s an even smaller group that does things like read the release notes for their updates and upgrades. They don’t read the notes about software upgrades and they don’t definitely don’t pay attention to what’s going on at the project(s) level(s).

This is too bad. There’s a lot to learn and gathering information is good.

These are the people who are then surprised by things that were covered in the release notes, just as people are surprised by changes that have been covered by the journalists. (Well, I’m going to call them journalists for the sake of this article, and to avoid unneeded complexity.)

Now, I admit that I’m not always as diligent as I would suggest others be. I can be pretty lazy. I might even move to a new distro point release without actually reading the release notes. So, do as I say, not as I do!

Or not…

Just keep up with what you want to keep up with. For the most part, you’ll be just fine. Anyhow, I am not feeling all that great and I need a quick/easy article. So, you get this article about finding Linux news.

How I Find Linux News:

Below, you’ll find some links to news sites that I use when I want to keep up with Linux news. If you have your own sites, feel free to add them as a comment below. If you want your site added, feel free to ask in a comment below and I’ll take a look.

My first stop is quite often just an aggregator. It’s not complete, but it’s useful. I’ll often visit some of their aggregated URLs in person. If you just visit one site, this is a good choice:

tuxurls.com

My next choice is a site that tends to have plenty of content. I try to catch them daily, but obviously don’t always have time to do so:

linuxtoday.com

This next choice also has a ton of content. In theory, you can comment on the stories, but there’s not a lot of community involvement in those regards. Still, they tend to have a bunch of Linux news:

lxer.com

This next one doesn’t always have the same amount of content as some of the others, but it’s usually pretty good. Plus the site is well-designed and it even looks like a proper news site:

linuxinsider.com

If you want less content, but things like tech data and well-thought-out articles that tend to be a bit more in-depth, then you would do well to consider this site long-lived Linux news site:

phoronix.com

This next site tends to have some good content – and it’s reader-supported. As such, you will find there’s some decent commentary here. If you don’t know what to think about an article, you can head to the comments and someone will tell you what to think! See:

lwn.net

There are more but this is the final one I’ll list. I know, not everyone likes Google. But, their news section is usually pretty good at finding Linux news that might not have been covered elsewhere. I actually tend to check this one fairly frequently. The link should work for you, regardless of where you live:

news.google.com/search?q=Linux

So, those are a few of the places I go to for news. You should also consider finding your distro’s news outlet (often a blog of sorts). There you can keep up with distro-specific things and find stuff like release notes. You should be able to find that on your own.

Closure:

There you have it, you have another article. This time, we’ve seen a few of the places I go to when I want to find Linux news. I try to keep up with a bunch of it, and some subjects interest me more than others. If nothing else, you may want to consider keeping up with the news published by the distro you’re using. You’ll know more and not be surprised when changes happen.

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your own site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

Prevent Application Updates With ‘YUM-VERSIONLOCK’

I recently wrote a similar article, illustrating how you can use ‘apt-mark’ to prevent application updates. While that was handy, it only applied to those who use APT as their package manager. It offered nothing of value to those who use YUM.

This article will explain how you can prevent application updates with ‘yum-versionlock’. You will learn how you can temporarily prevent application updates when you have no choice but to.

In the previous article, I explained that you should always use the most up-to-date software that you can, at least if your system is connected to the public internet. Software updates provide security fixes, not just bug fixes.

Not updating means you’re vulnerable and your vulnerabilities may impact other users. For example, your computer may become a part of a botnet, a spam relay, or even be used as a command and control device for those things. As a global citizen of the ‘net, you’re obligated to do what you can to minimize harm.

So, it is possible to prevent application updates, but you really should only do so when it’s absolutely necessary. In an ideal world, you’d be able to always use the updated version, but we don’t live in that world. We live in the real world, where we have things like compliance and compatibility issues. 

YUM, what is it? YUM stands for Yellowdog Updater, Modified. It’s a package management utility for RPM based distros. You’ll find YUM in distros like RHEL, Fedora, and even OpenSUSE. It’s fairly widely used, though many of the RPM-based distros are more prominent in the server space than they are in the desktop space.

These days there’s actually DNF (which stands for Dandified YUM – don’t blame me, I don’t name these things) but that’s not important today. Today, we’ll be using ‘YUM-VERSIONLOCK‘ to prevent application updates.

Prevent Updates with ‘yum-versionlock’

Unlike ‘apt-mark’, you’ll need to install something in order to do this. It should also be mentioned that there are other ways to accomplish this, but this is the easiest way to prevent application updates. Using versionlock is the most straightforward way of accomplishing this.

First, you’re gonna need to crack open your terminal. You can do that by using your keyboard. Just press CTRL + ALT + T

Once your terminal is open, you’ll need to install ‘yum-versionlock’. You can try this first:

If that gives you an error, I can’t figure out where the name changed, then you can most likely install it with:

Once you have it installed, you can check the man page to see how you use it. Even if you installed it with the second command, the man page is still found at:

The one-liner quite accurately defines versionlock as:

yum-versionlock – Version lock rpm packages

Anyhow, to use it to hold a package at its current version, you simply use:

NOTE: The command supports wildcards. You can use an asterisk with this command. The command will give you feedback. You can also use ‘add’, but it’s redundant.

If you want to remove the lock, which you should do as soon as realistically possible, then the command is fairly evident. It’s just:

If you, like me, don’t always keep the best notes and don’t have the greatest memory, then you can list the locked packages with this command:

There’s no need for elevated permissions with that command, but it will take a little while for it to complete. It will output any locked packages and you can unlock them individually. Again, you can use wildcards in this command.

However, you can remove all the locks with just one command:

As you might expect, that removes all the locks and your system will resume updating normally. You should not keep software locked to one version for long. Though you may be using a LTS-type distro, only getting minor point release upgrades, you are still getting security updates. Keeping your system secure makes you a good netizen. 

Closure:

And there you have it. Another article in the books, this one explaining how to stop updates for specific applications. Thanks for reading and feel free, nay encouraged, to leave feedback. If you have any ideas for articles, feel free to share them. You can also contribute by writing your own article. I’ll even edit it up for you!

Don’t forget that there’s a newsletter (we never spam or share your address with anyone, it’s all in-house) and you can even donate. I’d kinda like the site to at least pay for itself, simply out of principle. If not, there are ads you can unblock! Even if you do none of those things, there are good odds that I’ll keep this site up, running, and interesting.

Prevent Application Updates With ‘APT-MARK’

While unwise, there are times when you need to prevent application updates. You can do this with ‘apt-mark’ and this article will explain how. Obviously, this method is only effective if you use a Linux distro that has an APT-based package manager.

For the most part, you should always keep your software updated. However, that’s a rule for the Ideal World®. For the rest of us, those of us that live in the Real World®, you’ll almost certainly run into an eventuality that requires you to keep an existing, specific version of software.

While entirely stupid and irresponsible, I kept a version of Thunderbird past its due date because the update simply ruined my existing installation. I only kept that outdated version long enough to make the leap to a more recent distro version. The tool I used to prevent application updates was apt-mark.

You will have your own reasons, from compliance to stability to functionality, for keeping the same version of your installed software. You should only use this sparingly, only as necessary, when there’s simply no other solution. This should also be a temporary measure. You should always try to use the upgraded software because there are (possibly) security implications if you don’t.

A little about APT

While we’ll technically be using ‘apt-mark‘, it should be mentioned that APT stands for Advanced Package Tool. It’s the default package manager that is used in many distros, mostly Debian and those of Debian descent. So, you’ll see it in everything from Ubuntu to Linux Mint. 

In the desktop scene, I suspect it’d be the most common of all package management tools. Even if you use a different distro with a different package manager, you should probably have a basic familiarity.

Using ‘apt-mark’ hold and unhold

The tool we’ll be using is ‘apt-mark’, and the man page helpfully defines it as:

apt-mark – show, set and unset various settings for a package

We’ll only be concentrating on a couple of commands, those necessary when you want to prevent application updates, plus one extra command that will help you keep track of the two commands we’ll be focusing on.

The first of those two commands is ‘hold’. This command is used when you want to ‘hold’ a package at its current version, preventing upgrades. Remember, this should really be used only when there’s no other solution, as many upgrades fix security issues as well as bugs. It’s actually a fairly simple command.

When you enter this command, you’ll get a confirmation message. It will tell you that the application is now being held. It will remain held until you ‘unhold’ it. So, it’s a set-it-and-forget-it type of deal, though you shouldn’t really forget it. You should undo it as soon as you realistically can.

To reverse the restriction, resuming your normal updates, you simply need to ‘unhold’ it. The command is fairly obvious, and it looks like this:

That will free the hold on the package and tell you that the hold has been lifted. The package should then upgrade as necessary and as issued. If new upgrades show up in the repositories, it should function as normal and upgrade like it did prior to the hold.

If you are like me, you may well forget that you’ve held packages back. The package names are often long and nonsensical, so they’re easy to forget. In the heat of the moment, you may have forgotten to make a note of the package(s) you’ve held.

Don’t worry, ‘apt-mark’ has you covered! When you want to know what packages are being held, just run this command:

Note the lack of ‘sudo’ in that command. You don’t need sudo because you don’t need elevated permissions to list held packages. You only need elevated permission if you want to change something. As that command only lists them, you can run it as a normal user.

The apt-mark command has a ton of other uses, this is not an all-inclusive article. You can always see the man page for more help and the rest of the features. This article is only covering the ‘hold’ and ‘unhold’ functions. Maybe there will be another article covering other aspects, but this limited in scope – preventing application updates.

Like always, thanks for reading and I appreciate the feedback! Don’t forget that the site has ads enabled and that you can donate. So, if this article helped you learn how to prevent application updates then show some love! Otherwise, sign up for the newsletter or share this article with your friends on social media. Thanks!

 

Subscribe To Our Newsletter
Get notified when new articles are published! It's free and I won't send you any spam.
Linux Tips
Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 International License.