linux-restricted package not updated with new kernel package in dapper

[ben hall]

Binary package hint: update-manager

On updating with update-manager (or alternatively apt-get or aptitude from the command line) if a new kernel package (linux-image-2.6.x.y-z-arch) is found and selected the associated restricted modules packages (linux-restricted-modules-2.6.x.y-z-arch) is not installed by default. This has occurred a couple of times and whilst it is not a show stopper, it does stop X and some other hardware dependent software from starting (I use an nvidia video card). It also occurs rarely enough to require some time troubleshooting before realizing what the problem is, and I would argue is unexpected behaviour.
I believe that I have encountered the same problems with edgy, but I don't have access to a machine running edgy to test any more. I have however also been using feisty (since ~herd 4) but haven't come across this yet.
Is it possible to make the linux-image package conditionally dependent on linux-restricted, if an older version of linux-restricted is installed? Alternatively the linux-restricted package could be made to update more appropriately.

Many thanks

[Sebastian Heinlein (glatzor)]

There are virtual packages that ensure that you always have got the latest kernel and the corresponding restricted modules installed on your system: linux-image-386 and linux-restricted-modules-386.

This is a packaging issue and not one of update-manager.

Cheers,

Sebastian

[Mike Dahlgren (dahlgren)]

I believe this has been fixed in all new supported versions of Ubuntu (post Edgy)