udevadm trigger is called so that the events can all intentionally be
replayed in case a piece of hardware is now supported by that module. How
else would you achieve this behavior?
On Wed, Dec 17, 2008 at 15:40, Michael <email address hidden> wrote:
> Shoot me for not reading all the comments above. The udevadm trigger is
> what is causing it in my case too. This bug should probably be
> reassigned to dkms, as it should definitely not be calling that.
>
> --
> [MASTER] networkmanager display connections twice in intrepid
> https://bugs.launchpad.net/bugs/262974
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
udevadm trigger is called so that the events can all intentionally be
replayed in case a piece of hardware is now supported by that module. How
else would you achieve this behavior?
On Wed, Dec 17, 2008 at 15:40, Michael <email address hidden> wrote:
> Shoot me for not reading all the comments above. The udevadm trigger is /bugs.launchpad .net/bugs/ 262974
> what is causing it in my case too. This bug should probably be
> reassigned to dkms, as it should definitely not be calling that.
>
> --
> [MASTER] networkmanager display connections twice in intrepid
> https:/
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
--
Mario Limonciello
<email address hidden>