Clicking "Reboot Now" after 14.04-->16.04 upgrade has no effect

[Jason Gerard DeRose]

After doing a 14.04 to 16.04 upgrade, clicking "Reboot Now" has no effect. update-manager simply closes. However, I could then reboot fine using the indicator or the power button, which kinda suggests the problem is in update-manager rather than in the general state of such an upgraded but not yet rebooted system.

In the 3 test upgrades I did, this was reproducible 100% of the time.

Steps I used to reproduce:

1) Fresh install of 14.04.4

2) Run updates and reboot

3) Launch update-manager with `update-manager -d`

4) Start upgrade, let it complete

5) Once upgrade is completed, click "Reboot Now" on the shown dialogue

FYI, thus far I've only tested on a UEFI system, haven't had time to test a BIOS system (and I wont likely have time to test on a BIOS system). But I wouldn't expect this to behave differently on a BIOS system.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.14
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: Unity
Date: Mon Jul 18 15:42:56 2016
InstallationDate: Installed on 2016-07-18 (0 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to xenial on 2016-07-18 (0 days ago)
VarLogDistupgradeTermlog:

[Brian Murray (brian-murray)]

The code seems to just call /sbin/reboot. See DistUpgrade/DistUpgradeController.py lines 1868 - 1871. Could you try calling that directly after the upgrade? Thanks!

[Jason Gerard DeRose (jderose)]

Brain,

Strange. So I just tried the upgrade again, and after the upgrade completed, I:

1) Clicked "Reboot Now" (which did nothing, same as yesterday)

2) Ran `sudo reboot` - it worked, but seemed to hang for some time before doing anything (it hung for maybe 20 seconds or so)

I'm not sure how clicking "Reboot Now" first might be interacting with then running `sudo reboot`. I wonder if I tried `sudo reboot` first if it would do nothing. I'll try that tomorrow if I have time.