From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrey Borzenkov Date: Sat, 14 Aug 2010 16:16:09 +0000 Subject: udevadm triggers wrong event type for failed events Message-Id: <201008142016.12747.arvidjaar@mail.ru> MIME-Version: 1 Content-Type: multipart/mixed; boundary="nextPart7047355.5oCfA6OMbW" List-Id: To: linux-hotplug@vger.kernel.org --nextPart7047355.5oCfA6OMbW Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I was puzzled why my bluetoothd was not started on boot. It turned out=20 the following: =2D bluetoothd requires D-Bus so attempt to start it early (may be, as=20 early as initrd) fails =2D event is saved as failed event; but only device path is preserved, no=20 information about which event type failed =2D later udevadm trigger --type=3Dfailed is run; but by default this=20 triggers "change" event instead of "add". There is no "change" action=20 for bluetooth subsystem (nor do I think it normally emits such event) so=20 nothing happens. This change was introduced relatively recently in commit 236fae6cf1a619a92174efdf84cd7d91e7d4348d Author: Kay Sievers Date: Mon Apr 12 17:56:32 2010 +0200 udevadm: trigger - switch default action from "add" to "change" Now, I could of course just go and add --action=3Dadd to udev-post=20 initscript. The question is - is it correct to assume that every failed=20 event is "add"? Should not event type be preserved for later correct re- trigger? BTW both init/udev-retry.service from udev GIT and udev-post from Fedora=20 have the same problem (Mandriva is using Fedora version). --nextPart7047355.5oCfA6OMbW Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEABECAAYFAkxmwUoACgkQR6LMutpd94ygswCgu0qawXF2i6C+XRTSJXVm++Jp 96EAnjEKDbtff2Dso8xnXL+Beb1/FdCu =jelu -----END PGP SIGNATURE----- --nextPart7047355.5oCfA6OMbW--