Created attachment 334821 [details] additional entry to 19-libsane.fdi to support HP OfficeJet 6110 Description of problem: OfficeJet 6110 not included in 19-libsane.fdi Version-Release number of selected component (if applicable): sane-backends-1.0.19-12.fc10.x86_64 How reproducible: grep for product id 0x2d11 in 19-libsane.fdi and its not found Expected results: expect to find product id 0x2d11 for Hewlett-Packard vendor id 0x03f0 listed under USB scanners section. Additional info: Should be a matter of adding the attached entry to 19-libsane.fdi After doing so, and rebooting, lshal shows correct access_control.type, etc: access_control.type = 'scanner' (string) info.bus = 'usb_device' (string) info.callouts.add = {'hal-usb-scanner-add', 'hal-acl-tool --add-device', 'hal\ -usb-scanner-add'} (string list) info.callouts.remove = {'hal-acl-tool --remove-device'} (string list) info.capabilities = {'scanner', 'access_control', 'access_control', 'access_c\ ontrol'} (string list) info.linux.driver = 'usb' (string) info.parent = '/org/freedesktop/Hal/devices/usb_device_1d6b_1_0000_00_13_0' \ (string) info.product = 'OfficeJet 6110' (string) info.subsystem = 'usb_device' (string)
The support for these HP scanners is in the hplip and libsane-hpaio packages. The hplip package seems to contain the configuration for HAL you requested -- it doesn't make much sense to put this in sane-backends when sane-backends doesn't drive the device. Please check if you can use your scanner with these packages installed.
I dug a bit more and I think you are correct... the 10-hplip.fdi policy file should cover my scanner. I did not have libsane-hpaio installed when I started configuring scanning for my OfficeJet 6110 and did not find the specific product id (0x2d11) when I grep'd the policy files. After adding that product id to 19-libsane.fdi I realized the hpaio driver was in a separate package and installed it. The 10-hplip.fdi file matches all usb devices for vendor id 0x03f0 (HP) and assumes they're all scanners - no explicit product ids in it so my grep turned up empty. I'm not near my scanner to turn it on and test, but I expect the hplip policy file will recognize my scanner. I'll test this evening when I get home and update this bug.
Yep - I removed my OfficeJet 6110 section from 19-libsane.fdi and rebooted. The scanner was still recognized as such, presumably by the 10-hplip.fdi policy. So I'll close this as an error with the carbon-based mass between the chair and keyboard. Cheers!