It's about time :)

[claydoh]

Neon 22.04 based ISOs are the default now, upgrades happen Monday

https://blog.neon.kde.org/2022/10/21...ased-on-jammy/

[dequire]

Very cool! I just received notification today that the 22.04 LTS is now available. To YOLO or not to YOLO, that is the question!

[claydoh]

I did so weeks ago (semi-official testing so y'all don't have to yolo it ),

But is it YOLOing if I backups/snapshots?

I did upgrade on this install this morning while working, stopping long enough to reboot......

[dequire]

Good to know! I should be pretty OK. Gonna give it a go here momentarily

[benny_fletch]

I am definitely interested to hear how people's upgrades go

[GreyGeek]

I triggered the popup telling me that Neon's update to 22.04 was available. It started at 12:05PM and finished at about 1:30PM. I've been playing with it since then. So far ... no problems. The system icons remained visible as I had set them and they all work: psensor, clipboard, battery, kdeconnect, speaker, printer cue, and calander/weather widget. This afternoon I am going to check my Python3 environments and qtcreat.

Dmesg used to work as me, now I have to use sudo. Here is a check of all Errors that appeared during the boot:

$ sudo dmesg | grep Error
[ 0.157993] ACPI BIOS Error (bug): Failure creating named object [\_TZ.FN00], AE_ALREADY_EXISTS (20210730/dswload2-326)
[ 0.158008] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
[ 0.158012] ACPI BIOS Error (bug): Failure creating named object [\_TZ.FAN0], AE_ALREADY_EXISTS (20210730/dswload2-326)
[ 0.158014] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
[ 0.158548] ACPI BIOS Error (bug): Failure creating named object [\_TZ.TZ00], AE_ALREADY_EXISTS (20210730/dswload2-326)
[ 0.158548] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
[ 0.683265] RAS: Correctable Errors collector initialized.
[ 3.995201] ACPI BIOS Error (bug): Attempt to CreateField of length zero (20210730/dsopcode-133)
[ 3.995266] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_OPERAND_VALUE) (20210730/psparse-529)
[ 3.995283] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_OPERAND_VALUE) (20210730/psparse-529)
[ 4.024291] ACPI BIOS Error (bug): Attempt to CreateField of length zero (20210730/dsopcode-133)
[ 4.024333] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_OPERAND_VALUE) (20210730/psparse-529)
[ 4.024343] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_OPERAND_VALUE) (20210730/psparse-529)
[ 4.025033] ACPI BIOS Error (bug): Attempt to CreateField of length zero (20210730/dsopcode-133)
[ 4.025064] ACPI Error: Aborting method \HWMC due to previous error (AE_AML_OPERAND_VALUE) (20210730/psparse-529)
[ 4.025072] ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_OPERAND_VALUE) (20210730/psparse-529)

They appear to be meaningless errors posted for information only.
I can sudo to root, mount /mnt and /backup, and all my snapshots are there.
Email works great. So does the "mailto" icon in my Brave browser.
The NetworkManager shows my wlan0 wifi connection and ALL of its connection properties! (Nice!) It's nice that my "wlan0" naming remained through the update.
Kate works nicely.
Some of my Python3 environment modules did not survive the update:

jerry@jerry-hp17cn1xxx:~/Documents/pythonprojects/firstproject$ source firstprojectenv/bin/activate
...
(firstprojectenv) jerry@jerry-hp17cn1xxx:~/Documents/pythonprojects/firstproject$ pip check
pynacl 1.5.0 requires cffi, which is not installed.
ipykernel 6.7.0 requires debugpy, which is not installed.
(firstprojectenv) jerry@jerry-hp17cn1xxx:~/Documents/pythonprojects/firstproject$
...
(firstprojectenv) jerry@jerry-hp17cn1xxx:~/Documents/pythonprojects/firstproject$ deactivate
jerry@jerry-hp17cn1xxx:~/Documents/pythonprojects/firstproject$

so I have some repairs to do in them in order to make my jupyter notebooks functional again, for those that use cffi and debugpy.

I've always favored a clean install from a verified ISO rather than a version upgrade like I did today. However, I am very pleased with how it went.
Now I've got some more stuff to check, like my Steam programs, Minecraft, Jupyter Notebooks, etc.

[GreyGeek]

UPDATE:
Steam updated nicely. I checked all the python environments and needed to fix only about half of the dozen I have.
After checking all of my menu entries I found that MULTIMC 5, a Minecraft GUI, had to be reconfigured, and, my wine32 installation was deleted, so my 32 bit ekg.exe heart display monitor wouldn't run. I decided against installing wine32 because ekg.exe is the only 32 bit program I used and python2.7, which was removed during the update, would take 595Mb of space. I haven't used that program in over a year because my wife's heart condition has stabilized so I didn't see any sense in wasting 1/2 a Gb of space on it.

All in all, the Neon update went smoothly, considering how customized my installation was. I'm pleased with the results. Great job, devs!!

[marco07]

Is there any specific action for having this upgrade. I have not seen any version upgrade notice since Monday. I am using fully updated KDE Neon user edition 20.04. I do however receive regular updates. Wondering why?? Thanks!

[claydoh]

Is there any specific action for having this upgrade. I have not seen any version upgrade notice since Monday. I am using fully updated KDE Neon user edition 20.04. I do however receive regular updates. Wondering why?? Thanks!

No, other than being fully updated.

Have you done so using apt, to see if there is anything happening there?

What does your neon source file look like?
$ cat /etc/apt/sources.list.d/neon.list

the command
neon-preview-upgrade
should manually start the process but we might want to look at why it hasn't started for you

[marco07]

Have you done so using apt, to see if there is anything happening there?

here is;
~$ sudo apt update
[sudo] password for marco:
Hit:1 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:2 http://us.archive.ubuntu.com/ubuntu focal InRelease
Hit:3 http://us.archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:4 http://us.archive.ubuntu.com/ubuntu focal-backports InRelease
Hit:5 http://security.ubuntu.com/ubuntu focal-security InRelease
Get:6 http://archive.neon.kde.org/user focal InRelease [163 kB]
Hit:7 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu focal InRelease
Fetched 163 kB in 1s (147 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
:~$

[marco07]

And here is:
marco@t540p:~$ cat /etc/apt/sources.list.d/neon.list
deb http://archive.neon.kde.org/user/ focal main
deb-src http://archive.neon.kde.org/user/ focal main

marco@t540p:~$

[claydoh]

Looks fine.
The only other obvious olace woukd be looking at /etc/update-manager/release-upgrades and seeing if things have been disabled there foe some reason. This is what the Ubuntu / kubuntu Software Sources tool would be editing for this option.

I would suggest starting the process manually if you want.

[marco07]

Here is the content of the my
/etc/update-manager/release-upgrades.d/neon.cfg

neon.cfg is the only file in the part. There does not seem to be any thing disabled.

[ThirdPartyMirrors]
neongitunstable=http://archive.neon.kde.org/unstable
neongitstable=http://archive.neon.kde.org/testing
neonuser=http://archive.neon.kde.org/user
neonuserlts=http://archive.neon.kde.org/user/lts
neonrelease=http://archive.neon.kde.org/release
neonreleaselts=http://archive.neon.kde.org/release/lts
mozilla=https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu

[Distro]
MetaPkgs=neon-desktop
.
[neon-desktop]
KeyDependencies=plasma-desktop, breeze, neon-settings-2
PostUpgradeRemove=libpoppler120, libavif12, kmix

[claydoh]

you should have a file in /etc/update-manager/ called release-upgrades that specifies upgrade notifications. This is common across *buntus.
I doubt this has been edited to have upgrade notifications set to be disabled, as either you would have done so, or installed and used the Kubuntu Software Sources tool to do so.

Since the upgrade tool is the same software as that used by Ubuntu/Kubuntu, I am thinking that it simply is not send you the notification (a bug), just like it seems to happen for some Kubuntu/Ubuntu upgradesrs perhaps?

I believe The notification just calls the command neon-preview-upgrade to start the upgrade gui anyway, so you can still start it manually that way.

[marco07]

you should have a file in /etc/update-manager/ called release-upgrades that specifies upgrade notifications. This is common across *buntus.

Yes. Here is its content:

# Default behavior for the release upgrader.

[DEFAULT]
# Default prompting and upgrade behavior, valid options:
#
#  never  - Never check for, or allow upgrading to, a new release.
#  normal - Check to see if a new release is available.  If more than one new
#           release is found, the release upgrader will attempt to upgrade to
#           the supported release that immediately succeeds the
#           currently-running release.
#  lts    - Check to see if a new LTS release is available.  The upgrader
#           will attempt to upgrade to the first LTS release available after
#           the currently-running one.  Note that if this option is used and
#           the currently-running release is not itself an LTS release the
#           upgrader will assume prompt was meant to be normal.
Prompt=lts

​

And Here is my system info (Kinf):

Operating System: KDE neon 5.26
KDE Plasma Version: 5.26.0
KDE Frameworks Version: 5.99.0
Qt Version: 5.15.6
Kernel Version: 5.15.0-52-generic (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i7-4600M CPU @ 2.90GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4600
Manufacturer: LENOVO
Product Name: 20BE003NUS
System Version: ThinkPad T540p​

Base on lts discription, is that why my system is not upgrading? I mean because it does not say 20.04 LTS.
Thanks!