Mint 17.2 has recently been released and I’m pretty sure I read somewhere that all I had to do was keep installing the usual series of updates and the OS would automatically be updated to the new version; however, that doesn’t seem to be happening.
I checked on my current installation using the Terminal command:
This confirmed that I was still running Linux Mint 17.1 Rebecca. Updating to Linux Mint 17.2 Rafaela is a four-step process.
(1) Run Update Manager, navigate to Edit – Upgrade to Linux Mint 17.2 Rafaela, keep pressing “Continue” until the “Requirements” tab is reached and use the first control button to install mint-meta-mate.
(2) Now, check the box marked “I understand the risk. I want to upgrade to Linux Mint 17.2 Rafaela” and press “Apply”.
(3) Reboot the computer (at which point the grub menu will still display Linux Mint 17.1)
(4) Use the Terminal command:
Next time the machine is booted, grub will show the (correct) option for Linux Mint 17.2
What version and flavor of Mint am I running?
Linux Mint 17.2 “Rafaela” MATE released!
Sometimes when trying to find a text string in Firefox, by using the Edit – Find command, it’s difficult to locate the result on the screen because of the text highlighting colour. One of the things I really like about Linux, and many of its associated programs, is that it is often easy to apply some form of customization. However, that’s not to say that the process is necessarily intuitive – and this is certainly the case for changing Firefox’s text highlight colour.
The other thing that no longer worked after my upgrade from Linux Mint 13 to Mint 17 (Moving from Mint 13 to Mint 17) was KAlarm. I installed this using Software Manger but, when I ran the program, I received the error message “The Akonadi personal information management service is not operational.”
Having updated from Linux Mint 13 to Mint 17, primarily to fix a problem with custom application launchers (see previous post), it’s ironic that one of the things that doesn’t work after the upgrade is the application launcher(s) in question! However, it turns out that there is an easy fix.
Recent updates to Linux Mint 13 (Maya) broke the custom application launchers to shutdown and restart my system at one click of the mouse. It wasn’t immediately obvious which of several updates was the culprit and, rather than put in time searching for the problem, I looked for an alternative solution. In particular, I have been wondering about when I should transition from the Mint 13 long-term support (LTS) version to Mint 17 LTS. I decided that I should upgrade the entire system and, hopefully, fix my launcher problem at the same time.
Once my problem with BitLocker disk encryption was solved (see previous posting), it was back to trying out Magic Stick as a bootable Linux/Android device. The instructions posted in the xdadevelopers forum indicate that “The installation procedure is extremely simple”. By “installation” the writer means booting from the USB drive since the instructions don’t actually include details of how to install either Linux or Android to the T100’s SSD. However, the “extremely simple” part is true – with one small caveat (see notes 2 and 3 below).
In my previous posting, I indicated that my attempts to install Linux on the T100 had eventually lead to my bricking the machine and, after it had been restored to health by an Asus Service Centre, I was planning to sit back and see how things developed. However, in a comment to my posting, “tr3w” suggested that I should continue using Linux through a bootable USB drive. Then, recently, in the Asus T100 Ubuntu Google+ Group, Ciprian Negrila indicated that the “Magic Stick” software would allow either Ubuntu or Android to be booted from a USB drive – without the dreaded mmcblk0rpmb timeout errors! Now, this sounded too good to miss, so I downloaded the Magic Stick package, installed it on a USB drive, disabled Secure Boot on the T100, and booted into the USB drive – only to be greeted by a “Preparing BitLocker Recovery” screen!