13.1 recently upgraded from 12.2 where scanning with XSane worked. Neither XSane nor simple-scan find the scanner
XSane with error: Failed to open device ‘naish:libusb:003:005’ Device busy
simple-scan with error: Unable to connect to scanner
:~> lsusb
Bus 003 Device 005: ID 03f0:0205 Hewlett-Packard ScanJet 3300c
:~> scanimage -T -d plustek:libusb:003:005
scanimage: open of device plustek:libusb:003:005 failed: Error during device I/O
Unplugging and plugging scanner produces the following output in ‘messages’
2014-09-01T09:35:05.119132-03:00 murdoch kernel: [146249.353437] usb 3-3: USB disconnect, device number 5
2014-09-01T09:35:05.139400-03:00 murdoch colord: device removed: sysfs-Hewlett-Packard-HP_ScanJet_3300C
2014-09-01T09:35:07.125709-03:00 murdoch kernel: [146251.357596] usb 3-3: new full-speed USB device number 6 using ohci-pci
2014-09-01T09:35:07.276494-03:00 murdoch kernel: [146251.508528] usb 3-3: New USB device found, idVendor=03f0, idProduct=0205
2014-09-01T09:35:07.276538-03:00 murdoch kernel: [146251.508542] usb 3-3: New USB device strings: Mfr=2, Product=4, SerialNumber=0
2014-09-01T09:35:07.276541-03:00 murdoch kernel: [146251.508549] usb 3-3: Product: HP ScanJet 3300C
2014-09-01T09:35:07.276568-03:00 murdoch kernel: [146251.508554] usb 3-3: Manufacturer: Hewlett-Packard
2014-09-01T09:35:07.284752-03:00 murdoch logger: udev hpmud.rules runs hp-firmware to test if HP device with USB vendor ID 03f0 and USB product ID 0205 at USB bus ID 003 and USB device ID 006 needs firmware and if yes to upload it
2014-09-01T09:35:07.523920-03:00 murdoch hp-firmware: hp-firmware[24306]: error: Invalid USB Device ID or USB bus ID. No device found.
2014-09-01T09:35:07.561704-03:00 murdoch colord: Device added: sysfs-Hewlett-Packard-HP_ScanJet_3300C
:~> hp-firmware
…]
error: No devices that support firmware download found.
I’m not sure what else to check to see why this scanner does not work in 13.1?
If you use hplip software/drivers you may need to activate hpaio by un-commenting the corresponding line in /etc/sane.d/dll.conf.
This solved a comparable problem for me lately.