[Pkg-kde-extras] Bug#720721: skanlite: usbfs: interface 0 claimed by usbfs while 'skanlite' sets config #1

[Ross Boylan]

I disconnected the USB cable and reconnected it. skanlite is working
again.  I waited several minutes between scans, leaving the program
running, and it still worked.

I also got red boxes on my preview again; apparently it automatically
tries to identify interesting regions.  It wasn't close, and so I
selected "disable automatic selections" in the settings.  That seems to
have fixed that problem.

I ran udevadm monitor and recorded what happened when I reconnected the
scanner. It appears there is more than one device, or at least more than
one bus location associated with the scanner.  It is not a multifunction
device.

root at tempserver:/# date; udevadm monitor --kernel --udev --property
Sat Aug 24 17:27:37 PDT 2013
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

# deleted output from the removal
# it looked similar, except it used bus/usb/003/009

KERNEL[6991172.123848]
add      /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2 (usb)
ACTION=add
BUSNUM=003
DEVICE=/proc/bus/usb/003/010
DEVNAME=bus/usb/003/010
DEVNUM=010
DEVPATH=/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2
DEVTYPE=usb_device
MAJOR=189
MINOR=265
PRODUCT=4b8/11e/100
SEQNUM=6721
SUBSYSTEM=usb
TYPE=255/255/255
UDEV_LOG=3

KERNEL[6991172.124434]
add      /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0 (usb)
ACTION=add
DEVICE=/proc/bus/usb/003/010
DEVPATH=/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0
DEVTYPE=usb_interface
INTERFACE=255/255/255
MODALIAS=usb:v04B8p011Ed0100dcFFdscFFdpFFicFFiscFFipFF
PRODUCT=4b8/11e/100
SEQNUM=6722
SUBSYSTEM=usb
TYPE=255/255/255
UDEV_LOG=3

UDEV  [6991172.129112]
add      /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2 (usb)
ACTION=add
BUSNUM=003
DEVICE=/proc/bus/usb/003/010
DEVNAME=/dev/bus/usb/003/010
DEVNUM=010
DEVPATH=/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2
DEVTYPE=usb_device
ID_BUS=usb
ID_MODEL=EPSON_Scanner
ID_MODEL_ENC=EPSON\x20Scanner
ID_MODEL_ID=011e
ID_REVISION=0100
ID_SERIAL=EPSON_EPSON_Scanner
ID_USB_INTERFACES=:ffffff:
ID_VENDOR=EPSON
ID_VENDOR_ENC=EPSON
ID_VENDOR_ID=04b8
MAJOR=189
MINOR=265
PRODUCT=4b8/11e/100
SEQNUM=6721
SUBSYSTEM=usb
TAGS=:udev-acl:
TYPE=255/255/255
UDEV_LOG=3
USEC_INITIALIZED=6991172125532
libsane_matched=yes

UDEV  [6991172.132784]
add      /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0 (usb)
ACTION=add
DEVICE=/proc/bus/usb/003/010
DEVPATH=/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0
DEVTYPE=usb_interface
INTERFACE=255/255/255
MODALIAS=usb:v04B8p011Ed0100dcFFdscFFdpFFicFFiscFFipFF
PRODUCT=4b8/11e/100
SEQNUM=6722
SUBSYSTEM=usb
TYPE=255/255/255
UDEV_LOG=3
USEC_INITIALIZED=6991172129552

There are 2 blocks for 
add      /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0 (usb)
and 2 for
add      /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2 (usb)

I'm not sure if that means there were 2 kernel add events for each, or
just that a block is printed each time a udev rule fires.  The 3rd block
appears to be from /lib/udev/rules.d/60-libsane.rules