Comment 55 for bug 249340

Martin, when you say "partial upgrade", "full apt-get dist-upgrade", etc. are you talking about upgrading after switching to hardy's repositories, or getting up to date with the latest gutsy packages?

As far as I can tell from my own experiences and the comments above, this bug only occurs when using the latest gutsy kernel (2.6.22-15). If you didn't already, I'd suggest trying:

1) Install gutsy (not just in a chroot, since you need to boot with its kernel)
2) Bring gutsy fully up-to-date with an apt-get dist-upgrade (don't yet use hardy's repositories)
3) Reboot so you are running with the latest gutsy kernel
4) Attempt to upgrade to hardy using whatever method pleases you (I used update-manager)

Unfortunately I'm not able to test this procedure myself at the moment, but it hopefully mirrors the state my system was in when I experienced this bug.