Re: [sane-devel] [sane-commit] [sane-backends] branch master updated (d5c7e22 - f69a1ad)
Hi René, Many thanks for your fast patch. 32-bit is compiling now. Cheers, Rolf Am 15.03.2015 um 00:21 schrieb René Rebe: Hi, thanks for the pointer, should be fixed in git:HEAD now. Let hem know if you find more ,-) René On Mar 14, 2015, at 21:40, Rolf Bensch r...@bensch-online.de mailto:r...@bensch-online.de wrote: Hi René, Your last commit breaks 32-bit Ubuntu Utopic, Precise and Trusty compilations. Please have a look to the log files: https://launchpadlibrarian.net/200238430/buildlog_ubuntu-utopic-i386.sane-backends_1.0.25-git20150314-utopic2_BUILDING.txt.gz https://launchpadlibrarian.net/200238372/buildlog_ubuntu-precise-i386.sane-backends_1.0.25-git20150314-precise2_BUILDING.txt.gz https://launchpadlibrarian.net/200238363/buildlog_ubuntu-trusty-i386.sane-backends_1.0.25-git20150314-trusty2_BUILDING.txt.gz However, 32-bit Trusty compilation is working: https://launchpadlibrarian.net/200201264/buildlog_ubuntu-lucid-i386.sane-backends_1.0.25-git20150314-lucid0_BUILDING.txt.gz The 64-bit compilations are working without any problems. Many thanks for help in advance. Cheers, Rolf Am 13.03.2015 um 15:18 schrieb René Rebe: This is an automated email from the git hooks/post-receive script. rene-guest pushed a change to branch master in repository sane-backends. from d5c7e22 fixed multiple Avision regressions: most scanner basically did not work at all anymore, ... range initilaizer, clobbering paper-length window bits, ...) introduced over the past years, added support for newer ASIC gamma table size, added AV220D2+ ID new e056073 fixed duplex for some avision scanners new f69a1ad removed unnecessary feature_type2 clutter by using a uint64_t to share all bits The 2 revisions listed above as new are entirely new to this repository and will be described in separate emails. The revisions listed as adds were already present in the repository and have only been added to this reference. Summary of changes: ChangeLog| 5 + backend/avision.c| 344 ++- backend/avision.h| 84 ++--- doc/sane-avision.man | 4 +- 4 files changed, 222 insertions(+), 215 deletions(-) -- http://t2-project.org http://t2-project.org/ | http://rene.rebe.de -- sane-devel mailing list: sane-devel@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-requ...@lists.alioth.debian.org
Re: [sane-devel] Canon LiDE 220 unexpected success
On 15/03/15 07:43, Stef wrote: what is needed is a log recorded when doing a preview when running windows O/S. The log tool to use is usbpcap http://desowin.org/usbpcap/ . Would a Wireshark log help, while running Windows in VirtualBox? I have such a log, however, am not able to generate further right now, since the 120 stopped responding to any commands. I'm waiting for a repair or replacement. Havard -- sane-devel mailing list: sane-devel@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-requ...@lists.alioth.debian.org
Re: [sane-devel] Canon LiDE 220 unexpected success
On 14/03/2015 18:12, Jochen wrote: Hi Stef, I understand you're asking for a log from somebody with a LiDE 120 doing a preview. Me, I'd be happy to see my LiDE 120 supported by SANE. So if you tell me what to do and how to even make my LiDE 120 do anything loggable, I'll see if I can provide that. Unfortunately, I am not much of a Linux crack, but I managed to compile and install sane-1.0.25. Regards, Jo --- Hello, Hello, what is needed is a log recorded when doing a preview when running windows O/S. The log tool to use is usbpcap http://desowin.org/usbpcap/ . Regards, Stef -- sane-devel mailing list: sane-devel@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-requ...@lists.alioth.debian.org
Re: [sane-devel] Canon LiDE 220 unexpected success
Hi Stef, I understand you're asking for a log from somebody with a LiDE 120 doing a preview. Me, I'd be happy to see my LiDE 120 supported by SANE. So if you tell me what to do and how to even make my LiDE 120 do anything loggable, I'll see if I can provide that. Unfortunately, I am not much of a Linux crack, but I managed to compile and install sane-1.0.25. Regards, Jo --- Hello, support for LiDE 220 has already been committed to SANE's git tree (see http://www.sane-project.org/cvs.html). However the scanarea geometry needs fixing, head is bump at end while trying to go too far. This will be fixed by Monday. Regarding LiDE 120 support, I'd need a log recorded with usbpcap of a preview (and only the preview) to check is like older models, this one is close to the 220, and possibly figure out hos to add support for it. Regards, Stef -- sane-devel mailing list: sane-devel@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-requ...@lists.alioth.debian.org
Re: [sane-devel] Error during device I/O with Fujitsu fi65-F (epjitsu backend)
hmm- I have never actually seen an fi-65f, I only have user reports from my patches. However, the initial development was done with firmware 65f_0A01.nal Can you try to extract that version (or later) from the Fujitsu windows drivers? You might have to get the latest version from their website. Maybe there is a difference? Otherwise, you would need to get a log of the scanner in action under windows, so we could try to reproduce the commands. allan On Sat, Mar 14, 2015 at 11:37 PM, Jonas Neubert jonas.neub...@gmail.com wrote: Thanks Allan, my mind was so set on thinking of output as the scanner output, I didn't even consider that this error might about the program's output! When doing 'scanimage file.pnm' the first attempt at scanning an image now ends with the same scanimage: sane_start: Error during device I/O as scanimage -T. Full output: jonas@sane-scanner:~$ sudo SANE_DEBUG_DLL=256 SANE_DEBUG_EPJITSU=25 scanimage file.pnm [sanei_debug] Setting debug level of dll to 256. [dll] sane_init: SANE dll backend version 1.0.13 from sane-backends 1.0.25git [dll] sane_init/read_dlld: attempting to open directory `./dll.d' [dll] sane_init/read_dlld: attempting to open directory `/etc/sane.d/dll.d' [dll] sane_init/read_dlld: using config directory `/etc/sane.d/dll.d' [dll] sane_init/read_dlld: done. [dll] sane_init/read_config: reading dll.conf [dll] add_backend: adding backend `epjitsu' [dll] sane_get_devices [dll] load: searching backend `epjitsu' in `/usr/lib/sane' [dll] load: trying to load `/usr/lib/sane/libsane-epjitsu.so.1' [dll] load: dlopen()ing `/usr/lib/sane/libsane-epjitsu.so.1' [dll] init: initializing backend `epjitsu' [sanei_debug] Setting debug level of epjitsu to 25. [epjitsu] sane_init: start [epjitsu] sane_init: epjitsu backend 1.0.27, from sane-backends 1.0.25git [epjitsu] sane_init: finish [dll] init: backend `epjitsu' is version 1.0.27 [epjitsu] sane_get_devices: start [epjitsu] sane_get_devices: reading config file epjitsu.conf [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/60f_0A00.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x10c7' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/300_0C00.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x1156' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/300M_0C00.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x117f' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/1300_0C26.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x11ed' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/65f_.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x11bd' [epjitsu] attach_one: start 'libusb:001:004' [epjitsu] attach_one: init struct [epjitsu] attach_one: connect fd [epjitsu] connect_fd: start [epjitsu] connect_fd: opening USB device [epjitsu] connect_fd: finish [epjitsu] load_fw: start [epjitsu] get_stat: start [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 2 bytes [epjitsu] in: reading 2 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 2 bytes [epjitsu] do_cmd: finish [epjitsu] load_fw: read firmware file /usr/share/sane/epjitsu/65f_.nal ok [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 4 bytes, timeout 1 [epjitsu] cmd: wrote 4 bytes, retVal 0 [epjitsu] out: writing 65536 bytes, timeout 1 [epjitsu] out: wrote 65536 bytes, retVal 0 [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 1 bytes, timeout 1 [epjitsu] cmd: wrote 1 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 1 bytes, timeout 1 [epjitsu] cmd: wrote 1 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu]
Re: [sane-devel] Error during device I/O with Fujitsu fi65-F (epjitsu backend)
Wireshark is fine, but this log does not contain the calibration step, which is where sane seems to fail. Can you unplug and replug the device while wireshark is running, and get a log of the initialization process? I'm not sure if wireshark can do that. allan On Sun, Mar 15, 2015 at 6:01 PM, Jonas Neubert jonas.neub...@gmail.com wrote: I see, installing that driver on Windows adds both a 65f_.nal in C:\Windows and a 65f_0A01.nal in C:\Windows\twain_32\fjscan32. I had missed that latter last time. Unfortunately, still no change in behavior. The output remains effectively same, but just in case I'm missing something, below is the full output again. Not sure what exactly you mean by log of the scanner in action under windows, but [1] is a .pcap captured with USBPcap on Windows while scanning a full page at 300dpi. I'd be happy to collect more data or dig deeper into this myself, but I'll definitely need guidance. -Jonas [1] https://www.dropbox.com/s/1yny75ns4qq6i4u/fi65_2.pcap?dl=0 jonas@sane-scanner:~$ sudo SANE_DEBUG_DLL=256 SANE_DEBUG_EPJITSU=25 scanimage file.pnm [sanei_debug] Setting debug level of dll to 256. [dll] sane_init: SANE dll backend version 1.0.13 from sane-backends 1.0.25git [dll] sane_init/read_dlld: attempting to open directory `./dll.d' [dll] sane_init/read_dlld: attempting to open directory `/etc/sane.d/dll.d' [dll] sane_init/read_dlld: using config directory `/etc/sane.d/dll.d' [dll] sane_init/read_dlld: done. [dll] sane_init/read_config: reading dll.conf [dll] add_backend: adding backend `epjitsu' [dll] sane_get_devices [dll] load: searching backend `epjitsu' in `/usr/lib/sane' [dll] load: trying to load `/usr/lib/sane/libsane-epjitsu.so.1' [dll] load: dlopen()ing `/usr/lib/sane/libsane-epjitsu.so.1' [dll] init: initializing backend `epjitsu' [sanei_debug] Setting debug level of epjitsu to 25. [epjitsu] sane_init: start [epjitsu] sane_init: epjitsu backend 1.0.27, from sane-backends 1.0.25git [epjitsu] sane_init: finish [dll] init: backend `epjitsu' is version 1.0.27 [epjitsu] sane_get_devices: start [epjitsu] sane_get_devices: reading config file epjitsu.conf [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/60f_0A00.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x10c7' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/300_0C00.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x1156' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/300M_0C00.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x117f' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/1300_0C26.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x11ed' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/65f_0A01.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x11bd' [epjitsu] attach_one: start 'libusb:001:002' [epjitsu] attach_one: init struct [epjitsu] attach_one: connect fd [epjitsu] connect_fd: start [epjitsu] connect_fd: opening USB device [epjitsu] connect_fd: finish [epjitsu] load_fw: start [epjitsu] get_stat: start [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 2 bytes [epjitsu] in: reading 2 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 2 bytes [epjitsu] do_cmd: finish [epjitsu] load_fw: read firmware file /usr/share/sane/epjitsu/65f_0A01.nal ok [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 4 bytes, timeout 1 [epjitsu] cmd: wrote 4 bytes, retVal 0 [epjitsu] out: writing 65536 bytes, timeout 1 [epjitsu] out: wrote 65536 bytes, retVal 0 [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 1 bytes, timeout 1 [epjitsu] cmd: wrote 1 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 1 bytes, timeout 1 [epjitsu] cmd: wrote 1 bytes, retVal 0 [epjitsu] in: memset 1 bytes
Re: [sane-devel] Error during device I/O with Fujitsu fi65-F (epjitsu backend)
I think this should cover it, started capture before plugging in, then initialization and then a full page scan: https://www.dropbox.com/s/y0mz0by18r1uti5/fi65_3.pcap?dl=0 -Jonas On Sun, 15 Mar 2015 15:39:16 -0700 m. allan noahkitno...@gmail.com wrote Wireshark is fine, but this log does not contain the calibration step, which is where sane seems to fail. Can you unplug and replug the device while wireshark is running, and get a log of the initialization process? I'm not sure if wireshark can do that. allan -- sane-devel mailing list: sane-devel@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-requ...@lists.alioth.debian.org
Re: [sane-devel] Error during device I/O with Fujitsu fi65-F (epjitsu backend)
Hmm- perhaps you can try scanimage again, but at resolution 300? Also increase the epjitsu debug level to 25, and don't set the dll debug level, it is not helpful. I see a couple possible differences that have never been important with prior scanners, but perhaps are important with yours. allan On Sun, Mar 15, 2015 at 6:53 PM, Jonas Neubert jonas.neub...@gmail.com wrote: I think this should cover it, started capture before plugging in, then initialization and then a full page scan: https://www.dropbox.com/s/y0mz0by18r1uti5/fi65_3.pcap?dl=0 -Jonas On Sun, 15 Mar 2015 15:39:16 -0700 m. allan noahkitno...@gmail.com wrote Wireshark is fine, but this log does not contain the calibration step, which is where sane seems to fail. Can you unplug and replug the device while wireshark is running, and get a log of the initialization process? I'm not sure if wireshark can do that. allan -- well, I stand up next to a mountain- and I chop it down with the edge of my hand -- sane-devel mailing list: sane-devel@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-requ...@lists.alioth.debian.org
Re: [sane-devel] Error during device I/O with Fujitsu fi65-F (epjitsu backend)
I see, installing that driver on Windows adds both a 65f_.nal in C:\Windows and a 65f_0A01.nal in C:\Windows\twain_32\fjscan32. I had missed that latter last time. Unfortunately, still no change in behavior. The output remains effectively same, but just in case I'm missing something, below is the full output again. Not sure what exactly you mean by log of the scanner in action under windows, but [1] is a .pcap captured with USBPcap on Windows while scanning a full page at 300dpi. I'd be happy to collect more data or dig deeper into this myself, but I'll definitely need guidance. -Jonas [1] https://www.dropbox.com/s/1yny75ns4qq6i4u/fi65_2.pcap?dl=0 jonas@sane-scanner:~$ sudo SANE_DEBUG_DLL=256 SANE_DEBUG_EPJITSU=25 scanimage file.pnm [sanei_debug] Setting debug level of dll to 256. [dll] sane_init: SANE dll backend version 1.0.13 from sane-backends 1.0.25git [dll] sane_init/read_dlld: attempting to open directory `./dll.d' [dll] sane_init/read_dlld: attempting to open directory `/etc/sane.d/dll.d' [dll] sane_init/read_dlld: using config directory `/etc/sane.d/dll.d' [dll] sane_init/read_dlld: done. [dll] sane_init/read_config: reading dll.conf [dll] add_backend: adding backend `epjitsu' [dll] sane_get_devices [dll] load: searching backend `epjitsu' in `/usr/lib/sane' [dll] load: trying to load `/usr/lib/sane/libsane-epjitsu.so.1' [dll] load: dlopen()ing `/usr/lib/sane/libsane-epjitsu.so.1' [dll] init: initializing backend `epjitsu' [sanei_debug] Setting debug level of epjitsu to 25. [epjitsu] sane_init: start [epjitsu] sane_init: epjitsu backend 1.0.27, from sane-backends 1.0.25git [epjitsu] sane_init: finish [dll] init: backend `epjitsu' is version 1.0.27 [epjitsu] sane_get_devices: start [epjitsu] sane_get_devices: reading config file epjitsu.conf [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/60f_0A00.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x10c7' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/300_0C00.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x1156' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/300M_0C00.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x117f' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/1300_0C26.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x11ed' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/65f_0A01.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x11bd' [epjitsu] attach_one: start 'libusb:001:002' [epjitsu] attach_one: init struct [epjitsu] attach_one: connect fd [epjitsu] connect_fd: start [epjitsu] connect_fd: opening USB device [epjitsu] connect_fd: finish [epjitsu] load_fw: start [epjitsu] get_stat: start [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 2 bytes [epjitsu] in: reading 2 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 2 bytes [epjitsu] do_cmd: finish [epjitsu] load_fw: read firmware file /usr/share/sane/epjitsu/65f_0A01.nal ok [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 4 bytes, timeout 1 [epjitsu] cmd: wrote 4 bytes, retVal 0 [epjitsu] out: writing 65536 bytes, timeout 1 [epjitsu] out: wrote 65536 bytes, retVal 0 [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 1 bytes, timeout 1 [epjitsu] cmd: wrote 1 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 1 bytes, timeout 1 [epjitsu] cmd: wrote 1 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] get_stat: start [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 2 bytes [epjitsu] in: reading 2 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 2 bytes [epjitsu] do_cmd:
Re: [sane-devel] Canon LiDE 120 preview log
I also have a Canon LiDE 120 that I hope SANE will support soon. If there's any other log/capture files that you need I'd be happy to provide them. Thanks, Steven -- sane-devel mailing list: sane-devel@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-requ...@lists.alioth.debian.org
Re: [sane-devel] xsane crashes using Acquire Preview on Color
Hi All, Any idea on this? From: sane-devel [mailto:sane-devel-bounces+arielramonito.edera=ddp.kyocera@lists.alioth.debian.org] On Behalf Of Ariel Ramonito Edera Sent: Friday, March 13, 2015 5:41 PM To: sane-devel@lists.alioth.debian.org Subject: [sane-devel] xsane crashes using Acquire Preview on Color Hi All, I am currently developing a backend for our scanner device. The maximum page width and height of our device is 432 and 297 respectively. I am able to successfully scan using monochrome, grayscale, and color settings. I don't have any problem if I SCAN, the problem is using Acquire Preview. XSANE crashes when I use the Acquire Preview feature. Acquire Preview successfully displays scanned image IF settings is monochrome or grayscale. But using color setting on Acquire Preview, XSANE crashes. I have tried changing the page width and height to 297 and 210, respectively, (with color setting) and it successfully displays a scanned image using Acquire Preview. I am using xsane-0.998 version by the way. Do you have any idea if this is a problem on frontend or backend? Best Regards, Ariel IMPORTANT NOTICE: This e-mail and its attachments may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of KYOCERA Document Solutions Development Philippines, Inc. If you are not the intended recipient of this e-mail and its attachments, you must take no action based upon them, nor must you copy or show them to anyone. Please contact the sender if you believe you have received this e-mail in error. The integrity and security of this message cannot be guaranteed on the Internet. IMPORTANT NOTICE: This e-mail and its attachments may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of KYOCERA Document Solutions Development Philippines, Inc. If you are not the intended recipient of this e-mail and its attachments, you must take no action based upon them, nor must you copy or show them to anyone. Please contact the sender if you believe you have received this e-mail in error. The integrity and security of this message cannot be guaranteed on the Internet. -- sane-devel mailing list: sane-devel@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-requ...@lists.alioth.debian.org
Re: [sane-devel] Canon LiDE 120 preview log
On 15/03/2015 12:23, Mr. Kraus wrote: Hello, what is needed is a log recorded when doing a preview when running windows O/S. The log tool to use is usbpcap http://desowin.org/usbpcap/ . Regards, Stef Hi, here you go! To be complete, I added the log of an actual scan, as well: http://weshare.me/5c5cfb7b52a8ab9d/lide120_preview.pcap http://weshare.me/5c5cfb7b52a8ab9d/lide120_scan.pcap Thanx for your efforts, looking forward to your feedback. Enjoy! Jo Hello, thanks for the data. It seems that both posted logs are the same, and are the one of a scan. A preview should be less big. Could you retry it ? What was the resolution used for the scan, 600 dpi ? Regards, Stef -- sane-devel mailing list: sane-devel@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-requ...@lists.alioth.debian.org
