https://bugzilla.novell.com/show_bug.cgi?id=283132 ------- Comment #1 from siegfried.olschner@novell.com 2007-06-12 01:57 MST ------- Created an attachment (id=145478) --> (https://bugzilla.novell.com/attachment.cgi?id=145478&action=view) Message was displayed -- scanner is not plugged in! No other device available at the USB 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=283132 coolo@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |coolo@novell.com AssignedTo|coolo@novell.com |kasievers@novell.com Component|KDE |Hotplug ------- Comment #3 from coolo@novell.com 2007-06-12 02:00 MST ------- The "scanner" is there, so it's not a KDE problem: udi = '/org/freedesktop/Hal/devices/usb_device_0_0_0000_00_1d_7_usbraw' linux.device_file = '/dev/bus/usb/001/001' (string) org.freedesktop.Hal.Device.resmgr.method_execpaths = {'hal-resmgr-grant', 'hal-resmgr-revoke'} (string list) usbraw.device = '/dev/bus/usb/001/001' (string) info.capabilities = {'usbraw', 'scanner'} (string list) info.udi = '/org/freedesktop/Hal/devices/usb_device_0_0_0000_00_1d_7_usbraw' (string) linux.subsystem = 'usb_device' (string) org.freedesktop.Hal.Device.resmgr.method_signatures = {'', ''} (string list) info.interfaces = {'org.freedesktop.Hal.Device.resmgr'} (string list) org.freedesktop.Hal.Device.resmgr.method_names = {'Grant', 'Revoke'} (string list) info.product = 'USB Raw Device Access' (string) linux.hotplug_type = 2 (0x2) (int) linux.sysfs_path = '/sys/class/usb_device/usbdev1.1' (string) info.callouts.remove = {'hal-resmgr'} (string list) info.category = 'usbraw' (string) resmgr.class = 'scanner' (string) info.callouts.add = {'hal-resmgr'} (string list) info.parent = '/org/freedesktop/Hal/devices/usb_device_0_0_0000_00_1d_7' (string) org.freedesktop.Hal.Device.resmgr.method_argnames = {'', ''} (string list) The 001/001 is nothing real though: g22:/suse/coolo # lsusb Bus 002 Device 001: ID 0000:0000 Bus 001 Device 002: ID 10df:0500 In-Win Development, Inc. Bus 001 Device 001: ID 0000:0000 Bus 001 Device 003: ID 2001:f103 D-Link Corp. [hex] Bus 004 Device 001: ID 0000:0000 Bus 003 Device 001: ID 0000:0000 Bus 005 Device 001: ID 0000:0000 So I'd go for either kernel or udev problem. -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=283132 lnussel@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lnussel@novell.com ------- Comment #5 from lnussel@novell.com 2007-06-12 04:24 MST ------- I guess yast2-scanner installs an fdi file that does this. -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=283132 jsmeix@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |siegfried.olschner@novell.com ------- Comment #6 from jsmeix@novell.com 2007-06-12 07:03 MST ------- /etc/hal/fdi/policy/10osvendor/70-scanner.fdi is created via postinstall script when the sane package is installed. I lists all known scanners. Additionally /etc/hal/fdi/policy/10osvendor/80-scanner.fdi is created by the YaST scanner config and it may list scanners which are not yet in 70-scanner.fdi The entries look like this: <match key="info.category" string="usbraw"> <match key="@info.parent:usb_device.vendor_id" int="0x03f0"> <match key="@info.parent:usb_device.product_id" int="0x0101"> <append key="info.capabilities" type="strlist">scanner</append> </match> </match> </match> The question is now what the values of @info.parent:usb_device.vendor_id and @info.parent:usb_device.product_id are in this particular case. Sigi, please provide a complete lshal output and your /etc/hal/fdi/policy/10osvendor/80-scanner.fdi 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=283132 ------- Comment #8 from jsmeix@novell.com 2007-06-13 07:49 MST ------- The interesting part of attachment #145950: ---------------------------------------------------------------------------- udi = '/org/freedesktop/Hal/devices/usb_device_0_0_0000_00_1d_7' ... usb_device.vendor_id = 0 (0x0) (int) ... usb_device.product_id = 0 (0x0) (int) .. udi = '/org/freedesktop/Hal/devices/usb_device_0_0_0000_00_1d_7_usbraw' ... info.capabilities = {'usbraw', 'scanner'} (string list) ... info.parent = '/org/freedesktop/Hal/devices/usb_device_0_0_0000_00_1d_7' (string) ---------------------------------------------------------------------------- In /etc/hal/fdi/policy/10osvendor/80-scanner.fdi there is the reason: ---------------------------------------------------------------------------- <match key="info.category" string="usbraw"> <match key="@info.parent:usb_device.vendor_id" int="0x"> <match key="@info.parent:usb_device.product_id" int="0x"> <append key="info.capabilities" type="strlist">scanner</append> </match> </match> </match> ---------------------------------------------------------------------------- I have no idea how YaST writes this entry. ---------------------------------------------------------------------------- g22:~ # grep test_and_set_scanner_access_permissions /var/log/YaST2/y2log* /var/log/YaST2/y2log-1:2007-04-26 09:05:13 <1> e138(13959) [YCP] Scanner.ycp:262 Executing bash commandline: /usr/lib/YaST2/bin/test_and_set_scanner_access_permissions 'epkowa:libusb:005:009;unknown;' ---------------------------------------------------------------------------- looks perfectly normal. Perhaps "lsusb" lists this scanner with ID 0000:0000 and then /usr/lib/YaST2/bin/test_and_set_scanner_access_permissions would write the above entry using this IDs? But at least sane-find-scanner detects it with a correct ID because ---------------------------------------------------------------------------- g22:~ # grep 'Autodetected scanners:' /var/log/YaST2/y2log* /var/log/YaST2/y2log-1:2007-04-26 09:00:20 <1> e138(13959) [YCP] Scanner.ycp:523 Autodetected scanners: [$[]] /var/log/YaST2/y2log-1:2007-04-26 09:00:31 <1> e138(13959) [YCP] Scanner.ycp:523 Autodetected scanners: [$["connection":"USB", "description":"USB scanner (vendor=0x04b8 [EPSON], product=0x010c [Perfection640 ]) at libusb:005:009", "device":"libusb:005:009", "manufacturer":"EPSON", "model":"Perfection640 ", "usb_product_id":"0x010c", "usb_vendor_id":"0x04b8"], $[]] ---------------------------------------------------------------------------- Sigi, please connect your scanner and provide a "lsusb" output. -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=283132#c10 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #10 from Johannes Meixner 2007-06-29 08:13:12 MST --- In comment #8 I wrote: 'epkowa:libusb:005:009;unknown;' See https://bugzilla.novell.com/show_bug.cgi?id=285934#c13 009 is an illegal octal value so that this is probably the reason why a wrong USB device was entered in 80-scanner.fdi -- 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.