Neon/NobleUpgrades/Results

--
Josep M. (txemaq)
User edition jammy to noble upgrade on a VM (QEMU/KVM)
First upgrade was interrupted downloading/installing packages (sorry I don't remember about that error), but second try ended successfully. All working fine.
2024-10-11
User edition jammy to noble upgrade on a laptop (ThinkPad X1). Upgrade was fine. But suspension/hibernation closing lid doesn't work after upgrade. I fixed this problem thanks to https://ubuntuhandbook.org/index.php/2021/08/enable-hibernate-ubuntu-21-10/ and https://ubuntuhandbook.org/index.php/2020/05/lid-close-behavior-ubuntu-20-04/
2024-10-12

--
Krake
User edition jammy to noble upgrade
Went through without any issue as far as I can tell so far
2024-10-12

--
jisbetterthanj
Testing edition jammy daily driver system (from ISO) to noble upgrade on Dell XPS 9300
12/10/24 Getting packages up to date before installation was a slight pain, for some reason it took multiple reboots before flatpak user updates appeared in cli, and they errored via appstream. appstream requiring flatpak to be up to date seems inconvenient, but could be a good reason.
Had to run apt download plasma5support && apt download plasma-workspace && sudo apt install ./plasma5support*deb && sudo apt install ./plasma-workspace*deb to get apt up to date.
Installation process was flawless.
(Minor) Issues I've noticed with Noble:

• Gimp was uninstalled for seemingly no reason and reinstalled fine
  
• My preference to install firefox from mozilla's repository was reversed in the upgrader
  and then firefox "downgraded" again to Mozilla's when I updated once in Noble.
• /etc/os-release hasn't updated, apparently I'm on Jammy with Kernel 6.8.0-45-generic!
  

Specific to my hardware: howdy and my PAM configuration were reset, and while howdy reinstalls I haven't got it to work just yet (I have no idea what I'm doing with python system vs py env) - probs for the best that PAM isn't trying to use a broken package. jisbetterthanj 07:22, 12 October 2024 (UTC)
--
chaikney

Slimbook Neon upgrade

2024-10-11

Thank you Fabian! I was stuck in a bootloop after the upgrade: BIOS (or UEFI now?) screen over and over again with no clues as to why I couldn't get past the logo.

To get out of it, it is not the boot disk order I had to change but the one referring to UEFI. I selected "KDE Neon" (or "kde neon"?) over the previous top choice "neon". From there, all normal booting.

But it was a really disagreeable experience that should be avoided / fixed if possible. I only got out because I knew this page existed before the upgrade. In general, can't expect that people would see that.

Fabian
User Edition 22.04 -> 24.04
10/10/24
The upgrade created a new UEFI entry called "KDE Neon 6.1". The older one "neon" is no longer working.

After upgrading to 24.04 I had to run "apt --fix-broken-install". But I think that's because the Firefox .deb repo got deactivated with the upgrade and then the installed version of Firefox conflicted with the transitional package from the Ubuntu repo which wants to install the snap version.

In Plasma Discover the Ubuntu repositories are no longer shown, but that was expected. With Ubuntu 24.04 Canonical changed their location. You have the same problem in Kubuntu.
--
Jonathan Riddell
User edition jammy to noble upgrade
1/10/24
Worked great
--
Jonathan Riddell
Testing edition jammy ISO to noble upgrade on VM
1/10/24 Worked great
--
Jonathan Riddell
Unstable edition jammy ISO to noble upgrade on VM
1/10/24 Worked great
--
Camilla uwu
neon-noble-user-20240930-1043
1/10/24
only black screen with plymouth enabled (AMD driver/plymouth/sddm) issue
Workaround (for me):
- Edit /etc/default/grub: the line "GRUB_CMDLINE_LINUX_DEFAULT=". Delete the words "quiet splash" (leave the quotation marks ).
- Run sudo update-grub
https://bugs.launchpad.net/ubuntu/+bug/2063877
--
Christian Lindberg
User edition Jammy to Noble upgrade
2/10/24
Only issue was having to fix sound input again with alsamixer, rest was perfect, upgrade from nvidia-535 to 550 worked well afterwards as well with dkms --