[sane-devel] problems with genesys and MD6228
Am Montag, 19. Mai 2008 21:04:22 schrieb stef: ???could you try to run scanimage with debug logs enabled with the following commands in a shell: export SANE_DEBUG_GENESYS=255 export SANE_DEBUG_GENESYS_GL646=255 scanimage -d genesys scan.pnm 2scan.log Thank you for the completly commands. The tar.gz.file is coming separat. Other interested person welcome, please send a e-mail. ??BTW, is your model really a MD6228 ? Yes, this is the number on the type label. -- Viele Gr??e Werner Holtfreter
[sane-devel] HP 5590 not working in 1.0.19
On Mon, May 19, 2008 at 10:18 PM, Albert Cervera i Areny albert at nan-tic.com wrote: Attached are Xsane output with debug = 50 with ADF and PLAIN. It worked correctly. But I don't see how that should help with the messages we saw with scanimage. Thank you for the logs. As far as I see Xsane was told to scan only one page from ADF. Thus we didn't get the same bahaviour as with scanimage. usbsnoop.log is also bzipped and attached.
[sane-devel] problems with genesys and MD6228
Le Monday 19 May 2008 23:33:08 Werner Holtfreter, vous avez ?crit?: Am Montag, 19. Mai 2008 21:04:22 schrieb stef: ???could you try to run scanimage with debug logs enabled with the following commands in a shell: export SANE_DEBUG_GENESYS=255 export SANE_DEBUG_GENESYS_GL646=255 scanimage -d genesys scan.pnm 2scan.log Thank you for the completly commands. The tar.gz.file is coming separat. Other interested person welcome, please send a e-mail. ??BTW, is your model really a MD6228 ? Yes, this is the number on the type label. -- Viele Gr??e Werner Holtfreter Thanks for the data. The bug in start of scan area detection is due to the fact the plastic used in the casing is darker than the one used to develop the backend. So detection of a black strip in a white area fails. Top of the strip is detected OK, but bottom detection fails. I will change the detection function to only use the 'top' since only this value is reliable for MD6228 and MD6471 models. Will look into black and white scan modes problems when this bug will be fixed, since it possibly gives negative offset that would confuse the scanner like you saw. For the backward/forward moves at high resolution, like you allready guessed, it is a USB bandwidth issue. Scanning head pauses until th PC read all the data. Regards, Stef
[sane-devel] Double-free following scan on ubuntu hardy 8.04 with epjitsu fi-60f
On Tue, 29 Apr 2008 09:20:04 +0100, Chris Lale wrote: Jeff Kowalczyk wrote: On Mon, 28 Apr 2008 21:01:08 -0400, m. allan noah wrote: well, i've just committed a patch to fix this, but please test, as i never saw the error message in the first place... Does anyone have a good procedure for patching and rebuilding released ubuntu .debs to test upstream changes? Or a way to build new debs from sane snapshots at a particular revision? The originally reported platform (Ubuntu) is not my familiar source-based system (Gentoo). This is how you could do it in Debian [1]. Basic method for a package somepackage version 0.7.1-1 is as follows. (This does not change the version number, but that is explained in the documentation.): 0. Get the source package. 1. put somepackage_0.7.1-1.diff.gz somepackage_0.7.1.orig.tar.gz somepackage_0.7.1-1.dsc in a directory. 2. Run dpkg-source -x somepackage_0.7.1-1.dsc to recreate build directory. 3. cd to somepackage-0.7.1 Do what you need. 4. Run dpkg-buildpackage -rfakeroot Completes with message dpkg-buildpackage: full upload (original source is included) 5. Run checks: lintian somepackage_0.7.1-1_i386.changes and linda somepackage_0.7.1-1_i386.changes Both should complete with no errors reported. debc somepackage_0.7.1-1_i386.changes | less On inspection, files contained in package should look OK. # debi somepackage_0.7.1-1_i386.changes should install package OK. # dpkg --purge somepackage removes package. [1] http://www.us.debian.org/doc/maint-guide/ Hope that helps. -- Chris. I've tried the above procedure several times over the past weeks, and I can't get it right. The ubuntu sane-backends package is missing the .changes files, etc. Also, I'm missing the punchline of the procedure, I want to make a new .deb that I can dpkg install on any number of machines, report upstream that the patches help. I'd like to do the hardware testing on the patch, since it's a relatively uncommon scanner, and the patch seems like it will make this hardware usable on Ubuntu. Can anyone with ubuntu-flavored dpkg-fu either list a working procedure, or post a deb with the patches integrated? Any info would be much appreciated. Thanks, Jeff
