Jump into Jammy Kubuntu 22.04 LTS

[NoWorries]

It is now 4 months before the release of Jammy Jellyfish LTS.

Up to this stage of development Jammy has had only two hitches from my perspective. The first was that some iso file dates would not boot Jammy and the second was grub 2.06-2 not coping with multiple OS installations.

Several helpful contributors to this forum have given advice to resolve these hitches. Even though this is a per-pre-pre-pre-release (many thanks claydoh), I find that I use it without apprehension for everything I do, including Presentations, in public, with LibreOffice.

Now for a list of the progress by developers since the last month. This is listed below for the items in the Info Center.

	Last Month Status	4 Month Status
KDE Plasma Version	5.23.3	5.23.4
KDE Frameworks Version	5.88.0	5.89
QT Version	5.15.2	5.15.2
Kernel Version	5.15.0-11-generic	5.15.0-13-generic

This list doesn't include the many applications which have been upgraded. For example, Kdenlive and Dolphin are both at versions 21.12.0 as well as others.

I must confess that when I was faced with Jammy hitches, I de-selected Pre-released and Unsupported updates. I now have reversed this decision and I am also using the non-standard repositories:

sudo add-apt-repository ppa:kubuntu-ppa/staging-plasma
sudo add-apt-repository ppa:kubuntu-ppa/staging-frameworks
sudo add-apt-repository ppa:canonical-kernel-team/unstable

As stated above, I find that, for me, Jammy is very reliable. The developers have done a great job and I like the evolutionary approach to development as this minimises any stumbling blocks.

[claydoh]

https://github.com/rhboot/grub2/comm...e580c66f517666
https://wiki.archlinux.org/title/GRU...rating_systems

So, it seems to me that it may be just a pass-the-buck security 'fix'
And we are being Chicken Little crossing the road to count her eggs here, as the mailing list thread is discussion toward which method to use for this change by Grub.
Option '0' is the easiest - just re-enable it in the config, as the default setting.

Of course it creates fun here, during the pre-pre-pre-pre-pre-release state of development at this stage of 22.04's life.

[NoWorries]

+++ A safe solution needs to be found for being able to choose other OS installations. Otherwise I will have to resort to the approach that I used in my previous post to restore all my OS installations.

[MoonRise]

Wow!

Dual-booting and multiple OS installations isn't uncommon! This issue is going to create a lot of user angst.

I can say it will here. That really is a poor decision.

[Snowhog]

See: https://lists.ubuntu.com/archives/ub...er/041769.html

Wow!

Dual-booting and multiple OS installations isn't uncommon! This issue is going to create a lot of user angst.

[acheron]

See: https://lists.ubuntu.com/archives/ub...er/041769.html

[NoWorries]

I am beginning to wonder if the developers are being affected by Covid-19 as the latest updates to grub left me with one operating system Kubuntu 22.04. Kubuntu 21.10 and Windows 10 were not listed.

To avoid re-installing either versions of Kubuntu, I decided to look into Grub. I edited /etc/default/grub and added the line

GRUB_DISABLE_OS_PROBER=false

I made sure that os-prober was installed and I followed this by

sudo update-grub

This did not solve my problem other than giving two identical systems with Windows 10.

To make sure that I had all systems detected I ran

sudo grub-mkconfig -o /boot/grub/grub.cfg

Once again I had two identical Kubuntu systems as well as Windows. This time I decided to expand the Advanced options under 21.10 and selected the top entry. This gave me Kubuntu 21.10 and I then used grub customizer to re-instate my boot options and I am now back to normal with grub 2.06-2 installed on Kubuntu 22.04.

At least, if I get another grub update which reduces my system to one operating system, I now know how to deal with it.

[jlittle]

grub issues...

I suppose if you want to test the full stack from iso to installed system, you test all the bits, including grub.

But, grub always screws up for me, too often sooner rather than later, so I try not to install grub or other boot-loader as part of an OS install. I use an existing grub set up, independent of any OS install, living in its own btrfs subvolume, to boot my test jammy installs. For the debian-derived installs that I keep for a while, I uninstall grub-efi-amd64 and, if I need grub stuff, install grub-efi-amd64-bin instead, which "will not automatically install GRUB as the active boot loader nor automatically update grub.cfg on upgrade".

[NoWorries]

Just over a day ago, I updated my Kubuntu 22.04 installations on my HP Laptop and then on my ASUS Laptop. My ASUS failed to boot past a message saying that I had to load the kernel first. My HP which has Windows 10, Kubuntu 22.04 and Kubuntu 21.10 on it, only booted up Kubuntu 22.04 and there was no indication of any other partitions even after installing grub-customizer.

To get my systems back again, I downloaded Kubuntu 22.04, 9th December, and created a USB installation disk. This failed to start on my ASUS and left me with a blue screen of death!!!

So I got an ISO dated 24 November and that successfully did the installation on my ASUS. After doing the backlog of packages to install, I then selected the pre-released updates for installation. After completing the updates, I was once again faced with a system that would not boot because the kernel needed to be loaded. I repeated the installation, but this time I did not select the pre-released updates and I had a workable system on my ASUS.

I then went back to my HP Laptop and used my Kubuntu 21.10 USB to install Kubuntu 21.10. I then used grub-customizer to define the startup screen for the selection of Kubuntu 21.10, Kubuntu 22.04 and Windows 10 as all these systems were still on my HP disk. So I go my system back.

I then went back to Kubuntu 22.04 on my HP Laptop and found the version of grub that I suspected was causing all my problems. It was version 2.06-2ubuntu2.

The following day I found that the Kubuntu 22.04 ISO for the 10th December gave a USB that worked for installing Kubuntu 22.04. So I had another go at installing Kubuntu 22.04 on my ASUS. Once again, after updating with the pre-released updates, I got a system that would not boot because the kernel was not loaded.

As I am not familiar with Grub functions and let alone editing grub, I decided to re-install Kubuntu 22.04, but this time I used Muon to lock all packages starting with "grub". The locked versions on my ASUS are 2.04-1ubuntu48. After doing all the pre-released updates on my ASUS system, it now works like a charm. It is worth noting that there are 48 updates to grub 2.04, whereas there are only 2 for grub 2.06.

So if you are having boot problems with a Kubuntu 22.04 installation, your problems may be resolved by locking grub before doing updates.

[cookiemuncher]

Did you verify the checksum on the downloaded ISO before burning it to your bootable media?

From the site:
949685f6d26fb90ebd00d2f1ab0ff509fbc78e38012eebb51c 237eb2d9668517 *jammy-desktop-amd64.iso

~/Downloads$ sha256sum jammy-desktop-amd64.iso
949685f6d26fb90ebd00d2f1ab0ff509fbc78e38012eebb51c 237eb2d9668517 jammy-desktop-amd64.iso

Download checks out OK. I'll try again with the today's release when it appears.

[TWPonKubuntu]

Just upgraded to Jammy 22.04 LTS. So far, no problems and it looks nice. Downloaded .iso to USB stick, booted from USB and added my wireless connections (OK). Install took about 25 minutes with updates. Now I'm cleaning up my desktop to include many tools that were not automatically found by the install utility.

[Snowhog]

Rebooted and running Jammy Desktop.

[Snowhog]

I'm "doing the deed" and am in the processes of upgrading from 21.10 to 22.04 on my laptop as I type.

[Snowhog]

Did you verify the checksum on the downloaded ISO before burning it to your bootable media?

[cookiemuncher]

Anyone know what this means? Downloaded the latest release of Kubuntu 22.04 and that is what I get when attempting to boot into it .

incompatible license
Aborted. Press any key to exit.