Permits upgrade from an LTS system on an HWE stack to a broken system

Bug #1252843 reported by Robie Basak on 2013-11-19
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
Undecided
Unassigned
update-manager (Ubuntu)
High
Unassigned

Bug Description

See https://lists.ubuntu.com/archives/ubuntu-desktop/2013-November/thread.html for the discussion the led me to file this bug.

Steps to reproduce:

1. Install 12.04 with an HWE enablement stack, eg. with the 12.04.2 installer.
2. In update manager, choose to show upgrades to all releases, not just the LTS.
3. Upgrade to Quantal.

Expected results:

Since an upgrade from Precise with an HWE stack installed to Quantal is unsupported, the upgrade should either not be permitted from the GUI, or the user should be prompted to downgrade from the HWE first, or some other dire warning should be presented.

Actual results:

An upgrade is permitted. On reboot, the system has an HWE xorg from Precise that has not been upgraded, and the Quantal xorg release is not installed. On a system with an nvidia card, this completely broke the system and presented me with a black screen on reboot.

Critical Importance justification: Enabling an LTS to non-LTS release through the GUI is the standard recommended process to upgrade on a six-monthly cadence, and is valid on a non-HWE system. The HWE stack is default on the latest LTS point release, so users may not be aware of what the HWE stack is or if they are on one. So users can be led into a completely broken system just on the basis of timing of the latest installation image that gets chosen and timing of when to upgrade. I have heard general stories about systems being broken on upgrade, and as an Ubuntu developer was led into this myself. Given the "default" nature of this problem, I believe that it's reasonable to assume that this is an issue that has affected a large proportion of Ubuntu users.

Perhaps most users who could be affected by this have already been affected, in which case I'd understand a Won't Fix conclusion to this bug. The "default" window is still open though, as it's reasonable for a user to want to upgrade to 12.04 to 13.10 as 13.10 is still current. The pull to upgrade to a 6-monthly release grows as time goes on, since the benefits build up. As an example, this happened to me because I found that a 12.04 system didn't have certain packages I wanted, and so I considered it worth upgrading at that point.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in update-manager (Ubuntu):
status: New → Confirmed
Noé (theneo-ng) on 2013-12-16
Changed in update-manager (Ubuntu):
assignee: nobody → Noé (theneo-ng)
Changed in update-manager (Ubuntu):
assignee: Noé (theneo-ng) → nobody
Changed in update-manager (Ubuntu):
status: Confirmed → Triaged
Brian Murray (brian-murray) wrote :

Is this fixed by the fix for bug 1278737?

Sam Stoelinga (sammiestoel) wrote :

I want to update from 12.04 to 14.04 on Dell laptop pre-installed with Ubuntu. But I am hit by this bug https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1354825 not sure if it's a duplicate of this bug.

Brian Murray (brian-murray) wrote :

Given that Quantal is End of Life and the release-upgrader tarball for Quantal is no longer available, I am setting this bug to Won't Fix.

Changed in update-manager (Ubuntu):
status: Triaged → Won't Fix
no longer affects: update-manager
Changed in update-manager (Ubuntu):
importance: Critical → High
status: Won't Fix → Triaged
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

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

Other bug subscribers