Thanks for the additional information, I have everything I need now. The best solution would of course be to change the OSS modules to ship proper modaliases, so that they don't appear in the first place, but we cannot have that easily.
Some loud thinking/taking notes: Currently, state 'needs computer restart' is displayed if 'enabled' != 'loaded', which is bad because modules are enabled by default (this should really be 'allowed'), but not loaded for hardware which was not detected, i. e. for modules with overly generous modaliases. So let's change the rules like that: - initially, state is never 'needs restart'. for enabled and not loaded -> 'not used' - enabling a module modprobes it; success -> 'in use', failure -> 'needs restart' (this should work fine with the X.org drivers since they fail to modprobe if a free X driver is configured) - disabling a module -> needs restart (manual module unloading can have bad consequences) ** Changed in: restricted-manager (Ubuntu) Status: Needs Info => Confirmed -- restricted-manager shows all unused OSS modules as "needs computer restart" https://bugs.launchpad.net/bugs/102468 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs