On Fri, 02.10.09 19:26, Matthew W. S. Bell (matthew at bells23.org.uk) wrote: > > > To test this, I ran 'udevadm trigger', which resulted in both cards > > > being detected. However, I now cannot reproduce the original problem. > > > > This only triggers "change" events, which is what PA looks for. Try > > triggering "add" events. > > Er, yes, doing this works, because they are change events. The point is > that when module-udev-detect starts, it use the udev_enumerate interface > to get udev devices, and this is not a monitor interface. Therefore, > there is NO action associated with the device, so nothing gets triggered > in process_device(). I think. Oh, hmm, I was confused, sorry. Is the SOUND_INITIALIZED property set for your device when enumerating fails? If not then PA won't find the device, and you can blame this bug on Marco. He should really stop doing his own rule-nonsense. Lennart -- Lennart Poettering Red Hat, Inc. lennart [at] poettering [dot] net http://0pointer.net/lennart/ GnuPG 0x1A015CC4
