Greg Dennis

There may also be some undesirable interaction between the usbmuxd rules file and the libgpod rules file that may or may not be related. It looked like the presence of...

Sure, I'll try to provide more details. Linux kernel and distro: 3.13.0-30-generic #54~precise2-Ubuntu SMP Wed Jun 11 16:11:17 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux The udev rules are the same...

Yes, it does. I suspect usb_discover may be called just before it appears, though. The "Device discovery triggered by udev" log line, but I think usb_discover is just called too...

Hmm, the issue persists in usbmuxd 1.0.9, and adding that sleep(5) has no effect. I am not using systemd. I have to rerun usbmuxd at the command line to get...

To debug, I'm start from a clean state with no usbmuxd running and no devices attached. Now I run: $ sudo /usr/local/sbin/usbmuxd -u -U usbmux -v -f This produces the...

When the device is added, it is not automatically picked up by usbmuxd through the udev rules. That is _not_ expected, right? There looks to be some timing issue between...

Martin, my usbmuxd version was updated a couple weeks ago, but it looks to be just before the device discovery string was updated. I'm updating now, but before I post...

Assuming that lopping off that d from rules file is a mistake, then after upgrading to head usbmuxd and running with with the long command line options and finest grained...

Ok, I have a workaround/fix. On line 206, right before the usb_discover call, I insert sleep(5): http://cgit.sukimashita.com/usbmuxd.git/tree/src/main.c?id=1dc5437d7c25df26368dcce8db75785eb48ec6aa#n206 This delays usb_discover until after the new client is detected, and everything works....

I meant to write "libusb" not "libusbm" above. We are using libusb 1.0.18.