do-release-upgrade (19.04 -> 19.10) aborts when snapd is disabled
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-release-upgrader (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
Running sudo do-release-upgrade I get:
=======
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [1,554 B]
Get:2 Upgrade tool [1,319 kB]
Fetched 1,320 kB in 6s (21.3 kB/s)
authenticate 'eoan.tar.gz' against 'eoan.tar.gz.gpg'
extracting 'eoan.tar.gz'
Reading cache
Checking package manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
Hit http://
Hit http://
Get:1 http://
Get:2 http://
Get:3 http://
Fetched 284 kB in 0s (0 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
Restoring original system state
Aborting
Reading package lists... Done
Building dependency tree
Reading state information... Done
=======
I've had the problem for several days, but the system otherwise seems completely cool. I keep getting and successfully installing all the usual security updates (firefox this morning).
The only logs which seem relevant are in /var/log/
=======
2019-10-24 14:15:14,716 INFO Using config files '['./DistUpgrad
2019-10-24 14:15:14,716 INFO uname information: 'Linux chippo-
2019-10-24 14:15:15,262 INFO apt version: '1.8.3'
2019-10-24 14:15:15,262 INFO python version: '3.7.3 (default, Oct 7 2019, 12:56:13)
[GCC 8.3.0]'
2019-10-24 14:15:15,267 INFO release-upgrader version '19.10.12' started
2019-10-24 14:15:15,279 INFO locale: 'en_ZA' 'UTF-8'
2019-10-24 14:15:15,344 INFO screen could not be run
2019-10-24 14:15:15,388 DEBUG Using 'DistUpgradeVie
2019-10-24 14:15:15,451 DEBUG enable dpkg --force-overwrite
2019-10-24 14:15:15,495 DEBUG creating statefile: '/var/log/
2019-10-24 14:15:25,436 DEBUG lsb-release: 'disco'
2019-10-24 14:15:25,436 DEBUG _pythonSymlinkCheck run
2019-10-24 14:15:25,438 DEBUG openCache()
2019-10-24 14:15:25,438 DEBUG quirks: running PreCacheOpen
2019-10-24 14:15:25,438 DEBUG running Quirks.PreCacheOpen
2019-10-24 14:15:26,288 DEBUG /openCache(), new cache size 95789
2019-10-24 14:15:26,288 DEBUG need_server_mode(): run in 'desktop' mode, (because of pkg 'ubuntu-desktop')
2019-10-24 14:15:26,288 DEBUG checkViewDepends()
2019-10-24 14:15:26,290 DEBUG running doUpdate() (showErrors=False)
2019-10-24 14:15:29,239 DEBUG openCache()
2019-10-24 14:15:30,217 DEBUG /openCache(), new cache size 95789
2019-10-24 14:15:30,217 DEBUG doPostInitialUpdate
2019-10-24 14:15:30,217 DEBUG quirks: running eoanPostInitial
2019-10-24 14:15:30,217 DEBUG running Quirks.
2019-10-24 14:15:35,238 DEBUG abort called
2019-10-24 14:15:35,238 DEBUG openCache()
2019-10-24 14:15:36,226 DEBUG /openCache(), new cache size 95789
=======
lsb_release -rd
Description: Ubuntu 19.04
Release: 19.04
apt-cache policy ubuntu-
ubuntu-
Installed: 1:19.04.16.7
Candidate: 1:19.04.16.7
Version table:
*** 1:19.04.16.7 500
500 http://
500 http://
100 /var/lib/
1:19.04.16 500
500 http://
500 http://
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu27.2
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: LXDE
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-05 (1059 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
Package: ubuntu-
ProcVersionSign
Tags: disco dist-upgrade
Uname: Linux 5.0.0-34-generic x86_64
UpgradeStatus: Upgraded to disco on 2019-10-31 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
VarLogDistupgra
Log time: 2019-10-31 14:27:58.805832
Log time: 2019-10-31 14:28:05.066042
Log time: 2019-10-31 14:28:11.218874
_MarkForUpload: True
summary: |
- do-release-upgrade (19.04 -> 19.10) aborts + do-release-upgrade (19.04 -> 19.10) aborts when snapd is disabled |
Changed in ubuntu-release-upgrader (Ubuntu): | |
status: | Incomplete → Triaged |
importance: | Undecided → Medium |
tags: | added: eoan fossa |
tags: |
added: focal removed: fossa |
Arul in bug <https:/ /bugs.launchpad .net/ubuntu/ +source/ ubuntu- release- upgrader/ +bug/1848829> confirms this bug, but that bug seems to be different from this one. So, just check that bug too, for fixes/workarounds etc.