[sane-devel] OCR with Xsane?
Thanks to all for responses. I'm having a problem with the actual scanning of images using gscan2pdf, but rather than addressing that here, is there a users' group for gscan2pdf? > Date: Tue, 18 May 2010 17:10:56 +0200 > From: jeffrey.ratcliffe at gmail.com > To: tingox at gmail.com > CC: sane-devel at lists.alioth.debian.org > Subject: Re: [sane-devel] OCR with Xsane? > > On 17 May 2010 23:58, Torfinn Ingolfsen wrote: > > FWIW; I use gscan2pdf[1], which have a couple of ocr programs "built in". I > > Ubuntu has gscan2pdf, so you just need to > > $ sudo apt-get install gscan2pdf > > This gives you tesseract and ocropus from the GUI. cuneiform support > will be in the upcoming version. Get it now from the git repository on > sourceforge if you can't wait. > > Regards > > Jeff > > -- > sane-devel mailing list: sane-devel at lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to sane-devel-request at lists.alioth.debian.org _ The New Busy think 9 to 5 is a cute idea. Combine multiple calendars with Hotmail. http://www.windowslive.com/campaign/thenewbusy?tile=multicalendar&ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_5 -- next part -- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100518/7f150ee2/attachment-0001.htm>
[sane-devel] Canon P-150
Dear SANE, I recent purchased a Canon P-150 scanner optimistic that it would work with my suse 11.0 box. I was encouraged by the presence of the linux driver on the Canon website. Problem is the driver doesn't work and contains no documentation and Canon won't provide any support. I am posting in the hope that someone here * knows how make it work without the Canon driver * knows how to make the Canon driver work * know what the errors mean and can provide some advice Symptoms and diagnositcs: xsane can't find the scanner I get the following messages in the logs: dmesg usb 6-1: new high speed USB device using ehci_hcd and address 3 usb 6-1: configuration #1 chosen from 1 choice scsi7 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 3 usb-storage: waiting for device to settle before scanning usb 6-1: New USB device found, idVendor=1083, idProduct=162d usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 6-1: Product: CANON P-150 usb 6-1: Manufacturer: CANON usb 6-1: SerialNumber: FEA12953 usb 6-1: reset high speed USB device using ehci_hcd and address 3 usb 6-1: device descriptor read/64, error -110 usb 6-1: device descriptor read/64, error -110 last repeats slowly until the scanner is unplugged when I get: hub 1-0:1.0: unable to enumerate USB device on port 1 I am on kernel 2.6.25.20-0.7-default suse 11.0 I have sane BE 1.0.19-48-1, sane FE 1.0.14-250.1 and xsane .995-79-1 I have V 1.00-0.2 of the Canon driver installed using their RPM. Any clues! Thanks, SA _ Hotmail: Powerful Free email with security by Microsoft. https://signup.live.com/signup.aspx?id=60969 -- next part -- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100518/94c4e1d6/attachment.htm>
[sane-devel] Canoscan 8800F]
On Tue, May 18, 2010 at 6:10 PM, Gernot Hassenpflug wrote: > On Wed, May 19, 2010 at 2:25 AM, Kurt Rosenfeld > wrote: >> Here is some good news. ?I tried Backends 1.0.21 on a FreeBSD 9 >> machine and it works. ?Here is the stderr output: > > Well, interesting. Of course you need 1.0.21, since the scanner was > not supported in 1.0.20. However, it surprised me that the pixma > driver recognized the scanner since 1.0.20 would not have registered > the 8800F at all. > >> http://acm.poly.edu/~kurt/scanimage_freebsd_all255.txt >> >> This is the first time I tried it on a FreeBSD 9 machine. >> I tried it before on another older FreeBSD 7 machine and it >> seemed to fail in the same way as I have been seeing with >> Linux. ?In both cases a little bit of dirty stuff was needed >> to get it to compile since the current version of SANE Backends >> in the FreeBSD ports tree is 1.0.20, which does not support the >> Canon 8800F. ?The maintainer of the port recently submitted a >> patch (awaiting commit) that, among other things, updates the >> port to use 1.0.21. ?Today I manually applied that patch to my >> ports tree and built sane-backends on the FreeBSD 9 box here in >> the lab. ?What next? ?-kurt > > You could install 1.0.21 from source? > Thats what he did :) allan -- "The truth is an offense, but not a sin"
[sane-devel] Epson Artisan 710 support
>> Thanks for the samples. I've never seen this particular problem before. I'll >> have to take a crack at seeing if I can reproduce this to make 100% sure >> it's not an issue with your hardware. You'll have to hang tight before I can >> find an Artisan 710 and some free time to investigate. I couldn't get hold of an Artisan 710, so I instead used an Artisan 700 as you mentioned that the problem affected this scanner as well. I tried scanning with scanimage at 75, 150 and 300 dpi both with the latest development version of iscan and with iscan 2.21. Unfortunately, I was unable to reproduce the problem seen in the sample image you sent me. At this point I honestly don't know what the problem could be. A faulty USB cable perhaps? Just grasping at straws here. I am going to ask around a bit more to see if anyone else has seen this phenomenon before. I'll let you know if I dig anything up, but I wouldn't hold my breath. One more thing you could try is a different distro. You could try downloading Ubuntu 10.04, run it as a live cd and download and install the latest iscan/epkowa package found here (you have to select your scanner and fill in the short questionnaire): http://www.avasys.jp/lx-bin2/linux_e/spc/DL1.do Again, grasping at straws. Happy scanning, -- Alesh SlovakLinux Team -- AVASYS Corporation alesh.slovak at avasys.jp http://avasys.jp
[sane-devel] OCR with Xsane?
On 17 May 2010 23:58, Torfinn Ingolfsen wrote: > FWIW; I use gscan2pdf[1], which have a couple of ocr programs "built in". I Ubuntu has gscan2pdf, so you just need to $ sudo apt-get install gscan2pdf This gives you tesseract and ocropus from the GUI. cuneiform support will be in the upcoming version. Get it now from the git repository on sourceforge if you can't wait. Regards Jeff
[sane-devel] Canoscan 8800F]
what version of libusb is in use on these different machines- including you Gernot... allan On Tue, May 18, 2010 at 1:25 PM, Kurt Rosenfeld wrote: > Here is some good news. ?I tried Backends 1.0.21 on a FreeBSD 9 > machine and it works. ?Here is the stderr output: > > http://acm.poly.edu/~kurt/scanimage_freebsd_all255.txt > > This is the first time I tried it on a FreeBSD 9 machine. > I tried it before on another older FreeBSD 7 machine and it > seemed to fail in the same way as I have been seeing with > Linux. ?In both cases a little bit of dirty stuff was needed > to get it to compile since the current version of SANE Backends > in the FreeBSD ports tree is 1.0.20, which does not support the > Canon 8800F. ?The maintainer of the port recently submitted a > patch (awaiting commit) that, among other things, updates the > port to use 1.0.21. ?Today I manually applied that patch to my > ports tree and built sane-backends on the FreeBSD 9 box here in > the lab. ?What next? ?-kurt > > On Wed, May 19, 2010 at 12:01:29AM +0900, Gernot Hassenpflug wrote: >> On Tue, May 18, 2010 at 10:58 PM, Kurt Rosenfeld >> wrote: >> > With the environment set as follows: >> > >> > # env | grep SANE >> > DEBUG_SANE=255 >> > SANE_DEBUG_SANEI_USB=255 >> > SANE_DEBUG_DLL=255 >> > >> > the command: >> > >> > scanimage 2> scanimage_may18_all255.txt > ofile >> > >> > produces the following stderr output: >> > http://acm.poly.edu/~kurt/scanimage_may18_all255.txt >> >> Hi, and thanks. I don't know what this error means. Could this have >> something to do with permissions. I don't know the USB protocol well >> enough to tell if there is anything odd in the configuration or not. >> >> [sanei_usb] 000 EF 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 . >> .. >> libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=22 >> [sanei_usb] sanei_usb_write_bulk: write failed: Input/output error >> >> >> My 8800F gives the following (as root) using the same setup and command: >> >> 1) the result of the pixma backend during the scanning using all backend: >> >> [sanei_usb] sanei_usb_open: trying to open device `libusb:004:008' >> [sanei_usb] sanei_usb_open: configuration nr: 0 >> [sanei_usb] sanei_usb_open: ? ? interface nr: 0 >> [sanei_usb] sanei_usb_open: ? alt_setting nr: 0 >> [sanei_usb] sanei_usb_open: endpoint nr: 0 >> [sanei_usb] sanei_usb_open: direction: 0 >> [sanei_usb] sanei_usb_open: address: 7 transfertype: 2 >> [sanei_usb] sanei_usb_open: found bulk-out endpoint (address 0x07) >> [sanei_usb] sanei_usb_open: endpoint nr: 1 >> [sanei_usb] sanei_usb_open: direction: 128 >> [sanei_usb] sanei_usb_open: address: 8 transfertype: 2 >> [sanei_usb] sanei_usb_open: found bulk-in endpoint (address 0x08) >> [sanei_usb] sanei_usb_open: endpoint nr: 2 >> [sanei_usb] sanei_usb_open: direction: 128 >> [sanei_usb] sanei_usb_open: address: 9 transfertype: 3 >> [sanei_usb] sanei_usb_open: found interrupt-in endpoint (address 0x09) >> [sanei_usb] sanei_usb_open: opened usb device `libusb:004:008' (*dn=0) >> [sanei_usb] sanei_usb_control_msg: rtype = 0x80, req = 6, value = 256, >> index = 0, len = 18 >> [sanei_usb] 000 12 01 00 02 00 00 00 40 A9 04 01 19 01 01 01 02 ... at >> >> [sanei_usb] 010 00 01 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? .. >> [sanei_usb] sanei_usb_close: closing device 0 >> >> >> 2) the opening of the device after scanning of backends is complete >> and the 8800F is selected for operation: >> >> [dll] sane_get_devices: found 1 devices >> [dll] sane_open: trying to open `pixma:04A91901' >> [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1709 >> [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x170a >> [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x170b >> [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x170c >> [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1712 >> [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x170d >> [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x170e >> [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1713 >> [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x172b >> [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1714 >> [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1715 >> [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1716 >> [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1717 >> [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1718 >> [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1719 >> [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x171a >> [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x171b >> [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1721 >> [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1722 >> [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1723 >> [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, pr
[sane-devel] Canoscan 8800F]
Here is some good news. I tried Backends 1.0.21 on a FreeBSD 9 machine and it works. Here is the stderr output: http://acm.poly.edu/~kurt/scanimage_freebsd_all255.txt This is the first time I tried it on a FreeBSD 9 machine. I tried it before on another older FreeBSD 7 machine and it seemed to fail in the same way as I have been seeing with Linux. In both cases a little bit of dirty stuff was needed to get it to compile since the current version of SANE Backends in the FreeBSD ports tree is 1.0.20, which does not support the Canon 8800F. The maintainer of the port recently submitted a patch (awaiting commit) that, among other things, updates the port to use 1.0.21. Today I manually applied that patch to my ports tree and built sane-backends on the FreeBSD 9 box here in the lab. What next? -kurt On Wed, May 19, 2010 at 12:01:29AM +0900, Gernot Hassenpflug wrote: > On Tue, May 18, 2010 at 10:58 PM, Kurt Rosenfeld > wrote: > > With the environment set as follows: > > > > # env | grep SANE > > DEBUG_SANE=255 > > SANE_DEBUG_SANEI_USB=255 > > SANE_DEBUG_DLL=255 > > > > the command: > > > > scanimage 2> scanimage_may18_all255.txt > ofile > > > > produces the following stderr output: > > http://acm.poly.edu/~kurt/scanimage_may18_all255.txt > > Hi, and thanks. I don't know what this error means. Could this have > something to do with permissions. I don't know the USB protocol well > enough to tell if there is anything odd in the configuration or not. > > [sanei_usb] 000 EF 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 . > .. > libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=22 > [sanei_usb] sanei_usb_write_bulk: write failed: Input/output error > > > My 8800F gives the following (as root) using the same setup and command: > > 1) the result of the pixma backend during the scanning using all backend: > > [sanei_usb] sanei_usb_open: trying to open device `libusb:004:008' > [sanei_usb] sanei_usb_open: configuration nr: 0 > [sanei_usb] sanei_usb_open: interface nr: 0 > [sanei_usb] sanei_usb_open: alt_setting nr: 0 > [sanei_usb] sanei_usb_open: endpoint nr: 0 > [sanei_usb] sanei_usb_open: direction: 0 > [sanei_usb] sanei_usb_open: address: 7 transfertype: 2 > [sanei_usb] sanei_usb_open: found bulk-out endpoint (address 0x07) > [sanei_usb] sanei_usb_open: endpoint nr: 1 > [sanei_usb] sanei_usb_open: direction: 128 > [sanei_usb] sanei_usb_open: address: 8 transfertype: 2 > [sanei_usb] sanei_usb_open: found bulk-in endpoint (address 0x08) > [sanei_usb] sanei_usb_open: endpoint nr: 2 > [sanei_usb] sanei_usb_open: direction: 128 > [sanei_usb] sanei_usb_open: address: 9 transfertype: 3 > [sanei_usb] sanei_usb_open: found interrupt-in endpoint (address 0x09) > [sanei_usb] sanei_usb_open: opened usb device `libusb:004:008' (*dn=0) > [sanei_usb] sanei_usb_control_msg: rtype = 0x80, req = 6, value = 256, > index = 0, len = 18 > [sanei_usb] 000 12 01 00 02 00 00 00 40 A9 04 01 19 01 01 01 02 ... at > > [sanei_usb] 010 00 01 .. > [sanei_usb] sanei_usb_close: closing device 0 > > > 2) the opening of the device after scanning of backends is complete > and the 8800F is selected for operation: > > [dll] sane_get_devices: found 1 devices > [dll] sane_open: trying to open `pixma:04A91901' > [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1709 > [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x170a > [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x170b > [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x170c > [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1712 > [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x170d > [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x170e > [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1713 > [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x172b > [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1714 > [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1715 > [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1716 > [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1717 > [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1718 > [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1719 > [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x171a > [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x171b > [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1721 > [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1722 > [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1723 > [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1724 > [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1725 > [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1727 > [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1728 > [sanei_usb] sanei_usb_find_device
[sane-devel] Canoscan 8800F]
On Tue, May 18, 2010 at 10:32 AM, m. allan noah wrote: > DEBUG_SANE_SANEI_USB is not a proper variable. should be SANE_DEBUG_SANEI_USB Argh! Thanks for that, I checked the man pages and thought I had copied it down correctly. Kurt, can you please try again? Sorry about that. Regards, Gernot
[sane-devel] Canoscan 8800F]
On Tue, May 18, 2010 at 7:14 AM, Kurt Rosenfeld wrote: > Gernot, > > This is the stderr output of scanimage with DEBUG_SANE, > DEBUG_SANE_SANEI_USB, and SANE_DEBUG_DLL all set to 255: > http://acm.poly.edu/~kurt/scanimage_all255.txt > > Here is the stderr output of scanimage -d test > with SANE_DEBUG_TEST set to 255: > http://acm.poly.edu/~kurt/scanimage_-d_test.txt > > thanks, -kurt > > On Mon, May 17, 2010 at 01:09:23AM +0900, Gernot Hassenpflug wrote: >> Hello Kurt, >> >> I am concerned about this part of the log file: >> >> [pixma] pixma_open(): Canoscan 8800F >> [pixma] WARNING:pixma_write(): count(0) != len(16) >> [pixma] OUT ?T=3.054 len=-1 >> [pixma] ?:ef 20 00 00 00 00 00 00 ?00 00 00 00 00 00 00 00 >> [pixma] ? ERROR: EIO >> >> It looks as though the scanner is not responding even at the start of >> the operation. Maybe you can try setting more debug options to 255: Hi, looks like exactly the same. I thought we would see the raw USB operations now but apparently not: what I wanted to see was the USB attachment and configuration URBs. Since no I/O is possible at all, maybe the attachment or configuration is not going well. Q to the list: Are there any other DEBUG variables that can be set to see this kind of information? Otherwise, I recommend doing a USB snoop on a Windows machine (which I understand you do not have available) so I can try to see what if any differences there are to my scanner. No-one else has reported trouble using the 8800F, but I have no idea if Canon made different variations that require some tuning of the communication protocol. Regards, Gernot
[sane-devel] Canoscan 8800F]
With the environment set as follows: # env | grep SANE DEBUG_SANE=255 SANE_DEBUG_SANEI_USB=255 SANE_DEBUG_DLL=255 the command: scanimage 2> scanimage_may18_all255.txt > ofile produces the following stderr output: http://acm.poly.edu/~kurt/scanimage_may18_all255.txt thanks, -kurt On Tue, May 18, 2010 at 10:37:11AM +0900, Gernot Hassenpflug wrote: > On Tue, May 18, 2010 at 10:32 AM, m. allan noah wrote: > > DEBUG_SANE_SANEI_USB is not a proper variable. should be > > SANE_DEBUG_SANEI_USB > > Argh! Thanks for that, I checked the man pages and thought I had > copied it down correctly. Kurt, can you please try again? Sorry about > that. > > Regards, > Gernot
[sane-devel] Epson Artisan 710 support
On 05/18/2010 05:51 AM, Grant wrote: > Thanks Alesh. I previously owned an Artisan 700 and it developed the > same problem partway through the time I owned it. I remember > upgrading the epkowa backend a couple times, so the problem may have > been introduced by one of the upgrades. Thanks for the info. I'll take a look at older versions of iscan as well then. From what you say it may actually be easier to track this problem down by using the Artisan 700 instead of the 710. > Do you know which version of the epkowa backend was the first to > support the 710? Gentoo's package tree has 2.11.0 and 2.21.0. 2.21.0 > exhibits the problem, but 2.11.0 doesn't seem to support the 710. I'd > like to try the first version that supported the 710. Actually, the first version to support the 710 is 2.21.0. This information can be gleaned from the NEWS file. "Support", for the most part, usually just means we added the device name to the driver and tested it. Sometimes there are "special" devices that require a little bit of extra work, but for the most part the devices are well behaved and should actually work with almost any version of iscan/epkowa. All you would need to do to use your Artisan 710 with an older version of iscan/epkowa is to add the USB id to the /etc/sane.d/epkowa.conf file. Your mileage may vary. Happy scanning, -- Alesh SlovakLinux Team -- AVASYS Corporation alesh.slovak at avasys.jp http://avasys.jp
