Tag Archive | beta testing

Notes on OpenSUSE Leap 15.0

Since my last post on 15.0, there have been several new beta releases.  We have seen Build115.1, Build 124.1, Build 127.1, Build 128.1 and Build 129.1.

With that many builds, I have not been downloading them all.  I have been updating my 15.0 systems.  I am updating them in the same way that I update openSUSE Tumbleweed.  That is, I am using

zypper dup

to update from the repos.  My most recent install attempts have been with Build127.1, though most of my systems are now updated to the latest version.

Overall picture

Things are mostly going well with 15.0.  The final release is still planned for May.  But if you want to take a look at pre-release versions, then now is a good time to try.

What I have tested is mainly working well.  There are still a few bugs in the partitioner, as used for install.  Some of those bugs have already been fixed in the latest updates.

Read More…


OpenSUSE Leap 15.0 Beta

Build 109.3 of Leap 15.0 was announced on Friday.  So I download and installed.  With build 109.3, it is now announcing itself as a Beta release.  Previous releases that I tested have indicated that they were Alpha releases.


I followed my usual practice of downloading with “aria2c”.  I am using the download site download.opensuse.org/distribution/leap/15.0/iso/.  I first used “wget” to download “openSUSE-Leap-15.0-DVD-x86_64-Build109.3-Media.iso.sha256” (the checksum file).  I then verified its gpg signature.  Next, I downloaded the iso itself.  And I used “sha256sum” to verify the sha256 checksum.  And, following that, I wrote the iso to an 8G USB flash drive. Read More…

OpenSUSE Leap 15.0 Build 84.1

I notice, on Thursday Jan 4th, that Build 84.1 was available at the download site.  So I download, and did some testing.


As is my usual practice, I used “aria2c” to download the iso, and I used “wget” to download the checksum file.  I then verified the “gpg” signature on the checksum file, after which I used the checksum to verify the downloaded iso file.


My first test was to update an existing 15.0 system.  For that, I wrote the iso to a USB flash drive.  I then configured that flash drive as a repo.  And, following that, I used “zypper dup” to bring the existing 15.0 system up to date.  When I do this, I can see that most of the updated software comes from the local USB that I configured as a repo.  Some updated software comes from the online repos.  The “zypper” command seems to recognize that the repo on the local USB is to be preferred to the online repo, when the software is available in both places.

Read More…

OpenSUSE Leap 15.0 Build 79.1

The next Leap version, 15.0, is still showing as an alpha release.  Still, I was happy to see the install iso for Build 79.1 show up at the download site last Wednesday.  At around the same time, there was an update message on the factory mailing list, reporting the current status of Leap 15.0.

According to that update message, the current aim is for a final release in May of 2018.  That seems more realistic than the earlier (Feb/March) suggestion.


When I noticed that the iso was available, I of course downloaded it.  I followed my usual practice for this:

wget http://download.opensuse.org/distribution/leap/15.0/iso/openSUSE-Leap-15.0-DVD-x86_64-Build79.1-Media.iso.sha256
aria2c -V -R http://download.opensuse.org/distribution/leap/15.0/iso/openSUSE-Leap-15.0-DVD-x86_64-Build79.1-Media.iso
gpg --verify openSUSE-Leap-15.0-DVD-x86_64-Build79.1-Media.iso.sha256
sha256sum -c openSUSE-Leap-15.0-DVD-x86_64-Build79.1-Media.iso.sha256

In turn, those commands download the sha256 checksum and the iso itself.  Then they verify the gpg signature on the checksum file, and the checksum of the downloaded iso file.

Read More…

Another install of Leap 42.3 Beta

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.

Read More…

OpenSUSE Leap 42.2 RC2

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.

Nouveau graphics

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.

Read More…

OpenSUSE Leap 42.2 RC1 — a review

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.

Read More…

OpenSUSE Leap 42.2 Beta3

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.

Encrypted LVMs

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.

Read More…

Argon and Krypton

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.

Read More…

Tumbleweed install for November

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…