http://blog.gmane.org/gmane.comp.graphics.scanning.sane.devel hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.graphics.scanning.sane.devel/21034 <pre>Hi Oliver , I have few queries regarding xsane , I would be of great help if you can give some valuable inputs on this. In the investigation phase for a new scanner driver that would like to leverage the XSane application, 1.Does the vendor have a mechanism of disabling unsupported features in existed xsane 2.If the vendor wants to add a feature, is there a config file that you can modify without actually modifying code. Hence each vendor will not disturb other installations. If not, would XSane consider adding/disabling unsupported features? 3.And how do we submit our changes? 4.What is the mode of deployment for our scanner driver frontend ? Is it through XSane updates, or can we ship the same externally through an installer. Regards Ganapati Hegde ______________________________________________________________________________ DISCLAIMER: This electronic message and any attachments to this electronic message is intended for the exclusive use of the addressee(s) named herein and may contain legally privileged and confidential information. It is the property of Celstream Technologies Pvt Limited. If you are not the intended recipient, you are hereby strictly notified not to copy, forward, distribute or use this message or any attachments thereto. If you have received this message in error, please delete it and all copies thereof, from your system and notify the sender at Celstream Technologies or administrator&lt; at &gt;celstream.com immediately. ______________________________________________________________________________ </pre> Ganapati Hegde 2012-05-25T13:55:29 http://comments.gmane.org/gmane.comp.graphics.scanning.sane.devel/21033 <pre>I'm running mac osx 10.7 and originally was set up using the packages available here: http://www.ellert.se/twain-sane/ (libusb, sane backends, twain sane interface). My scanner was being detected fine last week, since then I installed drivers for a different scanner (No way that caused this problem I imagine) and configured, and make install'd the libusb source. After that scanimage -L was no longer working, but sane-find-scanner still found the device. The result for that is: found USB scanner (vendor=0x04a9 [Canon], product=0x2220 [CanoScan], chip=LM983x?) at libusb:001:002-04a9-2220-ff-00. I've tried reinstalling those pakcages again with no success. Searching around on this archive I found someone with a similar problem who fixed it by configuring and make installing his sources again but that has not worked for me. Any help would be appreciated, thanks. </pre> Bryan McNeil 2012-05-24T17:56:22 http://comments.gmane.org/gmane.comp.graphics.scanning.sane.devel/21029 <pre>Hi Oliver , I was looking into the xsane source code. I would like to know whether any changes to xsane will be integrated? For the new product that I am looking at, I will have to remove support to some of the existing xsane features for example 'gamma widgets' as well as some of the options under 'File, Preferences etc'. Also I will be adding couple of new product specific feature to the frontend "xsane". Will these changes be integrated into the Xsane release? If not kindly let me know how do we write new frontend that can use the sane-backend? Regards Ganapati Hegde From: m. allan noah [mailto:kitno455&lt; at &gt;gmail.com] Sent: Wednesday, May 23, 2012 6:22 PM To: Ganapati Hegde Cc: sane-devel&lt; at &gt;lists.alioth.debian.org; Tripti Rai Subject: Re: [sane-devel] Adding new product The author of XSane is not a member of the sane project. You would have to ask him about how he accepts patches. But I doubt he will remove features from XSane just for you. You could certainly fork XSane, but you would have to adhere to its license. Are your product specific features compatible with the SANE API? What is the license of your backend. allan On Wed, May 23, 2012 at 8:27 AM, Ganapati Hegde &lt;ganapati.hegde&lt; at &gt;celstream.com&gt; wrote: Hi, I have some more questions on the way releases and changes are handled. 1. I was looking into the xsane source code. I would like to know whether any changes to xsane will be integrated? a. For the new product that I am looking at, I will have to remove support to some of the existing xsane features for example 'gamma widgets' as well as some of the options under 'File, Preferences etc'. Also I will be adding couple of new product specific feature to the frontend "xsane". Will these changes be integrated into the Xsane release? If not kindly let me know how do we write new frontend that can use the sane-backend? 2. Once backend code is submitted how many days will it take for release to happen, and when will the new backend version be available in SANE repository. 3. Will the releases for frontend and backend happen at the same time? Regards Ganapati Hegde From: m. allan noah [mailto:kitno455&lt; at &gt;gmail.com] Sent: Wednesday, May 16, 2012 5:50 PM To: Ganapati Hegde Subject: Re: [sane-devel] Adding new product Does your backend meet the SANE API? Does it use the same license as the existing sane-backends? If so, we can include it in sane-backends. The sane-backends package no longer includes any GUI frontends, so a front-end would have to be distributed separately. allan On Wed, May 16, 2012 at 8:03 AM, Ganapati Hegde &lt;ganapati.hegde&lt; at &gt;celstream.com&gt; wrote: Hi , I have a requirement to support new device , How can I integrate new product specific backend code with sane and to whom I need to send my code. My widgets are different from existing xsane frontend. Can I write my own product specific frontend code and integrate with sane backend ? Thanks Ganapati Hegde ________________________________________________________________________ ______ DISCLAIMER: This electronic message and any attachments to this electronic message is intended for the exclusive use of the addressee(s) named herein and may contain legally privileged and confidential information. It is the property of Celstream Technologies Pvt Limited. If you are not the intended recipient, you are hereby strictly notified not to copy, forward, distribute or use this message or any attachments thereto. If you have received this message in error, please delete it and all copies thereof, from your system and notify the sender at Celstream Technologies or administrator&lt; at &gt;celstream.com immediately. ________________________________________________________________________ ______ -- sane-devel mailing list: sane-devel&lt; at &gt;lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-request&lt; at &gt;lists.alioth.debian.org </pre> Ganapati Hegde 2012-05-24T11:11:56 http://comments.gmane.org/gmane.comp.graphics.scanning.sane.devel/21027 <pre>Hi, I have some more questions on the way releases and changes are handled. 1. I was looking into the xsane source code. I would like to know whether any changes to xsane will be integrated? a. For the new product that I am looking at, I will have to remove support to some of the existing xsane features for example 'gamma widgets' as well as some of the options under 'File, Preferences etc'. Also I will be adding couple of new product specific feature to the frontend "xsane". Will these changes be integrated into the Xsane release? If not kindly let me know how do we write new frontend that can use the sane-backend? 2. Once backend code is submitted how many days will it take for release to happen, and when will the new backend version be available in SANE repository. 3. Will the releases for frontend and backend happen at the same time? Regards Ganapati Hegde From: m. allan noah [mailto:kitno455&lt; at &gt;gmail.com] Sent: Wednesday, May 16, 2012 5:50 PM To: Ganapati Hegde Subject: Re: [sane-devel] Adding new product Does your backend meet the SANE API? Does it use the same license as the existing sane-backends? If so, we can include it in sane-backends. The sane-backends package no longer includes any GUI frontends, so a front-end would have to be distributed separately. allan On Wed, May 16, 2012 at 8:03 AM, Ganapati Hegde &lt;ganapati.hegde&lt; at &gt;celstream.com&gt; wrote: Hi , I have a requirement to support new device , How can I integrate new product specific backend code with sane and to whom I need to send my code. My widgets are different from existing xsane frontend. Can I write my own product specific frontend code and integrate with sane backend ? Thanks Ganapati Hegde ________________________________________________________________________ ______ DISCLAIMER: This electronic message and any attachments to this electronic message is intended for the exclusive use of the addressee(s) named herein and may contain legally privileged and confidential information. It is the property of Celstream Technologies Pvt Limited. If you are not the intended recipient, you are hereby strictly notified not to copy, forward, distribute or use this message or any attachments thereto. If you have received this message in error, please delete it and all copies thereof, from your system and notify the sender at Celstream Technologies or administrator&lt; at &gt;celstream.com immediately. ________________________________________________________________________ ______ -- sane-devel mailing list: sane-devel&lt; at &gt;lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-request&lt; at &gt;lists.alioth.debian.org </pre> Ganapati Hegde 2012-05-23T12:27:57 http://comments.gmane.org/gmane.comp.graphics.scanning.sane.devel/21026 <pre>Hello, I've been trying to connect an HP ScanJet 5590 to an Atheros AR7241 rev 1 system (MIPS 24Kc V7.4 CPU), using OpenWrt. The CPU is big endian. I got the error: [hp5590] hp5590_get_ack [sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 12, value = 142, index = 32, len = 1 USB error: error sending control message: Connection timed out [sanei_usb] sanei_usb_control_msg: libusb complained: error sending control message: Connection timed out [hp5590] hp5590_get_ack: USB-in-USB: error getting acknowledge Using SANE_DEBUG_SANEI_USB=255 and SANE_DEBUG_HP5590=255 I got exactly the same result (even print_buffer() output was the same) as another user who tried to use this backend on a PPC (see this post: http://lists.alioth.debian.org/pipermail/sane-devel/2010-June/026900.html). So I tried to run the same device under a little endian platform and I saw a difference: Little Endian (working) ======================= [hp5590] hp5590_init_scanner [hp5590] hp5590_cmd: USB-in-USB: command : 0012 [hp5590] hp5590_control_msg: USB-in-USB: core data: no [hp5590] hp5590_control_msg: USB-in-USB: sending control msg [sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 4, value = 143, index = 0, len = 8 [sanei_usb] 0000: C0 04 00 12 00 00 32 00 Big Endian (not working) ======================== [hp5590] hp5590_init_scanner [hp5590] hp5590_cmd: USB-in-USB: command : 0012 [hp5590] hp5590_control_msg: USB-in-USB: core data: no [hp5590] hp5590_control_msg: USB-in-USB: sending control msg [sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 4, value = 143, index = 0, len = 8 [sanei_usb] 000 C0 04 00 12 00 00 00 32 There is a difference in the version of the backend (1.0.19 for little endian, 1.0.22 for big endian), so the output is not exactly identical, but in the last line you see that the last two bytes are swapped. This goes to hp5590_control_msg(), in hp5590_low.c line 251 and line 323 (version 1.0.22): 246: memset (&amp;ctrl, 0, sizeof (ctrl)); 247: ctrl.bRequestType = 0xc0; 248: ctrl.bRequest = request; 249: ctrl.wValue = htons (value); 250: ctrl.wIndex = htons (index); 251: ctrl.wLength = size; Since the module does work in little endian, and the content of ctrl is passed through, I assume that the hardware wants ctrl.wLength in little endian, so I replaced it with: ctrl.wLength = htole16 (size); Then, in hp5590_verify_last_cmd(), the code calls hp5590_control_msg() to retrieve a uint16_t buffer (line 469) to read it as it is returned without any byte swap (line 477). To correct this I've added the same command as above, assuming that the hardware does return a little endian 16-bit value: verify_cmd = le16toh (verify_cmd); I've tested the scanner with such modification and it works, but I've not tested it for regressions in little endian. The patch is attached. Regards, Nhan </pre> Nhan Ngo Dinh 2012-05-22T16:27:57 http://comments.gmane.org/gmane.comp.graphics.scanning.sane.devel/21025 <pre>Hi folks, I am using SANE (scanimage (sane-backends) 1.0.22; backend version 1.0.22) on OpenWRT Backfire 10.3.1 on a Buffalo WZR-HP-G300NH, attempting to interface with a Samsung SCX4300 MFP. This device is supported by the xerox_mfp backend, and has worked in the past. Now, for some odd reason, it is failing to detect the scanner. Here is the debugging output I have managed to obtain: root&lt; at &gt;gw:/# SANE_DEBUG_XEROX_MFP=128 SANE_DEBUG_SANEI_USB=4 sane-find-scanner # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. # Also you need support for SCSI Generic (sg) in your operating system. # If using Linux, try "modprobe sg". [sanei_debug] Setting debug level of sanei_usb to 4. [sanei_usb] sanei_usb_init: marking existing devices [sanei_usb] sanei_usb_init: Looking for kernel scanner devices [sanei_usb] sanei_usb_init: Looking for libusb devices [sanei_usb] sanei_usb_init: found libusb device (0x067b/0x2303) interface 0 at libusb:001:007 [sanei_usb] store_device: add dn 0 with libusb:001:007 [sanei_usb] sanei_usb_init: found libusb device (0x04e8/0x342e) interface 0 at libusb:001:006 [sanei_usb] store_device: add dn 1 with libusb:001:006 [sanei_usb] sanei_usb_open: can't find device `/dev/usb/scanner' in list [sanei_usb] sanei_usb_open: can't find device `/dev/usb/scanner0' in list [sanei_usb] sanei_usb_open: can't find device `/dev/usb/scanner1' in list [sanei_usb] sanei_usb_open: can't find device `/dev/usb/scanner2' in list [sanei_usb] sanei_usb_open: can't find device `/dev/usb/scanner3' in list [sanei_usb] sanei_usb_open: can't find device `/dev/usb/scanner4' in list [sanei_usb] sanei_usb_open: can't find device `/dev/usb/scanner5' in list [sanei_usb] sanei_usb_open: can't find device `/dev/usb/scanner5' in list [sanei_usb] sanei_usb_open: can't find device `/dev/usb/scanner7' in list [sanei_usb] sanei_usb_open: can't find device `/dev/usb/scanner8' in list [sanei_usb] sanei_usb_open: can't find device `/dev/usb/scanner9' in list [sanei_usb] sanei_usb_open: can't find device `/dev/usb/scanner10' in list [sanei_usb] sanei_usb_open: can't find device `/dev/usb/scanner11' in list [sanei_usb] sanei_usb_open: can't find device `/dev/usb/scanner12' in list [sanei_usb] sanei_usb_open: can't find device `/dev/usb/scanner13' in list [sanei_usb] sanei_usb_open: can't find device `/dev/usb/scanner14' in list [sanei_usb] sanei_usb_open: can't find device `/dev/usb/scanner15' in list [sanei_usb] sanei_usb_open: can't find device `/dev/usbscanner' in list [sanei_usb] sanei_usb_open: can't find device `/dev/usbscanner0' in list [sanei_usb] sanei_usb_open: can't find device `/dev/usbscanner1' in list [sanei_usb] sanei_usb_open: can't find device `/dev/usbscanner2' in list [sanei_usb] sanei_usb_open: can't find device `/dev/usbscanner3' in list [sanei_usb] sanei_usb_open: can't find device `/dev/usbscanner4' in list [sanei_usb] sanei_usb_open: can't find device `/dev/usbscanner5' in list [sanei_usb] sanei_usb_open: can't find device `/dev/usbscanner6' in list [sanei_usb] sanei_usb_open: can't find device `/dev/usbscanner7' in list [sanei_usb] sanei_usb_open: can't find device `/dev/usbscanner8' in list [sanei_usb] sanei_usb_open: can't find device `/dev/usbscanner9' in list [sanei_usb] sanei_usb_open: can't find device `/dev/usbscanner10' in list [sanei_usb] sanei_usb_open: can't find device `/dev/usbscanner11' in list [sanei_usb] sanei_usb_open: can't find device `/dev/usbscanner12' in list [sanei_usb] sanei_usb_open: can't find device `/dev/usbscanner13' in list [sanei_usb] sanei_usb_open: can't find device `/dev/usbscanner14' in list [sanei_usb] sanei_usb_open: can't find device `/dev/usbscanner15' in list found USB scanner (vendor=0x067b [Prolific Technology Inc.], product=0x2303 [USB-Serial Controller]) at libusb:001:007 found USB scanner (vendor=0x04e8 [Samsung], product=0x342e [SCX-4300 Series]) at libusb:001:006 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. # Not checking for parallel port scanners. # Most Scanners connected to the parallel port or other proprietary ports # can't be detected by this program. root&lt; at &gt;gw:/# As can be seen above, sane-find-scanner identifies the USB device representing the SCX4300. My dll.conf contains: root&lt; at &gt;gw:/# cat /etc/sane.d/dll.conf xerox_mfp root&lt; at &gt;gw:/# And my xerox_mfp.conf contains: root&lt; at &gt;gw:/# cat /etc/sane.d/xerox_mfp.conf #xerox_mfp.conf # Samsung SCX-4300 usb 0x04e8 0x342e root&lt; at &gt;gw:/# scanimage -L, however, fails to identify this device: root&lt; at &gt;gw:/# SANE_DEBUG_XEROX_MFP=128 SANE_DEBUG_SANEI_USB=4 scanimage -L [sanei_debug] Setting debug level of xerox_mfp to 128. [xerox_mfp] sane_init: Xerox backend (build 12), version != null, authorize != null [sanei_debug] Setting debug level of sanei_usb to 4. [sanei_usb] sanei_usb_init: marking existing devices [sanei_usb] sanei_usb_init: Looking for kernel scanner devices [sanei_usb] sanei_usb_init: Looking for libusb devices [sanei_usb] sanei_usb_init: found libusb device (0x067b/0x2303) interface 0 at libusb:001:007 [sanei_usb] store_device: add dn 0 with libusb:001:007 [sanei_usb] sanei_usb_init: found libusb device (0x04e8/0x342e) interface 0 at libusb:001:006 [sanei_usb] store_device: add dn 1 with libusb:001:006 [xerox_mfp] sane_xerox_mfp_get_devices: 0x7fcb5f60, 0 [sanei_usb] sanei_usb_find_devices: vendor=0x04e8, product=0x342e [xerox_mfp] list_one_device: libusb:001:006 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). root&lt; at &gt;gw:/# It seems to notice the existence of the device, reporting: [xerox_mfp] list_one_device: libusb:001:006 but it does nothing more than that. Does anyone have suggestions as to what I can try to debug this further? Many thanks Rogan Dawes </pre> Rogan Dawes 2012-05-22T14:52:36 http://comments.gmane.org/gmane.comp.graphics.scanning.sane.devel/21015 <pre>Hi , I have a requirement to support new device , How can I integrate new product specific backend code with sane and to whom I need to send my code. My widgets are different from existing xsane frontend. Can I write my own product specific frontend code and integrate with sane backend ? Thanks Ganapati Hegde ______________________________________________________________________________ DISCLAIMER: This electronic message and any attachments to this electronic message is intended for the exclusive use of the addressee(s) named herein and may contain legally privileged and confidential information. It is the property of Celstream Technologies Pvt Limited. If you are not the intended recipient, you are hereby strictly notified not to copy, forward, distribute or use this message or any attachments thereto. If you have received this message in error, please delete it and all copies thereof, from your system and notify the sender at Celstream Technologies or administrator&lt; at &gt;celstream.com immediately. ______________________________________________________________________________ </pre> Ganapati Hegde 2012-05-16T12:03:35 http://comments.gmane.org/gmane.comp.graphics.scanning.sane.devel/21012 <pre> Boa tarde, Scaner digitaliza, mas não aparece imagem. Xsane versão: 0.998 HP Scanjet G2410 Ubuntu 12.04 </pre> Bruno Detomi / Lidiane Carvalho 2012-05-15T19:23:31 http://comments.gmane.org/gmane.comp.graphics.scanning.sane.devel/21009 <pre> Hello! I have this scaner and I see status support at this url as "untested". I check scaner with SANE and it works fine. Please see log. [midnighter&lt; at &gt;localhost ~]$ scanimage --version scanimage scanimage (sane-backends) 1.0.22; backend version 1.0.22 [midnighter&lt; at &gt;localhost ~]$ sudo scanimage -v -d genesys:libusb:002:010 --mode color --format=tiff &gt; image.tiff [sudo] password for midnighter: [genesys] WARNING: Your scanner is not fully supported or at least [genesys] had only limited testing. Please be careful and [genesys] report any failure/success to [genesys] sane-devel&lt; at &gt;lists.alioth.debian.org. Please provide as many [genesys] details as possible, e.g. the exact name of your [genesys] scanner and what does (not) work. scanimage: scanning image of size 2549x3510 pixels at 24 bits/pixel scanimage: acquiring RGB frame scanimage: min/max graylevel value = 0/255 scanimage: read 26840970 bytes in total This is sane-find-scanner from sane-backends 1.0.22 # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. searching for SCSI scanners: checking /dev/scanner... failed to open (Invalid argument) checking /dev/sg0... failed to open (Access to resource has been denied) checking /dev/sg1... failed to open (Invalid argument) checking /dev/sg2... failed to open (Invalid argument) checking /dev/sg3... failed to open (Invalid argument) checking /dev/sg4... failed to open (Invalid argument) checking /dev/sg5... failed to open (Invalid argument) checking /dev/sg6... failed to open (Invalid argument) checking /dev/sg7... failed to open (Invalid argument) checking /dev/sg8... failed to open (Invalid argument) checking /dev/sg9... failed to open (Invalid argument) checking /dev/sga... failed to open (Invalid argument) checking /dev/sgb... failed to open (Invalid argument) checking /dev/sgc... failed to open (Invalid argument) checking /dev/sgd... failed to open (Invalid argument) checking /dev/sge... failed to open (Invalid argument) checking /dev/sgf... failed to open (Invalid argument) checking /dev/sgg... failed to open (Invalid argument) checking /dev/sgh... failed to open (Invalid argument) checking /dev/sgi... failed to open (Invalid argument) checking /dev/sgj... failed to open (Invalid argument) checking /dev/sgk... failed to open (Invalid argument) checking /dev/sgl... failed to open (Invalid argument) checking /dev/sgm... failed to open (Invalid argument) checking /dev/sgn... failed to open (Invalid argument) checking /dev/sgo... failed to open (Invalid argument) checking /dev/sgp... failed to open (Invalid argument) checking /dev/sgq... failed to open (Invalid argument) checking /dev/sgr... failed to open (Invalid argument) checking /dev/sgs... failed to open (Invalid argument) checking /dev/sgt... failed to open (Invalid argument) checking /dev/sgu... failed to open (Invalid argument) checking /dev/sgv... failed to open (Invalid argument) checking /dev/sgw... failed to open (Invalid argument) checking /dev/sgx... failed to open (Invalid argument) checking /dev/sgy... failed to open (Invalid argument) checking /dev/sgz... failed to open (Invalid argument) # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. searching for USB scanners: checking /dev/usb/scanner... failed to open (Invalid argument) checking /dev/usb/scanner0... failed to open (Invalid argument) checking /dev/usb/scanner1... failed to open (Invalid argument) checking /dev/usb/scanner2... failed to open (Invalid argument) checking /dev/usb/scanner3... failed to open (Invalid argument) checking /dev/usb/scanner4... failed to open (Invalid argument) checking /dev/usb/scanner5... failed to open (Invalid argument) checking /dev/usb/scanner5... failed to open (Invalid argument) checking /dev/usb/scanner7... failed to open (Invalid argument) checking /dev/usb/scanner8... failed to open (Invalid argument) checking /dev/usb/scanner9... failed to open (Invalid argument) checking /dev/usb/scanner10... failed to open (Invalid argument) checking /dev/usb/scanner11... failed to open (Invalid argument) checking /dev/usb/scanner12... failed to open (Invalid argument) checking /dev/usb/scanner13... failed to open (Invalid argument) checking /dev/usb/scanner14... failed to open (Invalid argument) checking /dev/usb/scanner15... failed to open (Invalid argument) checking /dev/usbscanner... failed to open (Invalid argument) checking /dev/usbscanner0... failed to open (Invalid argument) checking /dev/usbscanner1... failed to open (Invalid argument) checking /dev/usbscanner2... failed to open (Invalid argument) checking /dev/usbscanner3... failed to open (Invalid argument) checking /dev/usbscanner4... failed to open (Invalid argument) checking /dev/usbscanner5... failed to open (Invalid argument) checking /dev/usbscanner6... failed to open (Invalid argument) checking /dev/usbscanner7... failed to open (Invalid argument) checking /dev/usbscanner8... failed to open (Invalid argument) checking /dev/usbscanner9... failed to open (Invalid argument) checking /dev/usbscanner10... failed to open (Invalid argument) checking /dev/usbscanner11... failed to open (Invalid argument) checking /dev/usbscanner12... failed to open (Invalid argument) checking /dev/usbscanner13... failed to open (Invalid argument) checking /dev/usbscanner14... failed to open (Invalid argument) checking /dev/usbscanner15... failed to open (Invalid argument) trying libusb: &lt;device descriptor of 0x1d6b/0x0002 at 001:001&gt; bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 9 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x1D6B idProduct 0x0002 bcdDevice 3.03 iManufacturer 3 () iProduct 2 () iSerialNumber 1 () bNumConfigurations 1 &lt;configuration 0&gt; bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 224 (Self-poweredRemote Wakeup) MaxPower 0 mA &lt;interface 0&gt; &lt;altsetting 0&gt; bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 () &lt;endpoint 0&gt; bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 3 (interrupt) wMaxPacketSize 4 bInterval 12 ms bRefresh 0 bSynchAddress 0 &lt;device descriptor of 0x8087/0x0024 at 001:002&gt; bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 9 bDeviceSubClass 0 bDeviceProtocol 1 bMaxPacketSize0 64 idVendor 0x8087 idProduct 0x0024 bcdDevice 0.00 iManufacturer 0 () iProduct 0 () iSerialNumber 0 () bNumConfigurations 1 &lt;configuration 0&gt; bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 224 (Self-poweredRemote Wakeup) MaxPower 0 mA &lt;interface 0&gt; &lt;altsetting 0&gt; bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 () &lt;endpoint 0&gt; bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 3 (interrupt) wMaxPacketSize 1 bInterval 12 ms bRefresh 0 bSynchAddress 0 &lt;device descriptor of 0x8086/0x0189 at 001:003&gt; bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 224 bDeviceSubClass 1 bDeviceProtocol 1 bMaxPacketSize0 64 idVendor 0x8086 idProduct 0x0189 bcdDevice 105.19 iManufacturer 0 () iProduct 0 () iSerialNumber 0 () bNumConfigurations 1 &lt;configuration 0&gt; bLength 9 bDescriptorType 2 wTotalLength 177 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 () bmAttributes 224 (Self-poweredRemote Wakeup) MaxPower 0 mA &lt;interface 0&gt; &lt;altsetting 0&gt; bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 224 bInterfaceSubClass 1 bInterfaceProtocol 1 iInterface 0 () &lt;endpoint 0&gt; bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 3 (interrupt) wMaxPacketSize 16 bInterval 1 ms bRefresh 0 bSynchAddress 0 &lt;endpoint 1&gt; bLength 7 bDescriptorType 5 bEndpointAddress 0x02 (out 0x02) bmAttributes 2 (bulk) wMaxPacketSize 64 bInterval 1 ms bRefresh 0 bSynchAddress 0 &lt;endpoint 2&gt; bLength 7 bDescriptorType 5 bEndpointAddress 0x82 (in 0x02) bmAttributes 2 (bulk) wMaxPacketSize 64 bInterval 1 ms bRefresh 0 bSynchAddress 0 &lt;interface 1&gt; &lt;altsetting 0&gt; bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 224 bInterfaceSubClass 1 bInterfaceProtocol 1 iInterface 0 () &lt;endpoint 0&gt; bLength 7 bDescriptorType 5 bEndpointAddress 0x03 (out 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 0 bInterval 1 ms bRefresh 0 bSynchAddress 0 &lt;endpoint 1&gt; bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 0 bInterval 1 ms bRefresh 0 bSynchAddress 0 &lt;altsetting 1&gt; bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 1 bNumEndpoints 2 bInterfaceClass 224 bInterfaceSubClass 1 bInterfaceProtocol 1 iInterface 0 () &lt;endpoint 0&gt; bLength 7 bDescriptorType 5 bEndpointAddress 0x03 (out 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 9 bInterval 1 ms bRefresh 0 bSynchAddress 0 &lt;endpoint 1&gt; bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 9 bInterval 1 ms bRefresh 0 bSynchAddress 0 &lt;altsetting 2&gt; bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 2 bNumEndpoints 2 bInterfaceClass 224 bInterfaceSubClass 1 bInterfaceProtocol 1 iInterface 0 () &lt;endpoint 0&gt; bLength 7 bDescriptorType 5 bEndpointAddress 0x03 (out 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 17 bInterval 1 ms bRefresh 0 bSynchAddress 0 &lt;endpoint 1&gt; bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 17 bInterval 1 ms bRefresh 0 bSynchAddress 0 &lt;altsetting 3&gt; bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 3 bNumEndpoints 2 bInterfaceClass 224 bInterfaceSubClass 1 bInterfaceProtocol 1 iInterface 0 () &lt;endpoint 0&gt; bLength 7 bDescriptorType 5 bEndpointAddress 0x03 (out 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 25 bInterval 1 ms bRefresh 0 bSynchAddress 0 &lt;endpoint 1&gt; bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 25 bInterval 1 ms bRefresh 0 bSynchAddress 0 &lt;altsetting 4&gt; bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 4 bNumEndpoints 2 bInterfaceClass 224 bInterfaceSubClass 1 bInterfaceProtocol 1 iInterface 0 () &lt;endpoint 0&gt; bLength 7 bDescriptorType 5 bEndpointAddress 0x03 (out 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 33 bInterval 1 ms bRefresh 0 bSynchAddress 0 &lt;endpoint 1&gt; bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 33 bInterval 1 ms bRefresh 0 bSynchAddress 0 &lt;altsetting 5&gt; bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 5 bNumEndpoints 2 bInterfaceClass 224 bInterfaceSubClass 1 bInterfaceProtocol 1 iInterface 0 () &lt;endpoint 0&gt; bLength 7 bDescriptorType 5 bEndpointAddress 0x03 (out 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 49 bInterval 1 ms bRefresh 0 bSynchAddress 0 &lt;endpoint 1&gt; bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 49 bInterval 1 ms bRefresh 0 bSynchAddress 0 &lt;device descriptor of 0x1d6b/0x0002 at 002:001&gt; bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 9 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x1D6B idProduct 0x0002 bcdDevice 3.03 iManufacturer 3 () iProduct 2 () iSerialNumber 1 () bNumConfigurations 1 &lt;configuration 0&gt; bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 224 (Self-poweredRemote Wakeup) MaxPower 0 mA &lt;interface 0&gt; &lt;altsetting 0&gt; bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 () &lt;endpoint 0&gt; bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 3 (interrupt) wMaxPacketSize 4 bInterval 12 ms bRefresh 0 bSynchAddress 0 &lt;device descriptor of 0x8087/0x0024 at 002:002&gt; bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 9 bDeviceSubClass 0 bDeviceProtocol 1 bMaxPacketSize0 64 idVendor 0x8087 idProduct 0x0024 bcdDevice 0.00 iManufacturer 0 () iProduct 0 () iSerialNumber 0 () bNumConfigurations 1 &lt;configuration 0&gt; bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 224 (Self-poweredRemote Wakeup) MaxPower 0 mA &lt;interface 0&gt; &lt;altsetting 0&gt; bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 () &lt;endpoint 0&gt; bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 3 (interrupt) wMaxPacketSize 1 bInterval 12 ms bRefresh 0 bSynchAddress 0 &lt;device descriptor of 0x0408/0x10f3 at 002:004&gt; bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 239 bDeviceSubClass 2 bDeviceProtocol 1 bMaxPacketSize0 64 idVendor 0x0408 idProduct 0x10F3 bcdDevice 33.05 iManufacturer 3 () iProduct 2 () iSerialNumber 0 () bNumConfigurations 1 &lt;configuration 0&gt; bLength 9 bDescriptorType 2 wTotalLength 1585 bNumInterfaces 3 bConfigurationValue 1 iConfiguration 2 () bmAttributes 128 () MaxPower 250 mA &lt;interface 0&gt; &lt;altsetting 0&gt; bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 14 bInterfaceSubClass 1 bInterfaceProtocol 0 iInterface 2 () &lt;endpoint 0&gt; bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 3 (interrupt) wMaxPacketSize 32 bInterval 6 ms bRefresh 0 bSynchAddress 0 &lt;interface 1&gt; &lt;altsetting 0&gt; bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 0 bInterfaceClass 14 bInterfaceSubClass 2 bInterfaceProtocol 0 iInterface 0 () &lt;altsetting 1&gt; bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 1 bNumEndpoints 1 bInterfaceClass 14 bInterfaceSubClass 2 bInterfaceProtocol 0 iInterface 0 () &lt;endpoint 0&gt; bLength 7 bDescriptorType 5 bEndpointAddress 0x82 (in 0x02) bmAttributes 5 (isochronous) wMaxPacketSize 5120 bInterval 1 ms bRefresh 0 bSynchAddress 0 &lt;altsetting 2&gt; bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 2 bNumEndpoints 1 bInterfaceClass 14 bInterfaceSubClass 2 bInterfaceProtocol 0 iInterface 0 () &lt;endpoint 0&gt; bLength 7 bDescriptorType 5 bEndpointAddress 0x82 (in 0x02) bmAttributes 5 (isochronous) wMaxPacketSize 1024 bInterval 1 ms bRefresh 0 bSynchAddress 0 &lt;altsetting 3&gt; bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 3 bNumEndpoints 1 bInterfaceClass 14 bInterfaceSubClass 2 bInterfaceProtocol 0 iInterface 0 () &lt;endpoint 0&gt; bLength 7 bDescriptorType 5 bEndpointAddress 0x82 (in 0x02) bmAttributes 5 (isochronous) wMaxPacketSize 760 bInterval 1 ms bRefresh 0 bSynchAddress 0 &lt;altsetting 4&gt; bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 4 bNumEndpoints 1 bInterfaceClass 14 bInterfaceSubClass 2 bInterfaceProtocol 0 iInterface 0 () &lt;endpoint 0&gt; bLength 7 bDescriptorType 5 bEndpointAddress 0x82 (in 0x02) bmAttributes 5 (isochronous) wMaxPacketSize 512 bInterval 1 ms bRefresh 0 bSynchAddress 0 &lt;interface 2&gt; &lt;altsetting 0&gt; bLength 9 bDescriptorType 4 bInterfaceNumber 2 bAlternateSetting 0 bNumEndpoints 0 bInterfaceClass 14 bInterfaceSubClass 2 bInterfaceProtocol 0 iInterface 0 () &lt;altsetting 1&gt; bLength 9 bDescriptorType 4 bInterfaceNumber 2 bAlternateSetting 1 bNumEndpoints 1 bInterfaceClass 14 bInterfaceSubClass 2 bInterfaceProtocol 0 iInterface 0 () &lt;endpoint 0&gt; bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 5 (isochronous) wMaxPacketSize 792 bInterval 1 ms bRefresh 0 bSynchAddress 0 &lt;altsetting 2&gt; bLength 9 bDescriptorType 4 bInterfaceNumber 2 bAlternateSetting 2 bNumEndpoints 1 bInterfaceClass 14 bInterfaceSubClass 2 bInterfaceProtocol 0 iInterface 0 () &lt;endpoint 0&gt; bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 5 (isochronous) wMaxPacketSize 256 bInterval 1 ms bRefresh 0 bSynchAddress 0 &lt;device descriptor of 0x03f0/0x0a01 at 002:008 (Hewlett-Packard hp scanjet scanner)&gt; bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 255 bDeviceSubClass 255 bDeviceProtocol 255 bMaxPacketSize0 8 idVendor 0x03F0 idProduct 0x0A01 bcdDevice 1.01 iManufacturer 1 (Hewlett-Packard) iProduct 2 (hp scanjet scanner) iSerialNumber 12 (-- sane-devel mailing list: sane-devel&lt; at &gt;lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-request&lt; at &gt;lists.alioth.debian.org</pre> Михаил 2012-05-14T19:02:31 http://comments.gmane.org/gmane.comp.graphics.scanning.sane.devel/21006 <pre>Hi When I connect the scanner and turn it on, I get the following response: $ dmesg | tail -6 usb 4-1: new full speed USB device using uhci_hcd and address 7 usb 4-1: New USB device found, idVendor=03f0, idProduct=1405 usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=12 usb 4-1: Product: HP Scanjet Scanner usb 4-1: Manufacturer: Hewlett-Packard usb 4-1: SerialNumber: CN38DS24YS $ 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). $ sane-find-scanner # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. [...] found USB scanner (vendor=0x03f0, product=0x1405, chip=GL646_HP?) at libusb:004:007 [...] I was under the impression that HP 3690 should be working with Sane, so I wonder if I'm missing something. System references: $ rpm -qa | grep sane sane-backends-iscan-1.0.22-1.mga1 libsane1-1.0.22-1.mga1 libsane-hpaio1-3.11.7-1.2.mga1 libksane0-4.6.5-0.mga1 sane-backends-1.0.22-1.mga1 xsane-0.998-1.mga1 $ uname -a Linux corax 2.6.38.8-desktop586-10.mga #1 SMP Wed Jan 25 10:18:54 UTC 2012 i686 i686 i386 GNU/Linux Any suggestions will be appreciated. Best regards Michael Steen </pre> Michael N. Steen 2012-05-14T00:47:22 http://comments.gmane.org/gmane.comp.graphics.scanning.sane.devel/21002 <pre>Hi I have not developed Linux libraries, so there may be something obvious I missed here ... I want to use my Canon Pixma MP495 scanner from simple-scan. Sane on Ubuntu 12.04 seems old and doesn't include MP495 support. After building and installing sane on my Ubuntu 12.04 64 bit system, simple-scan and xsane were still using old drivers. I fixed this by updating a link to point to the new sane. Is this correct behaviour? I built and installed sane as follows ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var make sudo make install After install I had (new drivers are dated 13 May) 2883607 0 lrwxrwxrwx 1 root root 23 May 13 07:58 /usr/lib/sane/libsane-pixma.so.1 -&gt; libsane-pixma.so.1.0.23 2883608 0 lrwxrwxrwx 1 root root 23 May 13 07:58 /usr/lib/sane/libsane-pixma.so -&gt; libsane-pixma.so.1.0.23 2883606 496 -rwxr-xr-x 1 root root 506908 May 13 07:58 /usr/lib/sane/libsane-pixma.so.1.0.23 2885985 0 lrwxrwxrwx 1 root root 21 May 8 19:54 /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 -&gt; libpixman-1.so.0.24.4 2885986 540 -rw-r--r-- 1 root root 551176 Feb 10 10:10 /usr/lib/x86_64-linux-gnu/libpixman-1.so.0.24.4 3147637 0 lrwxrwxrwx 1 root root 37 May 13 08:03 /usr/lib/x86_64-linux-gnu/sane/libsane-pixma.so.1 -&gt; libsane-pixma.so.1.0.22 3141066 136 -rw-r--r-- 1 root root 138064 Dec 5 04:57 /usr/lib/x86_64-linux-gnu/sane/libsane-pixma.so.1.0.22 so the new 64 bit drivers were installed into /usr/lib/sane, the link used by xsane and simple-scan still pointed to the old driver in /usr/lib/x86_64-linux-gnu/sane It was necessary to make the following change 3147637 0 lrwxrwxrwx 1 root root 37 May 13 08:03 /usr/lib/x86_64-linux-gnu/sane/libsane-pixma.so.1 -&gt; /usr/lib/sane/libsane--pixma.so.1.0.23 Thanks Justin </pre> Justin Harding 2012-05-13T07:59:27 http://comments.gmane.org/gmane.comp.graphics.scanning.sane.devel/20990 <pre>Good afternoon, Yesterday I started setting up my CanoScan 9000F. According to the docs sane supports this scaner since last year. I compiled the sources for sane-backend (with libusb) the sane-find-scaner output is the following: anydoby&lt; at &gt;anydoby-System-Product-Name:~/sane/sane-backends/backend$ sane-find-scanner # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. found USB scanner (vendor=0x04a9, product=0x1908) at libusb:002:012 found USB scanner (vendor=0x0df6, product=0x0040) at libusb:001:004 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. # Not checking for parallel port scanners. # Most Scanners connected to the parallel port or other proprietary ports # can't be detected by this program. # You may want to run this program as root to find all devices. Once you # found the scanner devices, be sure to adjust access permissions as # necessary. I assume the (vendor=0x04a9, product=0x1908) is my scanner, as for the second line, I suspect this is my webcam. The scanimage -L output is not good: anydoby&lt; at &gt;anydoby-System-Product-Name:~/sane/sane-backends/backend$ scanimage -L device `v4l:/dev/video0' is a Noname VF0610 Live! Cam Socialize HD virtual device I do not see the scaner. I have added an entry "usb 0x04a9 0x1908" to the /etc/sane.d/pixma.conf as was recommended in some post on the topic, but still nothing is detected. What can I do about it? I am sure that the scaner works, as under Windows it worked ok. </pre> Sergey Zolotaryov 2012-05-11T11:19:13 http://comments.gmane.org/gmane.comp.graphics.scanning.sane.devel/20984 <pre>Hi, There seems to be a name and/or password length limitation of 8 chars for sending scans to an email account. I would like to increase this to at least 16 chars and recompile the current version of xsane. If you can help me find the code that needs to be changed, I would appreciate it. In the future , it would be useful if xsane email settings allowed passwords longer than 8 chars. Thank you, Barry </pre> Barry Tigner 2012-05-09T16:47:24 http://comments.gmane.org/gmane.comp.graphics.scanning.sane.devel/20978 <pre>I asked this question a long time ago on Ubuntu Forum, with no result. http://ubuntuforums.org/showthread.php?t=1576401 Probably this is a more suitable spot? I have an Epson Perfection V200 Photo scanner. It works as you would expect in XP, whites come out white, automatically. In Ubuntu (10.04 thru 11.10) using the flatbed, real whites (white paper backgrounds, even the scanner's own white background) come out noticeably blue. This is annoying anyway &amp; especially when printing afterwards. It is about the same using any of the available Scanner Applications (XSane / Image Scan! / Simple Scan / AcquireImages etc.) See example in above post. I can roughly correct the problem, once per scanning session, using the "Tone Control" in Image Scan! or (much more fiddly) using the "Set as White" tool in XSane, but the settings don't 'stick'. Is there any way to dial this problem out, once &amp; for all, for any or preferably all of the applications? Thanks! 2CV67 </pre> 2cv67 2012-05-08T19:19:17 http://comments.gmane.org/gmane.comp.graphics.scanning.sane.devel/20975 <pre>Hi, I would like to know if someone use this scanner. I plan to buy it and I did not found anything and the sane site does not even mention it. Thierry B. </pre> Thierry B. 2012-05-07T16:02:53 http://comments.gmane.org/gmane.comp.graphics.scanning.sane.devel/20970 <pre>These videos are comparation of Elcot driver and Genesys driver for HP Scanjet 2400. There is a difference in scanner behaviour, in my case, on 300 dpi. LINK: https://www.rapidshare.com/files/1734812743/hp2400Svracak.zip Best regards! </pre> Svracak RS 2012-05-03T23:24:03 http://comments.gmane.org/gmane.comp.graphics.scanning.sane.devel/20965 <pre> --- doc/descriptions/pixma.desc | 6 ++++++ 1 files changed, 6 insertions(+), 0 deletions(-) diff --git a/doc/descriptions/pixma.desc b/doc/descriptions/pixma.desc index 402d0f3..635030d 100644 --- a/doc/descriptions/pixma.desc +++ b/doc/descriptions/pixma.desc &lt; at &gt;&lt; at &gt; -63,6 +63,12 &lt; at &gt;&lt; at &gt; :status :complete :comment "All resolutions supported (up to 1200DPI)." +:model "PIXMA MP280" +:interface "USB" +:usbid "0x04a9" "0x1746" +:status :complete +:comment "All resolutions supported (up to 600DPI)." + :model "PIXMA MP450" :interface "USB" :usbid "0x04a9" "0x170b" </pre> Daniel Beer 2012-05-02T20:57:11 http://comments.gmane.org/gmane.comp.graphics.scanning.sane.devel/20964 <pre>I tested commit c4a287e3f28eab0ceb0ef8f0a1d17cb724ad612f with a Canon MP280 (Linux 2.6.38.5, libusb-0.1.12). scanimage -T failed with an IO error, which I traced to pixma_wait_interrupt(). This function calls sanei_usb_read_int(). If no data is received, it returns SANE_STATUS_EOF, which maps to PIXMA_EOF, which is in turn treated as a fatal error in the calling function. With the following patch, the MP280 works pretty well. Occasionally an IO error occurs if you try to scan immediately after power-on ("warming up"?), but it always works on a retry. --- backend/pixma_io_sanei.c | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/backend/pixma_io_sanei.c b/backend/pixma_io_sanei.c index 0a79bfa..06a6d0f 100644 --- a/backend/pixma_io_sanei.c +++ b/backend/pixma_io_sanei.c &lt; at &gt;&lt; at &gt; -567,7 +567,8 &lt; at &gt;&lt; at &gt; pixma_wait_interrupt (pixma_io_t * io, void *buf, unsigned size, int timeout) #endif error = map_error (sanei_usb_read_int (io-&gt;dev, buf, &amp;count)); } - if (error == PIXMA_EIO) + if (error == PIXMA_EIO || + (io-&gt;interface == INT_USB &amp;&amp; error == PIXMA_EOF)) error = PIXMA_ETIMEDOUT;/* FIXME: SANE doesn't have ETIMEDOUT!! */ if (error == 0) error = count; </pre> Daniel Beer 2012-05-02T20:55:59 http://comments.gmane.org/gmane.comp.graphics.scanning.sane.devel/20962 <pre>As described here: http://unix.stackexchange.com/questions/36894/hewlett-packard-scanjet-2200c-on-scientific-linux-6-1-64bit I have a Hewlett-Packard ScanJet 2200c scanner connected via USB to my notebook that has Scientific Linux 6.1 64bit OS with the rpmforge repo. Bus 006 Device 002: ID 03f0:0605 Hewlett-Packard ScanJet 2200c Scanner plugged in via USB to my notebook. When I launch this command (no matter that I use it with a normal user or root, does the same): scanimage --format=tiff --resolution=150 --mode=color &gt; a.tiff The scanner just waits for ~30 sec then starts actually scanning, but it stops after going about ~8cm's.. (so it's scanning just the ~1/3 part of an A/4 paper..) but the scanned part looks good. So the problem is that why doesn't this scanner scans a full A4 paper size? I can't find relevant logs.. I wanted to try out the scanner on a Win7Pro64bit machine.. I didn't found any drivers to it :D How can I make this scanner work under my OS? Can anyone help me with this please? Thank you. </pre> Gasko, Peter 2012-05-01T10:01:39 http://comments.gmane.org/gmane.comp.graphics.scanning.sane.devel/20959 <pre>All, Upgraded to Ubuntu 12.04. And was using gscan2pdf when I realized that I could not scan in any other mode than color. Previous version, 10.04 Ubuntu, I could scan in all three modes, color, line art &amp; gray scale. This does not appear to be the case with the sane-backend 1.0.22 installed. Options specific to device `avision:libusb:001:005': Scan mode: --mode Color [Color] Selects the scan mode (e.g., lineart, monochrome, or color). --resolution 50..600dpi (in steps of 1) [150] Sets the resolution of the scanned image. --speed 0..4 (in steps of 1) [inactive] Determines the speed at which the scan proceeds. --preview[=(yes|no)] [no] Request a preview-quality scan. --source ADF Front|ADF Back|ADF Duplex [ADF Front] Selects the scan source (such as a document-feeder). Geometry: -l 0..216mm [0] Top-left x position of scan area. -t 0..362mm [0] Top-left y position of scan area. -x 0..216mm [216] Width of scan-area. -y 0..362mm [362] Height of scan-area. --overscan-top 0..4mm [inactive] The top overscan controls the additional area to scan before the paper is detected. --overscan-bottom 0..4mm [inactive] The bottom overscan controls the additional area to scan after the paper end is detected. --background-lines 0..50pel [inactive] The background raster controls the additional background lines to scan before the paper is feed through the scanner. Enhancement: --brightness -100..100% (in steps of 1) [0] Controls the brightness of the acquired image. --contrast -100..100% (in steps of 1) [0] Controls the contrast of the acquired image. --quality-scan[=(yes|no)] [yes] Turn on quality scanning (slower but better). --quality-cal[=(yes|no)] [yes] Do a quality white-calibration --gamma-table 0..255,... [inactive] Gamma-correction table. In color mode this option equally affects the red, green, and blue channels simultaneously (i.e., it is an intensity gamma table). --red-gamma-table 0..255,... Gamma-correction table for the red band. --green-gamma-table 0..255,... Gamma-correction table for the green band. --blue-gamma-table 0..255,... Gamma-correction table for the blue band. --exposure 0..1000% (in steps of 1) [inactive] Manual exposure adjustment. --infra-red[=(yes|no)] [inactive] Enable infra-red scan mode. --multi-sample[=(yes|no)] [inactive] Enable multi-sample scan mode. Scan mode: --frame 0..0 [inactive] Selects the number of the frame to scan --power-save-time &lt;int&gt; [15] Allows control of the scanner's power save timer, dimming or turning off the light. --paper-length[=(yes|no)] [no] Newer scanners can utilize this paper length to detect double feeds. However some others (DM152) can get confused during media flush if it is set. --flip-page[=(auto|yes|no)] [inactive] Tells page-flipping document scanners to flip the paper back to its original orientation before dropping it in the output tray. Turning this off might make scanning a little faster if you don't care about manually flipping the pages afterwards. Type ``scanimage --help -d DEVICE'' to get list of all options for DEVICE. List of available devices: avision:libusb:001:005 Any help would be appreciated and would prefer to use the latest version. Thanks, Dean </pre> dgronos 2012-04-30T04:07:41 http://comments.gmane.org/gmane.comp.graphics.scanning.sane.devel/20956 <pre>Hi, I've the same problem as reported here in 2008: http://lists.alioth.debian.org/pipermail/sane-devel/2008-July/022451.html So when I do scanadf -d hp5590 --source "ADF Duplex" I get one image file with the front site on the top and the reverse site on the bottom flipped by 180°. I searched the mailing list but could not find any solution. Please CC me in replies. Regards, Thomas Koch, http://www.koch.ro </pre> Thomas Koch 2012-04-29T19:22:38 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.graphics.scanning.sane.devel