https://bugzilla.novell.com/show_bug.cgi?id=335674#c1 --- Comment #1 from Oliver Neukum 2007-10-22 08:45:05 MST --- oneukum@oenone:~> scanimage -L No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). oneukum@oenone:~> cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 01 Lun: 00 Vendor: ATA Model: IBM-DTTA-351010 Rev: T56O Type: Direct-Access ANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 00 Vendor: HL-DT-ST Model: DVD-RAM GSA-H50L Rev: 1.00 Type: CD-ROM ANSI SCSI revision: 05 Host: scsi2 Channel: 00 Id: 00 Lun: 00 Vendor: ATA Model: SAMSUNG HD403LJ Rev: CT10 Type: Direct-Access ANSI SCSI revision: 05 Host: scsi3 Channel: 00 Id: 00 Lun: 00 Vendor: ATA Model: WDC WD740ADFD-00 Rev: 21.0 Type: Direct-Access ANSI SCSI revision: 05 Host: scsi4 Channel: 00 Id: 01 Lun: 00 Vendor: PIONEER Model: DVD-ROM DVD-303 Rev: 1.09 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi5 Channel: 00 Id: 00 Lun: 00 Vendor: Model: Scanner 636A4 Rev: 1.50 Type: Scanner ANSI SCSI revision: 02 oneukum@oenone:~> ll /dev/sg5 crw-r----- 1 root disk 21, 5 22. Okt 15:11 /dev/sg5 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=335674#c3 --- Comment #3 from Oliver Neukum 2007-10-22 08:49:48 MST --- oenone:/home/oliver # hwinfo --scanner 22: SCSI 600.0: 10c04 Scanner [Created at scsi.1561] Unique ID: 9IX0.tzaGPR0_7p8 SysFS ID: /class/scsi_generic/sg5 SysFS BusID: 6:0:0:0 Hardware Class: scanner Model: "Scanner 636A4" Device: "Scanner 636A4" Revision: "1.50" Device File: /dev/sg5 Device Number: char 21:5 Config Status: cfg=new, avail=yes, need=no, active=unknown 34: USB 00.0: 10c00 Scanner [Created at usb.122] UDI: /org/freedesktop/Hal/devices/usb_device_5da_99_noserial_if0 Unique ID: DHyf.RrixO09E+o1 Parent ID: 2UT6.4uPzupm_EOA SysFS ID: /devices/pci0000:00/0000:00:02.2/usb1/1-3/1-3.4/1-3.4:1.0 SysFS BusID: 1-3.4:1.0 Hardware Class: scanner Model: "Microtek ScanMaker X6" Hotplug: USB Vendor: usb 0x05da "Microtek" Device: usb 0x0099 "ScanMaker X6" Driver: "microtekX6" Driver Modules: "microtek" Speed: 12 Mbps Module Alias: "usb:v05DAp0099d0000dcFFdsc03dp00ic00isc00ip00" Driver Info #0: Driver Status: microtek is active Driver Activation Cmd: "modprobe microtek" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #31 (Hub) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=335674#c4 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |oneukum@novell.com --- Comment #4 from Johannes Meixner 2007-10-26 08:23:13 MST --- Oliver, can you activate the "set -x" line in /usr/lib/YaST2/bin/test_and_set_scanner_access_permissions and then attach its stdout and stderr output as text/plain attachments to this bug. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=335674#c6 --- Comment #6 from Oliver Neukum 2007-10-29 04:12:57 MST --- /etc/hal/fdi/policy/10osvendor/70-scanner.fdi: <?xml version="1.0" encoding="ISO-8859-1"?> <deviceinfo version="0.2"> <device> <match key="info.category" string="scsi_generic"> <match key="@info.parent:scsi.type" string="scanner"> <append key="info.capabilities" type="strlist">scanner</append> </match> </match> <match key="info.bus" string="usb_device"> <match key="usb_device.vendor_id" int="0x03f0"> <match key="usb_device.product_id" int="0x0101"> <append key="info.capabilities" type="strlist">scanner</append> </match> </match> </match> -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=335674#c8 --- Comment #8 from Oliver Neukum 2007-10-29 04:43:14 MST --- Created an attachment (id=180999) --> (https://bugzilla.novell.com/attachment.cgi?id=180999) /usr/lib/YaST2/bin/test_and_set_scanner_access_permissions > /tmp/stdout 2> /tmp/stderr stdout is empty -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=335674#c10 --- Comment #10 from Oliver Neukum 2007-10-29 08:11:56 MST --- I found out that the scanner no longer reliably works. I suggest you close the report until I can make sure it isn't caused by hardware failure. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=335674#c14 --- Comment #14 from Oliver Neukum 2007-10-30 03:50:14 MST --- OK, we are probably suffering from miscommunication. 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) }, -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=335674#c16 --- Comment #16 from Johannes Meixner 2007-10-30 04:12:44 MST --- Many thanks for the explanation in comment #14! 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* I assume it worked for you in the past when we had the ugly hack "/etc/init.d/sane-dev", see https://bugzilla.novell.com/show_bug.cgi?id=218393#c26 how you could re-enable it again. 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. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.