Jump into Jammy Kubuntu 22.04 LTS

[NoWorries]

Same here. It'll get fixed.

I also found this with Muon and I got around it by starting Muon with sudo and it then works for Configure Software Sources.

There is another more serious problem that I have and that is with Kdenlive on Wayland. With Wayland, after I do a render, I then try to run the rendered file with VLC and it fails to start. Even if I try VLC using the command line, that also fails. I also find that I cannot shutdown and I have to make sure that I have Konsole open so that I can do a

shutdown -h now

On X11 I do not have this problem after all the Plasma and Frameworks updates today, Kdenlive now works as it should. It renders OK and VLC works OK and I can logout. I hope the Wayland problem is easily fixed. My current work-around is to use X11 for all video editing with Kdenlive.

[Snowhog]

Same here. It'll get fixed.

[MeMyself]

Well..... I've run into my first odd glitch on Jammy. Updated via Proposed, which I have been doing somewhat consistently without issue, The system has been and is running great.

The glitch I have run into seems to only effect Software Sources:

My password works perfectly for everything - except Software Sources, where I get the error shown in the attached image.

Steps to the Error:

Opened Discover
Settings Tab
Click Software Sources
Enter Password
---Error---

Opened Muon
Settings Menu
Configure Software Sources
Enter Password
---Error---

***If I select a Repository listed on the Settings page of Discover (either checking or unchecking the applicable box), the password works perfectly fine and processes the action

[jlittle]

The daily jammy iso today fails to isoboot for me, looping on

stdin: Not a typewriter

I forget why, but I've got the lubuntu daily iso too, and it has the same problem.

[dejjanku]

Did anyone had luck making nvidia drivers working with this new version ? 510 or ... ?

[jfabernathy]

I'm not totally clear on what you're asking here. Let me explain my confusion:

The way one moves from one release version to the next doesn't vary: "sudo do-release-upgrade". So the literal answer to the question is: "Yes."

I think you know this, so it seems you might be asking something else. 22.04.1 won't be released until sometime in July or August (based on history). So are you asking "If I wait for the first LTS point release, is the upgrade done differently? The answer to that is "No."

I remember back while I was using Ubuntu 20.04 I tried to use "sudo do-release-upgrade" and it would not upgrade to 20.10 or 21.04 because they were not LTS release.

What I'm confused about is if I take my 21.10 system and do "sudo do-release-upgrade" after 22.04 LTS is released will it upgrade me to 22.04 LTS and keep me on the LTS?

[oshunluvr]

Do you think that there will be a standard way to migrate to 22.04.1 LTS from 21.10 once the point release is out maybe this summer? I had to move from 20.04.3 LTS to 21.10 due to my latest hardware not supported at the time.

I'm not totally clear on what you're asking here. Let me explain my confusion:

The way one moves from one release version to the next doesn't vary: "sudo do-release-upgrade". So the literal answer to the question is: "Yes."

I think you know this, so it seems you might be asking something else. 22.04.1 won't be released until sometime in July or August (based on history). So are you asking "If I wait for the first LTS point release, is the upgrade done differently? The answer to that is "No."

The Ubuntu "point" release really only signifies a change in the packaging (the ISO for example) that includes all the additions, updates, and bug fixes that have occurred before the point release date. It's done only with LTS versions and because the length of time the LTS versions are supported. So If one comes along mid-way in the LTS life cycle and wants to install Kubuntu, instead of installing Kubuntu 22.04 and then two years worth of updates (which could number over a 1000), one could just install Kubuntu 22.04.4 or whatever is current. Doing either gives the exact same result, the post-install updates just take longer if you don't use the current point release.

So whenever you decide to upgrade to 22.04, "do-release-upgrade" will take you to the most current available set of packages for 22.04, regardless if a point release (or two or three) has occurred.

I'm guessing, like me, that you wait a bit into the release cycle before upgrading to the next release. I use my computer every day and need some stability so I wait for a few months to let the larger bugs get handled before making the leap.

Now as far as "Migration" - here's an interesting way you can test the release upgrade over without fully committing: Install both versions side-by-side. Since I know you use BTRFS you don't need another partition - you can do this directly to the same file system already 21.10 is on, and there's a couple different ways - "Dual boot" or "Snapshot rollback."

Assuming you are using a default BTRFS install, you have two subvolumes @ and @home that contain 21.10:

Snapshot rollback is the easiest. Simply snapshot both subvolumes and then run "do-release-upgrade". Use it for a bit and if you're satisfied, delete the snapshots. If you're not, delete the 22.04 subvolumes and rename the snapshots back to the default and reboot. Honestly, when you do the upgrade, you should do it this way regardless of your intentions.

Dual boot takes a bit more work to set up but allows you to switch back and forth by booting either install for as long as you'd like without extra snapshot actions. To do this, you need to migrate your current install from @ and @home to another name, create a custom grub stanza, and once it works, then install 22.04 and add the custom grub stanza to it so you can boot either install.

[jglen490]

I would think it would be a logical thing to do, but there have been glitches in the past couple of LTS releases that made updating from a prior release difficult. I can only speak of LTS releases, in recent years, as that's all I have used, so I can only talk to the process that I use which is a clean install - it never fails

[jfabernathy]

Looking forward to 22.04 LTS - probably at 22.04.1

Do you think that there will be a standard way to migrate to 22.04.1 LTS from 21.10 once the point release is out maybe this summer? I had to move from 20.04.3 LTS to 21.10 due to my latest hardware not supported at the time.

[jglen490]

Looking forward to 22.04 LTS - probably at 22.04.1

[MeMyself]

5.24.0 landed in Jammy

Really enjoying it! Great job Devs!

[acheron]

5.24.0 landed in Jammy

[NoWorries]

I assume they mean 5.24, which is out this coming Tuesday.

Thanks very much for the polite correction of the error that I made. I am looking forward to the updated KDE Plasma Version 5.24 on Wednesday morning Australia Time.

One problem that I had was

I have found that the Wayland desktop is somewhat variable in speed between logins. For example, glmark2-wayland gives say 4600 when Wayland is responsive or say 1200 when it is slow. I certainly hope this variability is resolved by the 8th February.

I am very pleased to report that this problem no longer exists and Wayland is now consistently super fast for me!

I certainly greatly appreciate the quick response by all developers in solving problems It does look like the Virtual Keyboard option is here to stay, so I will ignore this option.

[acheron]

I think you have that wrong; the version number. Plasma - 25th Anniversary Edition (5.23) has been out since October 14, 2021.

I assume they mean 5.24, which is out this coming Tuesday.

[Snowhog]

KDE plasma 4.24

I think you have that wrong; the version number. Plasma - 25th Anniversary Edition (5.23) has been out since October 14, 2021.