update-manager -d failing from 14.10 to 15.04

Bug #1405943 reported by Removed by request
52
This bug affects 11 people
Affects Status Importance Assigned to Milestone
One Hundred Papercuts
Invalid
High
Unassigned
ubuntu-release-upgrader (Ubuntu)
Won't Fix
High
Unassigned

Bug Description

"undefined problem" according message box. Can the error be identified from the log files / documentation? Best regards

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: ubuntu-release-upgrader-core 1:14.10.9
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: GNOME
Date: Sat Dec 27 11:02:02 2014
EcryptfsInUse: Yes
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to utopic on 2014-12-27 (0 days ago)
VarLogDistupgradeTermlog:

Revision history for this message
Removed by request (stoni.ch-deactivatedaccount) wrote :
Revision history for this message
Removed by request (stoni.ch-deactivatedaccount) wrote :

Did some research. Removed 3rd party ppas manually, removed all packages install found with

   apt-show-versions|egrep "No\ available"

no change.

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

From Aptlog.txt:

Investigating (0) systemd-sysv [ amd64 ] < 208-8ubuntu8.1 -> 218-2ubuntu3 > ( universe/admin )
Broken systemd-sysv:amd64 Kollidiert mit on upstart [ amd64 ] < none -> 1.13.2-0ubuntu5 > ( admin )
  Considering upstart:amd64 9 as a solution to systemd-sysv:amd64 15
  Added upstart:amd64 to the remove list
  Conflicts//Breaks against version 1.13.1-0ubuntu3 for upstart but that is not InstVer, ignoring
  Conflicts//Breaks against version 1.13.2-0ubuntu5 for upstart but that is not InstVer, ignoring
Broken systemd-sysv:amd64 Kollidiert mit on upstart [ i386 ] < none -> 1.13.2-0ubuntu5 > ( admin )
  Conflicts//Breaks against version 1.13.2-0ubuntu5 for upstart but that is not InstVer, ignoring
  Conflicts//Breaks against version 1.13.1-0ubuntu3 for upstart but that is not InstVer, ignoring
  Considering upstart:amd64 9 as a solution to systemd-sysv:amd64 15
  Added upstart:amd64 to the remove list
  Fixing systemd-sysv:amd64 via keep of upstart:amd64
  MarkKeep upstart [ amd64 ] < none -> 1.13.2-0ubuntu5 > ( admin ) FU=0
  Fixing systemd-sysv:amd64 via keep of upstart:amd64
Investigating (0) ureadahead [ amd64 ] < none -> 0.100.0-17 > ( admin )
Broken ureadahead:amd64 Hängt ab von on upstart [ amd64 ] < none -> 1.13.2-0ubuntu5 > ( admin ) (>= 0.6.0)
  Considering upstart:amd64 9 as a solution to ureadahead:amd64 7
  MarkKeep ureadahead [ amd64 ] < none -> 0.100.0-17 > ( admin ) FU=0
  Holding Back ureadahead:amd64 rather than change upstart:amd64
Investigating (1) ubuntu-minimal [ amd64 ] < none -> 1.327 > ( metapackages )
Broken ubuntu-minimal:amd64 Hängt ab von on upstart [ amd64 ] < none -> 1.13.2-0ubuntu5 > ( admin )
  Considering upstart:amd64 9 as a solution to ubuntu-minimal:amd64 10003
  Re-Instated upstart:amd64

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu-release-upgrader (Ubuntu):
status: New → Confirmed
Revision history for this message
Gabriel de Perthuis (g2p) wrote :

I worked around it by running:

    sudo apt-get purge systemd-sysv

I'll probably have to reinstall it after. The problem is that ubuntu-minimal gets installed on upgrades, and that it depends on upstart and ureadahead which clash with systemd-sysv.

Changed in ubuntu-release-upgrader (Ubuntu):
importance: Undecided → High
Changed in hundredpapercuts:
status: New → Confirmed
importance: Undecided → High
Revision history for this message
Phillip Susi (psusi) wrote :

14.10 and 15.04 have long since reached end of life.

Changed in ubuntu-release-upgrader (Ubuntu):
status: Confirmed → Won't Fix
Changed in hundredpapercuts:
status: Confirmed → Invalid
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.