I wondered if this bug might be fixed in the recent kernel update that was distributed for 7.04 Feisty, but it seems not. The update restored my /boot/grub/menu.lst file to it's original state with no 'break=mount', and the result was that my system again failed to boot. I've reinstated my amendments to menu.lst and can get round the problem again, but can anyone explain what the 'fixed' status of the bug on launchpad really means? In the case of this particular problem it looks as though a 'fix' has been available since 13th April?
>From the evidence, I guess it means the source now contains a fix but, as far as many Ubuntu users are concerned, that's a mile away from it meaning the fix is distributed as an update to the user-base. Is there anything in launchpad that indicates when a bug-fix has been released in the sense of being available as an updated binary that's accessible via update manager, as opposed to being available as amended source code? Apologies if this is not the best place to ask this question, but I've asked launchpad-related questions elsewhere and had no reply.... -- boot-time race condition initializing md https://bugs.launchpad.net/bugs/103177 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
