Comment 12 for bug 695658

@Eric Arthur
OK, this is my not-stupid post. ;-)

This bug is marked as a duplicate of bug 700686. That bug was fixed, and the fix works in some situations. It appears that most, or at least some, Ubuntu Server installations don't suffer from the problem anymore. Since this really was the original report, it makes sense to continue considering this to be the same bug as bug 700686.

When I saw that I could still reproduce this bug on some Natty systems (this was on April 14th, 2011), I asked how best to report that, by posting a comment in bug 700686. (I posted there instead of here, since this bug is a duplicate, and that bug is not.) Colin Watson instructed me to create a *new* bug, which I did. That new bug is bug 761830. I posted a link to bug 761830 in bug 700686, but I did not post a link to it in this bug, since this bug is marked as a duplicate.

From your description in your post here (post #9), your experience is entirely consistent with the continued problem described in bug 761830. So I've subscribed you to bug 761830, and I recommend you re-post the information that you've posted here in bug 761830 (and also mark that bug as affecting you, using the green "This bug affects..." link at the top). I don't think anyone else has reported that bug 761830 occurs for minimal Maverick systems upgraded to Natty, so it's particularly valuable for you to post about that, but you should also mention (in the same post) that it happened when you installed from the Natty amd64 minimal CD.