<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <span class="author-g-palxbpuayj09o35u b"><b>Current situation with
        Xubuntu 16.04 upgrades</b></span>
    <div class="ace-line" id="magicdomid1622"><br>
    </div>
    <div class="ace-line" id="magicdomid2326"><span class="">As promised
        earlier, this is where we stand currently with upgrading </span><span
        class="author-g-palxbpuayj09o35u">–</span><span class=""> note
        that the tests we have undertaken so far have for the most part
        only been in virtual machines, though see bug reported by one of
        our testers on hardware [1]</span><span
        class="author-g-palxbpuayj09o35u">.</span></div>
    <div class="ace-line" id="magicdomid2268"><br>
    </div>
    <div class="ace-line" id="magicdomid2285"><span
        class="author-g-palxbpuayj09o35u">1) Upgrading from 15.10 to
        16.04 works</span><span class="author-g-tkgsbwca10vmw9mc"> using
      </span><span class="author-g-palxbpuayj09o35u">any method</span><span
        class="author-g-tkgsbwca10vmw9mc">.</span></div>
    <div class="ace-line" id="magicdomid2287"><span
        class="author-g-palxbpuayj09o35u">2) Upgrading from 14.04 to
        16.04 works when you use the ISO to upgrade; see </span><span
        class="author-g-tkgsbwca10vmw9mc">[2]</span><span
        class="author-g-palxbpuayj09o35u">.</span></div>
    <div class="ace-line" id="magicdomid2272"><span
        class="author-g-palxbpuayj09o35u">3) </span><span class="">Upgrading
        from 14.04 to 16.04 FAILS using update-manager</span><span
        class="author-g-palxbpuayj09o35u">.</span></div>
    <div class="ace-line" id="magicdomid2288"><br>
    </div>
    <div class="ace-line" id="magicdomid2246"><span
        class="author-g-palxbpuayj09o35u">In the original bug report the
        tester was left with a frozen system after upgrading. After a
        hard reset, they could get into a VT, but not the GUI. It is
        possible that you don't see all of the symptoms mentioned here,
        but it is likely you will end up in a broken environment. As
        noted in the bug report [1], running "dpkg  --configure -a"
        should</span><span class="author-g-tkgsbwca10vmw9mc"> allow you
        to finish the upgrade and then</span><span
        class="author-g-palxbpuayj09o35u"> let the system boot normally.</span></div>
    <div class="ace-line" id="magicdomid2029"><br>
    </div>
    <div class="ace-line" id="magicdomid2258"><span
        class="author-g-palxbpuayj09o35u">All information we can get to
        triage the source of the fail is welcome. If</span><span
        class=""> </span><span class="author-g-palxbpuayj09o35u">you</span><span
        class=""> have</span><span class="author-g-palxbpuayj09o35u"> a</span><span
        class=""> machine</span><span class="author-g-palxbpuayj09o35u">
        or two</span><span class=""> y</span><span
        class="author-g-palxbpuayj09o35u">ou</span><span class=""> can
        afford to 'break' and then attempt to fix</span><span
        class="author-g-palxbpuayj09o35u">, we would be very happy to
        hear your </span><span class="">results from </span><span
        class="author-g-palxbpuayj09o35u">such testing</span><span
        class="">.</span></div>
    <div class="ace-line" id="magicdomid1632"><br>
    </div>
    <div class="ace-line" id="magicdomid1633"><span class="">If you're
        in a situation where you cannot afford to break your system,
        then </span><span class="author-g-palxbpuayj09o35u">we do NOT
        recommend trying to proceed with the upgrade</span><span
        class="">.</span><span class="author-g-palxbpuayj09o35u"> </span><span
        class="">The choice of course is yours to make</span><span
        class="author-g-palxbpuayj09o35u">, but we don't want our
        testers to be left with broken machines.</span></div>
    <div class="ace-line" id="magicdomid1634"><br>
    </div>
    <div class="ace-line" id="magicdomid2311"><span class="">Work on</span><span
        class="author-g-palxbpuayj09o35u"> fixing</span><span class="">
      </span><span class="author-g-palxbpuayj09o35u">the </span><span
        class="">upgrad</span><span class="author-g-palxbpuayj09o35u">e
        path</span><span class=""> from 14.04 to 16.04 is being
        undertaken by Canonical</span><span
        class="author-g-palxbpuayj09o35u">.</span><span class=""> More
        information and calls for testing will follow in due course.</span></div>
    <div class="ace-line" id="magicdomid2316"><br>
    </div>
    <br>
    <div class="ace-line" id="magicdomid1977"><span class="">[1] </span><span
        class=" url"><a
href="https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1559463"><a class="moz-txt-link-freetext" href="https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1559463">https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1559463</a></a></span></div>
    <div class="ace-line" id="magicdomid1587"><span
        class="author-g-tkgsbwca10vmw9mc">[2] </span><span
        class="author-g-tkgsbwca10vmw9mc url"><a
          href="http://iso.qa.ubuntu.com/qatracker/testcases/1498/info"><a class="moz-txt-link-freetext" href="http://iso.qa.ubuntu.com/qatracker/testcases/1498/info">http://iso.qa.ubuntu.com/qatracker/testcases/1498/info</a></a></span></div>
    <br>
  </body>
</html>