Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade to 22.04 fails #2303

Closed
edap opened this issue Apr 26, 2022 · 20 comments
Closed

Upgrade to 22.04 fails #2303

edap opened this issue Apr 26, 2022 · 20 comments

Comments

@edap
Copy link

edap commented Apr 26, 2022

Distribution (run cat /etc/os-release):

NAME="Pop!_OS"
VERSION="22.04 LTS"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 22.04 LTS"
VERSION_ID="22.04"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=jammy
UBUNTU_CODENAME=jammy
LOGO=distributor-logo-pop-os

**Related Application and/or Package Version **

Upgrade tool

Issue/Bug Description:

The upgrade failed.

sudo dpkg --configure -a
Setting up libdrm-dev:amd64 (2.4.110-1pop0~1648761328~21.10~166056a) ...
dpkg: dependency problems prevent configuration of systemd:
 udev (249.11-0ubuntu3pop0~1650312774~22.04~cecf6af) breaks systemd (<< 249.11-0ubuntu3pop0~1650312774~22.04~cecf6af) and is installed.
  Version of systemd to be configured is 248.3-1ubuntu8.6~1650893010~21.10~9a0cd5e.

dpkg: error processing package systemd (--configure):
 dependency problems - leaving unconfigured
Setting up libsystemd0:i386 (248.3-1ubuntu8.6~1650893010~21.10~9a0cd5e) ...
dpkg: dependency problems prevent configuration of libudev-dev:amd64:
 libudev-dev:amd64 depends on libudev1 (= 248.3-1ubuntu8.6~1650893010~21.10~9a0cd5e); however:
  Version of libudev1:amd64 on system is 249.11-0ubuntu3pop0~1650312774~22.04~cecf6af.

dpkg: error processing package libudev-dev:amd64 (--configure):
 dependency problems - leaving unconfigured
Setting up libdrm2:i386 (2.4.110-1pop0~1648761328~21.10~166056a) ...
Setting up libdrm-amdgpu1:i386 (2.4.110-1pop0~1648761328~21.10~166056a) ...
Setting up libdrm-nouveau2:i386 (2.4.110-1pop0~1648761328~21.10~166056a) ...
Setting up libdrm-radeon1:i386 (2.4.110-1pop0~1648761328~21.10~166056a) ...
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for dbus (1.12.20-2ubuntu4) ...
Processing triggers for libglib2.0-0:amd64 (2.72.1-1) ...
Processing triggers for libglib2.0-0:i386 (2.72.1-1) ...
Processing triggers for libc-bin (2.35-0ubuntu3) ...
Errors were encountered while processing:
 systemd
 libudev-dev:amd64

Steps to reproduce (if you know):

From settings, I have clicked on upgrade. If fails, and it gave me a list of command that I am supposed to launch. The first 3 were:

sudo apt clean

sudo apt update -m

sudo dpkg --configure -a

This last command fails with the error above.

Expected behavior:

The upgrade should work

Other Notes:

I have created a pop_support_log.tar.xz, please contact me and I will send it to you in case you need it

@edap
Copy link
Author

edap commented Apr 27, 2022

Also, if I click to the update button, the shop crashes without any modal window error.

Screenshot from 2022-04-27 09-35-10

@edap
Copy link
Author

edap commented Apr 27, 2022

I am trying to fix the mess that this upgrade created, I am using apt --fix-broken install and it did not work. Any suggestion? is there anything that I can do to help you debugging this bug in the upgrade process?

sudo apt --fix-broken install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
  libpam-systemd libudev1 libudev1:i386 systemd-sysv systemd-timesyncd udev
The following packages will be DOWNGRADED:
  libpam-systemd libudev1 libudev1:i386 systemd-sysv systemd-timesyncd udev
0 upgraded, 0 newly installed, 6 downgraded, 0 to remove and 6 not upgraded.
3 not fully installed or removed.
Need to get 2,809 kB of archives.
After this operation, 230 kB disk space will be freed.
Do you want to continue? [Y/n] Y
Get:1 http://apt.pop-os.org/release impish/main amd64 libpam-systemd amd64 248.3-1ubuntu8.6~1650893010~21.10~9a0cd5e [349 kB]
Get:2 http://apt.pop-os.org/release impish/main amd64 libudev1 amd64 248.3-1ubuntu8.6~1650893010~21.10~9a0cd5e [223 kB]
Get:3 http://apt.pop-os.org/release impish/main i386 libudev1 i386 248.3-1ubuntu8.6~1650893010~21.10~9a0cd5e [227 kB]
Get:4 http://apt.pop-os.org/release impish/main amd64 udev amd64 248.3-1ubuntu8.6~1650893010~21.10~9a0cd5e [1,668 kB]
Get:5 http://apt.pop-os.org/release impish/main amd64 systemd-timesyncd amd64 248.3-1ubuntu8.6~1650893010~21.10~9a0cd5e [181 kB]
Get:6 http://apt.pop-os.org/release impish/main amd64 systemd-sysv amd64 248.3-1ubuntu8.6~1650893010~21.10~9a0cd5e [161 kB]
Fetched 2,809 kB in 3s (949 kB/s)     
dpkg: dependency problems prevent configuration of systemd:
 udev (249.11-0ubuntu3pop0~1650312774~22.04~cecf6af) breaks systemd (<< 249.11-0ubuntu3pop0~1650312774~22.04~cecf6af) and is installed.
  Version of systemd to be configured is 248.3-1ubuntu8.6~1650893010~21.10~9a0cd5e.

dpkg: error processing package systemd (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
                                                                                                          Errors were encountered while processing:
 systemd
E: Sub-process /usr/bin/dpkg returned an error code (1)

@jelmerk
Copy link

jelmerk commented Apr 27, 2022

did you find any solution? i have the same problem

@elliott-with-the-longest-name-on-github

@edap

Same issue -- down to the exact error logs. Weird / random question due to a suggestion I saw on StackOverflow -- do you have SonicWall Net Extender or the Pritunl client installed?

@IbsanjU
Copy link

IbsanjU commented Apr 28, 2022

I'm facing the same problem
OS upgrade and recovery says I'm running the most current Pop!_OS version

@theBrash
Copy link

Same problem here. I tried to fix the sources.list files by replacing the impish with jammy, but that didn't help.
It looks like the systemd package has a problem with the dependencies:

# sudo apt install systemd
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 libnss-systemd : Depends: systemd (= 248.3-1ubuntu8.6~1650893010~21.10~9a0cd5e)
 systemd : Depends: libsystemd0 (= 249.11-0ubuntu3pop0~1650312774~22.04~cecf6af) but 248.3-1ubuntu8.6~1650893010~21.10~9a0cd5e is to be installed

@theBrash
Copy link

theBrash commented Apr 28, 2022

I fixed it.
The installed udev version was 249.11-0ubuntu3pop0~1650312774~22.04~cecf6af and prevented apt from installing systemd.
As far as i can tell systemd should install with the version 249.11-0ubuntu3pop0~1650312774~22.04~cecf6af, but for some reason it tried to install some 248 version.

Please be cautious with the following commands, as they could break stuff.

# replacing the old impish repositories with jammy
sudo sed -i 's/impish/jammy/g' /etc/apt/sources.list.d/system.sources /etc/apt/sources.list.d/pop-os-release.sources /etc/apt/sources.list.d/pop-os-apps.sources 
# download new package information
sudo apt update
# install specific version of systemd
sudo apt install systemd=249.11-0ubuntu3pop0~1650312774~22.04~cecf6af libnss-systemd=249.11-0ubuntu3pop0~1650312774~22.04~cecf6af libsystemd0=249.11-0ubuntu3pop0~1650312774~22.04~cecf6af
# now the dependencies should be fixed
sudo apt upgrade

@Mach10k
Copy link

Mach10k commented Apr 28, 2022

@theBrash your fix almost worked for me. In my case ( upgrade from 21.10 to 22.04 ) i had to do:

# replacing the old impish repositories with jammy
sudo sed -i 's/impish/jammy/g' /etc/apt/sources.list.d/system.sources /etc/apt/sources.list.d/pop-os-release.sources /etc/apt/sources.list.d/pop-os-apps.sources 
# download new package information
sudo apt update
# fix broken
sudo apt --fix-broken install
# now the dependencies should be fixed
sudo apt upgrade

@theBrash
Copy link

@Mach10k I also upgraded from 21.10 to 22.04 and also tried sudo apt --fix-broken install, but unfortunately it didn't work for me.

@Seibz
Copy link

Seibz commented Apr 28, 2022

@edap
Copy link
Author

edap commented Apr 29, 2022

Thanks @Seibz , but there are no info at that page to this particular scenario. The command that failed was sudo dpkg --configure -a. @theBrash your fixed worked for me too, the right version of systemd to install is 249.11-0ubuntu3pop0~1650312774~22.04~cecf6a . thanks ;)

@Goseale
Copy link

Goseale commented May 2, 2022

@theBrash @Mach10k You both are legends. This fixed my issue with apt by following what @theBrash said then doing --fix-broken install as @Mach10k said. Thank you!

@gruvw
Copy link

gruvw commented May 11, 2022

I still get some issues when running the last command of the fix: sudo apt upgrade

Preparing to unpack .../libldacbt-enc2_2.0.2.3+git20200429+ed310a0-4_amd64.deb ...
Unpacking libldacbt-enc2:amd64 (2.0.2.3+git20200429+ed310a0-4) ...
dpkg: error processing archive /var/cache/apt/archives/libldacbt-enc2_2.0.2.3+git20200429+ed310a0-4_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libldacBT_enc.so.2', which is also in package libldac:amd64 2.0.2.3~r26719261
Errors were encountered while processing:
 /var/cache/apt/archives/libldacbt-enc2_2.0.2.3+git20200429+ed310a0-4_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

@ajasonwang
Copy link

I still get some issues when running the last command of the fix: sudo apt upgrade

Preparing to unpack .../libldacbt-enc2_2.0.2.3+git20200429+ed310a0-4_amd64.deb ...
Unpacking libldacbt-enc2:amd64 (2.0.2.3+git20200429+ed310a0-4) ...
dpkg: error processing archive /var/cache/apt/archives/libldacbt-enc2_2.0.2.3+git20200429+ed310a0-4_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libldacBT_enc.so.2', which is also in package libldac:amd64 2.0.2.3~r26719261
Errors were encountered while processing:
 /var/cache/apt/archives/libldacbt-enc2_2.0.2.3+git20200429+ed310a0-4_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

I have the same issue trying to do a dist-upgrade, sudo apt --fix-broken install -y won't fix.

@jonathancross
Copy link

After following the recommendation from @theBrash :

# replacing the old impish repositories with jammy
sudo sed -i 's/impish/jammy/g' /etc/apt/sources.list.d/system.sources /etc/apt/sources.list.d/pop-os-release.sources /etc/apt/sources.list.d/pop-os-apps.sources 

I had to also fix the server names:

sudo sed -i 's/old-releases/archive/g' /etc/apt/sources.list.d/system.sources /etc/apt/sources.list.d/pop-os-release.sources /etc/apt/sources.list.d/pop-os-apps.sources

After this I was finally able to upgrade from 21.10 to 22.04

(I have been trying to get this to work since May! What a pain!)

@jharshman
Copy link

Ran into the same issue. The OS was actually updated to 22.04 as indicated by the /etc/os-release file but the apt sources did not reflect the update from impish to jammy. This left the machine in a weird limbo state. Fortunately updating the repos as described by @theBrash does fix the issue.

I've pasted the diffs of the updated files below.

This is the 2nd time I've had serious upgrade issues with Pop!_OS. Unfortunately the commonly distributed article https://support.system76.com/articles/upgrade-pop/ does not sufficiently address any update issue that I have come across.

/etc/os-release:

NAME="Pop!_OS"
VERSION="22.04 LTS"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 22.04 LTS"
VERSION_ID="22.04"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=jammy
UBUNTU_CODENAME=jammy
LOGO=distributor-logo-pop-os

pop-os-release.sources:

--- pop-os-release.sources.save	2022-09-27 21:02:28.000000000 -0600
+++ pop-os-release.sources	2022-09-27 21:02:50.000000000 -0600
@@ -2,5 +2,5 @@
 Enabled: yes
 Types: deb deb-src
 URIs: http://apt.pop-os.org/release
-Suites: impish
+Suites: jammy
 Components: main

pop-os-apps.sources:

--- pop-os-apps.sources.save	2022-09-27 21:03:19.000000000 -0600
+++ pop-os-apps.sources	2022-09-27 21:03:25.000000000 -0600
@@ -2,5 +2,5 @@
 Enabled: yes
 Types: deb
 URIs: http://apt.pop-os.org/proprietary
-Suites: impish
+Suites: jammy
 Components: main

system.sources:

--- system.sources.save	2022-09-27 21:00:54.000000000 -0600
+++ system.sources	2022-09-27 21:01:58.000000000 -0600
@@ -1,7 +1,7 @@
 X-Repolib-Name: Pop_OS System Sources
 Enabled: yes
 Types: deb deb-src
-URIs: http://old-releases.ubuntu.com/ubuntu
-Suites: impish impish-security impish-updates impish-backports
+URIs: http://apt.pop-os.org/ubuntu
+Suites: jammy jammy-security jammy-updates jammy-backports
 Components: main restricted universe multiverse
-X-Repolib-Default-Mirror: http://old-releases.ubuntu.com/ubuntu
+X-Repolib-Default-Mirror: http://us.archive.ubuntu.com/ubuntu

@ChiefHart
Copy link

Well here it is FEB 2023 and I have the same problem updating POP22.04. It has partially upgraded but I still have 20.04 showing. I get the same messages as above.
So what is the problem? How do I upgrade successfully?

@jacobgkau
Copy link
Member

Well here it is FEB 2023

There is no need to sign a date on your comments, GitHub has timestamps on each comment automatically.

So what is the problem? How do I upgrade successfully?

Nobody can tell you the problem on your system with certainty since you didn't provide any diagnostic data. I would suggest running sudo apt update and seeing if jammy or focal are in the sources. If the sources say jammy and most of the packages are up-to-date, and the system still thinks you're on 20.04, then I'd suggest running the commands in this comment to attempt to correct that: pop-os/upgrade#320 (comment)

You are welcome to join the Mattermost server at https://chat.pop-os.org/pop-os/channel/upgrade-help for community assistance, or you can open a support ticket at https://support.system76.com if you own System76 hardware.

@jacobgkau
Copy link
Member

@ChiefHart If the issue you're experiencing is the one referenced by the comment that I linked (there's not enough info in your comment to tell), then it will be fixed by pop-os/default-settings#165 (once tested, approved, merged, and released) so running those commands manually is no longer necessary.

@jacobgkau
Copy link
Member

Closing now that pop-os/default-settings#165 has been merged, it should be released later this week.

If anyone else has upgrade issue in the future, please ask at https://chat.pop-os.org/pop-os/channels/upgrade-help if you want help recovering, or open an issue in https://github.com/pop-os/upgrade/issues if you have a reproducible issue and/or you would like to help find the root cause of an issue to fix. (Or, of course, open a ticket at https://support.system76.com/ if you own System76 hardware.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests