I do the upgrade from 16 to 17.1 on my Lenovo P14s (work computer) and since the computer's fan turn everytime, loudly and extract very hot air. Before it's not the cas. And the worst is the battery life. Before it's not like with Windows (dual-boot) but it's was correct. Now I can use the laptop one hour max.
But for now It's still the same after reboot. 30 min work and 30% battery out... And I just do mail via Ferdium. Before the upgrade it's not like this at all.
Just in case, since the upgrade I have this message with the session opening :
# deb cdrom:[Zorin-OS 16.3 Core 64bit]/ focal main restricted
# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
deb http://be.archive.ubuntu.com/ubuntu/ jammy main restricted
# deb-src http://be.archive.ubuntu.com/ubuntu/ jammy main restricted
## Major bug fix updates produced after the final release of the
## distribution.
deb http://be.archive.ubuntu.com/ubuntu/ jammy-updates main restricted
# deb-src http://be.archive.ubuntu.com/ubuntu/ jammy-updates main restricted
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://be.archive.ubuntu.com/ubuntu/ jammy universe
# deb-src http://be.archive.ubuntu.com/ubuntu/ jammy universe
deb http://be.archive.ubuntu.com/ubuntu/ jammy-updates universe
# deb-src http://be.archive.ubuntu.com/ubuntu/ jammy-updates universe
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://be.archive.ubuntu.com/ubuntu/ jammy multiverse
# deb-src http://be.archive.ubuntu.com/ubuntu/ jammy multiverse
deb http://be.archive.ubuntu.com/ubuntu/ jammy-updates multiverse
# deb-src http://be.archive.ubuntu.com/ubuntu/ jammy-updates multiverse
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://be.archive.ubuntu.com/ubuntu/ jammy-backports universe multiverse main restricted
# deb-src http://be.archive.ubuntu.com/ubuntu/ jammy-backports main restricted universe multiverse
## Uncomment the following two lines to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
## respective vendors as a service to Ubuntu users.
# deb http://archive.canonical.com/ubuntu jammy partner
# deb-src http://archive.canonical.com/ubuntu jammy partner
deb http://security.ubuntu.com/ubuntu jammy-security main restricted
# deb-src http://security.ubuntu.com/ubuntu jammy-security main restricted
deb http://security.ubuntu.com/ubuntu jammy-security universe
# deb-src http://security.ubuntu.com/ubuntu jammy-security universe
deb http://security.ubuntu.com/ubuntu jammy-security multiverse
# deb-src http://security.ubuntu.com/ubuntu jammy-security multiverse
# This system was installed using small removable media
# (e.g. netinst, live or single CD). The matching "deb cdrom"
# entries were disabled at the end of the installation process.
# For information about how to configure apt package sources,
# see the sources.list(5) manual.
These may say Focal, still and the only way to know is to open the file and check.
You can elevate to Root:
sudo -i
Launch the GUI file manager from your elevated Root prompt:
nautilus
Navigate to Other Locations > Computer > /etc/apt/sources.list.d folder and right click each file and check the name and contents, looking for Focal being present instead of Jammy.
You can see how this could be a problem since having two different sources with different dependencies can create conflicts or package deference.
The "Could not get a lock /var..." warning only means that you have another package manager open when you tried running the command in terminal. Package management only allows one lock at a time. Closing out the other manager is all that is needed to resolve that.