Comment 28 for bug 281335

Thanks for the attribute-walk outputs, they showed that all attribute checks in

  SUBSYSTEM=="usb", ATTR{bDeviceClass}=="00|ff", ATTR{bDeviceSubClass}=="00|ff", ENV{DEVTYPE}=="usb_device"

*should* match.

Now I still don't understand why the rule doesn't work in the mobile_action_switch block. The problem with your separate one is that it is called several times, which we want to avoid.

With the rule in /lib and in the switch block (as currently in Karmic), could you please give me the output of

  udevadm test --action=add /devices/pci0000:00/0000:00:1d.7/usb2/2-4

after plugging in the device (but not ejecting it yet).

Also, let's eliminate what clause is responsible for breaking the rule: Can you please comment the

   SUBSYSTEM=="usb", ATTR{bDeviceClass}=="00|ff", ATTR{bDeviceSubClass}=="00|ff", ENV{DEVTYPE}=="usb_device"
   GOTO="mobile_action_end"

lines in /lib/udev/rules.d/61-mobile-action.rules entirely by prepending a "#", replug the device, and check if it works?

If that works, can you please restore the two lines, and then drop each test in succession and see which one breaks? (i. e. delete everything after a comma until and including to the next comma).

Thanks!