During upgrade, user is able to quit without warning

Bug #1391828 reported by James Tait
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I wanted to upgrade a laptop from 12.04.5 to 14.04.1 using the USB installer. Ubiquity correctly detected my existing installation and I selected to upgrade that. Due to Bug #763075 I was then prompted to choose a username and password for my "new" installation. Thinking I'd chosen the wrong option (because an upgrade wouldn't need me to create a new user, right?) I wanted to go back to the partman screen.

The details here are a little hazy, but I think the back button and quit button were both greyed out. However, I was able to right-click the Ubiquity icon in the launcher and select Quit from the quick menu. I may have seen a dialogue box asking if I was sure, with Cancel and Quit buttons, but I don't recall exactly (I've been through the installer several times since, trying to recover things, so I may be remembering that dialogue from one of those attempts). I definitely did not see a prominent warning to the effect of "We've already started deleting your old installation, if you quit now, you'll hose your system."

Anyway, I was able to quit Ubiquity, and I then rebooted, thinking maybe I could insert the USB stick in the running 12.04 session and upgrade from there (is that still possible?). But the system failed to boot, and upon further inspection after booting from the USB again, I see a lot of the old system has been deleted, including /etc - so now Ubiquity doesn't even detect that it was a previous Ubuntu installation (because there's no /etc/lsb-release - though even restoring that file hasn't enabled the upgrade option again, I can only install alongside, or wipe the disk and install from scratch).

Revision history for this message
Simon Quigley (tsimonq2) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. If you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 1391828

and any other logs that are relevant for this particular issue.

Changed in ubiquity (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.