© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
@psusi, Philip, Just responding to your comments
> I am not aware of any documentation since normally the installer takes care of it.
So this tells me that from the PoV of the developers there is no relevant user documentation on this which I read is a statement that it is undocumented.
> Also it does rewrite the mbr any and all drives you selected from the menu.
I am not doing a virgin install, and there is no such dialogue in the upgrade process. But yes, I did specify this drive in the original install at 12.10, three upgrades ago and it didn't update the MBR on this upgrade, so this context has been lost somewhere along the line.
> As far as the number of people being hit, 89, out of the what? A million people ...
This is flawed logic. To put these numbers in perspective the corresponding counts for the 3 "critical" grub issues are:
#1024383: 77 in 21 months
#1061255: 20 in 18 months
#1183392: 6 in 11 months
So in two weeks since the 14.04 release, this issue (#1289977) at 89 reports is already at the top, but is still not rated as critical, or from your wording as very important. note that one reporter (#117) stated: "This is a real bug as we have around 25% of users hit in a corporate environment". Luckily, most corporate and complex users (the sort that will be hit by this) wait a few months before upgrading -- to let such teething issues be fixed. IMO, if this issue isn't addressed soon then Ubuntu could face a shit-storm of bad publicity.
The respective counts for the 11 know issues detailed in the Release Notes section on Boot, Installation and Upgrade are 13, 4, 2, 2, 6, 6 3, 5, 5, 5 and 12 users. This issue at 89 clearly tops this total of 63 especially as only 5 these cause loss total system functionality as opposed to all 89 here.
It merits an explicit mention in the Release Notes, and it merits treatment as a serious issue.