Bug 701069
| Summary: | Samsung SCX-4500W scanner not recognised | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mike C <mike.cloaked> |
| Component: | sane-backends | Assignee: | Nils Philippsen <nphilipp> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 14 | CC: | covex, nphilipp |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | sane-backends-1.0.22-3.fc14 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-05-17 01:06:56 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Same applies for my SCX-4500 on F14. I can not scan anymore. I did not need to add any udev rules as I have a ID 04e8:3426 Samsung Electronics Co., Ltd SCX-4500 Laser Printer that was supported out of the box. $ sane-find-scanner found USB scanner (vendor=0x04e8 [Samsung], product=0x3426 [SCX-4500 Series]) at libusb:001:002 $ scanimage -L No scanners were identified. I can confirm that downgrading yum downgrade sane-backends sane-backends-libs works around the problem and scanner is found by xsane and working, while scanimage still complains no devices found. I never used scanimage commandline tool before. Forgot: downgrade was to 1.0.21-3.fc14 Thanks Adam - worth knowing - though I wonder what got broken in the newer package build? Is there anything that can be tested to diagnose where the specific fix is needed so that a working version can be built? By the way I believe that the scanner hardware and internals for both 4500 and 4500W are the same - the only difference as far as I know is that the W has the wireless networking - so any fix for one should fix the other as far as scanning goes. The newest package in updates-testing fixes the issue for me in f14 with my SCX4500W. https://admin.fedoraproject.org/updates/sane-backends-1.0.22-3.fc14?_csrf_token=c2619671c51f746e7eda09a9f244f193655e3811 sane-backends-1.0.22-3.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/sane-backends-1.0.22-3.fc14 sane-backends-1.0.22-3.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report. |
Description of problem: Where previously the scanner section of this multifunction printer was working provided the correct entry was in /lib/udev/rules.d/65-libsane.rules it is no longer working with current sane-backends Version-Release number of selected component (if applicable): sane-backends-1.0.22-1.fc14.i686 How reproducible: Every time Steps to Reproduce: 1. Plug in printer/scanner and switch on 2. Go to GIMP and select File->Create->XSane: Device Dialog... 3. Receive message Device not found. Alternatively do scanimage -L gives No scanners were identified. .... Actual results: Cannot get device identified, and yet: [root@home1 ~]# sane-find-scanner gives: found USB scanner (vendor=0x04e8 [Samsung Electronics Co., Ltd.], product=0x342b [SCX-4500W Series]) at libusb:001:007 Expected results: Scanner should be identified and begin working correctly as a scanner. Additional info: lsusb -v gives output that includes: Bus 001 Device 007: ID 04e8:342b Samsung Electronics Co., Ltd Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x04e8 Samsung Electronics Co., Ltd idProduct 0x342b bcdDevice 1.00 iManufacturer 1 Samsung Electronics Co., Ltd. iProduct 2 SCX-4500W Series xxxxx bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 55 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower 2mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 10 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x84 EP 4 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 10 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 7 Printer bInterfaceSubClass 1 Printer bInterfaceProtocol 2 Bidirectional iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 10 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 10 Device Qualifier (for other device speed): bLength 10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 bNumConfigurations 1 Device Status: 0x0001 Self Powered The file /lib/udev/rules.d/65-libsane.rules correctly contains: # Samsung SCX-4500W ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="342b", ENV{libsane_matched}="yes" The file /etc/sane.d/dll.conf contains xerox_mfp at the bottom and /etc/sane.d/xerox_mfp.conf has: # Samsung SCX-4500W usb 0x04e8 0x342b and I have checked that selinux is not involved by switching to permissive. The scanner is still not identified and remains not working. The device was working properly prior to recent updates in f14 but several updates have occurred to sane-backends between when it was working and the present time. The file /var/log/messages contains the following relevant to the device turning on: Apr 30 21:32:57 home1 kernel: [ 1952.492083] usb 1-1: new high speed USB device using ehci_hcd and address 7 Apr 30 21:32:57 home1 kernel: [ 1952.606978] usb 1-1: New USB device found, idVendor=04e8, idProduct=342b Apr 30 21:32:57 home1 kernel: [ 1952.606982] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Apr 30 21:32:57 home1 kernel: [ 1952.606985] usb 1-1: Product: SCX-4500W Series Apr 30 21:32:57 home1 kernel: [ 1952.606987] usb 1-1: Manufacturer: Samsung Electronics Co., Ltd. Apr 30 21:32:57 home1 kernel: [ 1952.606989] usb 1-1: SerialNumber: 9J21BFFS800593Y Apr 30 21:32:57 home1 kernel: [ 1952.608225] usblp0: USB Bidirectional printer dev 7 if 1 alt 0 proto 2 vid 0x04E8 pid 0x342B Apr 30 21:32:59 home1 hp[3735]: io/hpmud/pp.c 627: unable to read device-id ret=-1 Apr 30 21:32:59 home1 python: io/hpmud/pp.c 627: unable to read device-id ret=-1 Apr 30 21:32:59 home1 udev-configure-printer: Re-enabled printer ipp://localhost:631/printers/SCX-4500W-Series Apr 30 21:45:31 home1 scanimage: io/hpmud/pp.c 627: unable to read device-id ret=-1 Apr 30 21:53:52 home1 scanimage: io/hpmud/pp.c 627: unable to read device-id ret=-1 The system is fully up to date and has been rebooted today as a further check. The following packages are also installed: xsane-gimp-0.998-3.fc14.i686 xsane-common-0.998-3.fc14.i686