Update manager between 17.04 and 17.10

Bug #1720222 reported by Bruno Fernandez-Ruiz on 2017-09-28
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)

Bug Description

$ update-manager -cd
Checking for a new Ubuntu release
Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect: Connection refused
Invalid MIT-MAGIC-COOKIE-1 keyUnable 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 17.04
Package: ubuntu-release-upgrader-core 1:17.04.9
ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: GNOME
Date: Thu Sep 28 20:28:27 2017
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
InstallationDate: Installed on 2016-09-02 (391 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to zesty on 2017-02-27 (213 days ago)

Jean-Baptiste Lallement (jibel) wrote :

Thanks for your report. It is very likely because you are running wayland. Could you run the same command under X and tell us if it is still failing?

Changed in ubuntu-release-upgrader (Ubuntu):
importance: Undecided → High
status: New → Incomplete
tags: added: yakkety2zesty

Confirmed - the command runs without segfault when I start a session under X, so it's only under Wayland.

tags: added: wayland
removed: wayland-session
Changed in ubuntu-release-upgrader (Ubuntu):
status: Incomplete → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers