[dapper->hardy] udev not upgraded (was: using kernel 2.6.24-12 after upgrading from dapper to hardy isn't possible)

[Brian Murray]

Binary package hint: update-manager

I was upgrading from dapper to hardy today and the upgrade seemed successful. However, when I boot the 2.6.24-12 kernel the system is unusable - even in single user mode.

[Brian Murray (brian-murray)]

Bug 203385 has some information about how using friendly-recovery isn't really possible.

[Michael Vogt (mvo)]

Thanks for your bugreport.

It looks like the problem is the following:

2008-03-18 10:59:41,931 DEBUG Held-back: gnome-games-data udev lvm2 mdadm dmsetup xserver-xorg-input-synaptics python-launchpad-integration rhythmbox

[Albert Damen (albrt)]

I got the same problem after an LTS upgrade in kvm. After manually upgrading udev, I could login in gnome again.
There still is some problem: hal did not start due to missing symlinks in rcX.d Manually starting hal works ok.

[Michael Vogt (mvo)]

@Albert: thanks for this additional information. The fix for udev should be in the archive once it gets unfrozen. I will try to reproduce the hal problem you mentioned in my next test-run.

[Steve Langasek (vorlon)]

I believe this is now fixed in udev, but the bug report was not auto-closed because the bug was assigned to the wrong package. Changelog was:

udev (117-4ubuntu1) hardy; urgency=low

 * change the "Breaks: libdevmapper1.02" to a Conflict to help
    the apt resolver calculating the upgrade (LP: #203756)

 -- Michael Vogt < <email address hidden>> Wed, 19 Mar 2008 16:27:39 +0100

[Albert Damen (albrt)]

Confirming the fix of udev and hal. I just completed a new LTS upgrade in kvm. This time I could login in Gnome without problems and hal was running.

hal (0.5.10+git20080301-1ubuntu3) hardy; urgency=low

  * debian/hal.postinst:
    - make sure that the start scripts are installed on
      dapper->hardy upgrades (LP: #203756)

 -- Michael Vogt <email address hidden> Thu, 20 Mar 2008 10:17:43 +0100