Graphical update from 15.10->16.04 failed with apparent window manager crash

Bug #1573952 reported by Neil McPhail on 2016-04-23
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)

Bug Description

This may be related to bug #1555237, although that is marked as "fix released"

I was prompted to upgrade from 15.10 to 16.04 last night, by the graphical updater. It disabled my PPAs, downloaded the packages and began the install. When I looked again later, I had a dialog box giving information on the networking changes in LXC, but the window manager decorations had gone, unity sidebar was gone, top bar was gone, screen and windows unresponsive to mouse clicks and alt-tab not working. There was no way to switch to the dialog box to continue the update.

Running "ps aux | grep update" gave:

neil 3473 0.1 0.0 4476 688 ? SN 16:52 0:13 /bin/sh -c /usr/bin/pkexec /usr/bin/do-release-upgrade --frontend=DistUpgradeViewGtk3
root 5556 1.3 1.7 638124 144824 ? SNl 16:59 1:53 /usr/bin/python3 /tmp/ubuntu-release-upgrader-31my8tm6/xenial --mode=server --frontend=DistUpgradeViewGtk3
root 6290 5.4 1.3 634492 108848 pts/5 SNs+ 18:18 3:18 /usr/bin/python3 /tmp/ubuntu-release-upgrader-31my8tm6/xenial --mode=server --frontend=DistUpgradeViewGtk3
root 15461 0.0 0.2 66592 17348 pts/14 SN+ 18:35 0:00 /usr/bin/perl -w /usr/share/debconf/frontend /var/lib/dpkg/ upgrade 0.20-0ubuntu4.1
root 15478 0.0 0.0 4508 1708 pts/14 SN+ 18:35 0:00 /bin/sh /var/lib/dpkg/ upgrade 0.20-0ubuntu4.1
root 15490 0.0 0.0 24676 3332 pts/14 SN+ 18:35 0:00 whiptail --backtitle Package configuration --title Configuring lxd --output-fd 11 --nocancel --msgbox lxcbr0 is being replaced by lxdbr0 With this package upgrade LXD is moving away from the LXC provided lxcbr0 bridge and moving to its own lxdbr0 bridge. The reason for this switch is: - Drop the dependency on the old LXC (lxc1) package. - Only run the bridge when LXD is running. - Don't hardcode a subnet which may be used by the user. Important differences between lxcbr0 and lxdbr0: - The lxdbr0 bridge DOES NOT come with ANY configured IPv4 or IPv6 subnet. - The bridge provides basic HTTP connectivity out of the box by way of a tiny HTTP PROXY server running on an IPv6 link-local address. - The user IS EXPECTED to configure the bridge to use an UNUSED subnet on their network. To configure lxdbr0 to your liking, please run: dpkg-reconfigure -p medium lxd To stay on the old lxcbr0 bridge, make sure you have the "lxc1" package installed, then select the "use an existing bridge" option. --scrolltext 20 77
neil 18178 0.0 0.0 18368 504 tty4 S+ 19:18 0:00 grep upgrade

I killed PID 15490, which allowed the install process to continue, but without any graphical progress box. I had to monitor the upgrade process in "top" and manually reboot when all the likely upgrade processes were finished.

On rebooting into 16.04 and logging in, I had to reset compiz with "dconf reset -f /org/compiz/ && setsid unity" to bring back my sidebar and window decorations.

There have been a couple of similar bugs mentioned which may be similar. See and the transcript from user "xenialdenial" on

My system -
15.10 amd64 on a bcache'd ext4 partition (installed de novo) with an attempted upgrade to 16.04 using standard graphical updater when prompted. Using proprietary nvidia drivers from the ubuntu repos. My post-upgrade /etc/apt/sources.list.d/ contains the following PPAs/repos:

BCB (fdajkddcek) wrote :

Similar situation on a Ubuntu Headless Server on AWS
upgraded from 15.05 to 16.04 and after the install interruptedI now have:

Distributor ID: Ubuntu
Description: Ubuntu 16.04 LTS
Release: 16.04
Codename: xenial

however when I long in I get

New release '16.04 LTS' available.
Run 'do-release-upgrade' to upgrade to it.


~$ do-release-upgrade
Checking for a new Ubuntu release
No new release found

#sudo apt-get update && sudo apt-get dist-upgrade
Hit:1 wily InRelease
Get:2 wily-updates InRelease [65.9 kB]
Get:3 wily-security InRelease [65.9 kB]
Fetched 132 kB in 0s (327 kB/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

fired up a back up aws instance and did a release upgrade to 15.0
did another release upgrade to 16.4
upgrade failed at the same place.

killed the hung process as described above and the upgrade continued until.

Errors were encountered while processing:
Error in function:

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the
automatically opened web browser.

What would you like to do? Your options are:
  S: Send report (293.0 KB)
  V: View report
  K: Keep report file for sending later or copying to somewhere else
  I: Cancel and ignore future crashes of this program version
  C: Cancel
Please choose (S/V/K/I/C):

Errors were encountered while processing:

Upgrade complete

The upgrade has completed but there were errors during the upgrade

Brian Murray (brian-murray) wrote :

@BCB - that issue is not related to the one in this report and you should open a new bug report.

Brian Murray (brian-murray) wrote :

Are there any crash files in /var/crash?

Changed in ubuntu-release-upgrader (Ubuntu):
importance: Undecided → High
status: New → Incomplete
Neil McPhail (njmcphail) wrote :


$ ls -lh /var/crash/
total 69M
-rw-r----- 1 neil whoopsie 9.9M Apr 22 20:07 _usr_bin_compiz.1000.crash
-rw-r----- 1 neil whoopsie 59M Apr 22 20:04 _usr_bin_skype.1000.crash

Do you want me to upload them here? Do I need to redact anything in them?

Brian Murray (brian-murray) wrote :

It'd be better if the crash report were sent separately. You might be able to get the compiz one to send by using ubuntu-bug compiz.

Brian Murray (brian-murray) wrote :

I meant 'ubuntu-bug /var/crash/_usr_bin_compiz.1000.crash'.

Neil McPhail (njmcphail) wrote :

'ubuntu-bug /var/crash/_usr_bin_compiz.1000.crash' doesn't seem to be doing anything useful. I get the "Ubuntu has experienced an error" dialog but, when I click "send", the dialog just closes and nothing else happens. I'm not sent to launchpad in the browser to file the bug report. I've attached the output of "ps aux", and I can't see any evidence of the crash reporter being active. Is there a better way to send the crash file?

Neil McPhail (njmcphail) wrote :

Actually, I see the crash has been uploaded to but there is no way I can add any information to it or access it as, apparently, I don't have the correct permissions. The bug is at .

Brian Murray (brian-murray) wrote :

The crash file itself isn't that informative as it did not get retraced. I think it's enough to know that there was a compiz crash and that it made interacting with the upgrade process hard.

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

Other bug subscribers