Bump. Any another thoughts on this bug? It's hard to tell if this is a usb-modeswitch bug (i.e. a problem with usb_modeswitch_dispatcher) or if this is a problem with the udev rule itself (a usb-modeswitch-data bug).
Again, to summarize, I think that the non-working rule triggers when the USB interface is attached and executes the command: /lib/udev/usb_modeswitch '2-1/2-1:1.0'. The working rule triggers when the device itself is attached and executes the command: /lib/udev/usb_modeswitch '/2-1'. /lib/udev/usb_modeswitch '2-1/2-1:1.0' does not work. /lib/udev/usb_modeswitch '/2-1' works just fine. Thanks. On Fri, Nov 20, 2015 at 1:37 PM Blake Miner <miner.bl...@gmail.com> wrote: > ​Josh, > > Thanks for your response. > > Here's the thing... the udev rule is triggering, and systemd is running > the /lib/udev/usb_modeswitch program, which ends up running > usb_modeswitch_dispatcher. All is good there, but the problem (I think) is > as follows: > > The working udev rule: > * Triggered when the USB device is attached > * Ends up executing /lib/udev/usb_modeswitch '/2-1' > > The non-working catch-all udev rule: > * Triggered when the USB device **interface** is attached > * Ends up executing /lib/udev/usb_modeswitch '2-1/2-1:1.0' > > I don't understand the inner-workings of the usb_modeswitch_dispatcher, > but why does one rule work and not the other? >
