Bugzilla – Bug 337766
set ACL via hal-resmgr even for "USB via SCSI" scanners
Last modified: 2007-10-30 11:03:20 UTC
see bug #335674 starting at https://bugzilla.novell.com/show_bug.cgi?id=335674#c14 There's a small number of USB scanners which are not talked to via libusb. They talk an unusual protocol which is a derivative of usb storage. Therefore they have their own kernel driver which registers with the SCSI subsystem. User space should treat them as SCSI scanners. These are their device ids: { USB_DEVICE(0x4ce, 0x0300) }, { USB_DEVICE(0x5da, 0x0094) }, { USB_DEVICE(0x5da, 0x0099) }, { USB_DEVICE(0x5da, 0x009a) }, { USB_DEVICE(0x5da, 0x00a0) }, { USB_DEVICE(0x5da, 0x00a3) }, { USB_DEVICE(0x5da, 0x80a3) }, { USB_DEVICE(0x5da, 0x80ac) }, { USB_DEVICE(0x5da, 0x00b6) }, As far as I see this means the current udev/HAL/hal-resmgr magic cannot work for those USB devices which are not accessed via /dev/bus/usb/*/* but via /dev/sg* For next openSUSE version I try to cover even those special devices by the udev/HAL/hal-resmgr magic. As far as I see the problem is how to find out via HAL which SCSI device file such an USB device actually uses so that hal-resmgr could set the appropriate ACL for the correct SCSI device file. Here is a "lshal" output of such a device: https://bugzilla.novell.com/attachment.cgi?id=180993
*** Bug 335674 has been marked as a duplicate of this bug. ***
To match via fdi file there must be either a hierarchical relationship from the usb device to the sg device (e.g usb device parent of sg device) or the scsi device (or its parent) itself must have vendor/product id.
But according to the "lshal" output, there seems to be no SCSI entry at all for this device (at least I don't find any by using "grep -i 5da"), so that it seems, we cannot solve it. I close it as WONTFIX but actually it is CANTFIX. Oliver, I cannot do much here because I don't have such a device. Feel free to reopen it if you have an idea how we could determine the SCSI device file from the HAL USB device entry.