Since my last post on Leap 15.0, Build 139.1 was released. It was time for a new install, so I downloaded the iso. And then I installed to a virtual machine.
I ran into some interesting bugs.
It told me that my EFI partition (at 33M) was too small. Well, I agree that’s small. But it is what an earlier build of 15.0 had created. It looks as if they have adjusted to a more reasonable size.
I told the installer to go ahead, in spite of the small EFI partition size. And I then ran into an additional bug. The installer said that some devices (the ones to which I was installing) did not exist. See bug 1082143 for details.
The installer allowed me to continue in spite of those errors. And the install was successful. So the errors were bogus.
A Tumbleweed install
Back to Tumbleweed. Actually, that Leap 15.0 is part of the background. I decided to try installing Tumbleweed into the same virtual machine where I had just installed Leap 15.0. However, this time I would allow it to delete everything on disk and make a fresh start.
There have been several Tumbleweed snapshots over the last few days. But today we saw the first with a 2018 snapshot date. So I decided to do a test install.
As usual, I used “aria2c” to download the iso (“openSUSE-Tumbleweed-DVD-x86_64-Snapshot20180101-Media.iso”). I also downloaded the sha256 checksum file. I then verified the gpg signature on the checksum file. Then I verified the checksum on the iso, to make sure that I had a good download.
I saw the announcement for Tumbleweed snapshot 20171022. So I booted up Tumbleweed in the KVM virtual machine on my desktop. And I ran “zypper dup” to apply the update. I then rebooted.
Then came the surprise. I had been using “lightdm” to login to the desktop. But, after reboot, the login screen appeared to be from “gdm”. I logged in, which took me to the KDE Plasma 5 desktop. And, from there, I checked the displaymanager setting in “/etc/sysconfig”. And that still said “lightdm”. Hmm, something was up.
Last month, I created a Tumbleweed Virtual Machine (or VM), using KVM. Yesterday’s project was to install into that existing VM. I wanted a clean install, retaining “/home” but reformatting everything else.
Fortunately, that previous install was for UEFI booting. I’m not sure how easy it would have been to do new install into the same BIOS based virtual machine.
I started by downloading the DVD installer for Tumbleweed snapshot 20171007. As usual, I downloaded the sha256 checksum file with “wget”, and I downloaded the iso itself using “aria2c”.
I then verified the gpg signature on the sha256 checksum file, using gpg. Then I used “sha256sum -c” to verify the checksum of the download iso file.
It was time for another Tumbleweed install.
This time, I decided to use KVM and install Tumbleweed into a virtual machine.
As is my usual practice, I went to the Tumbleweed download site. There, I found the latest image for snapshot 20170913. I downloaded the DVD iso image (64-bit version) using “aria2c”. And I downloaded the sha256 checksum file using “wget”.
Next, I used “gpg” to verify the signature on the sha256 checksum file. And then I used “sha256sum -c” to verify the checksum of the DVD iso file.
I’m no longer doing monthly installs of Tumbleweed. But I do installs when there is a reason.
In this case it was another computer. And what use is a computer without some form of linux?
My wife purchased a new laptop for use with Windows 10. So I got the previous laptop as a hand-me-down. I already have a laptop with Windows 7, and also dual-booting to openSUSE. So I did not need another Windows 7 system. So this became my linux laptop.
Around two months ago, another computer died. That was an older desktop — the one with an nVidia graphics card. That older desktop is now in computer heaven (otherwise known as the electronics recycling center). With the arrival of this hand-me-down, I’m now back to my former number of computers. But this one has Intel graphics, so I no longer have anything with nVidia graphics.
I wanted to use an encrypted LVM for this install. And I find it more convenient to prepare the disk ahead of time.
Recently, openSUSE Tumbleweed updated Gnome to version 3.24. So I decided to give it a test. And I ran into some “problems”. This post will discuss those problems.
Gnome under Wayland
My oldest Tumbleweed system was installed in November 2014. And that’s where I first tested Gnome. At the time, I was using “sddm” for logins. Selecting “Gnome” on the login menu gave me a Gnome session running under X11. This was as expected. There was also a menu item for “Gnome-Wayland”. Selecting that gave me Gnome running under Wayland for managing the graphics.
I later switched to using “gdm” as login manager. And, with “gdm”, selecting “Gnome” gave me a Wayland session.
Next, I tried on my laptop. Tumbleweed was installed there on March 14 this year. I was already configured to use “gdm” for logins there. But, try as I did, I was unable to get a Wayland session for Gnome.
It has been a few months since I last tried installing Tumbleweed. I wanted to install on my laptop, to test the latest version of NetworkManager.
The install went pretty well. The most obvious problem was a black screen on the first boot of the newly installed system. But that was not as bad as it sounds. I’ll give more details below. The install was for snapshot 20170314.
As is my usual practice, I used “aria2c” to download the iso, and I used “wget” to download the sha256 checksum file. Both were the 64-bit versions.
I downloaded both the DVD installer and the live rescue CD.
After downloading, I used
gpg --verify filename.sha256
to verify the gpg signature on the checksum file (where “filename” depends on whether this was for the live CD or the DVD installer.
I then used
sha256sum -c filename.sha256
to verify the checksum of the downloaded iso file.
After download, I wrote both isos to USB devices. My typical command for this is
dd_rescue filename.iso /dev/sdd
where “/dev/sdd” is the device where the USB shows up. I used a 4G USB device for the live rescue CD, and an 8G USB for the DVD installer.
I then booted the live rescue CD on two systems. It booted up without any difficulty. On the first boot, a hybrid partition was created, where any changes made can be saved to disk. Read More…
It has been a while since I last installed Tumbleweed. I decided that it was time to again check the installer.
The Tumbleweed system that I already have installed had desktops KDE, Gnome, XFCE and LXDE. But for recent intstalls (as with Leap 42.2), I have been going with KDE, Gnome, XFCE, LXQt, FVWM and MATE. So it seemed reasonable for the new Tumbleweed install to follow the same path. I also added Enlightenment for experimenting.
As usual, I downloaded via the command line. The install was for snapshot 20161128. I chose to download both the DVD iso and the rescue iso.
For the rescue iso, the commands that I used were:
wget http://download.opensuse.org/tumbleweed/iso/openSUSE-Tumbleweed-Rescue-CD-x86_64-Snapshot20161128-Media.iso.sha256 gpg --verify openSUSE-Tumbleweed-Rescue-CD-x86_64-Snapshot20161128-Media.iso.sha256 aria2c -V -R http://download.opensuse.org/tumbleweed/iso/openSUSE-Tumbleweed-Rescue-CD-x86_64-Snapshot20161128-Media.iso sha256sum -c openSUSE-Tumbleweed-Rescue-CD-x86_64-Snapshot20161128-Media.iso.sha256
And, for the DVD iso, I similarly used:
wget http://download.opensuse.org/tumbleweed/iso/openSUSE-Tumbleweed-DVD-x86_64-Snapshot20161128-Media.iso.sha256 gpg --verify openSUSE-Tumbleweed-DVD-x86_64-Snapshot20161128-Media.iso.sha256 aria2c -V -R http://download.opensuse.org/tumbleweed/iso/openSUSE-Tumbleweed-DVD-x86_64-Snapshot20161128-Media.iso sha256sum -c openSUSE-Tumbleweed-DVD-x86_64-Snapshot20161128-Media.iso.sha256
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.