It still sounds a bit radical. Basically dkms is causing an additional add event to be sent for every device in the system. What are the benefits for the user? The disadvantages seem to be clear, as hal's device database is messed up, along with anything that depends on it (in this case, the network manager applet). And this for a situation in which nothing was even added to the system. Perhaps just restarting hal would be good enough? Then its database would be up-to-date. I don't think that hotplug events are absolutely necessary in this case. Alternatively (and more difficult) one could try to work out which devices had changed in sysfs and only trigger event replay for those (although one should probably find some way to get "remove" events for them before the "add" ones get sent).
By the way, I did some quick (random) checking, and udevtrigger also messes up the hal database in Ubuntu 8.04, and in Fedora 8. In Fedora 8 it also messes up networking. I really don't think that this command is intended to be used once the system is up and running. -- [MASTER] networkmanager display connections twice in intrepid https://bugs.launchpad.net/bugs/262974 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
