[Bug 36079] Kernel updates do not install new linux-restricted modules, brakes X.

afonic afonic at gmail.com
Wed Mar 22 23:40:37 UTC 2006


Public bug report changed:
https://launchpad.net/malone/bugs/36079

Description changed to:
    When a user installs a specific linux-restricted-modules package,
    like for example linux-restricted-modules-2.6.15-18-386 the
    metapackage (in this example linux-restricted-modules-386) does NOT
    get installed.

    This has as a result that when the kernel is updated (like in last
    update) the linux-restricted-modules packages is NOT updated to the
    new version kernel which results in an error message from the X
    server when using nVidia or other binary drivers, causing the X not
    to start at all and shooting the unexperienced user back in the
    console.

    I think this dependancy problem should be solved and an install of
    a specific linux-restricted-modules package should trigger the
    install of the general metapackage.

    This occured in Dapper Drake, during the 2.6.15-18 -> 2.6.15-19
    update.




More information about the kernel-bugs mailing list