** Description changed: - Binary package hint: dkms + IMPACT: + DKMS must *NOT* call udevadm trigger. + This will have utterly dire consequences for the installed machine. + Minor bugs will be things like Network Manager and GNOME Power Manager reporting multiple copies of network cards, or batteries. + Major bugs will be apparent corruption of mounted filesystems (e.g. "/usr: data error") until a reboot. + And critical bugs include the entire /dev changing to root:root/660 on upgrade. - DKMS must *NOT* call udevadm trigger. + ADDRESSING BUG: + This has been fixed in git HEAD, as well as in jaunty. - This will have utterly dire consequences for the installed machine. + TEST CASE: + On a system that is using DKMS, try to remove an installed module and reinstall it. When DKMS is using udevadm trigger, you will see your network device duplicated in Network Manager. You will also disconnect and reconnect from the network. - Minor bugs will be things like Network Manager and GNOME Power Manager - reporting multiple copies of network cards, or batteries. + For a specified MODULE and VERSION, the following should be a good test + case. - Major bugs will be apparent corruption of mounted filesystems (e.g. - "/usr: data error") until a reboot. + dkms remove -m MODULE -v VERSION --all + /etc/init.d/dkms_autoinstaller start - And critical bugs include the entire /dev changing to root:root/660 on - upgrade. - - - If you want to find out whether the module can claim a device, why not just modprobe it? If it doesn't claim a device, it should error out and not be loaded. + REGRESSION POTENTIAL: + Anyone that was relying on this behavior of DKMS will have to add the optional UDEV_TRIGGER flag to the dkms.conf included with their driver package. The worst behavior expected from this is that the user will have to modprobe the module themselves initially rather that having udev replay the entire database. Also, a reboot would resolve this behavior.
-- Never call udevadm trigger! https://bugs.launchpad.net/bugs/320200 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
