Upgrade jaunty -> karmic beta problematic
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
udev (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
update-manager (Ubuntu) |
Invalid
|
High
|
Unassigned |
Bug Description
I performed an update-manager controlled upgrade from jaunty to karmic on 20091009.
Update-manager told me it could not complete the upgrade, but would do as much as possible. I expected it to tell me how to proceed after finishing, but that did not happen. From earlier experience, I know that you have to reboot; in a clean installation the installer knows to continue after the reboot.
After reboot, I seemingly did not have network connection, but I soon found out that it was the resolver that was broken. I was not familiar with the new resolver, but eventually found out that I had to do:
resolvconf -a eth0 < /etc/resolv.
The installation had overwritten /etc/resolv.conf, but luckily I had a copy. The network was back. It now turns out that I need to repeat the above resolvconf call after every reboot.
I had to complete the install "manually". The package db was left in an unconfigured by the update-manager, so I had to go through a number of aptitude commands to complete the upgrade, including the manual remove of some packages. During this process, aptitude suggested to remove e.g. kubuntu-desktop.
As an experienced Ubuntu user, I was able to get a working kubuntu system relatively fast, but a novice would have been completely lost.
After the upgrade, I am left with some messages on the console which I still don't understand:
1) Shortly after boot, this:
[ 0.746572] pci 0000:05:04.0: BAR 6: address space collision on of device [0xfeac0000-
2) Lots of these:
Oct 6 13:57:49 dmz-212 udevd-work[928]: rename(
In addtion, there are problems with postgresql and mysql which I have not had time to investigate.
affects: | ubuntu → update-manager (Ubuntu) |
Thanks for your bugreport.
Could you please attach the logs from /var/log/ dist-upgrade/ * ?