Comment 5 for bug 568422

I'm trying to see why we have two reporters of this bug and you can't reproduce it. One difference is that they ran the recommended way to upgrade (update-manager -> upgrade to the new version of the distribution), which runs extra scripts to make sure the upgrade runs correctly. Scott seems to have used a different path, which may or may not explain the difference...

"update-manager -d" is the same as "update-manager" except that it enables the possibility to upgrade to the release in development. Normal users won't have that option until Lucid is released.