Right, I'm talking about installing non-free OSS after installing Ubuntu, and then looking in restricted-manager. I am using OSS because ALSA doesn't support one of my audio interfaces. And the kernel is stock from the installation CD image.
OSS seems to install a module for *every* known sound card architecture, regardless of whether an instance of the hardware is present in the system it is installing into. The ones actually present in my system show up correctly in restricted-manager (they show as "in use"); all others show as "needs computer restart" even after restart. I think restricted-manager is failing in this case to distinguish between modules that (a) aren't working because a restart is needed, and (b) aren't working because the hardware isn't there. I agree this is a low-priority item, and definitely not a blocking bug. It's mostly a concern for new users who might see the persistent "needs computer restart" message as a sign that something is wrong -- whereas I know it just means those modules are not active and there's a perfectly good reason for that. Adding to the confusion is the fact that the module names used by OSS (and probably others out there) are in many cases non-intuitive -- I personally know that "envy24" is used by my M-Audio Delta TDIF, "hdaudio" is my motherboard's onboard audio, and "emu10k1x" is a module for hardware I don't have, for example, but a less experienced user might not appreciate that. And hence the bug report. I will attach your requested files later today; I don't have access to the system in question right now. -- 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
