crash when trying to upgrade from yakkety to zesty

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

Bug Description

After clicking the 'upgrade' button in update-manager, the upgrader crashes, with the following cmdline output:

Checking for a new Ubuntu release
No protocol specified
Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused
No protocol specified
Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused
/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeFetcher.py:23: PyGIWarning: Gtk was imported without specifying a version first. Use gi.require_version('Gtk', '3.0') before import to ensure that the right version gets loaded.
  from gi.repository import Gtk, Gdk
Segmentation fault (core dumped)

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: ubuntu-release-upgrader-core 1:16.10.10
ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
Uname: Linux 4.8.0-39-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: GNOME
Date: Tue Mar 7 10:13:35 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-08-21 (564 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
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: ubuntu-release-upgrader
UpgradeStatus: Upgraded to yakkety on 2016-09-29 (159 days ago)
VarLogDistupgradeTermlog:

Revision history for this message
Joe Barnett (thejoe) wrote :
tags: added: xenial2yakkety
Revision history for this message
Brian Murray (brian-murray) wrote :

The log files attached to the bug report are from an upgrade from X to Y in September of 2016. Could you include the crash file from /var/crash/ regarding ubuntu-release-upgrader? Thanks in advance.

Changed in ubuntu-release-upgrader (Ubuntu):
status: New → Incomplete
Revision history for this message
Joe Barnett (thejoe) wrote :

There is no ubuntu-release-upgrade crash file unfortunately. I ended up doing a do-release-upgrade from a terminal that did everything through the console instead of the gtk interface and that worked. possibly this is related to being in a wayland gnome session?

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.