I will try this again. I am not 100% sure I had easyubuntu on the machine (95% sure). However, I would recommend not rejecting this bug because aside from the easyubuntu part, what I did was in every case precisely what was recommended on the ubuntu/kubuntu sites. The package manager was unable to determine in advance that the upgrade would fail, and left the machine in a pretty fubar state. This would be very bad if it happens to people with real data on their machines.
(Not to mention that most people will be upgrading machines with easyubuntu on them.) Is there some way to determine from what's on the machine itself now where it was in the upgrade process so we can at least possibly track down where in the upgrade process it was when it decided to quit? -- Upgrading from dapper to edgy fails if KDE 3.5.4 is present https://launchpad.net/bugs/63694 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
