Zorin OS (Linux) source update

Today I finally decided to fix several
errors that were happening while I was updating a Zorin OS box.

I update over the network using ssh, but this will also work if you do it
from the terminal.

First, we will update the source list

sudo apt-get update

Now we will run the updates

Sudo apt-get upgrade

All normal now. I mean, we run these commands weekly right? (or at least you
have your system to auto update)

The difference today is that we will read the output.

Lets fix the easy parts fix. Most likely we have old kernels (when running
upgrade it would have notified you)

sudo apt-get autoremove

That was easy…but wait, it is possible that it will complaint about running the auto
loader because a symbolic is damaged. Silly link. Usually this does not cause
problem, but lets just fix it. The exact error is “The link /initrd.img.old is a
damaged link “ “you may need to re-run your boot loader[grub]”

sudo update-grub

OK, now that is fixed, lets fix the other possible errors.

Running update we could get either or both of these errors

We could google the errors. That is the easiest way, and probably how you got
here, but let’s do the short version instead.

The Google error looks worse so lets take a look at it.

It is complaining that the package could not be found. This is because Google
Chrome is not available in 32-bit anymore. So first lets check If your system is
running a 64-bit OS

uname -a or you can also use arch

If you would like more information check this page


http://www.howtogeek.com/198615/how-to-check-if-your-linux-system-is-32-bit-or-64-bit/

If your system is i386 or 686 then the best option is to uninstall Chrome,
or re-install Linux using 64-bit. If you are running 64 bit (x86_64) then we can
switch the repository.

To switch the repository to 64 bit you will have to modify the google sources

cd /etc/apt/sources.list.d/

Once inside the folder then we will edit using nano

sudo nano google-chrome.list

Once we have the list open, we can
see that most likely there is only 1 entry and it is for Chrome. To this entry
we will add right after deb and before the link,
[arch=amd64]
. This will force apt to download the 64 bit
binaries. The line should look as

deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main

Now we can update the repositories again and that error will be gone. Then
run an upgrade to update Chrome. You can also for an install by entering

sudo apt-get install google-chrome-stable

This is easier and faster than it seems, but I don’t like to post commands
without explaining what they do

That is all. Good night…..Just kidding, we still have an Opera issue.

Opera has been moved to the repository, so the easiest thing to do is just
remove the source. Remember that to fix Chrome we went to the sounces.list.d
folder? We should still be there. Run a directory listing (ls -la) and you will
see 2 files.

  • opera.list
  • opera.list.save

You have 2 options. You can comment out the line or just directly remove the
file.

Before though, I would check whether you have it installed.

sudo dpkg --get-selections | grep opera

If nothing shows, then it is not installed. Simply comment out or delete the files (I suggest to delete to keep a clean system).
That is it.

If it was installed, simply remove it, then comment out or delete the source
file.

If you like Opera download the deb from their web page


http://www.opera.com/computer/linux

It seems like a lot of work, but honestly I have no paid attention to the
errors for quite a while. So it is not as bad. All of these can take less than
10 minutes to fix if you just enter the commands.

I had to search a bit, and still took me about 30 minutes to get everything
fixed, which is not bad.

The Chrome information I got it mainly from a Reddit page. Opera from the
Ubuntu forum. I had to customize a bit the commands because they were for Ubuntu
Vanilla, and I am working from a Zorin OS (based on Ubuntu/Mint), but the
commands should work in all flavors. This is the main reason I explained what
they do

At the end I also like to do a reboot to make sure everything is working
peachy :). It is a good practice, because if something is not working as it
should, the information is still fresh in your mind and it is easier to
troubleshoot. To make it clean I also always restart before I start.

Advertisements

If you would like to comment, please refer to which section of the article you liked so I know you are not a spammer. Too many out there :)

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s