I did another install of 42.3 on Thursday. I guess I’m a tad slow reporting that. This install was for Build 0283. I installed it on my main desktop. At the moment, I am still running 42.2 on that computer. I installed 42.3 on a separate area of the disk.
I do plan to soon switch to running 42.3 full time. That’s the best way of testing this beta release. The final release is due in about one month.
Downloading and installing
I followed my usual procedure. I used “aria2c” to download the iso for the DVD installer. I used “wget” to download the sha256 checksum file. Then I verified the gpg signature on the checksum file, and verified that the checksum matched the downloaded iso.
The next step was to write the iso file to a USB flash drive. I used “dd_rescue” for that. Then I booted the USB, and installed 42.3
Installation itself went well. Everything worked about as expected. Following the install, I booted into 42.3, and did a little final tweaking. And I also added additional software that is not on the install media but is in the repos.
Release candidate 2 (or RC2) is now out. It was announced earlier today:
As you might expect, I downloaded the iso for the DVD installer, and “burned” that to a USB flash drive. I then did an install using it.
The install went quite well. I followed the same general method as in my install for RC1.
I noticed one change. Early in the install, I was told about “Mesa-dri-nouveau”. This is a new package, broken out from mesa. The notification asked me whether I wanted to accept this package. If I did not accept, then 3D would be emulated in software.
I accepted the package. I cannot test it otherwise.
Unfortunately, it does not work well enough with my nvidia card.
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.
A recent announcement from openSUSE listed new live media (iso files) for Argon and Krypton. Argon is based on Leap 42.1, while Krypton is based on Tumbleweed.
The openSUSE team maintains development repositories, in addition to the standard repos for the distributions. The development repos are where they build new or updated versions of the software for testing prior to adding that software to the standard repos. Both Argon and Krypton include some of these development repos.
For this month, I installed Tumbleweed on my laptop. I had installed Leap 42.1 to overwrite my previous Tumbleweed install on that laptop.
This computer uses legacy booting. I gave Tumbleweed a 40G partition, which I formatted as “ext4”. I also allowed it to use the swap and home file systems from my encrypted LVM on that computer.
I mounted the home file system to “/xhome”. That left “/home” as part of the root file system. So I created symbolic links into “/xhome” for most of my saved files. Doing it this way allows me to avoid conflicting desktop configurations. So the new install has its own “.config” and “.kde4”, but uses the same “$HOME/bin” and document directories as my other installs on that box. Read More…
The release candidate for Leap 42.1 was published on Thursday. So I downloaded and installed.
It is mostly looking pretty good. There is a glaring bug when you login to Plasma 5 (or KDE) — namely “kdeinit5” and “Kmix” crash. However, there’s an easy workaround. This should be fixed by the time of the final 42.1 release.
Apart from that one problem, it looks pretty good. I’m sure there are other bugs, but mostly it all works.
Up through Beta1, “ecryptfs” was missing. But it is now there. Most of the software that I normally use is there. One exception is “sendmail”, but I don’t really need that. Read More…
The beta1 release was announced on Thursday. So I downloaded and installed.
The downloading went smoothly. I used “aria2c” to download “openSUSE-Leap-42.1-DVD-x86_64-Build0186-Media.iso” (the DVD installer iso for beta1). Then I used “wget” to download the sha256 checksum file “openSUSE-Leap-42.1-DVD-x86_64-Build0186-Media.iso.sha256”. Then I used “gpg” to verify the signature of that checksum file. Finally, I used the “sha256sum” command to computer the checksum of the downloaded iso, and compare that to the checksum in the “.sha256” file.
A bit more detail. On the download page for the development version, I checked the box for “Pick Mirror” and clicked “download”. That gave me a list of mirrors and it gave me the url for the meta4 download link. I copied that link, and used it as an argument for “aria2c” on a command line to download the iso. Then I replaced the final “.meta4” with “.sha256” in that link, and used that with “wget” to download the sha256 checksum file. Read More…
Milestone 2 for Leap 42.1 was announced on Friday. So, naturally, I downloaded the install DVD iso, and attempted an install.
Both the download and the install went quite well. As usual, I wrote the iso to a USB flash drive, and used that for installing. I installed Leap on its own (unencrypted) partition, but with swap and home coming from an existing encrypted LVM. I mounted the home volume from the LVM as “/xhome”, so that “/home” is actually part of the root partition. The idea was that users could symlink back to files in “/xhome” to make their usual files/directories available. But desktop configuration would be kept separate to avoid conflicts between different desktop versions.
Trouble began with the first boot. I was prompted for the encryption key, but the system was not reading the keyboard and this prevented entering the key.
In my previous post, I described my experience in downloading and installing opensuse Leap 42.1 Milestone 1. That was a week ago. I’ve booted Leap every day since then. So it’s time to add to my previous report.
Overall, Leap 42.1 appears to run well. I have seen relatively few bug reports, and not too many problems mentioned on the forum. I take that as a good sign.
That booting problem
In my prior post, I did mention that Leap would not boot. And I described a workaround that I used to get past that. I have since reported that problem as bug 939411. It turns out that this is essentially the same problem as I had previously reported for Tumbleweed, as bug 911319. Apparently the fix for that had not been backported to the SuSE enterprise system on which Leap is based.