Jump into Jammy Kubuntu 22.04 LTS

[oshunluvr]

I had the same issue with Ubuntu Server 22.04 iso. I had to go back several releases until I found one where the installer worked.

[NoWorries]

Sorry that you are having problems related to snap. I have just checked the snap packages that I have on my Laptops and they are listed in the graphic below:

[jglen490]

And that's the biggest fault with individual snaps. Yes, they are containers, but they would be more useful, and probably secure, as integrated containers such that related software products are packaged together. Security/hardening is a real benefit of containerizing, but neither snaps nor flats do that particularly well.

[Notsonoble]

Attempting now, still no zfs install option I noticed.

Update:

Plasma integration with firefox is broken in the snap but not in the apt install version probably because the snap creates the .mozilla folder somewhere weird and isolated.

This also breaks things like say, libreoffice using ff or thunderbird as a cert manager. Another reason snaps annoy me.

[jlittle]

That crash has been fixed now...

Indeed, I've done a Jammy install.

[verndog]

I found a new 23rd November "jammy-desktop-amd64.iso" that was 3.8G. When I used it to do an installation, it crashed after entering the user details followed by selecting Install. So I think I will have to wait longer.

That crash has been fixed now see this bug report:
https://bugs.launchpad.net/ubuntu/+s...y/+bug/1951399

[NoWorries]

For those interested in knowing the notification and solution to the problems with the Jammy iso's failure to install, you can see this at:

https://bugs.launchpad.net/ubuntu/+s...y/+bug/1951399.

The comments were made that during this period no realistic testing of Jammy could be made from the 8th November until now.

It seems that the bug first appeared in 08-11-2021 and a solution was found in 21-11-2021 by Norbert post #26 in file `debianutils` version 5.5-1. By reverting to the previous version 4.11.2build1 he was able to get the installation to work.

[NoWorries]

It is now DEFINITELY WORTH downloading the latest Jammy Laptop. I found a new 24th November "jammy-desktop-amd64.iso" that was 3.8G. When I used it to do an installation it was totally successful on my Sacrificial Laptop.

I have installed my favourite packages and networked my Sacrificial Laptop to my other laptops. So it is great to see it working so well.

Thanks very much to all the hard work by those developers who resolved the reasons for the previous iso installations crashing.

[NoWorries]

I found a new 23rd November "jammy-desktop-amd64.iso" that was 3.8G. When I used it to do an installation, it crashed after entering the user details followed by selecting Install. So I think I will have to wait longer.

[NoWorries]

It is now 5 months to go before the release of Jammy Jellyfish.

For those who have succeeded with the installation and testing of Jammy, you may have a similar summary of System Information as shown in the table below.

	5 Months to go
KDE Plasma Version	5.23.3
KDE Frameworks Version	5.88.0
QT Version	5.15.2
Kernel Version	5.15.0-11-generic

I must confess that I use Pre-released and Unsupported updates. 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

In all areas that I use frequently, Jammy works perfectly. I am very pleased with the performance of Jammy and very grateful to the developers for the progress at this very early stage of development.

There is only one outstanding hurdle to jump over and that is the current iso files for Jammy crash when trying to install after entering all the user details. I hope it is not too long before this problem is fixed. In hindsight, I regret not keeping older Jammy iso files for doing a re-installation when needed. In my case, my Sacrificial Laptop somehow got sacrificed and I needed to do a re-installation which I cannot achieve at the moment.

Bug Report:

Looks like the problem with not being able to install Jammy from the recent iso files is also reported by other users of: Ubuntu, Budge, Kylin, MATE, Xubuntu. I had reported Jammy's failure on launchpad over a day ago, but today I got notification of it being a duplicate You can find the bug report at:

https://bugs.launchpad.net/ubuntu/+s...y/+bug/1951399

---

[jglen490]

I'll be looking forward to Kubuntu 22.04 LTS. Sometime around July next year when the first point release comes out

[NoWorries]

Welcome cookiemuncher and congratulations on being able to overcome your UFEI problems.

This morning I found that there were a few updates related to KDE Frameworks, so that prompted me to add another ppa to my sources. For those who like to live on the edge, you could try these ppa's

sudo add-apt-repository ppa:kubuntu-ppa/staging-plasma
sudo add-apt-repository ppa:kubuntu-ppa/staging-frameworks

I find that Jammy is advancing at a great rate of knots.

[cookiemuncher]

I have 2 SSD's in my laptop. sda for Windows stuff and sdb for Linux stuff. I installed Kubuntu 22.04 onto sdb2, chose UEFI boot to install on sdb1. When rebooting I found that sda1 had been selected as the boot partition instead of sdb1, like it changed after reboot. I had to edit the fstab file to switch to boot from sdb1, then did a grub-install and update-grub to boot from the installation drive. Otherwise happy so far.

[jlittle]

One thing I did note was that the installer, when used to adjust the partitioning of the hard drive, wants to put a a full megabyte empty "buffer" between each partition. A million here and a million there, pretty soon we're talking about a big waste of disk space.

If you used btrfs, there'd be no need for lots of partitions, just two, or three if you want a swap partition. Subvolumes take over the role of partitions.

When I do test installs of new releases, I install into the same btrfs as other installs. Ubuntu installs into subvolumes called "@" and "@home", and I just have to rename them to something else to get them out of the way of another new install. It saves a lot of time and space, not juggling partitions.

[TWPonKubuntu]

Yes, but it triggered a series of warnings, starting with the minimum size for the EPI partition and then a warning about possible bad hard drive sectors. When I moved to 21.10, I left the newly created EPI partition in place and it worked without any warnings.

I suspect the pre-release 22.04 ISO has some problems which I don't want to take the time to debug. I blew an entire day going through the various installs and now I must catch up with my work flow missed in that day. I'll wait for a slightly more mature release of 22.04 before I try again.