I’m a tad slow reporting this.
Release candidate 1 (or RC1) for 42.2 was announced on Tuesday. I downloaded the DVD installer, and proceeded to install on three computers.
For the most part, everything went well. I noticed a couple of cosmetic issues. And Plasma 5 still won’t run under “nouveau” (with a Nvidia card). But at least there is a good workaround for that. I’ll discuss these in more detail below.
Gnome shows as version 3.20.2. To find that, I logged into Gnome, right-clicked on the desktop and selected “Settings”. On the window that showed up, I clicked “Details” to find the version.
Beta3 was announced yesterday. So, naturally, I prepared to download and install. We are getting close to final release time for 42.2. The biggest change for Beta3, is that Plasma 5 (or KDE) is now at release 5.8.
Download and install
As with prior development releases of 42.2, the download and installation went smoothly. I followed my normal practice of “burning” the DVD image to a USB flash drive. I then booted that flash drive to start the installer.
I have done three installs. Two of those were yesterday, and the third was this morning.
As with my previous installs, I have been installing to an encrypted LVM (two installs), and to an unencrypted partition but using the home file system from an encrypted LVM on the other install.
Download and install
I saw the announcement on Thursday morning. I immediately started a download. As is my practice, I used “wget” to download the sha256 checksum file, and “aria2c” to dowload the DVD installer iso. Once downloaded, I verified the gpg signature on the sha256 checksum file, and then used that file to verify the downloaded iso. That’s probably redundant, because “aria2c” does verification checks during the download.
Next, I wrote the downloaded iso to a USB flash drive. I used an 8G flash drive, and wrote with “dd_rescue”.
Rebooting the system, I hit F12 during boot. For that computer, it brings up a BIOS boot menu which allowed me to select booting from the USB flash drive.
I used the torrent from the announcement for download (with “ktorrent” as the client). The download went well. I then checked the sha256 checksum from the announcement. and that looked good. So I “burned” the installer image to an USB flash drive with
# dd_rescue Solus-184.108.40.206.iso /dev/sdd
We are getting nearer to the release date (November) for Leap 42.2. And the first beta release was announced on Wednesday. It was time for me to get busy and do some testing.
I used “aria2c” to download the iso, and “wget” to download the sha256 checksum file. I verified the “gpg” signature on the checksum file. And then I checked the sha256 hash of the downloaded iso against the checksum file. Everything checked out.
Next, I “burned” the iso to a usb flash drive, with:
dd_rescue openSUSE-Leap-42.2-DVD-x86_64-Build0164-Media.iso /dev/sdd
(“/dev/sdd” happens to be the device name for the first USB drive on this system).
I then booted from that USB to install beta1. My first install was on Wednesday. That was to a UEFI box, with secure-boot enabled. My second install was yesterday (Thursday), to an older computer with legacy booting. Both installs went smoothly.
The quick “tl;dr” version — updates don’t work, but updating is still possible.
I installed kubuntu-16.04 in April. Although I don’t use it much, I occasionally boot into it to check a few things. Whenever I booted into Kubuntu, I looked to see if the update applet was notifying me of updates. I left the system running for an hour or more, to give it plenty of time to find out.
It never showed any updates.
So I clicked on the applet (hidden tray icon) and asked it to check for updates. It told me that my system was up to date.
On opensuse forums, I often see complaints about KDEwallet (or “kwallet” for short). It can be annoying at times. In this post, I’ll indicate ways of keeping it under control.
While this is oriented toward opensuse, it should also apply to other distros with one caveat. In opensuse, some of the applications have their settings and configuration under the directory “$HOME/.kde4”. For other distros, it is more typical to use “$HOME/.kde” (without that final “4”). So just adjust my suggestions accordingly.
Starting with Leap 42.1 (and with Tumbleweed), opensuse now supports Plasma 5. And Plasma 5 keeps its configuration under “$HOME/.config” and under “$HOME/.local”. But there remain some older applications with configuration in the old location.
To further complicate things, there are now two versions of “kwallet”. I’ll call them “kwallet4” for the old version still used by some older software, and “kwallet5” for the newer version (for Plasma 5). That both wallets are there, and that they might independently prompt you to open the wallet, is part of the confusion.
I’ve simplified my life, so I am no longer doing regular monthly installs. But I still do occasional installs.
In this case, the occasion was a topic at opensuse forums:
A user was not sure how to install without a network. So I decided to do an install, to make sure that this was still possible.
I began by downloading the latest snapshot. I first used
to download the sha256 checksum file. That’s a small file (654 bytes), and I find it easier to use “wget” for small files. I then verified that file, using
gpg --verify openSUSE-Tumbleweed-DVD-x86_64-Snapshot20160813-Media.iso.sha256
The file itself has a gpg signature, so checking that signature is sufficient to verify the download.
I saw the announcement yesterday, so I downloaded and installed alpha3. I’ll note that I skipped alpha2, because it was mainly for testing Gnome and I’m don’t much use Gnome (though I do install it).
I downloaded the DVD installer (file “openSUSE-Leap-42.2-DVD-x86_64-Build0109-Media.iso”, of length 4647288832). After verifying the sha256 checksum and the gpg signature of the checksum file, I wrote the iso to a USB flash drive.
My install was to a UEFI system, with secure-boot enabled. I installed into an existing encrypted LVM. The install went quite smoothly.
This is mostly a followup to my earlier post on testing Slackware 14.2. Since then, I have spent a little time using the installed slackware. So here are some of my notes.
In my earlier post, I noted that slackware does not use repos in the way that many distros do. I got back a comment, informing me that the Slackware user community is maintaining repos, and that there are package managers available to access those repos.
It’s always great to see this kind of involvement of the user community.
I had installed Slackware onto its own partition. However, I also have an encrypted LVM on that box, which I use with opensuse. So I wanted to be able to access that from Slackware. The encrypted LVM includes a home volume and a swap volume, and I wanted to mount those. Specifically, I wanted to mount the home volume to “/xhome” so that I could add symbolic links to it. And I wanted to use the swap volume as swap for slackware.