Python3: After do-release-upgrade, all apt-installed modules need to be reinstalled, or they fail

Bug #1825234 reported by Brian Ealdwine
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I was running 18.10, and used do-release-upgrade from the cli. It seemed to end successfully, and asked to reboot.

Upon reboot, many/most python-related programs (apport, chrome-gnome-shell, ubuntu-bug) failed to work with `ModuleNotFoundError: No module named 'certifi'.`.

I verified that the version being used was Python 3.7 (3.7.3), and that python3 pointed to that executable.

After an `apt install --reinstall` for `certifi` and `idna`, critical things like apport are working.

I don't know if the '--reinstall' was necessary, unfortunately. I'd fixed it before I determined that.

I did "clear out obsolete packages" during the upgrade.

My guess is that the requests lib (or some other package) is missing some dependencies, but I'm not sure. I'm not that familiar with the mechanics of debian packaging.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubuntu-release-upgrader-core 1:19.04.16
Uname: Linux 5.0.8-050008-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: GNOME
Date: Wed Apr 17 14:37:03 2019
InstallationDate: Installed on 2018-11-17 (150 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: Upgraded to disco on 2019-04-17 (0 days ago)
VarLogDistupgradeXorgFixuplog:
 INFO:root:/usr/bin/do-release-upgrade running
 INFO:root:No xorg.conf, exiting

Revision history for this message
Brian Ealdwine (eode) wrote :
tags: added: cosmic2disco
tags: added: third-party-packages
Revision history for this message
Brian Murray (brian-murray) wrote :

I tried recreating this with an upgrade from Cosmic to Disco today and was unable to. I then restored the apt-clone file in this report to at test system (minus some packages from PPAs) and again was unable to recreate the issue when upgrading from Cosmic to Disco. That being said looking at the dmesg log file this doesn't look great:

[ 25.305257] Thread (pooled)[2724]: segfault at 7f5827136610 ip 00007f5826a5d0eb sp 00007f5821b789d8 error 7 in libc-2.29.so[7f58268f9000+173000]
[ 25.305264] Code: 0c 16 4c 39 cf 0f 82 c5 01 00 00 48 89 d1 f3 a4 c3 80 fa 10 73 17 80 fa 08 73 27 80 fa 04 73 33 80 fa 01 77 3b 72 05 0f b6 0e <88> 0f c3 c5 fa 6f 06 c5 fa 6f 4c 16 f0 c5 fa 7f 07 c5 fa 7f 4c 17

Revision history for this message
Brian Murray (brian-murray) wrote :

Is there a /var/log/dist-upgrade/screenlog.0 file on the system at all?

Changed in ubuntu-release-upgrader (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]

Changed in ubuntu-release-upgrader (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.