Tried to upgrade to Jammy, but I get no login prompt

[jfrodsham]

I have an HP Envy laptop that was working well. I tried to install something and got error messages about Impish no longer being supported which led me down the path of upgrading. It halts the booting on snap daemon and login manager trying to start (5.15.0-41-generic). I got back here by holding shift and selecting an earlier kernel (5.13.0-52-generic). Not sure how to diagnose.

[claydoh]

How did you proceed with the upgrade, specifically?
Were there any messages or issues noted during the process?




As the last kernel is working, I am wondering if you actually upgraded fully.
Either look at Kinfocenter, or use lsb_release -a to view the actual OS version you are at

[jfrodsham]

Operating System: Kubuntu 22.04
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.13.0-52-generic (64-bit)
Graphics Platform: X11
Processors: 8 × AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx
Memory: 60.7 GiB of RAM
Graphics Processor: AMD Radeon Vega 10 Graphics

I was following a guide, I think this one: linuxconfig.org / how-to-upgrade-ubuntu-to-22-04-lts-jammy-jellyfish
It was all on the command line and very similar to that.


sudo apt update
sudo apt upgrade
sudo apt dist-upgrade
sudo apt autoremove
sudo apt install update-manager-core
sudo do-release-upgrade

I am embarrassed to say I was multitasking and generally just accepted defaults. It asked me a couple times about keeping my config or using the one from the package owner, and I always picked the default from the packager owner.

-J

[claydoh]

As 21.10 went End of Life, its repos were moved recently. The error messaging when updating should have given better info, and a URL to check for info (I think?) , But anyway, this entails an extra step not seen in a normal, still-supported release, as you need to make sure *all* the packages were fully up to date before proceeding with the upgrade, so the addresses need changing.

From https://help.ubuntu.com/community/EOLUpgrades you should have edited your /etc/apt/sources.list file, to change any instance of archive.ubuntu.com (including us.archive.ubuntu.com, or similar) to old-releases.ubuntu.com, THEN update your system prior to doing the upgrade, following the links to the instructions here https://kubuntu.org/news/kubuntu-22-04-lts-released/ (although there is technically nothing wrong with the generic Ubuntu instructions you followed)

I am not sure what might fix this, though do look at your sources.list file to see that it is showing 'jammy' and not 'impish' in all the repository lines..
Then run :

sudo apt update
sudo apt full-upgrade

report any errors seen. If none, then follow with
sudo apt -f install to install any packages that might be missing, if any.

Otherwise, I can't say why the 22.04 kernel does not work, there isn't anything hardware wise that would be an issue, I think.

[jfrodsham]

Hit:1 http://us.archive.ubuntu.com/ubuntu jammy InRelease
Get:2 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease [114 kB]
Get:3 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
Get:4 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease [99.8 kB]
Get:5 http://security.ubuntu.com/ubuntu jammy-security/main amd64 DEP-11 Metadata [11.4 kB]
Get:6 http://security.ubuntu.com/ubuntu jammy-security/universe amd64 DEP-11 Metadata [608 B]
Get:7 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages [175 kB]
Get:8 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [384 kB]
Hit:9 https://brave-browser-apt-nightly.s3.brave.com stable InRelease
Get:10 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 DEP-11 Metadata [90.7 kB]
Get:11 http://us.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [177 kB]
Get:12 http://us.archive.ubuntu.com/ubuntu jammy-updates/universe i386 Packages [88.5 kB]
Get:13 http://us.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 DEP-11 Metadata [95.1 kB]
Get:14 http://us.archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 DEP-11 Metadata [940 B]
Get:15 http://us.archive.ubuntu.com/ubuntu jammy-backports/universe amd64 DEP-11 Metadata [12.5 kB]
Hit:16 https://updates.signal.org/desktop/apt xenial InRelease
Hit:17 https://repo.protonvpn.com/debian stable InRelease
Fetched 1,361 kB in 6s (240 kB/s)


Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

The sources file seems fine. The full upgrade seemed to think everything is good.

-J

[graemev]

OK, I obviously misunderstood one of these steps so for other people following:

Ign http://gb.old-releases.ubuntu.com/ubuntu impish-backports InRelease
Err http://gb.old-releases.ubuntu.com/ubuntu impish InRelease Er
Could not resolve ‘gb.old-releases.ubuntu.com’
Err http://gb.old-releases.ubuntu.com/ubuntu impish-updates InRelease Er
Could not resolve ‘gb.old-releases.ubuntu.com’
Err http://gb.old-releases.ubuntu.com/ubuntu impish-backports InRelease Er
Could not resolve ‘gb.old-releases.ubuntu.com’
Fetched 0 B in 6s (0 B/s)

claydoh really did mean change it to old-releases.ubuntu.com,
and not, as I assumed, s/archive.ubuntu.com/old-releases.ubuntu.com/g

I have a few items of feedback for the script developers , where is the best place to post these?