Re: [sane-devel] Martin passed away

[m. allan noah]

Rob, I am sorry to hear this. Martin maintained our Dutch translation,
and provided support on this mailing list for more than a decade. He
was a consistent, dependable contributor, who gave of his time to
improve our little corner of the world. Our condolences to you and
your family.

allan

On Sat, Mar 24, 2018 at 5:33 AM, Martin Kho  wrote:
> With deep sadness, I have to inform you that my brother Martin has passed away
> last Saturday. Most of the time, he enjoyed working with you. Keep up the good
> work,
> Rob
>
>
>
> --
> 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



-- 
"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] Looking for network scanner connection information

[m. allan noah]

The sane canon_dr backend does not support network scanners. You will need
to do some programming to make it work.

allan

On Jan 22, 2018 7:48 PM, "Jimi Damon"  wrote:

> Hi,
>
> I'm looking to get my Canon dr-c225w working with my Ubuntu 16.04 distro.
>
> The scanner is wifi enabled so I don't need a USB connected host to use it.
>
> My question  is: I can't find any examples (using my google-fu) that *just
> *allows a Linux pc to connect to the scanner without a dedicated USB
> device...ie only via Ethernet / wifi .
>
>
> Can anyone point me to a better reference ?
>
> Thanks,
>
> --
> 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
>
-- 
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] Cannot connect to my Fujitsu ScanSnap S1300i: connect_fd: could not open device: 3

[m. allan noah]

Well, you could git bisect between sane-backends 1.0.25 and 1.0.27,
and find the commit where it breaks.

Can you show the command you used to set the env var?

allan

On Tue, Dec 5, 2017 at 2:10 PM, Max Westen  wrote:
> Hi Allan,
>
> I've tried setting the env setting SANE_USB_WORKAROUND=1 before connecting
> my scanner.
> Output is still the same. The first scanimage -L returns the device. The
> second (or sometimes the third time) calling the same line and it's gone.
>
> I've looked at the specs of this macbookpro; it only contains 2 USB 2.0
> ports, so it shouldn't be a USB 3 issue
>
> https://everymac.com/systems/apple/macbook_pro/specs/macbook-pro-core-2-duo-2.2-15-santa-rosa-specs.html
>
> I also tried installing Arch (same setup as on macbookpro) with sane on
> another laptop lying around (with lower specs, so definately not usable as
> workstation) and the same scanner and that works flawless :(
>
> Is there anything I could try or anything I could do to try to get it
> resolved ?
>
> Thanks again!
>
> Max
>
>
> --
> 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



-- 
"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] Cannot connect to my Fujitsu ScanSnap S1300i: connect_fd: could not open device: 3

[m. allan noah]

Sounds like the typical Linux USB problem. Please see this statement
from the sane 1.0.27 release notes:

Note 3: The Linux USB3 workaround which was added in version 1.0.25 is
now disabled by default. If you have difficulty using a scanner which
previously worked, or intermittent scanner availability, try setting
the new environment variable SANE_USB_WORKAROUND=1 before starting
your frontend.

Please give this a try, and let us know if it helps.

allan

On Mon, Dec 4, 2017 at 5:47 AM, Max Westen  wrote:
> Follow up:
>
> Tried the other USB-port.
> detecting the scanner gives me a hit. Immediately rescanning and the device
> is 'gone':
>
> [max@Luminox test]$ scanadf -L
> device `epjitsu:libusb:002:002' is a FUJITSU ScanSnap S1300i scanner
> [max@Luminox test]$ scanadf -L
> [max@Luminox test]$
>
>
> After some trying, this behaviour keeps the same...
>
> I've prepared a comammandline with the next USB instance, unplug the USB,
> put it back in and then execute the command. Yay it works !
>
> [max@Luminox test]$ scanadf -d "epjitsu:libusb:002:009" --source "ADF
> Duplex" --mode Color --resolution 300dpi -o /tmp/20171204_113055/page_%04d
> --page-height 376
> scanadf: rounded value of page-height from 376 to 375.999
> Scanned document /tmp/20171204_113055/page_0001
> Scanned document /tmp/20171204_113055/page_0002
> Scanned 2 pages
> [max@Luminox test]$ scanadf -L
> device `epjitsu:libusb:002:009' is a FUJITSU ScanSnap S1300i scanner
> [max@Luminox test]$ scanadf -L
> [max@Luminox test]$
>
> but immediately running a scanadf -L afterwards, gets me the correct ID,
> giving the command another time, makes it disappear
>
> I can't get my head around this, but this isn't really workable
>
>
> Any help is greatly appreciated!
>
> Max
>
> --
> 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



-- 
"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] [inactive] options

[m. allan noah]

The page size options are disabled when you are using the flatbed, but
you should not need them. The bounds of the x/y options should be set
to the maximum supported by the flatbed in that case. It is possible
this is a bug in the old version of sane-backends you are using. Can
you provide your complete command line you are using with scanimage,
and all the options as listed by scanimage --help?

Also, please don't use nabble. It lies and says the emails came from
yahoo when they did not, which causes your mail to be sent to spam
filters.

allan

On Wed, Nov 29, 2017 at 10:34 AM, ylafont  wrote:
> I am trying to scan legal size pager over the ADF,   when setting the Scan
> area to legal on the command line, they are changed  back to letter size
>
> *scanimage: rounded value of br-x from 215.9 to 215.872
> scanimage: rounded value of br-y from 355.6 to 279.364
> *
>
> There are inactive options listed for the backend,  Is there a method of
> activating them for this purpose?
>
> *All options specific to device `net:localhost:fujitsu:fi-4220C2dj:100742':
> *
>   Geometry:
> -l 0..224.846mm (in steps of 0.0211639) [0]
> Top-left x position of scan area.
> -t 0..296.972mm (in steps of 0.0211639) [0]
> Top-left y position of scan area.
> -x 0..224.846mm (in steps of 0.0211639) [215.872]
> Width of scan-area.
> -y 0..296.972mm (in steps of 0.0211639) [279.364]
> Height of scan-area.
>* --page-width 0..224.846mm (in steps of 0.0211639) [inactive]*
> Specifies the width of the media.  Required for automatic centering
> of
> *sheet-fed scans.
> --page-height 0..863.489mm (in steps of 0.0211639) [inactive]*
> Specifies the height of the media.
>
>
> *backend - fujitsu:fi-4220C2dj:*
>
> *scanimage (sane-backends) 1.0.22; backend version 1.0.22*
>
> Any assistance is greatly appreciated.  Thank you in advance.
>
>
>
> --
> Sent from: http://sane.10972.n7.nabble.com/SANE-Dev-f3.html
>
> --
> 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



-- 
"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] Saned Tutorial is not correct -

[m. allan noah]

We are not the authors of the tutorial with the error.

allan

On Mon, Nov 6, 2017 at 10:29 PM, Alvaro Gil  wrote:
> Hi, the saned tutorial is not correct on this page:
> https://help.ubuntu.com/community/SaneDaemonTutorial
>
> Lots of people are having this issue:
> https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1577137
> I posted the fix to post #32
> ---
>
> The problem is the documentation is not correct, it states:
>
>for systemd we need to add 2 configuration files in
> /etc/systemd/system.
>
> This is incorrect, move the two files to:
>
>/etc/systemd/
>
> ---
>
> after continue with the tutorial.
>
> sudo systemctl enable saned.socket
> sudo systemctl start saned.socket
> systemctl status saned.socket
>
>
> now it will load correctly on restart.
>
> Alvaro Gil
> Gil Machine and Tool
> 1053 Bushkill Drive
> Easton, PA 18042
> http://www.GilMachine.com/
>
> --
> 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



-- 
"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] Fujitsu iX500 - No scanners were identified.

[m. allan noah]

The SANE_USB_WORKAROUND env var was added in sane-backends 1.0.27, so
I recommend an upgrade.

allan

On Mon, Oct 23, 2017 at 9:18 AM, Jiri Kanicky <j...@ganomi.com> wrote:
> Hi Allan,
>
>
>
> Thank you for your response. I really appreciate it.
>
>
>
> Currently I have latest sane-backends from Debian SID. Do I have to install
> the developer version or the SANE_USB_WORKAROUND variable also works in
> current debian version? As a workaround I might prefer to use the USB 2.0
> Type B plug until everything is fixed in the future or until I get new
> scanner. This is much easier workaround then maintaining the developer
> version. :). I can also try the experimental repo with sane-backends
> (1.0.27-1~experimental2) if needed.
>
>
>
> Here are some details for you.
>
>
>
> # dpkg -l | grep libsane
>
> ii libsane:amd64 1.0.25-4.1
>
> ii libsane-common 1.0.25-4.1
>
> ii libsane-extras:amd64 1.0.22.5
>
> ii libsane-extras-common 1.0.22.5
>
> Using cable with USB 3.0 Type B plug:
>
> ---
>
>
>
> jiri@superman:~$ SANE_USB_WORKAROUND=1 scanimage -L
> device `fujitsu:ScanSnap iX500:64324' is a FUJITSU ScanSnap iX500 scanner
>
>
> jiri@superman:~$ SANE_USB_WORKAROUND=1 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).
>
>
>
> jiri@superman:~$ 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=0x04c5 [Fujitsu], product=0x132b [ScanSnap iX500])
> at libusb:002:021
> could not open USB device 0x1d6b/0x0003 at 002:001: Access denied
> (insufficient permissions)
> could not open USB device 0x1bcf/0x2c6b at 001:004: Access denied
> (insufficient permissions)
> could not open USB device 0x1044/0x7a06 at 001:003: Access denied
> (insufficient permissions)
> could not open USB device 0x8087/0x0a2b at 001:002: Access denied
> (insufficient permissions)
> could not open USB device 0x1d6b/0x0002 at 001:001: Access denied
> (insufficient permissions)
>  # 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.
>
> Using cable with USB 2.0 Type B plug:
>
> -
>
>
>
> jiri@superman:~$ scanimage -L
> device `fujitsu:ScanSnap iX500:64324' is a FUJITSU ScanSnap iX500 scanner
>
>
> jiri@superman:~$ scanimage -L
> device `fujitsu:ScanSnap iX500:64324' is a FUJITSU ScanSnap iX500 scanner
>
>
> jiri@superman:~$ 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.
>
> could not open USB device 0x1d6b/0x0003 at 002:001: Access denied
> (insufficient permissions)
> could not open USB device 0x1bcf/0x2c6b at 001:004: Access denied
> (insufficient permissions)
> could not open USB device 0x1044/0x7a06 at 001:003: Access denied
> (insufficient permissions)
> could not open USB device 0x8087/0x0a2b at 001:002: Access denied
> (insufficient permissions)
> found USB scanner (vendor=0x04c5 [Fujitsu], product=0x132b [ScanSnap iX500])
> at libusb:001:024
> could not open USB device 0x1d6b/0x0002 at 001:001: Access denied
> (insufficient permissions)
>  # 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.
>
>

Re: [sane-devel] Fujitsu iX500 - No scanners were identified.

[m. allan noah]

What was the outcome from my suggestions last year?

allan

On Sat, Oct 21, 2017 at 12:09 PM, Jiri Kanicky <j...@ganomi.com> wrote:
> Hi,
>
> I know this is old topic, but I just would like to everyone know that:
>
> 1. When I use USB 3.0 Type B Plug connector (cable which comes with the
> scanner), scanimage -L recognizes the scanner only once and applications like
> Simple Scan or Skanlite are not able to scan.
>
> 2. However when I use USB 2.0 Type B Plug connector (i used cable from my
> externar HDD), everything seems to work just fine.
>
> My notebook has got all USB ports USB 3.0 and I don't have USB 2 hub to test.
>
> Anyway using cable with old USB 2.0 B plug is simple workaround.
>
> If I can provide any debug data, which can help to fix the issue, please let 
> me
> know and I can provide it for both cables.
>
> - Jiri
>
> On Monday, 21 November 2016 9:02:21 PM AEDT m. allan noah wrote:
>> You did not tell us what you upgraded? Sane-backends, your scanner, your
>> kernel?
>>
>> This sounds like a pretty typical linux usb bug. You might need to
>> install a development version of sane-backends from our git repo. Once
>> you have built and installed a sane-backends git snapshot (using the
>> info in README.linux), you can run scanimage -L repeatedly. You may
>> find that the scanner only shows up intermittently. If that is the
>> case, try running this repeatedly instead:
>>
>> SANE_USB_WORKAROUND=1 scanimage -L
>>
>> That might work better. If so, you will have to put
>> SANE_USB_WORKAROUND=1 into your environment.
>>
>> Oh, and BTW, your scanner is not supported by the snapscan backend.
>> Try fujitsu instead.
>>
>> allan
>>
>> On Mon, Nov 21, 2016 at 6:40 AM, Jiri <j...@ganomi.com> wrote:
>> > Hi,
>> >
>> > [Debian Sid]
>> >
>> > I started having problem with Fujitsu iX500 scanner after upgrade. It used
>> > to work fine, but now it seems the system identifies the scanner for a
>> > just
>> > a while and but apps cannot use it.
>> >
>> > Here is example. I run the following command two times right after each
>> > other. The scanner is recognized on first run (after plugging USB in), but
>> > when I run it second time it says the scanner was not identified.
>> >
>> > Any help would be appreciated.
>> >
>> >
>> > ganomi@knightrider:~$ SANE_DEBUG_FUJITSU=15 scanimage -L
>> > [sanei_debug] Setting debug level of fujitsu to 15.
>> > [fujitsu] sane_init: start
>> > [fujitsu] sane_init: fujitsu backend 1.0.127, from sane-backends 1.0.25
>> > [fujitsu] sane_init: finish
>> > [fujitsu] sane_get_devices: start
>> > [fujitsu] sane_get_devices: reading config file fujitsu.conf
>> > [fujitsu] sane_get_devices: setting "buffer-size" to 65536
>> > [fujitsu] sane_get_devices: looking for 'scsi FUJITSU'
>> > [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x1041'
>> > [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x1042'
>> > [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x1078'
>> > [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x1095'
>> > [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x1096'
>> > [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x1097'
>> > [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x10ad'
>> > [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x10ae'
>> > [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x10af'
>> > [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x10cf'
>> > [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x10e0'
>> > [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x10e1'
>> > [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x10e2'
>> > [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x10e6'
>> > [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x10e7'
>> > [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x10f2'
>> > [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x10fe'
>> > [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x1135'
>> > [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x114a'
>> > [fujitsu] sane_get_devices: config option "buffer-size" (262144) is >
>> > 65536, warning!
>> > [fujitsu] sane_get_devices: setting "buffer-size" to 262144
>> > [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x114d'
>> > [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x114e'
>> > [fujitsu] sane_get_de

Re: [sane-devel] VIDAR Digitizer

[m. allan noah]

Make some scans with the scanner on windows, and capture the USB
packets with wireshark. Then put the wireshark logs up on the web for
others to look at, while you attempt to make sense of them too :)

allan

On Fri, Oct 13, 2017 at 12:46 PM, Mark Thurston  wrote:
> Dear developers
>
> I've got an obscure scanner which I really need to get working and I'm 
> prepared to get my hands dirty but I can't find much documentation.
>
> Any tips/pointers would be very helpful.
>
> It's a Vidar Diagnostic Pro digitizer -- used in radiology to scan X-rays 
> from old radiographic film. As you can imagine, it's quite a niche product.
>
> Output:
>
> # dmesg
> [  179.813929] usb 1-2: USB disconnect, device number 6
> [  181.783329] usb 1-2: new high-speed USB device number 7 using xhci_hcd
> [  181.933595] usb 1-2: New USB device found, idVendor=0c58, idProduct=0100
> [  181.933599] usb 1-2: New USB device strings: Mfr=1, Product=2, 
> SerialNumber=3
> [  181.933602] usb 1-2: Product: VIDAR Film Digitizer
> [  181.933605] usb 1-2: Manufacturer: VIDAR
> [  181.933607] usb 1-2: SerialNumber: 30
>
> ~ # 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=0x0c58 [VIDAR], product=0x0100 [VIDAR Film 
> Digitizer]) at libusb:001:007
>   # 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.
>
> unfortunately it is not listed on # scanimage -L
>
> If I make any progress (with or without help), I would like to submit my work 
> back to the project. I have some experience in C and Python and am prepared 
> to learn as needed.
> The alternative is a very expensive proprietary closed source vendor solution 
> with unreliable support and a poor security update record.
>
> Best wishes
>
> Mark
>
>
>
>
>
> --
> 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



-- 
"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] Best way to stop scanimage?

[m. allan noah]

Just let it complete?

allan

On Thu, Sep 28, 2017 at 10:30 AM, Jeff Sadowski  wrote:
> Is there a good way to stop scanimage? Other signals to send to it that it
> may prefer?
>
> It seems sometimes if I stop it I need to reset the scanner.
>
>
> --
> 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



-- 
"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] Fujitsu scanner issues

[m. allan noah]

You've cut out a bit too much of the log for me to see what is going
on. Perhaps compress a full log and send it to me directly.

allan

On Wed, Sep 27, 2017 at 5:52 PM, Chris Ott  wrote:
>
>
> I wrote a scanning program that uses the Sane library eight or nine years
> ago, and have been using it happily, since then. A couple of weeks ago, it
> occurred to me the machines to which the scanners are connected hadn’t had
> their OSes upgraded in at least three years. Unfortunately, upgrading them
> broke my program, and I can’t figure out why.
>
>
>
> The scanners are Fujitsu fi-6770djs, with both document feeders and
> flatbeds. If we stick with the document feeders, everything is fine. If we
> scan on the flatbed, then switch back to the document feeder, sane_start
> returns SANE_STATUS_INVAL. Restarting the program resets everything and
> allows us to use the document feeder, again. Now, I know that when you use
> the document feeder, the page dimensions have to be specified with
> page-length/page-width, while the flatbed requires tl-x/tl-y/br-x/br-y, and
> my program accounts for that.
>
>
>
> I tried moving some stuff around so all the options are set right before
> sane_start is called (rather than immediately after the user sets them), but
> that didn’t help.
>
>
>
> I tried previous versions of the Sane library, from 1.0.22 to 1.0.27; didn’t
> help.
>
>
>
> Here’s the debug output:
>
>
>
> [sanei_debug] Setting debug level of dll to 255.
>
> [dll] sane_init: SANE dll backend version 1.0.13 from sane-backends
> 1.0.27git
>
> [dll] sane_init/read_dlld: attempting to open directory `./dll.d'
>
> [dll] sane_init/read_dlld: attempting to open directory
> `/usr/local/etc/sane.d/dll.d'
>
> [dll] sane_init/read_dlld: using config directory
> `/usr/local/etc/sane.d/dll.d'
>
> [dll] sane_init/read_dlld: done.
>
> [dll] sane_init/read_config: reading dll.conf
>
> [dll] add_backend: adding backend `net'
>
> ...
>
> [dll] add_backend: adding backend `xerox_mfp'
>
> [dll] sane_open: trying to open `fujitsu:fi-6770dj:1215'
>
> [dll] load: searching backend `fujitsu' in
> `/usr/local/lib:/usr/local/lib/sane'
>
> [dll] load: trying to load `/usr/local/lib/libsane-fujitsu.so.1'
>
> [dll] load: couldn't open `/usr/local/lib/libsane-fujitsu.so.1' (No such
> file or directory)
>
> [dll] load: trying to load `/usr/local/lib/sane/libsane-fujitsu.so.1'
>
> [dll] load: dlopen()ing `/usr/local/lib/sane/libsane-fujitsu.so.1'
>
> [dll] init: initializing backend `fujitsu'
>
> [sanei_debug] Setting debug level of fujitsu to 255.
>
> [fujitsu] sane_init: start
>
> [fujitsu] sane_init: fujitsu backend 1.0.133, from sane-backends 1.0.27git
>
> [fujitsu] sane_init: finish
>
> [dll] init: backend `fujitsu' is version 1.0.133
>
> [fujitsu] sane_open: start
>
> [fujitsu] sane_open: no scanners currently attached, attaching
>
> [fujitsu] sane_get_devices: start
>
> [fujitsu] sane_get_devices: reading config file fujitsu.conf
>
> [fujitsu] sane_get_devices: setting "buffer-size" to 65536
>
> [fujitsu] sane_get_devices: looking for 'scsi FUJITSU'
>
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x1041'
>
> ...
>
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x114a'
>
> [fujitsu] sane_get_devices: config option "buffer-size" (262144) is > 65536,
> warning!
>
> [fujitsu] sane_get_devices: setting "buffer-size" to 262144
>
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x114d'
>
> ...
>
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x1174'
>
> [fujitsu] attach_one: start
>
> [fujitsu] attach_one: looking for 'libusb:002:002'
>
> [fujitsu] connect_fd: start
>
> [fujitsu] connect_fd: opening USB device
>
> [fujitsu] wait_scanner: start
>
> [fujitsu] do_usb_cmd: start
>
> ...
>
> [fujitsu] do_usb_cmd: finish
>
> [fujitsu] init_inquire: Found FUJITSU scanner fi-6770dj version 03 at
> libusb:002:002
>
> ...
>
> [fujitsu] rs sub call >>
>
> [fujitsu] do_usb_cmd: start
>
> [fujitsu] cmd: writing 31 bytes, timeout 3
>
> [fujitsu] cmd: >>
>
> [fujitsu] 000: 43 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> C...
>
> [fujitsu] 010: 00 00 00 03 00 00 00 12 00 00 00 00 00 00 00
> ...
>
> [fujitsu] cmd: wrote 31 bytes, retVal 0
>
> [fujitsu] in: reading 18 bytes, timeout 3
>
> [fujitsu] in: retVal 0
>
> [fujitsu] in: read 18 bytes
>
> [fujitsu] in: <<
>
> [fujitsu] 000: f0 00 45 00 00 00 00 0a 00 00 00 00 26 00 00 80
> ..E.&...
>
> [fujitsu] 010: 00 3e   .>
>
> [fujitsu] stat: reading 13 bytes, timeout 3
>
> [fujitsu] stat: <<
>
> [fujitsu] 000: 53 00 00 00 00 00 00 00 00 00 00 00 00  S
>
> [fujitsu] stat: read 13 bytes, retVal 0
>
> [fujitsu] do_usb_cmd: finish
>
> [fujitsu] rs sub call <<
>
> [fujitsu] sense_handler: start
>
> [fujitsu] Sense=0x5, ASC=0x26, ASCQ=00, EOM=1, ILI=0, info=
>
> [fujitsu] Illegal request: invalid field in parm list
>
> [fujitsu] Offending byte is 0x3e
>
> 

Re: [sane-devel] [PATCH 3/3] saned: reorganize flags, remove run_mode SANED_RUN_DEBUG

[m. allan noah]

Feel free to update the NEWS file, I'll incorporate your changes when
we ship 1.0.28

allan

On Sun, Sep 10, 2017 at 6:55 PM, Luiz Angelo Daros de Luca
 wrote:
> Hi Olaf,
>
>> Apologies for the late follow-up.  Shame on me for pinging you on the
>> bug report for no follow-up for a long time and then ignoring it when
>> you promptly send some.  :-(
>>
>
> No apologies needed. We know how it works.
>
> I was just waiting for your reply. My changes were already at github (and
> just rebased):
> https://github.com/luizluca/sane-backends/tree/reorganize-saned-args
>
>>
>> >> If there is no clear use case, perhaps saned should not provide them.
>> >> In that case, I'd remove:
>> >>  - -D and make running in the background the default because saned is
>> >>normally meant to run as a daemon
>> >
>> > I beg to disagree. It's not true for (x)inet, systemd nor procd. They do
>> > expect process in foreground. Only running saned standalone might need
>> > it
>> > to go background. Also, I think that changing the default behavior is
>> > even
>> > more traumatic than changing any behavior of options.
>>
>> Rethinking this, I guess you're right.  It's not much effort to manually
>> background a daemon, simply add an `&` at the end of the command-line.
>
>
> An `&` is not enough as there are some extra logic when going backgroud.
> `-D` do just that.
>
>> > Something for the Release Notes as Changelog is built from git log. Is
>> > there any place to save relevant changes for the next release?
>>
>> Eh, I guess the NEWS file would be as good a place as any.  Something
>> like
>>
>>   New with the development version, not yet released:
>>
>> @Allan> Does that look okay?
>>
>
> I'll just wait for the "NEWS" answered you asked @Allan in order to update
> only that and send patches to ML.
>
>>> You mention something about creating a PID file for the -u option.  That
>>
>> >> made me think a -p option to specify where you want that file might be
>> >> a
>> >> nice addition.  The current location, /var/run/saned.pid, is
>> >> hard-coded.
>> >> It's not a bad location but one may want to change it.
>> >
>> > I'll take a look. Normally PID file location is something for a
>> > configuration file.
>> > Sometimes init would like to take care of the PID file life cycle.
>> > Besides
>> > being hard-coded, if a previous PID file exists, saned should do some
>> > checks, and abort on failure. Today, if someone manage to run two
>> > instances
>> > of a stand-alone saned, the last one would simply overwrite its own PID
>> > inside the PID file. Also it should replace PID file instead of simply
>> > rewriting it. At least it would avoid different code paths (and
>> > permission
>> > requirements) whether a file at PID file exists or not.
>>
>> Looks like any user with write access to the directory holding the PID
>> file can clobber it because
>>
>>   pidfile = fopen (SANED_PID_FILE, "w");
>>
>> doesn't pass O_EXCL to the underlying open().
>>
>> On my devuan box, /var/run is a symlink to /run which has 755 perms and
>> is owned by root.  Digging further, /run is actually a mount point for a
>> tmpfs.  But anyway, not all systems are created equally.
>
>
> I'll leave PID_FILE as is for now.
>
>>
>> >> Oh, about the code changes, there are a few places in the manual page
>> >> I'd change to improve the English but I can do that for you.  There is
>> >> one mistake though, you document a -B option (as if it were -D).
>> >
>> > Yeah, english skill aren't really my "expertise". :-) I do know my
>> > limitations. Feel free to point me or correct them directly.
>>
>> I'll correct them directly (if there are any ;-).  It's less overhead
>> for both of us.
>
>
> OK for me.
>
>>
>> PS: I'll be travelling a bit in the next two weeks so will probably be
>> late again in following up.
>
>
> Nobody is at a hurry.
>
> Regards,
>
>>
>> --
>> Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
>>  GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
>>  Support Free Softwarehttps://my.fsf.org/donate
>>  Join the Free Software Foundation  https://my.fsf.org/join
>
> --
>
> Luiz Angelo Daros de Luca
> luizl...@gmail.com



-- 
"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] Sane_debug not available and front buttons for i1220 not shown in scanimage -A

[m. allan noah]

You would need the source code to kodak's backend to do that. I don't
think they make that available.

allan

On Wed, Sep 6, 2017 at 6:03 AM, fm8758ye <fm875...@126.com> wrote:
> Thank you, and I have contacted Kodak last month but have received no
> response from them. In the likely case my request is ignored, it is possible
> for me to sniff packets on windows or linux and add support to the backend
> myself (I will look for a driver programmer for help)?
>
> Fan
>
>
>
> 在2017年08月22 21时02分, "m. allan noah"<kitno...@gmail.com>写道:
>
>
> The .conf file is not the backend, it is just configuration. The real
> code is a compiled library, usually installed somewhere in /usr/lib...
>
> The sane standard does not require that backends expose button options
> to the frontend. So, the kvs_i1200 backend can be sane compliant, but
> not support scanbd. You will need to get kodak to modify the backend
> to add options which expose buttons.
>
> This is one of the biggest dangers of closed-source software. Only a
> small number of people at one company can help you. And, their
> motivation to do so is questionable since it likely won't add
> significantly to their sales.
>
> allan
>
> On Mon, Aug 21, 2017 at 10:48 PM, fm8758ye <fm875...@126.com> wrote:
>> Dear Allan,
>>
>> Thank you for the input, do you mean the file kds_i1200.conf has to
>> provide
>> button support? I looked at the other conf files under sane.d and they all
>> look alike without any mentions of buttons. In the case that I have to
>> contact kodak, what should I ask them for?
>>
>> Fan
>>
>>
>>
>> 在2017年08月18 20时24分, "m. allan noah"<kitno...@gmail.com>写道:
>>
>>
>> kds_i1200 would have to provide button support. I suggest you contact
>> kodak.
>>
>>
>> allan
>>
>> On Fri, Aug 18, 2017 at 12:14 AM, fm8758ye <fm875...@126.com> wrote:
>>> I am trying to implement scanbd with the scanner as a scan station.
>>> However,
>>> I got stopped at the first step as scanimage -A only shows scan options
>>> (such as mode and profiles) and does not show any sensor or button.
>>> Holding
>>> down the front buttons and doing scanimage -A shows no value different.
>>> I
>>> have looked at previous mail lists and saw that sane_debug_? shows more
>>> options for scanner. However, the command is not available.
>>>
>>> Q: What do I have to do to get sane_debug_? command? What do I enter
>>> after
>>> debug_?
>>>
>>> Anyways, I went on installing scanbd following the readme and scanbd is
>>> able
>>> to poll the scanner but not detecting any button press, as expected.
>>> Scanbd
>>> -d7 -f shows around 20 options and none of them are related to a button
>>> press. With the default scanbd.conf, it kept checking for the change of
>>> [preview] value, which does not react to button press.
>>>
>>> Q: Am I out of luck as the backend does not support buttons?
>>>
>>> I have tried to capture usb traffic using wireshark but no button presses
>>> are recorded.
>>>
>>> Q: Does capturing a scan packet using scan GUI and analysing it help?
>>>
>>> Thank you in advance.
>>>
>>> Ubuntu 14.04 fresh install
>>> Sane 1.0.0.23 does not provide scanner backend for this model so external
>>> (official) driver is used instead (kds_i1200).
>>> sudo sane-find-scanner, scanimage -L and all other scanimage commands
>>> works
>>> fine
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> 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
>>
>>
>>
>> --
>> "well, I stand up next to a mountain- and I chop it down with the edge
>> of my hand"
>>
>>
>>
>>
>
>
>
> --
> "well, I stand up next to a mountain- and I chop it down with the edge
> of my hand"
>
>
>
>



-- 
"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] Sane_debug not available and front buttons for i1220 not shown in scanimage -A

[m. allan noah]

The .conf file is not the backend, it is just configuration. The real
code is a compiled library, usually installed somewhere in /usr/lib...

The sane standard does not require that backends expose button options
to the frontend. So, the kvs_i1200 backend can be sane compliant, but
not support scanbd. You will need to get kodak to modify the backend
to add options which expose buttons.

This is one of the biggest dangers of closed-source software. Only a
small number of people at one company can help you. And, their
motivation to do so is questionable since it likely won't add
significantly to their sales.

allan

On Mon, Aug 21, 2017 at 10:48 PM, fm8758ye <fm875...@126.com> wrote:
> Dear Allan,
>
> Thank you for the input, do you mean the file kds_i1200.conf has to provide
> button support? I looked at the other conf files under sane.d and they all
> look alike without any mentions of buttons. In the case that I have to
> contact kodak, what should I ask them for?
>
> Fan
>
>
>
> 在2017年08月18 20时24分, "m. allan noah"<kitno...@gmail.com>写道:
>
>
> kds_i1200 would have to provide button support. I suggest you contact kodak.
>
>
> allan
>
> On Fri, Aug 18, 2017 at 12:14 AM, fm8758ye <fm875...@126.com> wrote:
>> I am trying to implement scanbd with the scanner as a scan station.
>> However,
>> I got stopped at the first step as scanimage -A only shows scan options
>> (such as mode and profiles) and does not show any sensor or button.
>> Holding
>> down the front buttons and doing scanimage -A shows no value different.  I
>> have looked at previous mail lists and saw that sane_debug_? shows more
>> options for scanner. However, the command is not available.
>>
>> Q: What do I have to do to get sane_debug_? command? What do I enter after
>> debug_?
>>
>> Anyways, I went on installing scanbd following the readme and scanbd is
>> able
>> to poll the scanner but not detecting any button press, as expected.
>> Scanbd
>> -d7 -f shows around 20 options and none of them are related to a button
>> press. With the default scanbd.conf, it kept checking for the change of
>> [preview] value, which does not react to button press.
>>
>> Q: Am I out of luck as the backend does not support buttons?
>>
>> I have tried to capture usb traffic using wireshark but no button presses
>> are recorded.
>>
>> Q: Does capturing a scan packet using scan GUI and analysing it help?
>>
>> Thank you in advance.
>>
>> Ubuntu 14.04 fresh install
>> Sane 1.0.0.23 does not provide scanner backend for this model so external
>> (official) driver is used instead (kds_i1200).
>> sudo sane-find-scanner, scanimage -L and all other scanimage commands
>> works
>> fine
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>> 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
>
>
>
> --
> "well, I stand up next to a mountain- and I chop it down with the edge
> of my hand"
>
>
>
>



-- 
"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] Sane_debug not available and front buttons for i1220 not shown in scanimage -A

[m. allan noah]

kds_i1200 would have to provide button support. I suggest you contact kodak.


allan

On Fri, Aug 18, 2017 at 12:14 AM, fm8758ye  wrote:
> I am trying to implement scanbd with the scanner as a scan station. However,
> I got stopped at the first step as scanimage -A only shows scan options
> (such as mode and profiles) and does not show any sensor or button. Holding
> down the front buttons and doing scanimage -A shows no value different.  I
> have looked at previous mail lists and saw that sane_debug_? shows more
> options for scanner. However, the command is not available.
>
> Q: What do I have to do to get sane_debug_? command? What do I enter after
> debug_?
>
> Anyways, I went on installing scanbd following the readme and scanbd is able
> to poll the scanner but not detecting any button press, as expected. Scanbd
> -d7 -f shows around 20 options and none of them are related to a button
> press. With the default scanbd.conf, it kept checking for the change of
> [preview] value, which does not react to button press.
>
> Q: Am I out of luck as the backend does not support buttons?
>
> I have tried to capture usb traffic using wireshark but no button presses
> are recorded.
>
> Q: Does capturing a scan packet using scan GUI and analysing it help?
>
> Thank you in advance.
>
> Ubuntu 14.04 fresh install
> Sane 1.0.0.23 does not provide scanner backend for this model so external
> (official) driver is used instead (kds_i1200).
> sudo sane-find-scanner, scanimage -L and all other scanimage commands works
> fine
>
>
>
>
>
>
>
>
> --
> 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



-- 
"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] Olaf

[m. allan noah]

Thanks for the heads up, Curtis. I've taken care of this.

allan

On Fri, Aug 11, 2017 at 11:59 AM, Curtis Graham
 wrote:
> Hi Olaf,
>
> This was sent to me only it looks like. Could you look into this please.
>
> Thank You,
> Curtis
>
> -- Forwarded message -
> From: Doug Robinson 
>
>
> Hello,
>
> Please remove Doug off your email list as he has passed away.
>
> His widow
>
>
> --
> 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



-- 
"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] Scanning With Nikon Coolscan LS40 / IVED

[m. allan noah]

You might try sane-backends 1.0.27, which includes the following
statement in its release notes:

Note 3: The Linux USB3 workaround which was added in version 1.0.25 is
now disabled by default. If you have difficulty using a scanner which
previously worked, or intermittent scanner availability, try setting
the new environment variable SANE_USB_WORKAROUND=1 before starting
your frontend.

On Fri, Jul 28, 2017 at 10:02 PM, Leon Hauck  wrote:
> TLDR: are there any known issues using a Nikon Coolscan IV ED with
> libusb 0.1.12-30 and kernel 4.9.0?
>
> ---
>
> I'm trying to get an Coolscan IV ED (LS40) to work with Debian Stretch
> (current stable release).
>
> scanimage -L
>
> properly identifies the scanner, however
>
> scanimage > testme.pnm
>
> hangs and eventually errors out due to an i/o error.
>
> I connected this scanner to a laptop running the same software with the same
> results.
>
> I connected the scanner to an older laptop running Debian Jessie (previous
> stable release), and it works fine, and I can also pass along additional
> command line arguments for white balance, auto-focus, etc.
>
> I'm guessing something may have changed in libusb and/or the kernel, which
> is preventing communication with this older USB1.1 unit.
>
> Are there any known issues with this setup?
>
> --
> 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



-- 
"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] [janitorial] leading whitespace: spaces XOR tabs

[m. allan noah]

Olaf, you make a pretty convincing case, especially as regards to your
wider than average exposure to the codebase. If you feel strongly
about this, and are willing to do the work (which I think will be
harder than you expect), then I will remove my objections.

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] [janitorial] leading whitespace: spaces XOR tabs

[m. allan noah]

1. I routinely use git blame to find out when I changed some line of
code. A massive whitespace commit would wreck that. Yes, there are
other ways to get that info after such a cleanup, but I'm lazy :)

2. I've read a great deal of other people's code over the years, and I
am generally stumped by their logic and lack of comments. Whitespace
is rarely a concern, even when they used a weird layout.

3. There are patches floating around in private repos that may not
apply cleanly after such a change.

Given those, I'm inclined to leave maintained backends untouched. For
unmaintained backends, it certainly makes sense to do such
reformatting when a bugfix is done. Doing it beforehand is
questionable, I don't feel strongly either way. I suppose cleaning up
the unmaintained backends makes it slightly easier for a new
maintainer to step into the code.

allan

On Wed, Jul 12, 2017 at 9:35 AM, Gerhard Jäger  wrote:
> Hi Olaf,
>
> On 12.07.2017 at 14:33 Olaf Meeuwissen wrote:
>>
>> Hi all,
>>
>> I just committed the last compiler warning fixes and made the Debian 9
>> builds "AWARE".  Now any compiler warnings on all 4 Debian builds will
>> bomb the build in question and hence prevent the creation of a new
>> snapshot tarball.
>>
>> I mentioned[1] that the plustek-pp backend's indenting defied me but
>> after some staring at the code I realized it was using a four spaces to
>> the tab convention.  Convincing my editor to do the same made it a lot
>> easier to understand the intended behaviour but fixing the "mess" was
>> still a very delicate affair.  I had to change the mixed use of spaces
>> and tabs used to indent to *exactly* match in order to silence compiler
>> warnings.
>>
>>   [1]
>> https://lists.alioth.debian.org/pipermail/sane-devel/2017-June/035445.html
>
>
> [...]
>
> I obviously ignored you - sorry for that. And yes, I did follow at these old
> days my own rules, not using tabs, but 4 spaces - in an inconsistent way.
> Sorry - 'twas a long time ago ;)
>
>> This whole exercise has made me look at the whole code base in a little
>> more detail and, quite frankly, the use of leading whitespace is a total
>> and utter mess.  Some places are better of than others but on the whole
>> it's pretty pathetic.
>>
>> # Just make your editor visually distinguish spaces and tabs and you'll
>> # see.  I used Emacs' whitespace-mode (in its default configuration) and
>> # it "lit up the place" in a variety of colours.
>>
>> So here's a few "rules" I'd like to apply in order to address this.
>> Each file
>
> [...]
>>
>> # Personally, I would much prefer to uses spaces everywhere the file
>> # format permits (with a minor execption for files used by make, see
>> # above) over the board.
>> # You may find the following blog post of interest ;-)
>> #
>> #
>> https://stackoverflow.blog/2017/06/15/developers-use-spaces-make-money-use-tabs/
>>
>> If anyone objects, I'm open to suggestions, including "Why bother? Just
>> use spaces!" ;-)
>>
>> If I hear nothing, the tools/style-check.sh script will be modified to
>> implement these rules and can then be use to check for any "violations"
>> and (recursively) fix them.
>
>
> Are you sure you want to rework the whole code base? Is it a good idea?
> Well maybe for unmaintained backends, but what about the others? In fact
> I have here some long pending patch (64 bit awareness) that most probably
> no longer apply.
>
> Just my two cents,
>  Gerhard
>
> BTE: Thanks for caring anyhow.
>
>
> --
> 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



-- 
"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] Scan quality enhancements/processing (vs Windows with Fujitsu ScanSnap S1500)

[m. allan noah]

On Sun, Jul 9, 2017 at 2:54 PM, Matt Garman <matthew.gar...@gmail.com> wrote:
> Hi Allan,
>
> Thank you for taking the time to provide some feedback and look into this!
>
> More commentary inline below:
>
> On Fri, Jul 7, 2017 at 12:06 PM, m. allan noah <kitno...@gmail.com> wrote:
>> In general, if you are using swdeskew, it is probably better to scan
>> at full width, and use the swcrop option too. Also, some fujitsu
>> machines support the overscan option, which will cause the scanner to
>> output some extra background rows before the paper is ingested. This
>> can significantly improve the swdeskew performance. The S1500 does not
>> have a black background option, but the larger scanners do, and this
>> will also help.
>>
>> If you have a document that consistently reproduces poor deskewing,
>> even with those additional options, I'd like to see a .pnm file of the
>> scan with and without swdeskew enabled.
>
> Most of my documents have far too much personal info on them to
> publish publicly... but we'll try to make due with some generic
> documents.
>
> Here's a link to the output of "scanimage -h", just for reference for
> what default settings are.  I included the PDF as scanned under
> Windows, and the PNM files from a Linux scan, both with and without
> the --swdeskew option enabled.  (There are two files for each of the
> Linux/PNM, because it was a duplex scan, i.e. front and back.  Windows
> scan was also duplex, but the software concatenates all scans into one
> file.)
>
> http://raw-sewage.net/images/linux_scansnap_s1500/
>
> At any rate - this one doesn't demonstrate skew very well.  But it
> does sort of answer my previous question: you can see that when I used
> the swdeskew option, it actually cut off part of the document.  I
> previously assumed the scanner was mis-judging the actual scan
> area/document size, but from this simple experiment, it appears the
> swdeskew can get confused and cutoff parts of the document.

Well, I got over my fear of clicking on 'raw sewage' and looked at a
couple of your images. I agree that this is a bug, the swdeskew should
not crop the top of the image in this case. I wonder- is that purple
stripe near the left margin actually on the page, or does your scanner
have a problem?

> Under Linux, you can see I scanned at 300dpi.  I have it set to "auto"
> under Windows, but I'm quite sure it scanned at 300dpi or less.  If I
> specify anything over 300dpi (under either platform) the scanning is
> noticeably slower.  Not a precision measurement I know, but it's
> something.

I expect the sane driver to be equal or slightly faster than the
windows driver. If you find otherwise, let me know.

>
>> All the options you list here are values which we send to the
>> hardware. Frankly, I have little documentation about what they do, but
>> it is certainly possible that some of these only have effect in binary
>> mode, and they may not even work on the S1500. I'll see if I can track
>> that down, and disable them in cases where they cannot be used.
>> ( ... )
>> I'm willing to guess that much of what you are seeing is the windows
>> software making a larger, potentially higher resolution or color mode
>> scan, and then cleaning it up in software.
>
> I'm assuming similar open source tools exist for Linux; i.e.
> scanimage/sane doesn't have to do all the work... I just want to get a
> good, comprehensive scan out of sane.  Then I can script a pipeline of
> post-processing tools.

There are some tools like unpaper and leptonica which can do some of
these things. Perhaps they will be useful to you. Even still, I would
like to fix bugs in sane if I can. I'll take a crack at it using your
image.

> I'll continue to look for non-personal documents to present more
> examples.  I created a Windows virtual machine so now I can quickly
> test the two without having to turn on my old PC and switch the
> keyboard/video/mouse cables over!
>
> Thanks again, let me know if I can provide any more info.
>
> -Matt

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] Scan quality enhancements/processing (vs Windows with Fujitsu ScanSnap S1500)

[m. allan noah]

Matt-

I wrote both the sane-fujitsu backend, and the sanei_magic library
that it uses to provide the deskew/crop, etc functions. I'll try to
answer your questions as best I can. BTW, sorry I did not reply
sooner- I have been traveling, and wanted to write something a bit
longer than I could stand on my cell phone :)

Further comments inline:

On Mon, Jul 3, 2017 at 4:02 PM, Matt Garman  wrote:
> TL;DR: for those of you who have migrated your document scanning
> workflow from Windows to a Sane platform (e.g. Linux), what
> settings/tools have you found to maintain or improve quality of
> scanned documents (relative to Windows)?
>
> Long version:
>
> I have a Fujitsu ScanScan s1500 document scanner, and sane-1.0.27
> running on Arch Linux.  So far it seems to just work.  I've had this
> scanner for nearly a decade, and used it exclusively under Windows
> until now (trying to move to a pure Linux desktop).
>
> So while I can scan documents just fine, the results to me aren't as
> good as what I get under Windows using the proprietary ScanSnap
> software.  Specifically, they are too light/too dark, text not crisp
> enough, straight lines not straight, colors a bit off, etc.
>
> One example: de-skewing.  All the years I've had this scanner, I
> didn't even realize this was a thing until now.  I can use scanimage's
> software de-skewing (--swdeskew=yes), and it seems to *mostly* work,
> but pages are often still somewhat skewed.  Excepting for
> wacky/unusual documents, I don't recall ever seeing any skew under
> Windows.

That is not scanimage providing the deskew, but the fujitsu backend
(driver) itself, using the sanei_magic library, and your host system's
CPU. The deskewing algorithm uses a simplified Hough transform, which
attempts to detect the edges of the paper instead of the print on it.
This code works better if you expand the dimensions of the scan to
grab some of the background. If you attempt to crop the image too
small using the page_width and page_height or x/y params, it will
likely fail to deskew, or pick the wrong feature to align, which will
make things worse.

In general, if you are using swdeskew, it is probably better to scan
at full width, and use the swcrop option too. Also, some fujitsu
machines support the overscan option, which will cause the scanner to
output some extra background rows before the paper is ingested. This
can significantly improve the swdeskew performance. The S1500 does not
have a black background option, but the larger scanners do, and this
will also help.

If you have a document that consistently reproduces poor deskewing,
even with those additional options, I'd like to see a .pnm file of the
scan with and without swdeskew enabled.

>
> Despeckling (--swdespeck=n) does seem to be a major step in the right 
> direction.

Yes- particularly if you are scanning in binary (line art) mode, small
amounts of noise can be distracting.

>
> I'm also playing with all the enhancement options.  E.g.,
> --brightness, --contrast, --emphasis, etc.  Brightness and contrast
> are fairly intuitive, but I don't really understand what the other
> options actually mean, or what I should expect from them.  I've been
> taking the trial-and-error approach, but e.g. --variance doesn't seem
> to do anything.  And I'm not sure how the options interact with each
> other, so trial-and-error could take forever.

All the options you list here are values which we send to the
hardware. Frankly, I have little documentation about what they do, but
it is certainly possible that some of these only have effect in binary
mode, and they may not even work on the S1500. I'll see if I can track
that down, and disable them in cases where they cannot be used.

> Having said all that, my one test document is maybe 90% as "good" as
> the same scanned on Windows.  Probably good enough to live with, but:
>
> (1) This seems to be a very popular scanner - has anyone been able to
> back out the settings the proprietary ScanSnap software uses?
> - and -
> (2) I wonder if the Windows ScanSnap software settings are static or
> dynamic?  E.g., is there some kind of pre-processing algorithm applied
> to guess at the best enhancement settings?

I'm willing to guess that much of what you are seeing is the windows
software making a larger, potentially higher resolution or color mode
scan, and then cleaning it up in software.

I think we will need side-by-side example images from windows and
sane, along with the list of options for each to diagnose further.

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] ScanSnap S1100 on Linux Mint

[m. allan noah]

You may need to re-install the firmware file now.

allan

On Fri, Jun 23, 2017 at 9:12 PM, Crusader <crusader...@gmail.com> wrote:
> My post upgrade update can be found here.
>
> On Fri, Jun 23, 2017 at 7:37 PM, Crusader <crusader...@gmail.com> wrote:
>>
>> Continued support is greatly appreciated.
>>
>> I installed the update as suggested above. After that, I ran the following
>> programs with the results shown:
>>
>> From the Xsane Image scanning program, I continue to get the "Failed to
>> start scanner: Out of memory" message.
>>
>> From the Simple Scan program, I got the message, "Failed to scan Unable to
>> start scan."
>>
>> From the gscan2pdf v1.2.3, I got the message, "Out of Memory."
>>
>>
>> Since I was getting the same errors, I ran the "SANE_DEBUG_EPJITSU=5
>> scanimage -L" command and realized the sane-backends version had not
>> upgraded (still showed "sane-backends 1.0.23"). Since I wasn't sure about
>> how to "install" the new version, I checked Rolf Bensch website which had an
>> installation link, which brought me to the "sudo apt-get dist-upgrade"
>> command - which I (foolishly?) ran. Seemingly, this is upgrading the whole
>> distro. The "upgrade" continues as I write (has been running for quite a
>> while). I am not sure what I did. When the upgrade completes (and I come out
>> alive), I will run the version command to see if the sane-backends version
>> also updated (among the seemingly million things). I said "No" to many
>> installation options (have no idea what they meant), but did say "Yes" to
>> installing the new sane-backends version.
>>
>> I will update you on the outcome of the sane-backends version; however,
>> now the question is: what am I updating, do I need it, and is this going to
>> harm my laptop (and me)?
>>
>> On Fri, Jun 23, 2017 at 7:17 AM, abel deuring <adeur...@gmx.net> wrote:
>>>
>>> Am 23.06.2017 um 13:41 schrieb Crusader:
>>> > Thank you for identifying the problem, Allan.  Your finding brings me
>>> > very close to resolving the issue.
>>> >
>>> > My distro (Linux Mint 17.3 Cinnamon 64 bit, Cinnamon Version 2.8.8)
>>> > does
>>> > not have an update to sane-backends version 1.0.27, and as you pointed
>>> > out, compiling is complicated (I tried it).  I am open to suggestions.
>>>
>>> Since Mint is based on Ubuntu, Rolf Bensch's PPA can help you:
>>>
>>> https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-release
>>>
>>> It provides the most recent Sane release. Just follow the instructions
>>> "Adding this PPA to your system" from that page and then run
>>>
>>>   sudo apt-get upgrade
>>>
>>> Abel
>>>
>>> >
>>> > In the interim, I will take this issue back to the Linux Mint forum and
>>> > see if I can get further help there.
>>> >
>>> > Your support is greatly appreciated!
>>> >
>>> > On Thu, Jun 22, 2017 at 8:02 PM, m. allan noah <kitno...@gmail.com
>>> > <mailto:kitno...@gmail.com>> wrote:
>>> >
>>> > On Thu, Jun 22, 2017 at 7:46 PM, Crusader <crusader...@gmail.com
>>> > <mailto:crusader...@gmail.com>> wrote:
>>> > >
>>> > > 3. run 'SANE_DEBUG_EPJITSU=5 scanimage -L' and send the output
>>> > text to
>>> > > this list- I want to see what version of sane you are running.
>>> > > a@a-UL80VT ~ $ SANE_DEBUG_EPJITSU=5 scanimage -L
>>> > > [sanei_debug] Setting debug level of epjitsu to 5.
>>> > > [epjitsu] sane_init: epjitsu backend 1.0.20, from sane-backends
>>> > 1.0.23
>>> > > [epjitsu] load_fw: firmware already loaded?
>>> > > device `epjitsu:libusb:002:004' is a FUJITSU ScanSnap S1100
>>> > scanner
>>> >
>>> > Well, there is your problem, you are running an ancient version of
>>> > sane-backends, which does not support this scanner fully. You will
>>> > need to upgrade to something more recent. 1.0.25 was the first
>>> > version
>>> > that supported this scanner, but 1.0.27 would be better, as it
>>> > contains some fixes. You should see if your distro has some kind of
>>> > updated package you could load. If not, you will have to compile
>>> > from
>>> > source, which is more complicated.
>>> >
>>> > 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



-- 
"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] ScanSnap S1100 on Linux Mint

[m. allan noah]

On Thu, Jun 22, 2017 at 7:46 PM, Crusader  wrote:
>
> 3. run 'SANE_DEBUG_EPJITSU=5 scanimage -L' and send the output text to
> this list- I want to see what version of sane you are running.
> a@a-UL80VT ~ $ SANE_DEBUG_EPJITSU=5 scanimage -L
> [sanei_debug] Setting debug level of epjitsu to 5.
> [epjitsu] sane_init: epjitsu backend 1.0.20, from sane-backends 1.0.23
> [epjitsu] load_fw: firmware already loaded?
> device `epjitsu:libusb:002:004' is a FUJITSU ScanSnap S1100 scanner

Well, there is your problem, you are running an ancient version of
sane-backends, which does not support this scanner fully. You will
need to upgrade to something more recent. 1.0.25 was the first version
that supported this scanner, but 1.0.27 would be better, as it
contains some fixes. You should see if your distro has some kind of
updated package you could load. If not, you will have to compile from
source, which is more complicated.

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] Add supporting of device to the existing backend

[m. allan noah]

The previous maintainer has left some documentation at:
https://github.com/stefdev49/syseneg . Perhaps that will help you?


allan

On Mon, Jun 19, 2017 at 10:43 AM, Дмитрий Шелонин
 wrote:
> Hello
>
> I want to add new device based on unsupported controller to the genesys 
> backend. How can I do this or where can I find any information about steps of 
> this?
>
> Thanks
> --
> 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



-- 
"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] Adding a scanner backend (genesys) does not work

[m. allan noah]

On Tue, Jun 13, 2017 at 10:29 AM, Chris Mailer  wrote:
> I´m currently trying to get a newer usb-scanner to work, which is,
> according the documentation, "to be added to genesys backend"
> (whatever that means).

It means your scanner is not supported, but the genesys backend is the
best place to add support. Unfortunately, just adding the ID to the
config file is not enough, code would also need to be written.
Unfortunately, the genesys backend is effectively unmaintained. So,
unless you are able to reverse engineer the protocol and add your own
support, you might want to get a different scanner.

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 404

[m. allan noah]

Fixed. Thank you for the report.

allan

On Thu, May 25, 2017 at 9:29 AM, Matthias Erich Popp  wrote:
> I can't find this Site http://sane-project.org/sane-backends-1.0.25.html
>
> with best regards from Dortmund Matthias Popp
> --
> 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



-- 
"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] Hiring a SANE developer for custom backend

[m. allan noah]

You are in the right place.

Your paste indicates that this is a GL848 or later chipset. It could
be supported by the genesys sane backend, which is basically
unmaintained currently. However, you might get lucky and be able to
entice the former maintainer/author to come out of retirement
. If not, he has left some documentation at:
https://github.com/stefdev49/syseneg . Hopefully that will enable
someone on this list to take you up on your offer. If it is similar
enough to an existing scanner, support may be simple.

allan

On Tue, May 23, 2017 at 10:29 AM, Brandon Anderson
 wrote:
> Hey Everyone,
>
> I hope this is the correct area to post, I am looking for estimates in
> cost for developing a SANE backend to support the Ambir ImageScan Pro
> 687ix Card and ID scanner. If developers are interested I can provide
> information about the scanner, and remote access to a machine with shell
> access to evaluate cost and time estimate. We will be able to ship the
> scanner to the developer if needed should the job be accepted. I am
> attaching the output of `sudo sane-find-scanner -v -v` let me know if
> you need anything else. I am also available on the #sane channel on
> freenode under the nick "Brando753" if you want to message me there.
>
> Sincerely,
>
> Brandon Anderson
>
> Output of sane-find-scanner https://pastebin.com/2SPGZL2s
>
> --
> 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



-- 
"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

[sane-devel] Sane-backends is open for development

[m. allan noah]

Sorry for the delay, real life got in the way. But, sane-backends repo
is now out of code freeze. Feel free to fix bugs, etc.

Note that the version is now 1.0.27git, based on earlier discussions
about making packaging easier.

Let me know if you see any problems related to the repo or the website.

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

[sane-devel] Sane-backends 1.0.27 has been released

[m. allan noah]

2017-05-22: SANE-Backends-1.0.27 (see Note 1) has been released:

* Significant enhancements to canon_dr, epjitsu, epsonds, fujitsu,
genesys, hp3500, pixma and xerox-mfp backends.
* Minor updates, bugfixes or scanners added in several backends.
* 30+ new scanner models supported.
* Made libusb-1.0 the default for USB support (see Note 2).
* Switched code from C90 to C99 (Thanks to Volker Diels-Grabsch).
* Updated Linux USB3 workaround (see Note 3).
* Documentation and translation updates.
* Bugfixes (Avahi, threading, USB, ICC/PNG/JPEG, etc).
* Reduced compiler warnings, improved code (see Note 4).

Note 1: There is no 1.0.26 release of sane-backends. That number was
skipped so that our development version numbers would more clearly be
an extension of the prior release. This should make packaging a little
easier for our downstream users.

Note 2: On all systems, the --enable-libusb* flags are now ignored.
Instead, the --with-usb and --without-usb flags now control support.
When neither is given, USB support will be enabled if possible and
disabled otherwise. If --with-usb is requested but not possible,
./configure will fail. There is no support to prefer libusb-0.1 over
libusb-1.0. When libusb-1.0 is not found, libusb-0.1 will be tried.

Note 3: The Linux USB3 workaround which was added in version 1.0.25 is
now disabled by default. If you have difficulty using a scanner which
previously worked, or intermittent scanner availability, try setting
the new environment variable SANE_USB_WORKAROUND=1 before starting
your frontend.

Note 4: A special thanks goes to Olaf Meeuwissen for picking up the
janitorial duties in sane-backends. He has found and fixed a large
number of long-standing bugs, curated our bug tracker, improved our
build scripts and docs, and provided user support. Thank you Olaf!

More information about sane, and links to download are available at
http://sane-project.org/

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] Updated dutch translation

[m. allan noah]

Got it, thanks!

allan

On Fri, May 19, 2017 at 2:34 PM, Martin Kho  wrote:
> Hi,
>
> May be a little late, but I hope not too late. In the attachment you'll find
> an update to the dutch translation. It completely replaces the current po-
> file. B.t.w. the source was taken from git d.d. May 17, 2017
>
> Hope someone can take care of my translation, thanks
>
> Martin Kho
> --
> 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



-- 
"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] Possible to rename network scanner?

[m. allan noah]

The fujitsu backend includes the serial number of the scanner in the
device name. The users would have to memorize that number. Anything
more would be a code change. The best place to make such a change
would probably be in saned itself, so that all backends could benefit.
Unfortunately, many backends use a dynamically generated device name,
so saned might see different device names after the host reboots. So,
the easiest place to solve this would likely be in the fujitsu backend
itself. We could potentially replace the serial number with a
user-specified device name. This requires more thought.

allan

On Thu, May 18, 2017 at 7:46 PM,   wrote:
> I have a clinic where there are about seven scanners networked with sane.d
> and xinetd. Right now when users open SimpleScan
> and look at the list of available network scanners, they see all seven named
> 'fujitsu-fl7160' in the list and have to memorize which order
> their scanner is in the list.
>
> Is there a method to assign a descriptive name to each scanner like 'lab
> department 1' ?
>
>
> Clients are using Ubuntu/SimpleScan.
>
> Thanks.
>
> --
> 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



-- 
"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] sane-backends release 1.0.26 schedule

[m. allan noah]

What is the nature of the bug fix? Is it going to cause scanners that
worked with the prior release to be broken with this one? How big is
the fix? How likely to cause regressions?

allan

On Fri, May 19, 2017 at 5:13 AM, Rolf Bensch <r...@bensch-online.de> wrote:
> Are we already in Code Freeze?
>
> I would like to commit a bug fix this weekend.
>
> Rolf
>
>
> Am 28.04.2017 um 14:04 schrieb m. allan noah:
>> Ok folks, it's time to get another sane-backends release out the door.
>>
>> Olaf has done a good job of cleaning up our contributors list and
>> curating the bug tracker. However, there are a handful of patches in
>> the bug tracker that could still be applied, once they are reviewed.
>> Also, quite a number of backends that are now unmaintained. So, this
>> is a good time to get involved with sane. If you benefit from this
>> project, and have some programming experience, we could use the help.
>>
>> Schedule:
>>
>> May 7: Feature freeze (only fix bugs and update docs after this date)
>> May 14: Code freeze (only update docs after this date)
>> May 21: Release
>>
>> Any questions or concerns, let me know.
>>
>> 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] Motor movement and then time-out with Canon LIDE120

[m. allan noah]

You are running an older version of sane-backends. Our development
snapshots are oddly named, but a recent one would be 1.0.26git. I
suspect your problem is fixed there. We have a release in a few days,
and it would be nice to verify. Perhaps you can upgrade in the
meantime? You might be able to use Rolf's PPA for this, per recent
posts on this list.

allan

On Tue, May 16, 2017 at 11:40 PM, willismon...@gmail.com
 wrote:
> I bought a Canon LIDE120 a few years ago and have been watching the
> development of the driver on the sane-devel list since then.  It seems to
> have quieted off recently, so I thought I'd give the scanner another shot in
> Linux.
>
> I'm running Ubuntu 17.04, here's the output of an attempt to scan:
>
> ➜  ~ scanimage -L
> device `genesys:libusb:003:006' is a Canon LiDE 120 flatbed scanner
> ➜  ~ scanimage --device 'genesys:libusb:003:006' --format=tiff > test.tiff
> scanimage: sane_start: Invalid argument
> ➜  ~ scanimage --version
> scanimage (sane-backends) 1.0.25git; backend version 1.0.25
>
> When the command to scan is sent, the motor makes a audible sound and then
> nothing happens and the command times-out.
>
> I know the LIDE120 is listed as supported on the website, and I seem to be
> running up to date drivers...
>
> Thanks,
> -Willis
>
> --
> 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



-- 
"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] Updating backend version info

[m. allan noah]

I have never bumped backend version numbers for backends with a
maintainer, I leave that to them.

Given how few places we show the backend version number, I would not
worry about fixing this for any patches you have applied from the bug
tracker.

allan

On Mon, May 15, 2017 at 8:39 AM, Olaf Meeuwissen
 wrote:
> Hi Allan,
>
> While going through the changes since RELEASE_1_0_25 I realized that I
> did not update each backend's version info.  I've been happily fixing
> compiler warning and touched just about every backend.  Some have had
> their version info modified for other reasons and are probably okay but
> should I go and update backend version info?
>
> # Not looking forward to this, to be honest.
>
> If so, what part of the version info?  The standard seems to suggest the
> minor version ought to be updated.
>
> Hope this helps,
> --
> Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
>  GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
>  Support Free Softwarehttps://my.fsf.org/donate
>  Join the Free Software Foundation  https://my.fsf.org/join



-- 
"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] Getting ready for sane-backends release

[m. allan noah]

On Sun, May 14, 2017 at 7:31 AM, Yuri Chornoivan  wrote:
> неділя, 14-тра-2017 20:11:03 Olaf Meeuwissen написано:
>> Hi Allan,
>>
>> I just pushed an update of all the autotools and gettext derived files.
>> Unless there are any other updates to any of these files, all you need
>> to do to update the version number is
>>
>>   sed -i 's/1\.0\.26git/1.0.26/g' configure.ac configure
>>
>> Apart from making your mind up about whether we should skip 1.0.26 and
>> jump to 1.0.27 ;-)
>>
>> Please run autoreconf on Debian GNU/Linux 8.8, but only if you really,
>> really have to.

What so now you get to dictate my OS? :)

>>
>> Hope this helps,
>
> Hi,
>
> Is there any schedule for pushing po-files updates?
>
> I have sent an updated version of uk.po to Allan and to this list but it has
> not been pushed to the repo yet. :'(
>
> Best regards,
> Yuri
>

Sorry Yuri, I've been traveling. I just committed and pushed your
work. Thank you for your efforts, and sorry for the delay.

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] Fix PPA build

[m. allan noah]

this sounds like a reasonable plan to me, though I wonder what effect
it will have on the currently installed git-based packages. They are
already 1.0.26+git, and they will remain so after this release
(though the  part will be of a different format).

allan

On Thu, May 11, 2017 at 7:36 AM, Olaf Meeuwissen
 wrote:
> Hi all,
>
> This is something that I've been wondering about for a while and with
> the release coming up I thought I'd vent my thoughts/preferences on the
> version numbering of sane-backends (and sane-frontends if we should ever
> get around to releasing a new version of that).
>
> Rolf Bensch writes:
>
>> Hi James,
>>
>> Am 08.05.2017 um 22:22 schrieb James Duvall:
>>> Rolf,
>>>
>>> Thanks for getting your ppa back up and running.  However, I am not able
>>> to install the libsane package using apt, even when I try to force the
>>> version.  I believe that your new version numbering with ~ is causing
>>> the problem.
>>>
>>> ver=1.0.26~ppa20170508-yakkety0; sudo apt-get install libsane=$ver
>>> libsane-common=$versane-utils=$ver
>
> On Debian-based distributions:
>
>   1.0.26~this < 1.0.26 < 1.0.26+that
>
> I don't recall the details for RPM-based distributions re ~ (note that
> Fedora[1] says it should not be used), but the + works the same, so:
>
>   1.0.26 < 1.0.26+that
>
>   [1] https://fedoraproject.org/wiki/Packaging:Versioning
>
> The problem with the way we currently do the versioning of sane-backends
> is that we bump the version to what we *think* will be the next version.
> This would work for Debian-based distribution packages if they use a ~
> suffix to our version.  For RPM-based distributions I don't know what
> works.  It also causes confusing bug reports and mails to the list where
> people talk about using an upcoming release.
>
> To fix that, can we agree to a version number for HEAD on master that
> refers to the last *released* version?  Something like this
>
>   1.0.26+git
>
> for anything *after* the 1.0.26 release.  This should work for all folks
> rolling binary packages and indicates very clearly that it's 1.0.26 plus
> a bunch of edits.
>
> Actually, we may also want to look into using the output of
>
>   git describe
>
> When I run this on my current checkout of master, I get
>
>   RELEASE_1_0_25-552-ge6711c3
>
> This is --g, so this
> should work fine as long as people are using master.  The number of
> commits since the tag will sort later commits in the right order.
>
> # We haven't used branches much so far, so this would be a reasonably
> # safe assumption.  Anyway, if you're using any other branch, I would
> # assume you know what you're doing ;-)
>
> If we also switch tags to use the version number as is, that would
> become
>
>   1.0.25-552-ge6711c3
>
> # Debian-based distributions may need to replace the - with something
> # else.  Using `sed 's/-/+/g'` or something similar should work.
>
> Summarizing, let's use
>
>   +git
>
> from the 1.0.26 release onwards and look into using the output from `git
> describe` to get an even better idea of what people are really running
> when compiling from git.
>
> How's that sound?
>
> Hope this helps,
> --
> Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
>  GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
>  Support Free Softwarehttps://my.fsf.org/donate
>  Join the Free Software Foundation  https://my.fsf.org/join



-- 
"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] sane-backends release 1.0.26 schedule

[m. allan noah]

Hmm, I think we should not rush this change. We can do another sane
release once we have something we all agree on, and have spent more
time testing.

allan

On Sat, May 6, 2017 at 2:13 PM, Louis Lagendijk <lo...@fazant.net> wrote:
> On Sat, 2017-05-06 at 15:55 +0200, Wilhelm wrote:
>> Am 06.05.2017 um 14:27 schrieb m. allan noah:
>> > On Sat, May 6, 2017 at 5:52 AM, Louis Lagendijk <lo...@fazant.net>
>> > wrote:
>> > > On Fri, 2017-04-28 at 08:04 -0400, m. allan noah wrote:
>> > > > Ok folks, it's time to get another sane-backends release out
>> > > > the
>> > > > door.
>> > > >
>> > > > Olaf has done a good job of cleaning up our contributors list
>> > > > and
>> > > > curating the bug tracker. However, there are a handful of
>> > > > patches in
>> > > > the bug tracker that could still be applied, once they are
>> > > > reviewed.
>> > > > Also, quite a number of backends that are now unmaintained. So,
>> > > > this
>> > > > is a good time to get involved with sane. If you benefit from
>> > > > this
>> > > > project, and have some programming experience, we could use the
>> > > > help.
>> > > >
>> > > > Schedule:
>> > > >
>> > > > May 7: Feature freeze (only fix bugs and update docs after this
>> > > > date)
>> > > > May 14: Code freeze (only update docs after this date)
>> > > > May 21: Release
>> > > >
>> > >
>> > > Hi,
>> > > Yesterday when I had a look at our bug tracker for any issues in
>> > > my
>> > > code I found https://alioth.debian.org/tracker/?func=detail
>> > > _id=30
>> > > 186=315004=410366
>> > > This is an issue for scanbd integration that requires more
>> > > flexibility
>> > > for configuration of dll-loading: when scanbd is used users need
>> > > to use
>> > >  the net backend only, but scanbd/saned need to be fed with the
>> > > "normal" list of backends.
>> > > I made a patch to dll.c where
>> > > - It used the dll.conf with the name pointed out by env. var
>> > > SANE_CONFIG_FILE if defined, if not
>> > > - it tries to load a dll2.conf if it exists. This is meant to be
>> > > a file
>> > > dropped in thre sane config dir by scanbd. If that does not exist
>> > > - it follows the existing code path.
>> > >
>> > > I added a #include statement in the config file so dll2.conf can
>> > > include dll.conf if so required.
>> > >
>> > > I am in the process of testing and cleaningup. but my question
>> > > is:
>> > > should I commit this change so close to the freeze date?
>> > > Documentation
>> > > is still to be done, but I would still have 2 weeks for that.
>> > > Alan, what do you think?
>> > >
>> >
>> > I don't now recall the entire discussion around the guts of
>> > scanbd's
>> > implementation, but you description sounds a little odd to me.
>> >
>> > 1. If dll2.conf is created by scanbd, and scanbd is not running,
>> > and
>> > the user uses scanimage or another frontend, he will unknowingly
>> > load
>> > dll2.conf first. Even if dll2.conf #includes dll.conf, it is still
>> > a
>> > behavior change.
>> > 2. Do you not also need changes to saned to make this work? That
>> > seemed to be the case in the earlier discussion.
>> > 3. I think I would prefer a more clear name than dll2.conf, but I
>> > cannot think of one :)
>>
>> From a scanbd point of view it would be suffcient to have either:
>>
>> 1) an env-var e.g. SANE_CONFIG_FILE which is normally unset and all
>> sane-applications use the compile-time setting. scanbd can set this
>> to
>> an alternative (e.g. scanbd-dll.conf) file before starting saned.
>>
>> 2) give saned a -c  option
>>
>> I would prefer 1)
>>
> Well 2 is not an option in my opinion as there is no way for saned to
> pass an argument to the rest of saned. That is why I implemented 1).
>
> The change to an alternative dll.file was driven by the fact that when
> packaging scanbd you want to minimize the amount of configuration to be
> done by the user. If the scanbd package drops a dll2.conf file in
> SANE_CONFIG_DIR there is no need f

Re: [sane-devel] sane-backends release 1.0.26 schedule

[m. allan noah]

On Sat, May 6, 2017 at 5:52 AM, Louis Lagendijk <lo...@fazant.net> wrote:
> On Fri, 2017-04-28 at 08:04 -0400, m. allan noah wrote:
>> Ok folks, it's time to get another sane-backends release out the
>> door.
>>
>> Olaf has done a good job of cleaning up our contributors list and
>> curating the bug tracker. However, there are a handful of patches in
>> the bug tracker that could still be applied, once they are reviewed.
>> Also, quite a number of backends that are now unmaintained. So, this
>> is a good time to get involved with sane. If you benefit from this
>> project, and have some programming experience, we could use the help.
>>
>> Schedule:
>>
>> May 7: Feature freeze (only fix bugs and update docs after this date)
>> May 14: Code freeze (only update docs after this date)
>> May 21: Release
>>
>
> Hi,
> Yesterday when I had a look at our bug tracker for any issues in my
> code I found https://alioth.debian.org/tracker/?func=detail_id=30
> 186=315004=410366
> This is an issue for scanbd integration that requires more flexibility
> for configuration of dll-loading: when scanbd is used users need to use
>  the net backend only, but scanbd/saned need to be fed with the
> "normal" list of backends.
> I made a patch to dll.c where
> - It used the dll.conf with the name pointed out by env. var
> SANE_CONFIG_FILE if defined, if not
> - it tries to load a dll2.conf if it exists. This is meant to be a file
> dropped in thre sane config dir by scanbd. If that does not exist
> - it follows the existing code path.
>
> I added a #include statement in the config file so dll2.conf can
> include dll.conf if so required.
>
> I am in the process of testing and cleaningup. but my question is:
> should I commit this change so close to the freeze date? Documentation
> is still to be done, but I would still have 2 weeks for that.
> Alan, what do you think?
>

I don't now recall the entire discussion around the guts of scanbd's
implementation, but you description sounds a little odd to me.

1. If dll2.conf is created by scanbd, and scanbd is not running, and
the user uses scanimage or another frontend, he will unknowingly load
dll2.conf first. Even if dll2.conf #includes dll.conf, it is still a
behavior change.
2. Do you not also need changes to saned to make this work? That
seemed to be the case in the earlier discussion.
3. I think I would prefer a more clear name than dll2.conf, but I
cannot think of one :)

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] Is it time of a new release?

[m. allan noah]

On Tue, May 2, 2017 at 4:56 PM, Tom Myers  wrote:
> Do you know if the new release 1.0.26  will be built for macOS Sierra 
> (10.12)?  I would be willing to help a bit on this. I tried to build it with 
> the latest Xcode and had issues. Not sure if it was me or the code. I am a 
> bit rusty in using the latest code but would be willing to help if need be.
>

Tom, we have historically relied on Mattias Ellert to do the OSX
versions. I don't know if he had to apply patches to enable the
compilation. If you want to give it a go, I would look for any patches
like that first.

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] pixma backend: -x/y auto advertised but not available / how to crop?

[m. allan noah]

That 'auto' string is put there by scanimage, when it finds an option
with the SANE_CAP_AUTOMATIC capability set. Unfortunately, scanimage
has some special handling for the x/y/t/l parameters. It appears that
-l and -t will properly parse the 'auto' string, but -x and -y will
not. This is a bug in scanimage, specifically in parse_vector().

If the pixma devices are unable to detect paper width in hardware, the
SANE_CAP_AUTOMATIC cap should be removed from those options. Or, the
pixma backend could be extended to use sanei_magic library, which
other backends use to add features like deskew and crop.

Outside of modifying sane-backends, you might look at the program
unpaper for post-processing the images.

allan

On Thu, Apr 27, 2017 at 5:05 PM, Manuel Reiter  wrote:
> Nobody? I found this old discussion which seems to suggest the pixma devices 
> don't support auto-detection:
>
> http://lists.alioth.debian.org/pipermail/sane-devel/2009-December/025674.html
>
> If that's indeed the case, may I suggest updating the pixma backend so that 
> it doesn't advertise capabilities that don't exist?
>
> Also, I'd still appreciate suggestion for a scriptable approach to achieve 
> this functionality.
>
> Thanks,
>
>   Manuel
>
> Am 11.04.2017 um 16:44 schrieb Manuel Reiter:
>
>> I'm using saned with a Pixma MP610 all-in-one on a Raspberry Pi 3 running an 
>> up-to-date Rasbian Jessie. scanimage --help shows me the following options 
>> for Geometry:
>>
>> [...]
>> Options specific to device `net:localhost:pixma:04A91725_414EE7':
>> [...]
>>  Geometry:
>>-l auto|0..216.069mm [0]
>>Top-left x position of scan area.
>>-t auto|0..297.011mm [0]
>>Top-left y position of scan area.
>>-x auto|0..216.069mm [216.069]
>>Width of scan-area.
>>-y auto|0..297.011mm [297.011]
>>Height of scan-area.
>> [...]
>>
>> However, trying to actually use "-x auto" results in an error:
>>
>> --snip
>> reiter@hive:~ $ scanimage -d net:localhost:pixma --mode Color \
>> --resolution 300 -l auto -t auto -x auto -y auto > /dev/null
>> scanimage: option --x: bad option value (rest of option: auto)
>> --snip
>>
>> Is this a bug or an error on my part?
>>
>> I intend to use this scanner for a document management system and expect to 
>> scan quite a number of non-full-size documents. If x/y auto is indeed not 
>> available, what would be a good way to automatically crop my scans? The 
>> included (Mac) Software actually does a decent job so it seems to be 
>> possible.
>>
>> Thanks in advance for your answers!
>>
>> Cheers,
>>
>>  Manuel
>>
>> --
>> 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
>
>
> --
> 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



-- 
"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] adding a timeout for the scanner lamp

[m. allan noah]

 The driver (we call them backends) is the only part of sane that
knows the protocol the scanner speaks. So, the backend would have to
be called to perform this task. As an alternative, perhaps the
frontend (xsane in this case) could close the scanner when it is idle,
and re-open it when the user does something. That would in theory work
with all scanners.

allan

On Fri, Apr 28, 2017 at 11:15 AM, Fred 1 <zfre...@gmail.com> wrote:
> Mustek BearPaw 2448 TA
>
> does it matter ?
>
> so i should be looking at the driver code?
>
>
>
> On 29/04/17 01:11, m. allan noah wrote:
>>
>> Depends on which scanner you are talking about, which you did not say.
>>
>> allan
>>
>> On Fri, Apr 28, 2017 at 10:58 AM, Fred 1 <zfre...@gmail.com> wrote:
>>>
>>> i'm not quite familiar with the code yet, but say i want to add a timeout
>>> thingy for the scanner lamp,
>>>
>>> normally the lamp turns off when you exit xsane, ok, but failing that
>>> would
>>> like to have a configurable timeout
>>>
>>> so i'll take any advice from who is already more familiar with the codes,
>>>
>>> thanks
>>>
>>>
>>>
>>> --
>>> 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
>>
>>
>>
>



-- 
"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] adding a timeout for the scanner lamp

[m. allan noah]

Depends on which scanner you are talking about, which you did not say.

allan

On Fri, Apr 28, 2017 at 10:58 AM, Fred 1  wrote:
> i'm not quite familiar with the code yet, but say i want to add a timeout
> thingy for the scanner lamp,
>
> normally the lamp turns off when you exit xsane, ok, but failing that would
> like to have a configurable timeout
>
> so i'll take any advice from who is already more familiar with the codes,
>
> thanks
>
>
>
> --
> 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



-- 
"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] sane-backends release 1.0.26 schedule

[m. allan noah]

You can send translations at any time, up to the day of the release.

allan

On Fri, Apr 28, 2017 at 10:20 AM, Yuri Chornoivan <yurc...@ukr.net> wrote:
> п'ятниця, 28-кві-2017 08:04:55 m. allan noah написано:
>> Ok folks, it's time to get another sane-backends release out the door.
>>
>> Olaf has done a good job of cleaning up our contributors list and
>> curating the bug tracker. However, there are a handful of patches in
>> the bug tracker that could still be applied, once they are reviewed.
>> Also, quite a number of backends that are now unmaintained. So, this
>> is a good time to get involved with sane. If you benefit from this
>> project, and have some programming experience, we could use the help.
>>
>> Schedule:
>>
>> May 7: Feature freeze (only fix bugs and update docs after this date)
>> May 14: Code freeze (only update docs after this date)
>> May 21: Release
>>
>> Any questions or concerns, let me know.
>>
>> allan
>
> Hi,
>
> When is it possible/right to send translation updates?
>
> Thanks in advance for your answer.
>
> Best regards,
> Yuri
>
> --
> 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



-- 
"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] TIFF to PDF at 300dpi?

[m. allan noah]

do your tiffs have XResolution and YResolution tags in them before you convert?

allan

On Wed, Apr 12, 2017 at 11:05 AM, Manuel Reiter  wrote:
> Hi all,
>
> this might be a bit off topic here and if that's against this list's policy, 
> I apologize in advance, but I've been websearching literally for hours now 
> without finding a solution and I figure somebody here might have had the same 
> problem before.
>
> I want to convert a TIFF, scanned at 300 dpi, to a PDF of the same size and 
> dpi. From my searches, this should be achievable both with ImageMagick's 
> "convert" with output option "-r300" and with ghostscript and 
> "-dPDFSETTINGS=/printer". However, both approaches don't work for me. convert 
> resamples the image to 72 dpi while ghostscript correctly embeds the image at 
> full resolution but does apparently not set the required metadata for the 
> PDF/embedded image resolution to be recognised as 300 dpi.
>
> Any ideas anybody? Suggestions where else to ask are also highly welcome. 
> Thanks in advance!
>
> Cheers,
>
> Manuel
> --
> 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



-- 
"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] CanoScan 9000F not recognized on Lubuntu

[m. allan noah]

What version number of libsane?

allan

On Fri, Mar 31, 2017 at 1:57 AM, Jonathan Barés
<jonathan.ba...@umontpellier.fr> wrote:
> Hi Allan,
>
> Yes it is libsane.
>
> Thanks,
>
> Jonathan
>
>
>
> Le 30/03/2017 à 22:24, m. allan noah a écrit :
>>
>> What version of sane-backends are you running? It might be called
>> libsane on your system.
>>
>> allan
>>
>> On Thu, Mar 30, 2017 at 3:04 PM, Jonathan Barés
>> <jonathan.ba...@umontpellier.fr> wrote:
>>>
>>> Hi all,
>>>
>>> After googling for hours I still do not understand why my CanoScan 9000F
>>> MarkII is not recognized by my Lubuntu computer (14.04 kernel) and am
>>> hoping
>>> some of you could help with this.
>>>
>>> When I run sane-find-scanner I get:
>>>
>>># 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.
>>>
>>># No USB scanners found. If you expected something different, make
>>> sure
>>> that
>>># you have loaded a kernel driver for your USB host controller and
>>> have
>>> setup
>>># the USB system correctly. See man sane-usb for details.
>>># SANE has been built without libusb support. This may be a reason
>>># for not detecting USB scanners. Read README for more details.
>>>
>>># 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 have tried to add the rule:
>>> # Canon CanoScan 9000F Mark II
>>> ATTR{idVendor}=="04a9", ATTR{idProduct}=="190d", MODE="0664",
>>> GROUP="scaner", ENV{libsane_matched}="yes
>>> in /etc/udev/rules.d/50-CanonScan.rules but still get the same problem.
>>>
>>> I am really surprised because the scanner seems to be seen by the
>>> computer
>>> when I run lsusb:
>>> Bus 002 Device 002: ID 04a9:190d Canon, Inc. CanoScan 9000F Mark II
>>> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>>> Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>>> Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>>> Bus 003 Device 003: ID 1c4f:0048 SiGma Micro
>>> Bus 003 Device 002: ID 413c:2107 Dell Computer Corp.
>>> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>>>
>>> Here is also my version of sane:
>>> xsane-0.998 (c) 1998-2010 Oliver Rauch
>>>Courrier électronique : oliver.ra...@xsane.org
>>>paquet xsane-0.996
>>>compilé avec GTK-2.24.18
>>>avec fonction de gestion de la couleur
>>>avec support GIMP, compilé avec GIMP-2.8.4
>>>Formats de sortie de XSane : jpeg, pdf(compr.), png, pnm, ps(compr.),
>>> tiff, txt
>>>
>>> If anybody has an idea of what is happening I would be extremelly happy
>>> to
>>> have some help.
>>> I thank you in advance.
>>> Best,
>>> Jonathan
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> 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
>>
>>
>>
>



-- 
"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] FUJITSU ScanSnap iX500 - default page format?

[m. allan noah]

Thanks Peter- I've been doing some work in the epjitsu backend this
week. Hopefully I will have time to include your work.

allan

On Sat, Mar 25, 2017 at 4:05 AM, Peter Marschall <pe...@adpm.de> wrote:
> Hi,
>
> IIRC setting the page width  in the epjitsu backend was broken
> in 2015
>
> I reported this in 2015 in #315231
> ( https://alioth.debian.org/tracker/?
> func=detail=410366=315231_id=30186 )
> with a patch set that also contained further cleanups
>
> Unfortunetely there was no action until now.
>
> I will update the patchset mentioned in the bug with one that is rebased
> against current git head today.
>
> Best
> PETer
>
> Am Montag, 6. März 2017, 10:12:48 CET schrieb m. allan noah:
>> Frankly, your front-end program should save your preferences for
>> things like page size, so you only set them once. I was pretty sure
>> that xsane did so. For a front-end that does not, we could change
>> sane-backends defaults on a per-backend basis, I suppose. I the
>> backends I wrote (which includes fujitsu) it should be easy. For
>> example, edit backend/fujitsu.c and search for 8.5 and 11 (the width
>> and height of US Letter). Change those as required and recompile. A
>> better long term solution would be to make the default sizes
>> configurable from the backend's config file. I will think about the
>> best way to do that.
>>
>> allan
>>
>> On Mon, Mar 6, 2017 at 9:56 AM, Philipp Huebner <debala...@debian.org>
> wrote:
>> > Am 06.03.2017 um 15:54 schrieb m. allan noah:
>> >> The fujitsu backend does not have an automatic size option. The page
>> >> and image sizes default to US Letter, which is wider than A4. Perhaps
>> >> you are seeing some feature of your frontend program. Which frontend
>> >> are you using?
>> >
>> > You're probably right. xsane and gscan2pdf default to letter, only
>> > simple-scan defaults to automatic.
>> >
>> > I would still be interested in changing the default from letter to A4.
>> >
>> > Regards,
>> > --
>> >
>> >  .''`.   Philipp Huebner <debala...@debian.org>
>> >
>> > : :'  :  pgp fp: 6719 25C5 B8CD E74A 5225  3DF9 E5CA 8C49 25E4 205F
>> >
>> > `. `'`
>> >
>> >   `-
>> >
>> > --
>> > 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
>
>
> --
> Peter Marschall
> pe...@adpm.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



-- 
"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] Is it time of a new release?

[m. allan noah]

We were discussing another release recently. We have at least one
major networking security bug we need to fix, and there are a few
backends which have some outstanding patches yet to commit. I think
perhaps at the end of April these things will be ready. If you are
able, taking a pass through our bug tracker looking for things we
might have missed would be helpful.

allan

On Sun, Mar 12, 2017 at 5:29 PM, Luiz Angelo Daros de Luca
 wrote:
> Hi,
>
> We already have more than 500 commits since 1.0.25. As a downstream
> maintainer (openwrt/lede), I get lost between those tons of patches
> and how to select them to be backported.
>
> Shouldn't sane-backend release a new version?
>
> Also, It would be really nice if SANE could keep a stable branch. It would
> be, at least, a place to target cherry-picks.
>
> Maybe it could change its version number to something like other projects do
> as:
>
> x.y.0 - feature release x.y
> x.y.n - fix release n
>
> It would be better if x.y is year/month. At least there is no discussion on
> whether the new release is big enough to tic the first number.
>
> Regards,
> --
>
> Luiz Angelo Daros de Luca
> luizl...@gmail.com
>
>
> --
> 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



-- 
"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] FUJITSU ScanSnap iX500 - default page format?

[m. allan noah]

Frankly, your front-end program should save your preferences for
things like page size, so you only set them once. I was pretty sure
that xsane did so. For a front-end that does not, we could change
sane-backends defaults on a per-backend basis, I suppose. I the
backends I wrote (which includes fujitsu) it should be easy. For
example, edit backend/fujitsu.c and search for 8.5 and 11 (the width
and height of US Letter). Change those as required and recompile. A
better long term solution would be to make the default sizes
configurable from the backend's config file. I will think about the
best way to do that.

allan

On Mon, Mar 6, 2017 at 9:56 AM, Philipp Huebner <debala...@debian.org> wrote:
> Am 06.03.2017 um 15:54 schrieb m. allan noah:
>> The fujitsu backend does not have an automatic size option. The page
>> and image sizes default to US Letter, which is wider than A4. Perhaps
>> you are seeing some feature of your frontend program. Which frontend
>> are you using?
>
> You're probably right. xsane and gscan2pdf default to letter, only
> simple-scan defaults to automatic.
>
> I would still be interested in changing the default from letter to A4.
>
> Regards,
> --
>  .''`.   Philipp Huebner <debala...@debian.org>
> : :'  :  pgp fp: 6719 25C5 B8CD E74A 5225  3DF9 E5CA 8C49 25E4 205F
> `. `'`
>   `-
>
>
>
>
> --
> 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



-- 
"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] FUJITSU ScanSnap iX500 - default page format?

[m. allan noah]

The fujitsu backend does not have an automatic size option. The page
and image sizes default to US Letter, which is wider than A4. Perhaps
you are seeing some feature of your frontend program. Which frontend
are you using?

allan

On Mon, Mar 6, 2017 at 9:32 AM, Philipp Huebner  wrote:
> Hi,
>
> I have a FUJITSU ScanSnap iX500 that works quite well for the most part.
>
> One problem though: the default page format is "automatic", which fails
> to detect the righgt format rather often and cuts off parts of the pages.
>
> When I set it to the correct size manually (e.g. A4), it works fine.
>
> Can anybody tell me how to change the default page format from automatic
> to A4?
> I wouldn't mind re-compiling a custom sane-backends for that.
>
> Best wishes,
> --
>  .''`.   Philipp Huebner 
> : :'  :  pgp fp: 6719 25C5 B8CD E74A 5225  3DF9 E5CA 8C49 25E4 205F
> `. `'`
>   `-
>
>
> --
> 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



-- 
"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] fujitsu deskew background artifacts

[m. allan noah]

Paul- I'm sorry I missed your earlier email, gmail put it in spam. It
was only when Olaf replied that I saw anything about it (thanks
Olaf!). Further comments inline...

On Thu, Feb 9, 2017 at 4:39 PM, G. Paul Ziemba  wrote:
> There seems to be something wrong with the software deskew operation
> in SANE. I'm hoping someone can either confirm it is a bug or suggest
> alternate arguments to scanimage to fix the problem. I am also happy
> to modify C code and try patches.
>
> Many thanks for your anticipated suggestions.
>
> Goal: crop the deskewed image correctly.
>
> Version: scanimage reports:
> scanimage (sane-backends) 1.0.25; backend version 1.0.25
>
> Scanner: Fujitsu ScanSnap S1500

First- thanks for including that info, we have to tease that info out
of most bug reporters :)

[snip]

> To me, it looks like the color of the background filled in by the
> deskew operation does not match the "empty" background generated by
> the scanner.

Yes- that is exactly the problem. I bet if you scan in black and white
(lineart) mode, the problem would go away just because both background
colors would become white. We'll need to get better at background
color detection for gray and color modes to work.

> As an aside, if the deskewing code can already detect the edges before
> it rotates the image, maybe it can cache those parameters for subsequent
> use by the crop code.

It does do that- you notice that the deskew code moves the image to
the upper left corner rather than rotate it in place. Unfortunately,
the deskew code only finds the top and left edges because it is so
slow. I suppose we could detect if both deskew and crop are turned on
at the same time, and look for the other edges too, but fixing the
background color would be faster to code and faster to run.

[snipped very useful image links]

A quick workaround would be to modify backend/fujitsu.c in the
function buffer_deskew. Change:

  int bg_color = 0xd6;

to

  int bg_color = 0xbe;

Then rebuild and re-install.

Longer term, we need to either make the background color configurable
on a per-model basis (as done in canon_dr backend), or do a better job
of autodetecting it (made difficult by shadow edges on full-size
scans).

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] Does sane support sanner device Panasonic S1046C？

[m. allan noah]

The kvs1025 backend does not list the KV S1046C. It may be possible to
add it to the code, and have it work. The sane project has no way of
knowing, however, since the author of this backend is not a member of
the project.

Do you have access to this scanner? We could give you a patch to try,
but you would have to compile sane-backends from source.

allan

On Tue, Jan 17, 2017 at 12:47 AM, lichun...@cetc-cloud.com
 wrote:
> I find that sane support Panasonic S1045C， does it support Panasonic S1046C？
>
> Thank you
>
> 
> lichun...@cetc-cloud.com
>
> --
> 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



-- 
"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] Avision AV210D2+ segfaulting

[m. allan noah]

Always start with an upgrade to a current git repo checkout. There has
been some work on the avision backend recently, and you might get
lucky.

allan

On Mon, Jan 16, 2017 at 10:38 AM, skerr  wrote:
> Hi Wolf,
>
> Thanks for your response.
>
> I will be stuck using CentOS7. It uses a 3.10 kernel. But your correct,
> CentOS/RHEL, backport many patches/bugfixes/updates.
>
> Its the platform we use for a very heavily modified Kickstart server
> installation we provide to our end users. I have the scanner working on my
> CentOS 5 and 6 kickstarts,  but we have hundreds out in the field and will
> have to update to 7 in the not too distant future. It wont be a complete
> show stopper as long as I can get scanimage to scan over the network to an
> avision hanging off a windows workstation.
>
> Also , by you comments, I presume the maintainer listed in the avision conf
> file is no longer active. That was going to be my next recourse if noone on
> this list had any fruitful suggestions.
>
> Hopefully I can come up with a solution before CentOS7 goes live.
>
> Thanks,
>
> Steve
>
>
>
> On 01/14/2017 05:30 AM, Wolf Drechsel wrote:
>
> Hello,
>
> just my 2cts:
> I'm suffering from a "avision" problem as well - we seem to be quite a bit
> lost at the moment, as far as I understood, the avision backend does not
> have a maintainer at the moment.
>
> An ugly workaround for me is to scan from my laptop which is running debian
> 8.6 now - I do not have any problems scanning with that machine. Maybe you
> want to give a debian live system a try?
>
> My guess (but I do not know anything about programming) is that in the last
> few years USB timing was changed, so older kernels work better than newer
> ones. I read that CentOS is using a comparatively old kernel, but with quite
> a lot of patches - can those cause the harm?
>
> cheers,
> Wolf
>
> Am Freitag, den 13.01.2017, 09:26 -0500 schrieb skerr:
>
> Hello,
> I am having an issue when trying to use a Avision AV210D2+ scanner.
> I am running CentOS 7.2 using sane-backends 1.0.24.
>
> fujitsu fi-6130z and 7160 both work fine on the same platform.
>
> USB 3 is turned off in the bios and lsusb -t shows the scanner is using the
> ehci-pc usb module.
>
> The scanner is seen properly by sane-find-scanner  and scanimage -L.
> device `avision:libusb:002:032' is a Avision AV210D2+ sheetfed scanner
>
> When attempting to scan a documents, scanimage -d avision >test.jpg the
> console error message
> is segmentation fault. dmesg shows  segfault at 7fa93c82a9d0 ip
> 7fa94a2a1de0 sp  7fff384ef888 error 4 in
> libpthread-2.17.so[7fa94a299000+17000]
>
> Some things I have tried:
> - passing various supported geometry and resolution options to scanimage .
> - removing all backends from dll.conf except for avision
> - rotated amongst all usb ports
> - bios update to workstation
>
>
> 
> This email was scanned by Bitdefender.
>
>
>
> 
> The information contained in this e-mail message is intended only for the
> confidential use of the recipient/recipients named above. If the reader of
> this message is not the intended recipient or an agent responsible for
> delivering it to the intended recipient, you are hereby notified that you
> have received this document in error and that any review, dissemination,
> distribution, or copying of this message is strictly prohibited. If you have
> received this communication in error, please notify me immediately by e-mail
> and delete the original message.
>
> --
> 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



-- 
"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] Help, I pushed mucb more to got then I wanted

[m. allan noah]

git revert will add reversing commits to your tree, and you can push them.

allan

On Fri, Jan 6, 2017 at 4:28 PM, Louis Lagendijk  wrote:
> guys,
> My sincere apologies: I messed up my last push to git. I did not notice
> that I had already commited other changes to my local copy that should
> not go into master. how can I best revert the changes to pixma_mp150.c?
>
> /Louis
>
> --
> 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



-- 
"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] Samsung M2675FN

[m. allan noah]

No, it says that those models are unsupported:

http://www.sane-project.org/lists/sane-backends-cvs.html#S-XEROX-MFP

allan

On Fri, Dec 30, 2016 at 8:00 AM, Manuel Argüelles
 wrote:
> Hello,
>
> From the development (git) version of sane-backends I can see that
> xerox_mfp includes support for "Samsung M267x 287x Series", maybe you
> could try it and add support for it.
>
> Good luck!
>
> On Fri, Dec 30, 2016 at 01:03:50PM +0100, Hot wrote:
>> Dear Developers,
>>
>> I just found out that my Scanner is not supported by the SANE-Project.
>> Is there any chance for it to be supported in the near future, or do I
>> have to buy myself a new one (or use a Windows-VM)?
>>
>> Thank you.
>>
>> Best regards,
>> Horst Thiel
>>
>> --
>> 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
>
> --
> 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



-- 
"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] Cannot get hp scanjet 8200 working

[m. allan noah]

This sounds like the typical linux usb3 problems. If you use a
sane-backends git snapshot, the problem may go away. If not, that
version also has another option: you can try to invoke your scanning
program with an additional env var: SANE_USB_WORKAROUND=1


allan

On Fri, Nov 25, 2016 at 3:57 AM, Wolf Drechsel  wrote:
> Hello Dave,
>
> great you're taking care for me.
> A few days ago I filed a bug report which contains most of your requested
> info:
>
> https://bugs.launchpad.net/bugs/1643544
>
> The test you asked for have already been carried out:
>
>
> -  Test the scanner with the current Ubuntu/SANE distribution on
>another PC.  If it scans OK there, this would rather rule out the
>scanner itself as the problem.
>
>
> On my laptop, running ubuntu 16.04, the problem occurs as well.
> And: On my desktop, with fedora 24 - the problem ALSO EXISTS
>
> -  Test your PC's USB setup with some non-scanner high-speed transfers.
>One way would be to plug in a USB hard driver or data stick, and then
>"dd if=/dev/sdB bs=$((1024*1024)) of=/dev/null" (substitute the
>correct device identifier) and see if the transfer works successfully
>or if it triggers the USB hang.
>
>(Based on what you report, I've got a nasty feeling that your
> motherboard host controller may be ill... works OK for low-speed
> transfers, but hangs up somehow during sustained high-speed
> transfers.  The fact that it times out and leaves the bus hung
> is troubling.)
>
>
> Last days, I copied 3 250GB USB hard disks via USB. No problems.
>
> -  Boot up a different Linux distribution on your laptop (e.g. Knoppix)
>and see if you can get the scanner to work reliably.  If so it might
>point to a recent change in your normal kernel and/or libusb as
>being responsible.
>
>
> With a debian 8.6, kernel 3.2 (or so), booted for an external USB hdd - NO
> PROBLEM AT ALL. Multiple pages, high resolutions - everything fine.
>
> My conclusions from these experiments:
>
> * scanner is o.k.
> * desktop is o.k.
> * kernel 4.X causes problems, distro-independently
>
> Let me know if I can provide further information.
>
> Cheers,
> Wolf
>
>
> --
>
> --
> 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



-- 
"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] Fujitsu iX500 - No scanners were identified.

[m. allan noah]

You did not tell us what you upgraded? Sane-backends, your scanner, your kernel?

This sounds like a pretty typical linux usb bug. You might need to
install a development version of sane-backends from our git repo. Once
you have built and installed a sane-backends git snapshot (using the
info in README.linux), you can run scanimage -L repeatedly. You may
find that the scanner only shows up intermittently. If that is the
case, try running this repeatedly instead:

SANE_USB_WORKAROUND=1 scanimage -L

That might work better. If so, you will have to put
SANE_USB_WORKAROUND=1 into your environment.

Oh, and BTW, your scanner is not supported by the snapscan backend.
Try fujitsu instead.

allan



On Mon, Nov 21, 2016 at 6:40 AM, Jiri  wrote:
> Hi,
>
> [Debian Sid]
>
> I started having problem with Fujitsu iX500 scanner after upgrade. It used
> to work fine, but now it seems the system identifies the scanner for a just
> a while and but apps cannot use it.
>
> Here is example. I run the following command two times right after each
> other. The scanner is recognized on first run (after plugging USB in), but
> when I run it second time it says the scanner was not identified.
>
> Any help would be appreciated.
>
>
> ganomi@knightrider:~$ SANE_DEBUG_FUJITSU=15 scanimage -L
> [sanei_debug] Setting debug level of fujitsu to 15.
> [fujitsu] sane_init: start
> [fujitsu] sane_init: fujitsu backend 1.0.127, from sane-backends 1.0.25
> [fujitsu] sane_init: finish
> [fujitsu] sane_get_devices: start
> [fujitsu] sane_get_devices: reading config file fujitsu.conf
> [fujitsu] sane_get_devices: setting "buffer-size" to 65536
> [fujitsu] sane_get_devices: looking for 'scsi FUJITSU'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x1041'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x1042'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x1078'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x1095'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x1096'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x1097'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x10ad'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x10ae'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x10af'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x10cf'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x10e0'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x10e1'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x10e2'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x10e6'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x10e7'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x10f2'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x10fe'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x1135'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x114a'
> [fujitsu] sane_get_devices: config option "buffer-size" (262144) is > 65536,
> warning!
> [fujitsu] sane_get_devices: setting "buffer-size" to 262144
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x114d'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x114e'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x114f'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x1150'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x1155'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x116f'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x1174'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x1175'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x1176'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x1177'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x1178'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x119d'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x119e'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x11a2'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x11f1'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x11f2'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x11f3'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x11f4'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x11fc'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x1213'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x128e'
> [fujitsu] sane_get_devices: looking for 'usb 0x04c5 0x132b'
> [fujitsu] attach_one: start
> [fujitsu] attach_one: looking for 'libusb:003:004'
> [fujitsu] connect_fd: start
> [fujitsu] connect_fd: opening USB device
> [fujitsu] wait_scanner: start
> [fujitsu] do_usb_cmd: start
> [fujitsu] do_usb_cmd: finish
> [fujitsu] wait_scanner: finish
> [fujitsu] connect_fd: finish
> [fujitsu] init_inquire: start
> [fujitsu] do_usb_cmd: start
> [fujitsu] do_usb_cmd: finish
> [fujitsu] init_inquire: Found FUJITSU scanner ScanSnap iX500 version 0L00 at
> libusb:003:004
> [fujitsu] inquiry options
> [fujitsu]   color offset: 0 lines
> [fujitsu]   long gray scan: 1
> 

Re: [sane-devel] scanimage version

[m. allan noah]

I'm totally confused- the developers on this list are the authors of
the scanimage program you are using. The current version is 1.0.25.
But no matter, because I don't think scanimage is the source of your
problem. The issue here is with the brother driver, which you got from
brother, not from us. I've said this repeatedly, and am going to say
it louder now and in public, so maybe you will hear it. Contact
brother with your issues, as it is unlikely anyone here will be able
to help you.

allan

On Fri, Nov 4, 2016 at 6:47 PM, Vince Radice  wrote:
> Hello,
>
> I am having a problem with my scanner - Brother MFC240C.  It worked
> until I upgraded my pc hardware and also the os to Fedora 24 64bit.  I have
> been trying to figure out what is really wrong and came up to a stumbling
> block.  The version of scanimage I have is 1.0.25.  I have contacted the
> current vendor of scanimage. According to them the current version is 5.0
> and is windows only. They do not have the source code to any version earlier
> than 3.0.  I have used xsane in the past but I get an error every time I try
> the scanner.  The error is
>
> Failed to start scanner: Invalid argument
>
> Is this the place to get help trying to figure out what the problem is?
>
> Thank you,
> Vince Radice
>
> --
> 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



-- 
"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] microtek2 lineart threshold problem

[m. allan noah]

Change the order of your command line arguments. put lineart first.

On Thu, Nov 3, 2016 at 2:28 PM, Tom Canavan  wrote:
> Hello,
> I am a new member and this is my first post.  I wanted to post here before
> filing a bug report to make sure I am not doing something wrong.
>
> I am having trouble using the scanimage command with the microtek2 backend
> trying to control a Microtek V6USL.
>
> The problem is with the "--threshold" option in Lineart mode. I need to be
> able to control the threshold because with some scans the automatic setting of
> the threshold does not work very well when scanning documents that are printed
> over colored backgrounds.  And I need to do it via command line because I am
> writing a dialog script using Yad dialogs.
>
> I know the scanner Lineart threshold can be controlled, because I can do it
> with xsane and it works well.
>
> Here is my /etc/saned/microtek2.conf:
> option dump 1
> #option strip-height 14.0
> /dev/sg5
> option no-backtrack-option on
> option lightlid-35 on
> option toggle-lamp on
> option lineart-autoadjust on
> option backend-calibration on
> #option colorbalance-adjust on
> #scsi * * Scanner
>
> When I try to run a command to scan a document such as:
>
> scanimage -d microtek2:/dev/sg5 -x 250 -y 20 --resolution 200 --threshold 105
> --mode Lineart --format=tiff > $HOME/faxproject/scans/image.tif
>
> I get an error message:  scanimage: attempted to set inactive option threshold
>
> When I run scanimage -A it says that option is indeed inactive.  So I tried
> putting the line:
>
> option threshold on
>
> in my /etc/saned/microtek2.conf file.
> That did not work either.
>
> I then tried putting that line in and also turning off the option lineart-
> autoadjust.  That did not work either.
>
> So I am hoping that someone with more knowledge that I can tell me whether
> this is a bug or not, and if not, then show me how to turn the --threshold
> option on for this backend and this scanner.
> Any help appreciated.  Thank you.
>
> --
> 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



-- 
"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] A Cooperation Message from Plustek Inc.

[m. allan noah]

On Tue, Nov 1, 2016 at 12:43 PM, Yury Tarasievich
<yury.tarasiev...@gmail.com> wrote:
> On 01/11/16 14:37, m. allan noah wrote:
>>
>> Jenson- The SANE project certainly could accept your code for
>> inclusion into our repository, if a few conditions are met. Namely:
>>
>> 1. The code must be completely open and suitable for use with our
>> license. No binary or precompiled code, other than possible firmware
>> uploads.
>
> ...
>
> Isn't requiring anything beyond the point 1 a teensy bit over-reaching?

Perhaps you are right. In order to include the source in
sane-backends, it certainly must meet points 1,2,3 and 5. If Plustek
Inc is only able to comply with #1, some other developer will have to
perform the other steps, and hopefully point #4 as well. But we have
to be realistic about finding someone like 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] A Cooperation Message from Plustek Inc.

[m. allan noah]

Jenson- The SANE project certainly could accept your code for
inclusion into our repository, if a few conditions are met. Namely:

1. The code must be completely open and suitable for use with our
license. No binary or precompiled code, other than possible firmware
uploads.
2. The code must use our sanei_* libraries for things like usb or
threading. It should not directly use libusb or any kernel modules,
etc.
3. The code should be free from obvious security holes and bad
programming practices like using gets() or mktemp().
4. One or more members of your team need to join the SANE project so
you can see user support requests on this mailing list and our bug
tracker.
5. The code must build on other platforms that SANE supports, like the
various BSD Unixes. Generally, this just requires not calling anything
Linux specific.

Additionally, we prefer that all backends use our debugging library,
so that an environment variable like SANE_DEBUG_PLUSTEK=10 could be
used to enable user visible information from the backend.

If you and your management can accept those terms, the SANE project
would be glad to have your help. Additionally, your users would
benefit from having your drivers installed out of the box with their
distro of choice.

Thanks for contacting us.

allan


On Mon, Oct 31, 2016 at 11:22 PM,   wrote:
> Dear Team,
>
> I am the software PM from Plustek Inc. We are a major scanner manufacturer
> in Taiwan.  We meet many linux driver support requests from our customers.
> Linux has many distributions and versions and also sane too, we need put
> many RD resources to porting our driver to many version now. It's not a
> good idea to support linux driver. So we think, may be we can release the
> driver source code to your sane project, let you build in the driver at
> sane project.  What do you think about it? Thanks.
>
> Best Regards,
> Jenson
>
> 精益求精,超越卓越. A to A+
> --
> 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



-- 
"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

[sane-devel] Clarification: SANE Developer Status Reconfirmation Request

[m. allan noah]

The email below was sent to sane-devel on behalf of the project
admins, Gerhard, Olaf, and myself.

Our intention is to get a more accurate list of who should still have
commit permissions in our git repo, edit permissions in the bug
tracker, etc. The intended audience is effectively those listed on
this page: https://alioth.debian.org/project/memberlist.php?group_id=30186
If you are a mailing list member not listed on that page, there is no
need for you to respond. The sane-devel mailing list remains open for
everyone to contribute, and there is no official role or requirements
for inclusion in the discussions here.

Thanks for your understanding and support-
allan

On Sat, Oct 22, 2016 at 7:54 AM, Olaf Meeuwissen
 wrote:
> Dear SANE developer,
>
> The SANE project thanks you for your contributions, big and small,
> recent and in days gone by.
>
> Over the years, a long list of developers has joined the project.
> During that period, several have said the project farewell, on the
> list or in private communication.  Others have silently faded out,
> pursuing other goals.
>
> Unfortunately, we have not really kept the list of developers up to
> date.  The current list probably paints a rather inaccurate picture of
> who is still involved with the project.  This mail tries to fix that.
>
> Please reply[*] to this mail with one of the following statements:
>
>  1. Yes, I still consider myself a SANE developer.
>  2. No, I no longer consider myself a SANE developer.
>
> If you replied with the second statement, then we are sad to see you
> go.  We will un-assign all bugs and feature requests assigned to you
> and revoke your developer status.
>
> # Alternatively, log in on the Alioth website and remove yourself from
> # the project via https://alioth.debian.org/my/
>
> If you don't reply in about two weeks, we will contact you again via
> your Alioth address as well as any addresses we have on file for you.
> A final reminder will be sent some two weeks after that.
>
> After the reminder, we will wait another two weeks before revoking
> developer status for those who did not reply to any of these mails.
>
> We will gladly restore developer status should you have a change of
> heart.  Just reply to the mail we sent.
>
>  [*] The Reply-To: field has been set to the SANE project maintainers
>  and janitor (that's me).  Please keep it that way.  There is no need
>  to reply to the list.
>
> Hope this helps,
> --
> Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
>  GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
>  Support Free Softwarehttps://my.fsf.org/donate
>  Join the Free Software Foundation  https://my.fsf.org/join
>
> --
> 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



-- 
"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] option threshold without effect for fujitsu backend since 1.0.24-1

[m. allan noah]

I have just committed a fix in
e4aed53a1e46b9d46a76f814d414ef8d2c2276e3. If you are able, I would
appreciate if you could test it.

allan

On Wed, Oct 5, 2016 at 8:19 PM, m. allan noah <kitno...@gmail.com> wrote:
> It looks like commit 96628ed13f411298ee0681e7515745fdf85d1309 is the
> culprit. This change enabled the image processing functions by
> default, but that seems to have disabled the threshold algorithm in
> the scanner. I will look for an alternative implementation.
>
> allan
>
> On Tue, Oct 4, 2016 at 7:49 PM, m. allan noah <kitno...@gmail.com> wrote:
>> Mickael, thank you for the report. I thought I had fixed this problem
>> previously, but I am apparently wrong. I will investigate.
>>
>> allan
>>
>> On Mon, Oct 3, 2016 at 12:13 PM, PELUARD Mickael
>> <mickael.pelu...@smart-rx.com> wrote:
>>> Hello,
>>>
>>>
>>>
>>> we used Fujitsu scanner (fi-5110 / fi-5120 / fi-6110) for a
>>> long time with an old linux plateform and sane (1.0.22-9). These scanners
>>> used the fujitsu backend.
>>>
>>>
>>>
>>> We have recently changed to RHEL-6 with sane-backends-1.0.21
>>> and to Debian with libsane-1.0.25.
>>>
>>>
>>>
>>> We scan in lineart mode and we only put the threshold option
>>> to reduce the size of document : scanimage –d ‘fujitsu:XXX:XXX’ --resolution
>>> 150  --mode lineart  --threshold 140
>>>
>>> Then we convert the image to PDF-A1. With the old plateform
>>> and rhel-6, no problem. But with Debian and sane-1.0.25, the size of the
>>> documents increase a lot.
>>>
>>>
>>>
>>> Using a reference document, we get the following results with a fi-6110 :
>>>
>>> -  Rhel-6 / sane-1.0.21 = around 50 ko
>>>
>>> -  Debian / sane-1.0.25-2 = around 350 ko
>>>
>>> It’s quite the same problem if we used a fi-5110c and fi-5120c.
>>>
>>>
>>>
>>> I downgrade the libsane package and look the result :
>>>
>>> -  Debian / libsane-1.0.22-7 = good
>>>
>>> -  Debian / libsane-1.0.23-3+b1 = good
>>>
>>> -  Debian / libsane-1.0.24-1 = NOT GOOD
>>>
>>> -  Debian / libsane-1.0.24-8u5 = NOT GOOD
>>>
>>> -  Debian / libsane-1.0.26Git = NOT GOOD
>>>
>>>
>>>
>>> I change the value of threshold on Debian with sane-1.0.25 : threshold 0 or
>>> 200. But the image don’t change. It’s look like the threshold option has not
>>> effect.
>>>
>>> To reduce the problem, I play with the contrast and brightness option but
>>> the result is not entirely satisfactory.
>>>
>>>
>>>
>>> I think the problem is on the threshold option of the fujitsu backends.
>>>
>>>
>>>
>>> It is probably the same bug but it don’t lokk corrected in 1.0.26 :
>>>
>>> https://alioth.debian.org/tracker/?group_id=30186=410366=detail=315069
>>>
>>>
>>>
>>> Cordially.
>>>
>>>
>>> --
>>> 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
>>
>>
>>
>> --
>> "well, I stand up next to a mountain- and I chop it down with the edge
>> of my hand"
>
>
>
> --
> "well, I stand up next to a mountain- and I chop it down with the edge
> of my hand"



-- 
"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] option threshold without effect for fujitsu backend since 1.0.24-1

[m. allan noah]

It looks like commit 96628ed13f411298ee0681e7515745fdf85d1309 is the
culprit. This change enabled the image processing functions by
default, but that seems to have disabled the threshold algorithm in
the scanner. I will look for an alternative implementation.

allan

On Tue, Oct 4, 2016 at 7:49 PM, m. allan noah <kitno...@gmail.com> wrote:
> Mickael, thank you for the report. I thought I had fixed this problem
> previously, but I am apparently wrong. I will investigate.
>
> allan
>
> On Mon, Oct 3, 2016 at 12:13 PM, PELUARD Mickael
> <mickael.pelu...@smart-rx.com> wrote:
>> Hello,
>>
>>
>>
>> we used Fujitsu scanner (fi-5110 / fi-5120 / fi-6110) for a
>> long time with an old linux plateform and sane (1.0.22-9). These scanners
>> used the fujitsu backend.
>>
>>
>>
>> We have recently changed to RHEL-6 with sane-backends-1.0.21
>> and to Debian with libsane-1.0.25.
>>
>>
>>
>> We scan in lineart mode and we only put the threshold option
>> to reduce the size of document : scanimage –d ‘fujitsu:XXX:XXX’ --resolution
>> 150  --mode lineart  --threshold 140
>>
>> Then we convert the image to PDF-A1. With the old plateform
>> and rhel-6, no problem. But with Debian and sane-1.0.25, the size of the
>> documents increase a lot.
>>
>>
>>
>> Using a reference document, we get the following results with a fi-6110 :
>>
>> -  Rhel-6 / sane-1.0.21 = around 50 ko
>>
>> -  Debian / sane-1.0.25-2 = around 350 ko
>>
>> It’s quite the same problem if we used a fi-5110c and fi-5120c.
>>
>>
>>
>> I downgrade the libsane package and look the result :
>>
>> -  Debian / libsane-1.0.22-7 = good
>>
>> -  Debian / libsane-1.0.23-3+b1 = good
>>
>> -  Debian / libsane-1.0.24-1 = NOT GOOD
>>
>> -  Debian / libsane-1.0.24-8u5 = NOT GOOD
>>
>> -  Debian / libsane-1.0.26Git = NOT GOOD
>>
>>
>>
>> I change the value of threshold on Debian with sane-1.0.25 : threshold 0 or
>> 200. But the image don’t change. It’s look like the threshold option has not
>> effect.
>>
>> To reduce the problem, I play with the contrast and brightness option but
>> the result is not entirely satisfactory.
>>
>>
>>
>> I think the problem is on the threshold option of the fujitsu backends.
>>
>>
>>
>> It is probably the same bug but it don’t lokk corrected in 1.0.26 :
>>
>> https://alioth.debian.org/tracker/?group_id=30186=410366=detail=315069
>>
>>
>>
>> Cordially.
>>
>>
>> --
>> 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
>
>
>
> --
> "well, I stand up next to a mountain- and I chop it down with the edge
> of my hand"



-- 
"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] option threshold without effect for fujitsu backend since 1.0.24-1

[m. allan noah]

Mickael, thank you for the report. I thought I had fixed this problem
previously, but I am apparently wrong. I will investigate.

allan

On Mon, Oct 3, 2016 at 12:13 PM, PELUARD Mickael
 wrote:
> Hello,
>
>
>
> we used Fujitsu scanner (fi-5110 / fi-5120 / fi-6110) for a
> long time with an old linux plateform and sane (1.0.22-9). These scanners
> used the fujitsu backend.
>
>
>
> We have recently changed to RHEL-6 with sane-backends-1.0.21
> and to Debian with libsane-1.0.25.
>
>
>
> We scan in lineart mode and we only put the threshold option
> to reduce the size of document : scanimage –d ‘fujitsu:XXX:XXX’ --resolution
> 150  --mode lineart  --threshold 140
>
> Then we convert the image to PDF-A1. With the old plateform
> and rhel-6, no problem. But with Debian and sane-1.0.25, the size of the
> documents increase a lot.
>
>
>
> Using a reference document, we get the following results with a fi-6110 :
>
> -  Rhel-6 / sane-1.0.21 = around 50 ko
>
> -  Debian / sane-1.0.25-2 = around 350 ko
>
> It’s quite the same problem if we used a fi-5110c and fi-5120c.
>
>
>
> I downgrade the libsane package and look the result :
>
> -  Debian / libsane-1.0.22-7 = good
>
> -  Debian / libsane-1.0.23-3+b1 = good
>
> -  Debian / libsane-1.0.24-1 = NOT GOOD
>
> -  Debian / libsane-1.0.24-8u5 = NOT GOOD
>
> -  Debian / libsane-1.0.26Git = NOT GOOD
>
>
>
> I change the value of threshold on Debian with sane-1.0.25 : threshold 0 or
> 200. But the image don’t change. It’s look like the threshold option has not
> effect.
>
> To reduce the problem, I play with the contrast and brightness option but
> the result is not entirely satisfactory.
>
>
>
> I think the problem is on the threshold option of the fujitsu backends.
>
>
>
> It is probably the same bug but it don’t lokk corrected in 1.0.26 :
>
> https://alioth.debian.org/tracker/?group_id=30186=410366=detail=315069
>
>
>
> Cordially.
>
>
> --
> 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



-- 
"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] Canon Scanner P-208 II

[m. allan noah]

The canon_dr sane backend already has a deskew option. It is a
software implementation, as only the most expensive Canon machines
have hardware deskew.

I might be able to borrow from the canon driver, if it has a
compatible license with sane, and the source is truly included. Do you
have a link?

In the meantime, the brightness and contrast controls provided by the
backend might help.

allan


On Fri, Sep 23, 2016 at 3:53 AM, Thomas Geier  wrote:
> Hi,
>
> I think this is the known state for this scanner, which are the same as for
> the P-208 (without II). There is a Sane driver that can be downloaded from
> Canon with sources included. Apparently it was built against a very old
> version of sane, and I was not able to compile it. Maybe the missing parts
> (e.g. for color calibration and deskew) can be taken from this code?
>
> Best,
>
> Thomas
>
>
> On 21.09.2016 22:56, Oliver Jan Krylow wrote:
>
> Hello!
>
> Currently on the supported devices page the device "P-208II | USB |
> 0x1083/0x165f" is listed as "Untested".
>
> I'd like to announce a my test results for that device.
>
> Frontend :Simple Scan 3.20.0 under Fedora 24
> Backend : canon_dr:libusb
> Sane version: 1.0.25
> Manufacturer: Canon
> Device: P-208II
>
> What works
> --
>
> * All resolutions as specified in specifications
> * Simplex and Duplex ("Scan multiple images" in frontend needs to be used)
> * Staple Scans
>
> What does not work
> --
>
> * Everything "CaptureOnTouch"-related
> * "Auto Start" switch on the device has to be set to "OFF", otherwise the
> device will not be found
> * Automatic de-skew
> * White page ignore on staple scan
> * Poor colour calibration
> * See sample : https://box.bugabinga.net/cloud/index.php/s/HZKAgFbsQd4Ix08
> * See (manually) colour corrected sample to get an idea as to what was
> roughly expected:
> https://box.bugabinga.net/cloud/index.php/s/JxAbh2Md2stwfPG
>
>
>
> Thank you for your efforts and let me know if there is more for me to test,
>
> O.
>
>
>
>
>
> --
> 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



-- 
"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] [Janitorial] Zero(!) compiler warnings

[m. allan noah]

On Wed, Sep 21, 2016 at 9:12 AM, Olaf Meeuwissen
 wrote:
> Hi devs,
>
> About a year ago, I set out trying to get rid of *all* compiler warnings
> on a "well-defined" build platform.  I'm happy to report that we've made
> it!  With the commit of ee550e5d[1], the debian-8-full build[2], is free
> of compiler warnings!

My goodness! Now how will I know if the build is working, without all
the noise :) Nice work!

> ... next are four linker warnings about the use of `mktemp`, which, as
> we all know, is racey and should be avoided.  Like the plague, so I'd
> like to see these get fixed.
>
> # I have a patch for the avision backend already.  By all means, tackle
> # any of the canon, canon_dr and dc25 backends' use of mktemp.

Note: it is canon that is busted, canon_dr does not use mktemp.

I'm not sure if any of these four backends are maintained anymore.

Any thoughts on sending some kind of email to a committer, or to a
mailing list when we trip that -Werror?

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] Canoscan Lide 220 not works... :(

[m. allan noah]

What version of sane-backends are you running?

allan

On Tue, Sep 20, 2016 at 8:46 AM, csola48  wrote:
>
>
> --
> 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



-- 
"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] SANE-Backend for Brother PDS-series scanner

[m. allan noah]

On Sun, Sep 18, 2016 at 6:25 AM, Olaf Meeuwissen
<paddy-h...@member.fsf.org> wrote:
> Hi Allan,
>
> I just dashed off a rather long explation to James and the list.
>
> m. allan noah writes:
>
>> I personally am of the opinion that Brother is in violation of our
>> license. However, our license is not strictly GPL, and the differences
>> were clearly not written by a lawyer. You could argue that we give
>> some space for a company to steal our work, and keep it from their
>> users.
>
> The sane-backends source code contains files that are GPL and some that
> are GPL with an exception.  The exception is similar in spirit to what
> the LGPL allows and was, IIRC, added before (or around) the LGPL was
> introduced.  As long as they only used GPL with exception code (based on
> library symbols, I they did), there isn't really anything you can object
> to (unless you also object to using LGPL'd code ;-).

Well, I disagree on that point. In my mind, the key words in the
exception are 'an executable'. At the time the exception was added,
many people believed that free OS's were the way of the future, but we
would still be using large numbers of closed-source, shrink-wrapped
apps. The exception seems to have been intended to allow userspace
programs like StarOffice to initiate scanning. This is different from
linking SANE to a library, even if that library acts as a SANE
backend. I think it is a stretch to call Brother's usage in a backend
'an executable'. Yes, a library contains executable code, but it
cannot be started from the command line without a front-end.

>
> Personally, I wished that more of the sane-backends code is GPL, making
> it harder for folks to take what we share without sharing back.

I also wish we could change it, but it is too late. There have been
too many authors over too many years. There is a good chance that a
few of the authors have died. It would be very difficult to identify
entire files which could have their license changed.

When I added sanei_magic, I seriously debated making it GPL. But, I
decided that I could not find a way to convert my backends (which
needed to use it) to the GPL as well.

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] "No: command not found" when building sane-backends

[m. allan noah]

Hmm, sounds like fig2dev is missing on your machine, and we mistakenly
tested for it and let the string 'no' sneak thru when it was not
found. Looks like Olaf worked on this in cc8f99b9

allan

On Sat, Sep 17, 2016 at 12:50 PM, Tristan Miller
 wrote:
> Greetings.
>
> I'm trying to build sane-backends cloned from the Git repository.  This
> inevitably fails with the following error:
>
> Making all in doc
> make[1]: Entering directory '/home/psy/git/sane-backends/doc'
> no -L eps figs/area.fig figs/area.eps
> make[1]: no: Command not found
> Makefile:972: recipe for target 'figs/area.eps' failed
> make[1]: *** [figs/area.eps] Error 127
> make[1]: Leaving directory '/home/psy/git/sane-backends/doc'
> Makefile:542: recipe for target 'all-recursive' failed
> make: *** [all-recursive] Error 1
>
> The Sane FAQ at  addresses this
> problem for the case of building Xsane, but not sane-backends.  The suggested
> solution (passing --disable-nls to the configure script) has no effect.
>
> It seems this problem has been reported elsewhere on the web (e.g.,  lists.debian.org/debian-user/2016/08/msg00484.html> and  questions/1101439/error-building-sane-backend-on-debian>) but no solutions
> have been posted.  Can anyone help?
>
> I am using openSUSE 42.1 on an x86-64 system.
>
> Regards,
> Tristan
>
> --
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>   Tristan Miller
> Free Software developer, ferret herder, logologist
>  https://logological.org/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>
> --
> 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



-- 
"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] SANE-Backend for Brother PDS-series scanner

[m. allan noah]

I personally am of the opinion that Brother is in violation of our
license. However, our license is not strictly GPL, and the differences
were clearly not written by a lawyer. You could argue that we give
some space for a company to steal our work, and keep it from their
users. I vote with my money, and don't buy their products.

allan

On Fri, Sep 16, 2016 at 11:21 AM, James A. Robinson
 wrote:
> I was wondering whether or not any of the developers here know the
> story behind the Brother scanner drivers?   They offer a Debian
> package that identifies itself as GPL, and that claims it is based
> on sane-backends.When I asked them about getting ahold the
> source (I want to port it to ARM), I got the stock "thank you for
> choosing...  unfortunately we cannot support all models..." answer.
>
> I can't tell if that means that
>
> (a) they aren't really obligated to release their driver under the
> GPL, and mislabeled the Debian package as such.
>
> (b) they are obligated because they derived it from GPLed code, and
> are not following their obligations under that license.
>
> I did specifically mention the GPL confusion, but they didn't
> bother to address that point in their reply.
>
> The copyright file from the debian binary package
> http://support.brother.com/g/b/downloadlist.aspx?c=us=en=pds6000_us_eu_as=128
> says:
>
> Name : brother-pds-sane
> Version : 1.0.0
> Release : 4
> Architecture: amd64
> Install Date: (not installed)
> Group : Applications/System
> Size : 14276902
> License : GPL
> Signature : (none)
> Source RPM : brother-pds-sane-1.0.0-4.src.rpm
> Build Date : 2015年05月28日 (週四) 16時34分37秒
> Build Host : Brother
> Relocations : (not relocatable)
> Packager : Brother Industries, Ltd.
> Vendor : Brother Industries, Ltd.
> Summary : SANE-Backend for Brother PDS-series scanner
> Description :
> SANE-Backend for Brother PDS-series scanner. It based on sane-backends, so
> we need install sane-backends package first.
>
> --
> 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



-- 
"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] Search interface for sane-devel archive down?

[m. allan noah]

The sane project controls neither of the sites you link to. They are
maintained by former project members. I suggest you do a google site
search like so:

site:https://lists.alioth.debian.org/pipermail/sane-devel/ 'your search terms'

allan

On Tue, Sep 13, 2016 at 2:50 PM, James A. Robinson
 wrote:
> So http://sane-project.meier-geinitz.de/mailing-lists.html offers a link to
> a search interface that appears to be down:
> http://sane.informatik.uni-freiburg.de/htdig/search.html. Has the search
> engine moved?
>
> Jim
>
>
> --
> 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



-- 
"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] Testing a Canon imageFormula P-150M

[m. allan noah]

The canon machines with the autostart switch have two different usb
ids. I know neither of those for the P-150 or P-150M, so neither of
them would be in the config file. This makes me wonder if something is
wrong with your chronology- I don't think scanimage -L could have
found the scanner before you changed to config file. If you can get
back to that state, where the scanner was trying to work, we can do
some debugging:

SANE_DEBUG_CANON_DR=35 scanimage > foo.pnm 2>p150.log

then send me p150.log directly. You may need to compress it.

allan

On Sat, Aug 13, 2016 at 3:20 PM, Ben J  wrote:
> Hi, I've got a P-150M and am trying to get it running at the moment. The
> scanner was detected by scanimage -L as a P-150. I'm running Arch Linux 64
> bit with no frontend for SANE.
>
> When I tried to trigger a scan, SANE was able to detect that the document
> feeder was empty and that the cover was closed. Once I resolved both of
> these issue, I just got an error stating "scanimage: sane_start: Invalid
> argument." This occurs while running "scanimage -d canon_dr: > test.tiff" as
> root.
>
> So far I've tried to fix this by adding my scanner to
> /etc/sane.d/canon_dr.conf (usb 0x1083 0x162c). I've also tried switching the
> Auto Start switch to on. This caused the error "scanimage: open of device
> canon_dr: failed: Invalid argument" instead.
>
> If anyone has any ideas let me know. I'm comfortable with config files and
> small code changes, but I doubt I could write a full backend for this
> scanner on my own.
>
>
> --
> 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



-- 
"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] Fujitsu fi-6240

[m. allan noah]

The fi-6240 will work out of the box with any recent version of
sane-backends (libsane) and gscan2pdf comes with most Linux distros.
However, I don't know of anything that will parse the barcode
separation sheets.

allan

On Tue, Aug 2, 2016 at 7:58 AM, C Peeters  wrote:
> I would like to use my Fujitsu fi-6240 scanner, in combination with a Linux 
> or Mac computer, to scan documents to PDF using barcode separation sheets. I 
> have currently set this up and working with a Win7 machine using the the 
> ScandAll PRO software, but I prefer to move away from Windows. I would really 
> need to have this configured and packaged by someone capable as my technical 
> knowledge is limited on this aspect. Can anyone help me here? Thanks, Chris.
> --
> 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



-- 
"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] Canon Lide scanners stopped working in Ubuntu 16.04

[m. allan noah]

Sounds like we have some problem with the genesys backend. Can you
compile an older version of sane-backends (perhaps 1.0.24, or whatever
version Ubuntu 14.04 used)? If that works, then you can do a git
bisect, and find where it breaks. If that does not work, I think we
are looking at something else different in the newer Ubuntu, like
libusb or the kernel.

allan

On Tue, Jun 21, 2016 at 2:31 PM, Dmitry B  wrote:
> Hi everybody. Recently I used Canon Lide scanners 110 and 220. They used to
> work in Ubuntu 14.04. In 16.04 they stopped working. I see an error message
> "Device I/O error". There are many bug reports on Ubuntu's Launchpad, but
> they look like abandoned:
>
> https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1588878
> https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1587853
> https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1391038
>
> The version of libsane is 1.0.25+git20150528-1ubuntu2 . I also tried to
> build my own version from Debian experimental (1.0.26~git20151121-1), but
> this didn't help.
>
> The first link contains debugging information collected with scanimage -L/-T
> and debugging environment variables. In there any chance to fix Caon Lide
> scanners support?
>
> --
> 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



-- 
"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] SANE website on GitLab Pages (was Re: GitLab mirrors, GitLab-CI builds and GitLab Pages)

[m. allan noah]

Hmm, recently I have been getting this from the nightly cron
/home/groups/sane/bin/update-htdocs.sh

chgrp: changing group of `./.git/index': Operation not permitted

Is that related to a change you have made here?

allan

On Tue, Jun 21, 2016 at 9:23 AM, Olaf Meeuwissen
 wrote:
> Hi allan,
>
> First, a bit of background is probably in order.  I am playing around on
> GitLab trying to automate parts of the SANE development process.  Some
> of this is done already at Alioth but I get the impression that Alioth
> is not good enough or at least behind the curve.
>
> Below are my findings with respect to the website repository and the
> project's home pages at http://www.sane-project.org/
>
> I am mostly looking for advice/feedback on how to proceed and improve.
> With that in the back of your head, please read on.
>
> Olaf Meeuwissen writes:
>
>> [... based on the GitLab mirror of the website repository ...]
>> The website is rebuilt with every sync/commit as well and, if the build
>> was successfull and passed the tests, "deployed" to
>>
>>   https://sane-project.gitlab.io/
>>
>> Right now, there is very little testing going on (and even if there is a
>> problem the tests succeed).  Also, not all of the current website is up
>> yet.  Consider this a work in progress.
>
> I've been poking around a bit on alioth.debian.org, specifically in
> /home/groups/sane/bin/ in an attempt to reduce the error count on the
> GitLab Pages.  At the moment, these pages aims to mirror what's on
> www.sane-project.org but I'd like to give that a bit of an update (and
> face lift).
>
> Anyway, of the scripts in that directory make-git-snapshots.sh and
> update-htdocs.sh appear to run daily.  The update-lists.sh and
> update-search.sh scripts seem to run approximately weekly.  All this
> appears to be coordinated by kitno-guest cron jobs on alioth.
>
> I've got the make-git-snapshots and update-lists parts covered in my CI
> builds just fine (apart from the daily trigger but that can be solved,
> see https://gitlab.com/help/ci/triggers/README.md which actually makes
> me believe that commits to sane-backends can be used to trigger updates
> for the website, cool!).
>
> # Just noticed that the snapshots/ index doesn't render.  That's due to
> # the GitLab Pages being static and not backed by a web server HTMLizing
> # directory listings :-(  Todays tarballs *are* there, though.
>
> I even have the update-sanei-docs part covered.  The official website is
> using something that was generated 2011-01-31 by the looks of it.  Guess
> the lack of doxygen on alioth is to blame for that.  Is that right?
>
> With the above I think I have most of update-htdocs covered.  The only
> thing that seems to be missing is the relink to the old-archive.  That
> is a static directory and I am pondering how to get this integrated
> without undue overhead with every rebuild of the GitLab Pages site.
>
> The CGI interfaces to search the old-archive and supported device lists
> (input files maintained by update-search.sh?)  are something that won't
> work on a static site as exposed by the GitLab Pages.  The device lists
> might still work through an SPA (single page application) but the
> old-archive is too big to handle that way.  Do we still need it?
>
> The unused-driver-cvs.sh script seems to be unused.  Is that right?
>
> While going through getting this to work, I was wondering why the HTML'd
> manual pages and SANE API specs were not updated.  Apart from the latest
> released and current development version issue, I got the impression
> that part of the reason is that alioth doesn't have the required tools
> installed in order to automate this.  That would also explain why these
> files are in the website repository.  Still, automating this would beat
> the manual maintenance that is used now.
>
> The dlh source code[1] was last released in 1998 and isn't packaged by
> any distribution that I know of.  The man2html convertor originates from
> a BSD clone somewhere out there, is not compatible with Debian's
> man2html and seems abandoned as of 2003[2].
>
>  [1] ftp://ftp.cs.arizona.edu/dlh/
>  [2] 
> http://cvs.savannah.gnu.org/viewvc/man2html/man2html?root=man2html=log
>
> I did get man2html to work on Debian 8 but wasn't able to get dlh to do
> anything useful.  FTR, these two are used when you run
>
>   make -C doc html-man
>   make -C doc sane-html
>
> respectively.
>
> Seeing the current, rather sad, state of affairs, I got an urge to
> replace these fossilized tools with something more up-to-date.  Any
> suggestions?
>
> # Actually, I have also been toying with the idea of converting all the
> # documentation to reStructuredText.  There's plenty of tools that can
> # convert that to HTML, manual pages, PDF and what not.  I have recently
> # started using Sphinx[3] @the-office and that seems to support qthelp as
> # well as devhelp (for GTK) and applehelp, all of which would ease the
> # integration of the API 

Re: [sane-devel] Fwd: Canon DR-2580C commands hang with libusb: warning [libusb_code] ...

[m. allan noah]

Well, I don't have any good ideas, really, other than upgrading to a
newer kernel, a newer libusb, and/or a newer sane-backends.
Sane-backends can be built to use libusb1, so it does not need the
compat layer. That might help.

allan

On Sun, Jun 19, 2016 at 6:25 PM, Maarten Hoogendoorn <maar...@moretea.nl> wrote:
> No, I'm not getting any error messages in dmesg, just the registration:
>
> [ 6674.588453] usb 3-3.3: new high-speed USB device number 30 using xhci_hcd
> [ 6674.677625] usb 3-3.3: New USB device found, idVendor=04a9,
> idProduct=1608
> [ 6674.677632] usb 3-3.3: New USB device strings: Mfr=1, Product=2,
> SerialNumber=0
> [ 6674.677636] usb 3-3.3: Product: CANON   DR-2580C
> [ 6674.677654] usb 3-3.3: Manufacturer: CANON
>
> Would that point to a libusb bug?
>
> I've on which packages the sane package on nixos depends.
> I believe the relevant versions are:
>
> libusb-1.0.19
> libusb-compat-0.1.5
> sane-backends-1.0.24.73-g6c4f6bc
>
>
> 2016-06-18 22:25 GMT+02:00 m. allan noah <kitno...@gmail.com>:
>>
>> That message implies a kernel or libusb bug. Do you see any errors
>> around that time when you run dmesg?
>>
>> allan
>>
>> On Sat, Jun 18, 2016 at 3:47 PM, Maarten Hoogendoorn <maar...@moretea.nl>
>> wrote:
>> > Hi all,
>> >
>> > I've some problems with my ADF scanner. It's a Canon DR-2580C.
>> >
>> > Scanning works fine, as in: the pnm files get created and contain valid
>> > content, but scanimage does not terminate! It hangs after the following
>> > warning:
>> >
>> > libusb: warning [libusb_close] internal signalling write failed, closing
>> > anyway
>> >
>> > Some background information:
>> >
>> > I'm running nixos-unstable.
>> >
>> > $ scanimage -V
>> > scanimage (sane-backends) 1.0.25git; backend version 1.0.25
>> >
>> > $ scanimage -L
>> > device `v4l:/dev/video0' is a Noname Integrated Camera virtual device
>> > device `canon_dr:libusb:003:013' is a CANON DR-2580C scanner
>> >
>> > $ cat /sys/bus/usb/devices/3-2.2/power/control
>> > on
>> >
>> > ==> I don't believe that this is cause by usb autosuspend
>> >
>> > Furthermore, I had the scanner connected directly to my Thinkpad's USB
>> > port
>> >
>> > $ SANE_DEBUG_CANON_DR=30 scanimage -d 'canon_dr:libusb:003:013'
>> > --resolution=300 > 2580-1.pnm 2>2580-1.log
>> >
>> > This just hangs. The 2580-1.log can be found in [1], but I have included
>> > the
>> > last few lines of the log below:
>> >
>> > [canon_dr] sane_cancel: finish
>> > [canon_dr] sane_close: start
>> > [canon_dr] disconnect_fd: start
>> > [canon_dr] disconnecting usb device
>> > libusb: warning [libusb_close] internal signalling write failed, closing
>> > anyway
>> >
>> > Do you have any clue what might be the problem?
>> >
>> > Thanks,
>> > Maarten
>> >
>> > [1] http://maarten-hoogendoorn.nl/public-uploads/sane/2580-1.log
>> >
>> > --
>> > 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
>>
>>
>>
>> --
>> "well, I stand up next to a mountain- and I chop it down with the edge
>> of my hand"
>
>



-- 
"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] Burnt out bulb canoscan 110

[m. allan noah]

CIS machines don't have separate bulbs, they have a series of tricolor
LEDs that are integrated into the optical module. If the LEDs are not
lighting, I'd guess you have some other problem. What version of
sane-backends are you using?

allan

On Tue, Jun 14, 2016 at 10:42 AM, George S.  wrote:
> Hello - Apparently I have the problem named in the subject.  The scanner
> works, but I just get a black scan.  Where can I get a bulb?
>
> Thanks.  George
>
> --
> 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



-- 
"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] Comment about a patch

[m. allan noah]

hmm, slowing every call to sanei_usb_write_bulk by every backend, just
because some ancient discontinued scanner cannot keep up with modern
system speeds? The place to put this hack is in the plustek backend,
not the shared usb library.

allan

On Sat, Jun 11, 2016 at 12:16 PM, Jörg Frings-Fürst
 wrote:
> Hello,
>
> I need a comment about the patch at[1].
>
> Many thanks!
>
>
> CU
> Jörg
> (sane-backends Maintainer at Debian)
>
>
> [1] 
> https://alioth.debian.org/tracker/?func=detail=410366=315288_id=30186
> --
> New:
> GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
> GPG key (long) : 09F89F3C8CA1D25D
> GPG Key: 8CA1D25D
> CAcert Key S/N : 0E:D4:56
>
> Old pgp Key: BE581B6E (revoked since 2014-12-31).
>
> Jörg Frings-Fürst
> D-54538 Bausendorf
>
> Threema: SYR8SJXB
>
> IRC: j_...@freenode.net
>  j_...@oftc.net
>
> My wish list:
>  - Please send me a picture from the nature at your home.
> --
> 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



-- 
"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] Difficulty with HP 5300C in Ubuntu - sane_start: error during device I/O

[m. allan noah]

sane-backends 1.0.23 is pretty old. it is possible a later version of
sane-backends might help.

allan

On Tue, Jun 7, 2016 at 6:42 PM, Jon  wrote:
> Hello,
>
> I've been trying to use my HP 5300C to scan documents in Ubuntu. In the
> past, I had an older HP scanner working before, but it conked out.
>
> Whenever I try to capture an image, I get a variation of "error during
> device I/O"
>
> I've tried gscan2pdf, xsane, simple scan and scanimage.
>
> The only thing that works is the preview function in xsane. xsane's
> preview function produces a perfect image of the document on the scanner,
> but gives me no way to save. I can capture preview images again and again
> with no difficulty.
>
> When I try to do a full scan with xsane, the scanner makes noise, but
> stops partway through. A few minutes later, it produces "Error during
> read: Error during device I/O".
>
> With gscan2pdf on the flatbed or ADF, I get "error during device I/O" on
> attempts to scan.
>
> Once the system has produced "Error during device I/O", I have to power
> cycle the scanner to get any response at all.
>
> Here is the output of some relevant commands:
>
> scanimage -L: device `avision:libusb:001:022' is a Hewlett-Packard ScanJet
> 5300C flatbed scanner
>
> lsusb (removed other lines): Bus 001 Device 022: ID 03f0:0701
> Hewlett-Packard ScanJet 5300c/5370c
>
> apt-show-versions libsane: (some other stuff) 1.0.23-3ubuntu3.1 uptodate
>
> apt-show-versions sane: (some other stuff) 1.0.14-9 uptodate
>
> scanimage -v -p > file.pnm:
> scanimage: scanning image of size 1272x1748 pixels at 24 bits/pixel
> scanimage: acquiring RGB frame
> Progress: 12.3%
> (never finishes)
> Afterwards, the scanner flashes its light 5 times. Flashing the light 5
> times is supposed to correspond to "Home sensor failure OR carriage
> locked"
>
> I'm looking for help getting this scanner working. Since the preview
> function works perfectly, the hardware must be capable of scanning.
>
> For my tasks, I need to use the ADF. However, finding a command that will
> let me save the preview would bring me at least a step forward.
>
> Thanks!
>
>
> --
> 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



-- 
"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] xsane root only

[m. allan noah]

You need to set the permissions of the device file when it is created
by the OS. Different distros handle this in different ways, so I
cannot give you any Mint specific instructions. Generally, you will
look for udev or hal rules or hwdb files, and modify them.  My distro
sets up permissions for this scanner in
/usr/lib/udev/rules.d/65-sane-backends.rules

allan

On Sun, May 8, 2016 at 1:15 PM, tom  wrote:
> xsane 0.998 does not work for me with out root permissions. I found many
> accounts of this on many scanners and many Distros. I have gone thru a
> laundry list of changing ownership, permissions, etc. The problem is
> reported with both USB and parallel scanners. Seems to me that maybe xsane
> is using something in the kernel that it should not be using. Once I sudo
> xsane, it works perfectly. Problem is that besides being a security issue,
> the scanned objects belong to root, so can't open them unless I give gimp,
> etc root permissions. I could change ownership of the immages, but that is
> not a very elegant solution. I can boot an old CentOS 6.0 live DVD session
> and xsane works with out running it as root. Same problems using simple
> scan.
>
> Epson Expression 636 scanner connected via SCSI. Adaptec SCSI card, 32bit
> clone. Mint 17 MATE 32 bit.
>
>
>
> --
> 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



-- 
"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] Need sane docs

[m. allan noah]

Xsane has no networking code in it. Everything you have described so
far sounds like a problem in the brother4 backend. I suggest you try
the same test using scanimage at the command line, and if it is still
slow, compare to the windows driver. If you see a difference, ask
Brother about brother4.

allan

On Thu, May 5, 2016 at 2:05 PM, Gene Heskett  wrote:
> On Thursday 05 May 2016 10:31:53 Richard Ryniker wrote:
>
>> I doubt a gigabit Ethernet connection will make any significant
>> difference.
>
> After investigating the lcd panels network settings for a wired lan, and
> finding the best it can do is 100mbit-fd, that switch isn't going to do
> a lot of good.  But the old one had a port that comes and goes very
> intermittently, so I expect its been tapped by a local lightnings EMP
> somewhere along the 6+ years its been in use here.
>
> I as I said before, can ping it in an average time of .3 milliseconds.
> But when xsane inits on the lan address, on launch from a shell, the
> little "looking for scanners" box is drawn for about 1 screen refresh
> and its wiped.  Then the is a 5 or 6 second pause before xsane draws its
> windows.  Hooked up with a usb cable, the opening screen draws are a
> small fraction of a second being drawn.  And this is perceptually the
> exact same lag as the command delay is. So while its working, I'm of the
> opinion that the command lag is in xsane someplace.
>
> Since 99.9% of the scanners sane runs are hooked up to a USB cable, this
> lag may be a bug someplace that because its so rare, has not been well
> investigated.  The wheel only squeaks on the 29th day of February sort
> of thing. ;-)
>
> According to an xsane -v:
> gene@coyote:/etc$ xsane -v
> xsane-0.998 (c) 1998-2010 Oliver Rauch
>   E-mail: oliver.ra...@xsane.org
>   package xsane-0.996
>   compiled with GTK-2.24.10
>   with color management function
>   with GIMP support, compiled with GIMP-2.6.12
>   XSane output formats: jpeg, pdf(compr.), png, pnm, ps(compr.), tiff,
> txt
>
> From that it looks like its been a while since xsane has had any great
> amount of TLC.  Its also odd that the "about screen" says 0.998, not
> 0.996. ???
>
> Perhaps its time to troll thru the networking code & see if anything
> bites? So I'll renew my offer to serve as a test mule again.
>
> But please don't cut too deep, I am on 7.5 mg of warfarin a day for blood
> thinner. :)  One of those defective takata air bags could kill me long
> before the sirens could be heard in the distance. :(
>
>
>> Data rate from your scanner is dependent on the
>> mechanical speed of the sensor and scan resolution.  If you scan a
>> page 8.5 by 11 inches at 600 pixels per inch resolution with 24 bits
>> per pixel, there is about 100 megabytes of data.  With a 100-megabit
>> Ethernet connection, that is about 10 seconds transmission time.  If
>> your scanner requires 10 seconds for mechanical movement at that
>> resolution, the Ethernet connection should not limit scan speed.
>>
>> At 1200 pixel per inch resolution, there would be four times as much
>> data (400 Mbytes.) This would need roughly 40 seconds to transfer
>> using a 100-megabit Ethernet connection, but your scanner likely moves
>> more slowly at that resolution.  If you can scan faster than 40
>> seconds with a USB connection at that resolution, then gigabit
>> Ethernet might help.  Do you have any reason to believe your machine
>> even supports gigabit Ethernet?  Most do not.
>>
>> Eight seconds instead of two seconds to start a scan sounds like some
>> sort of time-out situation.  The tcpdump command could provide some
>> details about timing of the Ethernet traffic, though interpretation of
>> the data might be a challenge.
>
>
> Cheers, Gene Heskett
> --
> "There are four boxes to be used in defense of liberty:
>  soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> Genes Web page 
>
> --
> 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



-- 
"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] Need sane docs

[m. allan noah]

Gene- if your scanner has ethernet connectivity, you don't need to use
the net backend or saned. Those are basically adapters that allow you
to convert a non-networked scanner into a networked one, by using a
saned server as an intermediary.

I think you need to see if the brother docs list any debugging options
for the brother4 backend. Without more debugging info from that
backend, you are stuck.

allan

On Tue, May 3, 2016 at 11:58 PM, Gene Heskett <ghesk...@shentel.net> wrote:
> On Tuesday 03 May 2016 20:52:35 m. allan noah wrote:
>
>> Well, that implies that we are handing control to the brother4
>> backend, but it is not finding any scanners. Perhaps try the same as
>> root?
>>
>> allan
>
> That wasn't any help, but since the vendor/product was found when I
> plugged in a USB cable, running xsane then found it at the usb bus and
> address, and I ran a few scans.  Seems to work about as expected and I
> believe at a better color accuracy than the epson NX-515 scanner eve
> produced.  The gamma, brightness and contrast controls seemed to work
> backwards but they worked and I finally saved a profile of gamma=1.00,
> brightness and contrast at 0.00 so I'd have a default starting point.
>
> But this unit has its usb and ethernet connections on the top, with a
> molded plastic ditch for cable guidance that leads out the right rear of
> the top cover, using up 2 feet of cable while still inside the machine,
> so the 7 port hub its plugged into is now hanging about 18" up in the
> air with the other 5 cables hanging down from the other face.  hell of a
> way to run a train.  And the next usb extension cord I have is a 10
> meter.
>
> Because the usb hookup is such a kludge,  and I have no problem talking
> to it from a web browser, I would much rather use the ethernet
> connection cable that is driving the printer from cups.
>
> So I am thinking I need something different in the /etc/sane.d/net.conf
> which at the instant looks like this:
> =
> # This is the net backend config file.
>
> ## net backend options
> # Timeout for the initial connection to saned. This will prevent the
> backend
> # from blocking for several minutes trying to connect to an unresponsive
> # saned host (network outage, host down, ...). Value in seconds.
> connect_timeout = 10
>
> ## saned hosts
> # Each line names a host to attach to.
> # If you list "localhost" then your backends can be accessed either
> # directly or through the net backend.  Going through the net backend
> # may be necessary to access devices that need special privileges.
> scanner.coyote.den # this is in my /etc/hosts file defines its ipv4
> # address
> localhost
> ==
> and root@coyote:/etc/sane.d# SANE_DEBUG_NET=255 scanimage -L
> [sanei_debug] Setting debug level of net to 255.
> [net] sane_init: authorize != null, version_code != null
> [net] sane_init: SANE net backend version 1.0.14 (AF-indep+IPv6) from
> sane-backends 1.0.22
> [net] sane_init: Client has little endian byte order
> [net] sane_init: searching for config file
> [net] sane_init: connect timeout set to 10 seconds
> [net] net_avahi_browse_callback: CACHE_EXHAUSTED
> [net] [net] net_avahi_browse_callback: ALL_FOR_NOW
> sane_init: trying to add localhost
> [net] add_device: adding backend localhost
> [net] add_device: backend localhost added
> [net] sane_init: done reading config
> [net] sane_init: evaluating environment variable SANE_NET_HOSTS
> [net] sane_init: evaluating environment variable SANE_NET_TIMEOUT
> [net] sane_init: done
> [net] sane_get_devices: local_only = 0
> [net] connect_dev: trying to connect to localhost
> [net] connect_dev: [0] connection succeeded (IPv4)
> [net] connect_dev: sanei_w_init
> [net] connect_dev: net_init (user=gene, local version=1.0.3)
> [net] connect_dev: freeing init reply (status=Success, remote
> version=1.0.3)
> [net] connect_dev: done
> [net] sane_get_devices: got localhost:brother4:bus2;dev1
> [net] sane_get_devices: finished (1 devices)
> p11-kit: invalid config filename, will be ignored in the
> future: /etc/pkcs11/modules/gnome-keyring-module
> device `brother4:bus2;dev1' is a Brother MFC-J6920DW USB scanner
> device `net:localhost:brother4:bus2;dev1' is a Brother MFC-J6920DW USB
> scanner
> [net] sane_exit: exiting
> [net] net_avahi_cleanup: stopping thread
> [net] net_avahi_cleanup: done
> [net] sane_exit: closing dev 0x97518e8, ctl=296
> [net] sane_exit: finished.
> =
> running xsane shows both paths, but both are usb paths, and chosing the
> one labeled net:localhost:brother4:bus2;dev1, the last one above, gets
> me an invalid argument error. I

Re: [sane-devel] Need sane docs

[m. allan noah]

Well, that implies that we are handing control to the brother4
backend, but it is not finding any scanners. Perhaps try the same as
root?

allan

On Tue, May 3, 2016 at 8:06 PM, Gene Heskett <ghesk...@shentel.net> wrote:
> On Tuesday 03 May 2016 17:54:54 m. allan noah wrote:
>
>> SANE_DEBUG_DLL=255 scanimage -L
>
> And that query returns this enlightening report:
>
> [dll] load: searching backend `brother4' in
> `/usr/lib/i386-linux-gnu/sane:/usr/lib/sane'
> [dll] load: trying to load
> `/usr/lib/i386-linux-gnu/sane/libsane-brother4.so.1'
> [dll] load: couldn't open
> `/usr/lib/i386-linux-gnu/sane/libsane-brother4.so.1' (No such file or
> directory)
> [dll] load: trying to load `/usr/lib/sane/libsane-brother4.so.1'
> [dll] load: dlopen()ing `/usr/lib/sane/libsane-brother4.so.1'
> [dll] load: dlopen() failed (/usr/lib/sane/libsane-brother4.so.1: wrong
> ELF class: ELFCLASS64)
>  Which is a step in the right direction, so it looks as if I need to dl
> the 32 bit version of:
>
> Did that, now the above debug returns this:
>
> [dll] load: searching backend `brother4' in
> `/usr/lib/i386-linux-gnu/sane:/usr/lib/sane'
> [dll] load: trying to load
> `/usr/lib/i386-linux-gnu/sane/libsane-brother4.so.1'
> [dll] load: couldn't open
> `/usr/lib/i386-linux-gnu/sane/libsane-brother4.so.1' (No such file or
> directory)
> [dll] load: trying to load `/usr/lib/sane/libsane-brother4.so.1'
> [dll] load: dlopen()ing `/usr/lib/sane/libsane-brother4.so.1'
> [dll] init: initializing backend `brother4'
> [dll] init: backend `brother4' is version 1.0.1
>
> And then it goes on to the next available backend.  But that is
> essentially what it does to about 5 other active entries in the
> dll.conf.  So I believe itr to be orogress.
>
> But xsane still cannot find it.  Whats the next tracing command to try?
>
> Cheers, Gene Heskett
> --
> "There are four boxes to be used in defense of liberty:
>  soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> Genes Web page <http://geneslinuxbox.net:6309/gene>
>
> --
> 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



-- 
"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] Need sane docs

[m. allan noah]

We cannot really help you on the brother stuff, since it is closed
source, and not produced by us. But, we can suggest that you try the
following:

comment out every line of dll.conf except for the the brother lines
you need, and one other random backend (maybe, fujitsu). Then run:

SANE_DEBUG_DLL=255 scanimage -L

and see if the resulting noise contains any information that might help you.

allan

On Tue, May 3, 2016 at 10:07 AM, Gene Heskett  wrote:
> Greetings all;
>
> I just bought a Brother MFC-J6920DW, and installed the brother linux .deb
> drivers that are "supposed" to let xsane run the scanner.  But xsane
> makes no attempt to access it even if I plug in a USB cable.  It did
> install the name "brother4" in /etc/sane.d/dll.conf, but I can't find
> that name referenced in a strace, ltrace, or latrace output.
> There is no brother4.conf from the installation in that directory tree.
> And locate can't find it either.
>
> So IF I could find a step by step of how any of these names in the
> dll.conf winds up being coupled into sane, it would be a huge help.
>
> It is currently being driven by a cat5 cable, addressed on my local
> 192.168.xx.yy network. And the net entry in the dll is not commented
> out. And it even has a web page at that address.  The printer works for
> some definition of work, its said to be able to do 25 pages a minute,
> but in duplex, less than 2 pages a minute. And it doesn't have a very
> black ink, but that is not a sane problem. Just a heads up to potential
> MFC buyers.
>
> URL's are fine.
>
> Thank you.
>
> Cheers, Gene Heskett
> --
> "There are four boxes to be used in defense of liberty:
>  soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> Genes Web page 
>
> --
> 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



-- 
"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] [sane-standard] Older Version

[m. allan noah]

On Tue, Apr 19, 2016 at 4:11 PM, tom <thomas.w.crans...@gmail.com> wrote:
>
>
> On 04/19/2016 02:51 PM, m. allan noah wrote:
>>
>> On Tue, Apr 19, 2016 at 3:39 PM, tom <thomas.w.crans...@gmail.com> wrote:
>>>
>>>
>>> On 04/19/2016 06:27 AM, m. allan noah wrote:
>>>>
>>>> The Expression 636 is listed as supported by the epson2 backend that
>>>> ships with sane. Does it not work for you?
>>>
>>> No. I was told by Linux Mint Forum that support for the 636 is no longer
>>> in
>>> the linux kernel. I am running Mint 17. I booted Fedora 5 live, and it
>>> would
>>> not run it either. I had it connected with parallel cable, and also
>>> parallel
>>> to USB cable. does sane work with either? I have adaptec card i could add
>>> to
>>> a 32 bit machine and connect with SCSI. What is epson2 backend? not
>>> familiar
>>> with that term. Something I add?
>>>
>> So is it not supported by the kernel, or not supported by sane. Those
>> are two different software packages.
>>
>> allan
>>
> I was told my mint forum that it is no longer supported by the kernel. How
> can I verify? I ran simple scan got message 'scanner (probably) detected -
> may or may not be supported by SANE. Try scanimage -L and read the backends
> manual' I got no results from running scanimage -L


Let's keep the list included in the email, so there is some record.
You might also want to join the mailing list, since this could be a
long conversation :)

Try running the following at the terminal, as the root user:

SANE_DEBUG_EPSON2=255 scanimage -L

and lets see what kind of info you can find in the debugging log.

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] Problem with the Epson DS-560 using the epsonds backend

[m. allan noah]

This looks like the typical Linux USB problem, try using a
sane-backends git snapshot. http://www.sane-project.org/snapshots/

allan

On Tue, Apr 5, 2016 at 7:58 AM, Thorben Schröder
 wrote:
> Hey! I've a question regarding the epsonds backend. I'm trying to get my
> scanner working with the latest 1.0.25 release of sane-backends. I got it to
> a point where it now finds the scanner once when using
>
> scanimage -L
>
> but after that it doesn't find the scanner ever again until I unplug and
> plug it back again (USB).
>
> Here is the debugging output of the scanimage -L command I've used
> (https://gist.github.com/walski/7117f69c9e70b1733c6b14c928050ada):
>
> # First Run:
>
>> sudo SANE_DEBUG_EPSONDS=128 scanimage -L
>> [sanei_debug] Setting debug level of epsonds to 128.
>> [epsonds] sane_epsonds_init: sane-backends 1.0.25
>> [epsonds] epsonds backend, version 1.0.35
>> [epsonds] ** sane_epsonds_get_devices
>> [epsonds] probe_devices
>> [epsonds] attach_one_config: len = 15, line = usb 0x4b8 0x150
>> [epsonds]  user configured device
>> [epsonds] attach_one_usb: dev = libusb:001:006
>> [epsonds] attach: devname = libusb:001:006, type = 1
>> [epsonds] device_detect
>> [epsonds] open_scanner: libusb:001:006
>> [epsonds]  opened correctly
>> [epsonds] eds_lock
>> [epsonds] eds_control: size = 2
>> [epsonds] eds_send: size = 2
>> [epsonds] eds_send: FS X
>> [epsonds] eds_recv: size = 1, buf = 0x7eacc1ff
>> [epsonds] = gathering device information
>> [epsonds] esci2_cmd: INFOx000 len 12, payload len: 0
>> [epsonds] eds_send: size = 12
>> [epsonds] eds_recv: size = 64, buf = 0x7eacc1b0
>> [epsonds] info_cb: nrd / NONE / 4
>> [epsonds] eds_recv: size = 256, buf = 0x1e69ce8
>> [epsonds] info_cb: ADF / TYPEFEED / 8
>> [epsonds]  ADF: sheet feed type
>> [epsonds] info_cb: ADF / DPLX1SCN / 8
>> [epsonds]  ADF: duplex single pass
>> [epsonds] info_cb: ADF / FORDPF1N / 8
>> [epsonds]  ADF: order is 1 to N
>> [epsonds] info_cb: ADF / ALGNCNTR / 8
>> [epsonds]  ADF: center aligned
>> [epsonds] info_cb: ADF / AREAi850i0001400 / 20
>> [epsonds]  ADF: area 850x1400 @ 100dpi
>> [epsonds] info_cb: ADF / AMINi200i205 / 20
>> [epsonds]  ADF: min 200x205 @ 100dpi
>> [epsonds] info_cb: ADF / AMAXi850i0003600 / 20
>> [epsonds]  ADF: max 850x3600 @ 100dpi
>> [epsonds] eds_set_adf_area: 0.00,0.00 215.84,914.34 100
>> [mm]
>> [epsonds] info_cb: ADF / RESOi600 / 12
>> [epsonds]  ADF: basic resolution is 600 dpi
>> [epsonds] info_cb: ADF / RCVR / 4
>> [epsonds]  ADF: auto recovery
>> [epsonds] info_cb: ADF / OVSNd000d039 / 12
>> [epsonds]  ADF: overscan 0x39 @ 100dpi
>> [epsonds] info_cb: IMX / x000x000 / 16
>> [epsonds] info_cb: PRD / h008DS-560   / 12
>> [epsonds]  product: DS-560
>> [epsonds] info_cb: VER / h010IPL 1.00ADF 1.05 / 20
>> [epsonds]  version: IPL 1.00ADF 1.05
>> [epsonds] info_cb: DSZ / i0001536 / 8
>> [epsonds] info_cb: DLS /  / 0
>> [epsonds] info_cb: S/N / h00AU6NZ019428 / 14
>> [epsonds]   serial: U6NZ019428
>> [epsonds] esci2_cmd: CAPAx000 len 12, payload len: 0
>> [epsonds] eds_send: size = 12
>> [epsonds] eds_recv: size = 64, buf = 0x7eacc1c0
>> [epsonds] capa_cb: nrd / NONE / 4
>> [epsonds] eds_recv: size = 228, buf = 0x1e69ce8
>> [epsonds] capa_cb: ADF / DPLX / 4
>> [epsonds]  ADF: duplex
>> [epsonds] capa_cb: ADF / DFL1DFL2 / 8
>> [epsonds]  ADF: double feed detection (high sensitivity)
>> [epsonds] capa_cb: ADF / EJCT / 4
>> [epsonds]  ADF: paper eject
>> [epsonds] capa_cb: ADF / OVSN / 4
>> [epsonds]  ADF: overscan
>> [epsonds] capa_cb: COL / LISTC024M001M008R001R008G001G008B001B008 / 40
>> [epsonds] capa_cb: FMT / LISTJPG  / 8
>> [epsonds] capa_cb: JPG / RANGd001d100 / 12
>> [epsonds] capa_cb: THR / RANGd000d255 / 12
>> [epsonds] capa_cb: GMM / LISTUG10UG18 / 12
>> [epsonds] capa_cb: GMT / LISTRED GRN BLU MONO / 20
>> [epsonds] capa_cb: CMX / LISTUNITUM08 / 12
>> [epsonds] capa_cb: RSM / LISTi300i600 / 20
>> [epsonds] eds_add_resolution: add (dpi): 300
>> [epsonds] eds_add_resolution: add (dpi): 600
>> [epsonds] capa_cb: RSS / LISTi300i60 / 19
>> [epsonds] esci2_cmd: RESAx000 len 12, payload len: 0
>> [epsonds] eds_send: size = 12
>> [epsonds] eds_recv: size = 64, buf = 0x7eacc1c0
>> [epsonds] resa_cb: nrd / NONE / 4
>> [epsonds] resa_cb: par / OK   / 4
>> [epsonds] eds_recv: size = 1184, buf = 0x1e69ce8
>> [epsonds] resa_cb: ADF /  / 0
>> [epsonds] resa_cb: COL / M001 / 4
>> [epsonds] resa_cb: FMT / JPG  / 4
>> [epsonds] resa_cb: JPG / d090 / 4
>> [epsonds] resa_cb: THR / d128 / 4
>> [epsonds] resa_cb: GMM / UG10 / 4
>> [epsonds] resa_cb: $%& /
>> '()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~BLU
>> h100 / 225
>> [epsonds] resa_cb: $%& /
>> 

Re: [sane-devel] Request

[m. allan noah]

The author of XSane is not a member of this mailing list, try
contacting him directly. You might try gscan2pdf and see if you prefer
its behavior.

allan

On Tue, Mar 22, 2016 at 4:01 AM, MR ZenWiz  wrote:
> I have an HP Officejet 5740 which is an all-in-one with two scanning
> methods available - ADF and flatbed.  I'm currently running Xubuntu
> 14.04.4 LTS with all the latest updates, and xsane version 0.998
> (2010!).
>
> I love that sane handles this, but there are two settings that I
> cannot seem to control and they drive me up the wall every time I
> start xsane and don't remember I have to control this.
>
> Whenever I start xsane up for the first time with this scanner, it
> defaults to whatever feeder and resolution I had it set for last,
> which is fine.
>
> However, if I change from the current feeder (whether ADF or Ftalbad),
> it defaults to 75dpi for either new source, and size A for the
> flatbed, or "actual size" (legal) for the ADF.
>
> I routinely scan in forms that I need to fill-in and later print out
> on the same size paper I was given, which here in the US is routinely
> letter size (8.5"x11"), almost always in portrait layout, and 75dpi is
> not enough for a good reproduction for printing.
>
> I can't believe it would be too hard to add a couple of settings so
> the user could control these defaults such that:
>
> 1) I can tell xsane, use 200dpi as the default on EVERY scan,
> regardless of feeder (or at least a setting for each feed method), so
> if I switch feeders, my defaults take priority.
>
> 2) I can tell xsane to use a specific size of my choice WITHOUT having
> to invoke the preview pane and set it manually when I change feeders
> in either direction and back.
>
> It seems to me that if it can remember what I set it to with the
> preview window when I switch between the feeders the first time in
> either direction, it should be able to record this so the next time I
> change feed methods, it will restore what I had set for that feeder's
> defaults.
>
> I may be alone in this method of user xsane, but I can't believe that
> no one ever switches feeders between scans in a single session of use,
> or that people actually like having the software control what the
> resolution and paper size is, regardless of the reality of the paper.
>
> Is that even a possibility?  Is there another method (bugzilla?) where
> I can make this request and have it addressed (any response, even a
> yes or no, would be nice)?
>
> I really like xsane and from what I've seen, it works better than any
> other free scan software for Linux, but with the above deficiencies,
> it feels substandard.  I don't even have any software to compare it to
> since I never use other OSes for this type of function, although my
> photocopiers don't seem to be so deficient in their recognition of
> paper size (and higher default resolution - the norm is 200 on most
> photocopier/scanners Ive used in the last 20 years).
>
> Thank you for your time and anticipated response.
> MR
>
> --
> 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



-- 
"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] Canon DR-C125: Wrong colors when scanning Duplex

[m. allan noah]

Ok, that's better.

The yellow cast along the edge looks like a calibration problem. It
exists in all resolutions under 300 because this scanner only has 300
and 600 dpi modes in the X direction. The sane backend creates all the
lower resolutions. The sane backend also does the coarse and fine
calibration for this model, so it is possible that the calibration
could be improved. However, this is the hardest part of the code to
work with, as it is entirely reverse engineered without docs about the
calibration algorithm.

allan

On Sun, Mar 20, 2016 at 5:55 AM, el-ti <t...@ewetel.net> wrote:
> Wow! Amazing! That did the job – you should be paid by Canon! :-)
>
> There’s only a little color strip (a yellow tint) at one side (for dpi 
> 100-300; 400 and 600 don’t have it), but I guess, we have to live with that.
>
> Really amazing! Thank you so much for your work!
>
> See here: https://de.owncube.com/index.php/s/tJSe7f1Mlq7g1fG
>
> el-ti
>
> Am 20.03.2016 um 02:39 schrieb m. allan noah:
>> Ok, after further digging, I think the margin and color problems are
>> related. I have attached a new patch, please give it a try instead.
>>
>> allan
>>
>> On Sat, Mar 19, 2016 at 5:51 AM, el-ti <t...@ewetel.net> wrote:
>> > Hello Allan,
>> >
>> > I’m afraid, the cdr-55b didn’t change anything – although I don’t 
>> > understand this. I also double checked: first I followed your 
>> > instructions, but thenI unpacked the backends.tar.gz again to apply 
>> > cdr-55b on the fresh files, because I wanted to make sure, I did not make 
>> > a mistake. But even then, the scans returned the same results. Is that 
>> > even possible?
>> >
>> > See here: https://de.owncube.com/index.php/s/Dkqvp3O0hJEVPu7
>> >
>> > best regards,
>> > el-ti
>> >
>> > Am 18.03.2016 um 12:53 schrieb m. allan noah:
>> >> I have attached another patch. We will have to remove the first one,
>> >> and add this new one to the source code directory you made before:
>> >>
>> >> 1. Change into the source directory (update name as required)
>> >> cd sane-backends-gitXX/
>> >>
>> >> 2. Remove the old patch (update location as required, perhaps also 
>> >> ~/Downloads)
>> >> cat ~/Downloads/cdr-55a.diff | patch -p1 -R
>> >>
>> >> 3. Apply the new patch (update location as required, perhaps also 
>> >> ~/Downloads)
>> >> cat ~/Downloads/cdr-55b.diff | patch -p1
>> >>
>> >> 4. Rebuild, reinstall
>> >> make
>> >> sudo make install
>> >>
>> >> 5. Test again.
>> >>
>> >> allan
>> >>
>> >>
>> >> On Fri, Mar 18, 2016 at 6:04 AM, el-ti <t...@ewetel.net> wrote:
>> >>> Oh, I see!
>> >>>
>> >>> Now I did the scans again, each time power cycling the scanner:
>> >>>
>> >>> 1. Power on scanner.
>> >>> 2. Plug scanner in.
>> >>> 3. Start gscan2pdf.
>> >>> 4. Adjust settings and scan and save.
>> >>> 5. Quit gscan2pdf.
>> >>> 6. Plug out scanner.
>> >>> 7. Power off scanner.
>> >>>
>> >>> You can find the results here:
>> >>> https://de.owncube.com/index.php/s/wQuYx6dkz5D8Gau
>> >>>
>> >>> As far as I can see, nothing changed to the previous test. Hope this 
>> >>> helps.
>> >>>
>> >>> el-ti
>> >>>
>> >>>
>> >>> Am 17.03.2016 um 12:20 schrieb m. allan noah:
>> >>>> Yes, the patch changed something, you can look at it and see what it
>> >>>> did, it is fairly small. The problem is that I don't think it should
>> >>>> have changed 240, so if you are seeing a behavior change there, we
>> >>>> need to do further investigation. So, I will be more explicit:
>> >>>>
>> >>>> Please make another set of scans, the same as you last did, but turn
>> >>>> the scanner off and back on between each scan. Presumably you will
>> >>>> have to stop and restart your scanning program too. I want to see if
>> >>>> the earlier scans somehow pollute the later ones.
>> >>>>
>> >>>> After that, I will walk you thru adjusting the code, and we will try 
>> >>>> again.
>> >>>>
>> >>>> allan
>> >>>>
>> >&

Re: [sane-devel] Canon DR-C125: Wrong colors when scanning Duplex

[m. allan noah]

I have attached another patch. We will have to remove the first one,
and add this new one to the source code directory you made before:

1. Change into the source directory (update name as required)
cd sane-backends-gitXX/

2. Remove the old patch (update location as required, perhaps also ~/Downloads)
cat ~/Downloads/cdr-55a.diff | patch -p1 -R

3. Apply the new patch (update location as required, perhaps also ~/Downloads)
cat ~/Downloads/cdr-55b.diff | patch -p1

4. Rebuild, reinstall
make
sudo make install

5. Test again.

allan


On Fri, Mar 18, 2016 at 6:04 AM, el-ti <t...@ewetel.net> wrote:
> Oh, I see!
>
> Now I did the scans again, each time power cycling the scanner:
>
> 1. Power on scanner.
> 2. Plug scanner in.
> 3. Start gscan2pdf.
> 4. Adjust settings and scan and save.
> 5. Quit gscan2pdf.
> 6. Plug out scanner.
> 7. Power off scanner.
>
> You can find the results here:
> https://de.owncube.com/index.php/s/wQuYx6dkz5D8Gau
>
> As far as I can see, nothing changed to the previous test. Hope this helps.
>
> el-ti
>
>
> Am 17.03.2016 um 12:20 schrieb m. allan noah:
>> Yes, the patch changed something, you can look at it and see what it
>> did, it is fairly small. The problem is that I don't think it should
>> have changed 240, so if you are seeing a behavior change there, we
>> need to do further investigation. So, I will be more explicit:
>>
>> Please make another set of scans, the same as you last did, but turn
>> the scanner off and back on between each scan. Presumably you will
>> have to stop and restart your scanning program too. I want to see if
>> the earlier scans somehow pollute the later ones.
>>
>> After that, I will walk you thru adjusting the code, and we will try again.
>>
>> allan
>>
>> On Thu, Mar 17, 2016 at 4:28 AM, el-ti <t...@ewetel.net> wrote:
>> > Hmmm, but the patch changed something, didn’t it? Without the patch 300dpi 
>> > was wrong colors, now 300dpi is good. Unfortunately now 240dpi is wrong.
>> >
>> > If it’s too much work to get it running, It’s maybe okay, I normally do 
>> > color scans with 300dpi. But I would probably consider getting rid of this 
>> > model.
>> >
>> > If by power cycling you mean turning the scanner off and on, before using 
>> > it (after installing the patched version) – yes, I always do that.
>> >
>> > best regards,
>> > el-ti
>> >
>> >
>> > Am 16.03.2016 um 22:11 schrieb m. allan noah:
>> >> My patch did not change anything about 240dpi, since you said that was
>> >> already working. I think perhaps there is something else going on
>> >> here. Can you power cycle the scanner after each test?
>> >>
>> >> allan
>> >>
>> >> On Wed, Mar 16, 2016 at 1:45 PM, el-ti <t...@ewetel.net> wrote:
>> >>> Oh! Mea culpa – I missed that point. But now the scanner works again,
>> >>> and the behavior changed!  – That’s the good news. Not so good news is,
>> >>> that now I have the following:
>> >>>
>> >>> Resolutions 300 and 600 have the right colors.
>> >>>
>> >>> Scanning with 100,150, 200 and 400 is now:
>> >>> Blue -> Green
>> >>> Green -> Red
>> >>> Red -> Blue
>> >>>
>> >>> Scanning with 240 is now:
>> >>> Blue -> Red
>> >>> Red -> Green
>> >>> Green -> Blue
>> >>>
>> >>> I don’t know if it helps, but I created a pdf document with scans in
>> >>> color mode of the same page with the different resolutions in ascending
>> >>> order: 100,150,200,240,300,400,600
>> >>>
>> >>> You can get it here:
>> >>> https://de.owncube.com/index.php/s/KaSuVc4vRFWdOk4
>> >>>
>> >>> What you can also see there, is that there is a color strip on the left
>> >>> side and that the page is a bit shifted horizontally – but this is not
>> >>> our discussed problem at the moment.
>> >>>
>> >>> I hope this helps you.
>> >>>
>> >>> Thanks!
>> >>> el-ti
>> >>>
>> >>> Am 16.03.2016 um 15:01 schrieb m. allan noah:
>> >>>> Did you install libusb-devel before you compiled sane-backends?
>> >>>>
>> >>>> allan
>> >>>>
>> >>>> On Wed, Mar 16, 2016 at 9:29 AM, el-ti <t...@ewetel.net> wrote:
>&g

Re: [sane-devel] Canon DR-C125: Wrong colors when scanning Duplex

[m. allan noah]

Did you install libusb-devel before you compiled sane-backends?

allan

On Wed, Mar 16, 2016 at 9:29 AM, el-ti <t...@ewetel.net> wrote:
> All right, I’m pretty sure I got everything right, but surprisingly the 
> scanner is not detected anymore... ("scanimage -L" only gives back the 
> internal notebook camera) – is it even possible, that this is caused by the 
> steps above? Or did I do something wrong?
>
> Sorry for all the work…
>
>
> Am 16.03.2016 um 13:24 schrieb m. allan noah:
>> 1. Download sane-backends-git snapshot from:
>> http://www.sane-project.org/snapshots/
>>
>> 2. In a terminal, cd to the directory where you downloaded the file
>> (perhaps ~/Downloads)
>> cd ~/Downloads
>>
>> 3. Extract the file (update name as required)
>> tar xzf sane-backends-git.tar.gz
>>
>> 4. Change into the source directory (update name as required)
>> cd sane-backends-gitXX/
>>
>> 5. Apply the patch (update location as required, perhaps also ~/Downloads)
>> cat ~/Downloads/cdr-55a.diff | patch -p1
>>
>> 6. Then you need to follow the instructions at
>> http://www.sane-project.org/README.linux That will have you installing
>> an updated version of sane-backends in /usr/local, where it has a
>> reduced change of causing problems for your system.
>>
>> Let me know if you have questions.
>>
>> allan
>>
>> On Wed, Mar 16, 2016 at 6:38 AM, el-ti <t...@ewetel.net> wrote:
>> > Thank you very much for your work.
>> >
>> > Unfortunately, I have no experience with patching something like this so 
>> > far. I did some research, though – seems to be quite doable. I’m familiar 
>> > with the terminal etc. As I understand this, I have to apply the diff-file 
>> > on the original file with the patch command. So far, so good – but I have 
>> > no idea, which file it is. I couldn’t figure out by looking at the diff 
>> > file.
>> >
>> > If you could tell, on which file I have to apply this, that would be 
>> > great! Thanks!
>> >
>> > Tobias
>> >
>> >
>> > Am 16.03.2016 um 01:33 schrieb m. allan noah:
>> >> I have attached a patch for the sane-backends source code. This
>> >> attempts to provide alternate color de-interlacing for your scanner.
>> >> It does not attempt to fix any edge cropping issues. Let me know if
>> >> you need more instructions.
>> >>
>> >> allan
>> >>
>> >> On Tue, Mar 15, 2016 at 7:59 PM, m. allan noah <kitno...@gmail.com> wrote:
>> >>> Canon scanners often have this variable interlacing at different
>> >>> resolutions, so I am not surprised to see this. However, this
>> >>> particular scanner has the weirdest interlacing that canon does. If
>> >>> you can compile from source, I can send you some patches to try. See
>> >>> http://www.sane-project.org/README.linux
>> >>>
>> >>> allan
>> >>>
>> >>> On Tue, Mar 15, 2016 at 9:17 AM, el-ti <t...@ewetel.net> wrote:
>> >>>> Unfortunately, yes.
>> >>>>
>> >>>> I uninstalled "cndrvsane-drc125" and restartet the system. The color 
>> >>>> shift is still there.
>> >>>>
>> >>>> And there is also the problem, that there is a 1/2 cm cut on the long 
>> >>>> edge of the scanned page (the "duplex-offset" option only handles the 
>> >>>> short edge) – but I guess this is another problem.
>> >>>>
>> >>>> If you need more information, do not hesitate to tell me.
>> >>>>
>> >>>> el-ti
>> >>>>
>> >>>> Am 15.03.2016 um 12:41 schrieb m. allan noah:
>> >>>>> If you uninstall the Canon "DR-C125 Driver for Linux V1.0 (v1.0)"
>> >>>>> software, does this color shift still happen?
>> >>>>>
>> >>>>> allan
>> >>>>>
>> >>>>> On Tue, Mar 15, 2016 at 7:37 AM, el-ti <t...@ewetel.net> wrote:
>> >>>>>> The system is using the libsane version from the PPA: 
>> >>>>>> 1.0.26-git20160305-wily0
>> >>>>>>
>> >>>>>> It was installed above the one from Ubuntu’s repositories, when I 
>> >>>>>> added the PPA.
>> >>>>>>
>> >>>>>>

Re: [sane-devel] Canon DR-C125: Wrong colors when scanning Duplex

[m. allan noah]

Yes, the patch changed something, you can look at it and see what it
did, it is fairly small. The problem is that I don't think it should
have changed 240, so if you are seeing a behavior change there, we
need to do further investigation. So, I will be more explicit:

Please make another set of scans, the same as you last did, but turn
the scanner off and back on between each scan. Presumably you will
have to stop and restart your scanning program too. I want to see if
the earlier scans somehow pollute the later ones.

After that, I will walk you thru adjusting the code, and we will try again.

allan

On Thu, Mar 17, 2016 at 4:28 AM, el-ti <t...@ewetel.net> wrote:
> Hmmm, but the patch changed something, didn’t it? Without the patch 300dpi 
> was wrong colors, now 300dpi is good. Unfortunately now 240dpi is wrong.
>
> If it’s too much work to get it running, It’s maybe okay, I normally do color 
> scans with 300dpi. But I would probably consider getting rid of this model.
>
> If by power cycling you mean turning the scanner off and on, before using it 
> (after installing the patched version) – yes, I always do that.
>
> best regards,
> el-ti
>
>
> Am 16.03.2016 um 22:11 schrieb m. allan noah:
>> My patch did not change anything about 240dpi, since you said that was
>> already working. I think perhaps there is something else going on
>> here. Can you power cycle the scanner after each test?
>>
>> allan
>>
>> On Wed, Mar 16, 2016 at 1:45 PM, el-ti <t...@ewetel.net> wrote:
>> > Oh! Mea culpa – I missed that point. But now the scanner works again,
>> > and the behavior changed!  – That’s the good news. Not so good news is,
>> > that now I have the following:
>> >
>> > Resolutions 300 and 600 have the right colors.
>> >
>> > Scanning with 100,150, 200 and 400 is now:
>> > Blue -> Green
>> > Green -> Red
>> > Red -> Blue
>> >
>> > Scanning with 240 is now:
>> > Blue -> Red
>> > Red -> Green
>> > Green -> Blue
>> >
>> > I don’t know if it helps, but I created a pdf document with scans in
>> > color mode of the same page with the different resolutions in ascending
>> > order: 100,150,200,240,300,400,600
>> >
>> > You can get it here:
>> > https://de.owncube.com/index.php/s/KaSuVc4vRFWdOk4
>> >
>> > What you can also see there, is that there is a color strip on the left
>> > side and that the page is a bit shifted horizontally – but this is not
>> > our discussed problem at the moment.
>> >
>> > I hope this helps you.
>> >
>> > Thanks!
>> > el-ti
>> >
>> > Am 16.03.2016 um 15:01 schrieb m. allan noah:
>> >> Did you install libusb-devel before you compiled sane-backends?
>> >>
>> >> allan
>> >>
>> >> On Wed, Mar 16, 2016 at 9:29 AM, el-ti <t...@ewetel.net> wrote:
>> >>> All right, I’m pretty sure I got everything right, but surprisingly the 
>> >>> scanner is not detected anymore... ("scanimage -L" only gives back the 
>> >>> internal notebook camera) – is it even possible, that this is caused by 
>> >>> the steps above? Or did I do something wrong?
>> >>>
>> >>> Sorry for all the work…
>> >>>
>> >>>
>> >>> Am 16.03.2016 um 13:24 schrieb m. allan noah:
>> >>>> 1. Download sane-backends-git snapshot from:
>> >>>> http://www.sane-project.org/snapshots/
>> >>>>
>> >>>> 2. In a terminal, cd to the directory where you downloaded the file
>> >>>> (perhaps ~/Downloads)
>> >>>> cd ~/Downloads
>> >>>>
>> >>>> 3. Extract the file (update name as required)
>> >>>> tar xzf sane-backends-git.tar.gz
>> >>>>
>> >>>> 4. Change into the source directory (update name as required)
>> >>>> cd sane-backends-gitXX/
>> >>>>
>> >>>> 5. Apply the patch (update location as required, perhaps also 
>> >>>> ~/Downloads)
>> >>>> cat ~/Downloads/cdr-55a.diff | patch -p1
>> >>>>
>> >>>> 6. Then you need to follow the instructions at
>> >>>> http://www.sane-project.org/README.linux That will have you installing
>> >>>> an updated version of sane-backends in /usr/local, where it has a
>> >>>> reduced change of causing problems for your system.

Re: [sane-devel] Canon DR-C125: Wrong colors when scanning Duplex

[m. allan noah]

My patch did not change anything about 240dpi, since you said that was
already working. I think perhaps there is something else going on
here. Can you power cycle the scanner after each test?

allan

On Wed, Mar 16, 2016 at 1:45 PM, el-ti <t...@ewetel.net> wrote:
> Oh! Mea culpa – I missed that point. But now the scanner works again,
> and the behavior changed!  – That’s the good news. Not so good news is,
> that now I have the following:
>
> Resolutions 300 and 600 have the right colors.
>
> Scanning with 100,150, 200 and 400 is now:
> Blue -> Green
> Green -> Red
> Red -> Blue
>
> Scanning with 240 is now:
> Blue -> Red
> Red -> Green
> Green -> Blue
>
> I don’t know if it helps, but I created a pdf document with scans in
> color mode of the same page with the different resolutions in ascending
> order: 100,150,200,240,300,400,600
>
> You can get it here:
> https://de.owncube.com/index.php/s/KaSuVc4vRFWdOk4
>
> What you can also see there, is that there is a color strip on the left
> side and that the page is a bit shifted horizontally – but this is not
> our discussed problem at the moment.
>
> I hope this helps you.
>
> Thanks!
> el-ti
>
> Am 16.03.2016 um 15:01 schrieb m. allan noah:
>> Did you install libusb-devel before you compiled sane-backends?
>>
>> allan
>>
>> On Wed, Mar 16, 2016 at 9:29 AM, el-ti <t...@ewetel.net> wrote:
>>> All right, I’m pretty sure I got everything right, but surprisingly the 
>>> scanner is not detected anymore... ("scanimage -L" only gives back the 
>>> internal notebook camera) – is it even possible, that this is caused by the 
>>> steps above? Or did I do something wrong?
>>>
>>> Sorry for all the work…
>>>
>>>
>>> Am 16.03.2016 um 13:24 schrieb m. allan noah:
>>>> 1. Download sane-backends-git snapshot from:
>>>> http://www.sane-project.org/snapshots/
>>>>
>>>> 2. In a terminal, cd to the directory where you downloaded the file
>>>> (perhaps ~/Downloads)
>>>> cd ~/Downloads
>>>>
>>>> 3. Extract the file (update name as required)
>>>> tar xzf sane-backends-git.tar.gz
>>>>
>>>> 4. Change into the source directory (update name as required)
>>>> cd sane-backends-gitXX/
>>>>
>>>> 5. Apply the patch (update location as required, perhaps also ~/Downloads)
>>>> cat ~/Downloads/cdr-55a.diff | patch -p1
>>>>
>>>> 6. Then you need to follow the instructions at
>>>> http://www.sane-project.org/README.linux That will have you installing
>>>> an updated version of sane-backends in /usr/local, where it has a
>>>> reduced change of causing problems for your system.
>>>>
>>>> Let me know if you have questions.
>>>>
>>>> allan
>>>>
>>>> On Wed, Mar 16, 2016 at 6:38 AM, el-ti <t...@ewetel.net> wrote:
>>>>> Thank you very much for your work.
>>>>>
>>>>> Unfortunately, I have no experience with patching something like this so 
>>>>> far. I did some research, though – seems to be quite doable. I’m familiar 
>>>>> with the terminal etc. As I understand this, I have to apply the 
>>>>> diff-file on the original file with the patch command. So far, so good – 
>>>>> but I have no idea, which file it is. I couldn’t figure out by looking at 
>>>>> the diff file.
>>>>>
>>>>> If you could tell, on which file I have to apply this, that would be 
>>>>> great! Thanks!
>>>>>
>>>>> Tobias
>>>>>
>>>>>
>>>>> Am 16.03.2016 um 01:33 schrieb m. allan noah:
>>>>>> I have attached a patch for the sane-backends source code. This
>>>>>> attempts to provide alternate color de-interlacing for your scanner.
>>>>>> It does not attempt to fix any edge cropping issues. Let me know if
>>>>>> you need more instructions.
>>>>>>
>>>>>> allan
>>>>>>
>>>>>> On Tue, Mar 15, 2016 at 7:59 PM, m. allan noah <kitno...@gmail.com> 
>>>>>> wrote:
>>>>>>> Canon scanners often have this variable interlacing at different
>>>>>>> resolutions, so I am not surprised to see this. However, this
>>>>>>> particular scanner has the weirdest interlacing that canon does. If
>>>>>>> you ca

Re: [sane-devel] Canon DR-C125: Wrong colors when scanning Duplex

[m. allan noah]

1. Download sane-backends-git snapshot from:
http://www.sane-project.org/snapshots/

2. In a terminal, cd to the directory where you downloaded the file
(perhaps ~/Downloads)
cd ~/Downloads

3. Extract the file (update name as required)
tar xzf sane-backends-git.tar.gz

4. Change into the source directory (update name as required)
cd sane-backends-gitXX/

5. Apply the patch (update location as required, perhaps also ~/Downloads)
cat ~/Downloads/cdr-55a.diff | patch -p1

6. Then you need to follow the instructions at
http://www.sane-project.org/README.linux That will have you installing
an updated version of sane-backends in /usr/local, where it has a
reduced change of causing problems for your system.

Let me know if you have questions.

allan

On Wed, Mar 16, 2016 at 6:38 AM, el-ti <t...@ewetel.net> wrote:
> Thank you very much for your work.
>
> Unfortunately, I have no experience with patching something like this so far. 
> I did some research, though – seems to be quite doable. I’m familiar with the 
> terminal etc. As I understand this, I have to apply the diff-file on the 
> original file with the patch command. So far, so good – but I have no idea, 
> which file it is. I couldn’t figure out by looking at the diff file.
>
> If you could tell, on which file I have to apply this, that would be great! 
> Thanks!
>
> Tobias
>
>
> Am 16.03.2016 um 01:33 schrieb m. allan noah:
>> I have attached a patch for the sane-backends source code. This
>> attempts to provide alternate color de-interlacing for your scanner.
>> It does not attempt to fix any edge cropping issues. Let me know if
>> you need more instructions.
>>
>> allan
>>
>> On Tue, Mar 15, 2016 at 7:59 PM, m. allan noah <kitno...@gmail.com> wrote:
>> > Canon scanners often have this variable interlacing at different
>> > resolutions, so I am not surprised to see this. However, this
>> > particular scanner has the weirdest interlacing that canon does. If
>> > you can compile from source, I can send you some patches to try. See
>> > http://www.sane-project.org/README.linux
>> >
>> > allan
>> >
>> > On Tue, Mar 15, 2016 at 9:17 AM, el-ti <t...@ewetel.net> wrote:
>> >> Unfortunately, yes.
>> >>
>> >> I uninstalled "cndrvsane-drc125" and restartet the system. The color 
>> >> shift is still there.
>> >>
>> >> And there is also the problem, that there is a 1/2 cm cut on the long 
>> >> edge of the scanned page (the "duplex-offset" option only handles the 
>> >> short edge) – but I guess this is another problem.
>> >>
>> >> If you need more information, do not hesitate to tell me.
>> >>
>> >> el-ti
>> >>
>> >> Am 15.03.2016 um 12:41 schrieb m. allan noah:
>> >>> If you uninstall the Canon "DR-C125 Driver for Linux V1.0 (v1.0)"
>> >>> software, does this color shift still happen?
>> >>>
>> >>> allan
>> >>>
>> >>> On Tue, Mar 15, 2016 at 7:37 AM, el-ti <t...@ewetel.net> wrote:
>> >>>> The system is using the libsane version from the PPA: 
>> >>>> 1.0.26-git20160305-wily0
>> >>>>
>> >>>> It was installed above the one from Ubuntu’s repositories, when I added 
>> >>>> the PPA.
>> >>>>
>> >>>> el-ti
>> >>>>
>> >>>> Am 15.03.2016 um 12:22 schrieb m. allan noah:
>> >>>>> You have installed both sane-backends, and canon's driver? Which one
>> >>>>> are you using? Assuming you are actually using sane-backends, we will
>> >>>>> have to modify the code to control the color descrambling.
>> >>>>>
>> >>>>> allan
>> >>>>>
>> >>>>> On Tue, Mar 15, 2016 at 6:08 AM, el-ti <t...@ewetel.net> wrote:
>> >>>>>> Hello,
>> >>>>>>
>> >>>>>> I have an appendix to make – maybe someone has a hint for me, why the
>> >>>>>> scanner behaves really strange:
>> >>>>>>
>> >>>>>> Depending on the scanning resolution, the shifting on the color range 
>> >>>>>> is
>> >>>>>> different! I used the following command to test this:
>> >>>>>>
>> >>>>>> scanimage --batch --source "ADF Duplex" --page-width 210
>> >>>>>> --page-he

Re: [sane-devel] Canon DR-C125: Wrong colors when scanning Duplex

[m. allan noah]

I have attached a patch for the sane-backends source code. This
attempts to provide alternate color de-interlacing for your scanner.
It does not attempt to fix any edge cropping issues. Let me know if
you need more instructions.

allan

On Tue, Mar 15, 2016 at 7:59 PM, m. allan noah <kitno...@gmail.com> wrote:
> Canon scanners often have this variable interlacing at different
> resolutions, so I am not surprised to see this. However, this
> particular scanner has the weirdest interlacing that canon does. If
> you can compile from source, I can send you some patches to try. See
> http://www.sane-project.org/README.linux
>
> allan
>
> On Tue, Mar 15, 2016 at 9:17 AM, el-ti <t...@ewetel.net> wrote:
>> Unfortunately, yes.
>>
>> I uninstalled "cndrvsane-drc125" and restartet the system. The color shift 
>> is still there.
>>
>> And there is also the problem, that there is a 1/2 cm cut on the long edge 
>> of the scanned page (the "duplex-offset" option only handles the short edge) 
>> – but I guess this is another problem.
>>
>> If you need more information, do not hesitate to tell me.
>>
>> el-ti
>>
>> Am 15.03.2016 um 12:41 schrieb m. allan noah:
>>> If you uninstall the Canon "DR-C125 Driver for Linux V1.0 (v1.0)"
>>> software, does this color shift still happen?
>>>
>>> allan
>>>
>>> On Tue, Mar 15, 2016 at 7:37 AM, el-ti <t...@ewetel.net> wrote:
>>> > The system is using the libsane version from the PPA: 
>>> > 1.0.26-git20160305-wily0
>>> >
>>> > It was installed above the one from Ubuntu’s repositories, when I added 
>>> > the PPA.
>>> >
>>> > el-ti
>>> >
>>> > Am 15.03.2016 um 12:22 schrieb m. allan noah:
>>> >> You have installed both sane-backends, and canon's driver? Which one
>>> >> are you using? Assuming you are actually using sane-backends, we will
>>> >> have to modify the code to control the color descrambling.
>>> >>
>>> >> allan
>>> >>
>>> >> On Tue, Mar 15, 2016 at 6:08 AM, el-ti <t...@ewetel.net> wrote:
>>> >>> Hello,
>>> >>>
>>> >>> I have an appendix to make – maybe someone has a hint for me, why the
>>> >>> scanner behaves really strange:
>>> >>>
>>> >>> Depending on the scanning resolution, the shifting on the color range is
>>> >>> different! I used the following command to test this:
>>> >>>
>>> >>> scanimage --batch --source "ADF Duplex" --page-width 210
>>> >>> --page-height=297 -l 0 -t 0 -x 210 -y 297 --mode Color --resolution 300
>>> >>>
>>> >>> Then I tried all available resolutions: 100, 150, 200, 240, 300, 400,
>>> >>> 600. The results are strange:
>>> >>>
>>> >>> Scanning with 100,150,200 gives me:
>>> >>> Blue -> Red
>>> >>> Red -> Green
>>> >>> Green -> Blue
>>> >>>
>>> >>> Scanning with 300 and 400 gives me:
>>> >>> Blue -> Green
>>> >>> Green -> Red
>>> >>> Red -> Blue
>>> >>>
>>> >>> And scanning with 240 and 600 shows the RIGHT colors.
>>> >>>
>>> >>> How is that possible? And how can this problem be solved?
>>> >>>
>>> >>>
>>> >>> I installed Rolf Bensch’s PPA
>>> >>> (https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-git), because it
>>> >>> solved the back page cutting problem when scanning Duplex. (see
>>> >>> http://permalink.gmane.org/gmane.comp.graphics.scanning.sane.devel/24903)
>>> >>>
>>> >>> Other than that, I only installed the Canon "DR-C125 Driver for Linux
>>> >>> V1.0 (v1.0)".
>>> >>>
>>> >>> Any hint is appreciated!
>>> >>> el-ti
>>> >>>
>>> >>> Am 04.03.2016 um 10:59 schrieb el-ti:
>>> >>>> Dear Sane-developers and users,
>>> >>>>
>>> >>>> through this very helpful discussion
>>> >>>> (http://permalink.gmane.org/gmane.comp.graphics.scanning.sane.devel/24903),
>>> >>>> I managed to get my Canon Scanner working in Duplex without cutting 1 
>>> 

Re: [sane-devel] Canon DR-C125: Wrong colors when scanning Duplex

[m. allan noah]

Canon scanners often have this variable interlacing at different
resolutions, so I am not surprised to see this. However, this
particular scanner has the weirdest interlacing that canon does. If
you can compile from source, I can send you some patches to try. See
http://www.sane-project.org/README.linux

allan

On Tue, Mar 15, 2016 at 9:17 AM, el-ti <t...@ewetel.net> wrote:
> Unfortunately, yes.
>
> I uninstalled "cndrvsane-drc125" and restartet the system. The color shift is 
> still there.
>
> And there is also the problem, that there is a 1/2 cm cut on the long edge of 
> the scanned page (the "duplex-offset" option only handles the short edge) – 
> but I guess this is another problem.
>
> If you need more information, do not hesitate to tell me.
>
> el-ti
>
> Am 15.03.2016 um 12:41 schrieb m. allan noah:
>> If you uninstall the Canon "DR-C125 Driver for Linux V1.0 (v1.0)"
>> software, does this color shift still happen?
>>
>> allan
>>
>> On Tue, Mar 15, 2016 at 7:37 AM, el-ti <t...@ewetel.net> wrote:
>> > The system is using the libsane version from the PPA: 
>> > 1.0.26-git20160305-wily0
>> >
>> > It was installed above the one from Ubuntu’s repositories, when I added 
>> > the PPA.
>> >
>> > el-ti
>> >
>> > Am 15.03.2016 um 12:22 schrieb m. allan noah:
>> >> You have installed both sane-backends, and canon's driver? Which one
>> >> are you using? Assuming you are actually using sane-backends, we will
>> >> have to modify the code to control the color descrambling.
>> >>
>> >> allan
>> >>
>> >> On Tue, Mar 15, 2016 at 6:08 AM, el-ti <t...@ewetel.net> wrote:
>> >>> Hello,
>> >>>
>> >>> I have an appendix to make – maybe someone has a hint for me, why the
>> >>> scanner behaves really strange:
>> >>>
>> >>> Depending on the scanning resolution, the shifting on the color range is
>> >>> different! I used the following command to test this:
>> >>>
>> >>> scanimage --batch --source "ADF Duplex" --page-width 210
>> >>> --page-height=297 -l 0 -t 0 -x 210 -y 297 --mode Color --resolution 300
>> >>>
>> >>> Then I tried all available resolutions: 100, 150, 200, 240, 300, 400,
>> >>> 600. The results are strange:
>> >>>
>> >>> Scanning with 100,150,200 gives me:
>> >>> Blue -> Red
>> >>> Red -> Green
>> >>> Green -> Blue
>> >>>
>> >>> Scanning with 300 and 400 gives me:
>> >>> Blue -> Green
>> >>> Green -> Red
>> >>> Red -> Blue
>> >>>
>> >>> And scanning with 240 and 600 shows the RIGHT colors.
>> >>>
>> >>> How is that possible? And how can this problem be solved?
>> >>>
>> >>>
>> >>> I installed Rolf Bensch’s PPA
>> >>> (https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-git), because it
>> >>> solved the back page cutting problem when scanning Duplex. (see
>> >>> http://permalink.gmane.org/gmane.comp.graphics.scanning.sane.devel/24903)
>> >>>
>> >>> Other than that, I only installed the Canon "DR-C125 Driver for Linux
>> >>> V1.0 (v1.0)".
>> >>>
>> >>> Any hint is appreciated!
>> >>> el-ti
>> >>>
>> >>> Am 04.03.2016 um 10:59 schrieb el-ti:
>> >>>> Dear Sane-developers and users,
>> >>>>
>> >>>> through this very helpful discussion
>> >>>> (http://permalink.gmane.org/gmane.comp.graphics.scanning.sane.devel/24903),
>> >>>> I managed to get my Canon Scanner working in Duplex without cutting 1 cm
>> >>>> of the back page.
>> >>>>
>> >>>> Everything seems to work fine. However, I discovered a very strange
>> >>>> behaviour regarding the colour management: When scanning in simplex
>> >>>> mode, everything works fine. There is no page cutting and colours are as
>> >>>> they should be. But in duplex mode, the colours are somehow shifted on
>> >>>> the colour range: Blue is scanned as green, green is scanned as red, red
>> >>>> is scanned as blue (for both back and front page).
>> >>>>
>> >>>> Is there an easy solution for this? Or did I forget to install 
>> >>>> something?
>> >>>>
>> >>>> Thank you very much!
>> >>>> el-ti
>> >>>>
>> >>>
>> >>>
>> >>> --
>> >>> 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
>> >>
>> >>
>> >>
>> >
>>
>>
>>
>



-- 
"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] external backend license

[m. allan noah]

There are too many authors, some now missing. It is unfortunately
unrealistic to change the license now.

allan

On Tue, Mar 15, 2016 at 12:46 PM, Alessandro Zummo
<azummo-li...@towertech.it> wrote:
> On Tue, 15 Mar 2016 07:40:04 -0400
> "m. allan noah" <kitno...@gmail.com> wrote:
>
>> Third, the intention of the exception in the sane license was to allow
>> closed-source front ends to link to sane without becoming polluted. It
>> was not done to allow closed-source backends to re-use the internals
>> of sane-backends.
>
>  maybe it's time to remove this exception...
>
> --
>
>  Best regards,
>
>  Alessandro Zummo - CEO,
>   Tower Technologies - Torino, Italy
>
>   http://www.towertech.it
>



-- 
"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] Canon DR-C125: Wrong colors when scanning Duplex

[m. allan noah]

If you uninstall the Canon "DR-C125 Driver for Linux V1.0 (v1.0)"
software, does this color shift still happen?

allan

On Tue, Mar 15, 2016 at 7:37 AM, el-ti <t...@ewetel.net> wrote:
> The system is using the libsane version from the PPA: 1.0.26-git20160305-wily0
>
> It was installed above the one from Ubuntu’s repositories, when I added the 
> PPA.
>
> el-ti
>
> Am 15.03.2016 um 12:22 schrieb m. allan noah:
>> You have installed both sane-backends, and canon's driver? Which one
>> are you using? Assuming you are actually using sane-backends, we will
>> have to modify the code to control the color descrambling.
>>
>> allan
>>
>> On Tue, Mar 15, 2016 at 6:08 AM, el-ti <t...@ewetel.net> wrote:
>> > Hello,
>> >
>> > I have an appendix to make – maybe someone has a hint for me, why the
>> > scanner behaves really strange:
>> >
>> > Depending on the scanning resolution, the shifting on the color range is
>> > different! I used the following command to test this:
>> >
>> > scanimage --batch --source "ADF Duplex" --page-width 210
>> > --page-height=297 -l 0 -t 0 -x 210 -y 297 --mode Color --resolution 300
>> >
>> > Then I tried all available resolutions: 100, 150, 200, 240, 300, 400,
>> > 600. The results are strange:
>> >
>> > Scanning with 100,150,200 gives me:
>> > Blue -> Red
>> > Red -> Green
>> > Green -> Blue
>> >
>> > Scanning with 300 and 400 gives me:
>> > Blue -> Green
>> > Green -> Red
>> > Red -> Blue
>> >
>> > And scanning with 240 and 600 shows the RIGHT colors.
>> >
>> > How is that possible? And how can this problem be solved?
>> >
>> >
>> > I installed Rolf Bensch’s PPA
>> > (https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-git), because it
>> > solved the back page cutting problem when scanning Duplex. (see
>> > http://permalink.gmane.org/gmane.comp.graphics.scanning.sane.devel/24903)
>> >
>> > Other than that, I only installed the Canon "DR-C125 Driver for Linux
>> > V1.0 (v1.0)".
>> >
>> > Any hint is appreciated!
>> > el-ti
>> >
>> > Am 04.03.2016 um 10:59 schrieb el-ti:
>> >> Dear Sane-developers and users,
>> >>
>> >> through this very helpful discussion
>> >> (http://permalink.gmane.org/gmane.comp.graphics.scanning.sane.devel/24903),
>> >> I managed to get my Canon Scanner working in Duplex without cutting 1 cm
>> >> of the back page.
>> >>
>> >> Everything seems to work fine. However, I discovered a very strange
>> >> behaviour regarding the colour management: When scanning in simplex
>> >> mode, everything works fine. There is no page cutting and colours are as
>> >> they should be. But in duplex mode, the colours are somehow shifted on
>> >> the colour range: Blue is scanned as green, green is scanned as red, red
>> >> is scanned as blue (for both back and front page).
>> >>
>> >> Is there an easy solution for this? Or did I forget to install something?
>> >>
>> >> Thank you very much!
>> >> el-ti
>> >>
>> >
>> >
>> > --
>> > 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
>>
>>
>>
>



-- 
"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] external backend license

[m. allan noah]

First, let me state that I am not a lawyer, and much of what follows
is my opinion or interpretation.

Second, we have seen time and again that your users will be better
served by an open backend. If you keep the code closed, you will be
unable to support users on fringe platforms, (Do you build for the
BSDs? Do you build for unusual CPUs?) and you will probably fail to
keep up with changing times (when the Linux kernel has a new ABI in 4
years, are you going to provide recompiled versions?). Please
reconsider using the GPL.

Third, the intention of the exception in the sane license was to allow
closed-source front ends to link to sane without becoming polluted. It
was not done to allow closed-source backends to re-use the internals
of sane-backends.

Fourth, you are certainly free to use sane.h in your code, and
implement a backend from scratch. That is why sane.h is in the public
domain.  The questionable part is the use of sanei_* and related code
in a closed source backend. I believe this is against the spirit of
the exception. However, the exception is poorly worded, and could be
taken to allow static linking of sanei with an external backend. I
would not risk doing so without talking to my employer's lawyers
first.

allan


On Mon, Mar 14, 2016 at 10:43 PM, ky gcp  wrote:
> Hi,
>
> I hope someone have answers to my licensing concern. Based on the text for
> the exception, they put an exception into the GPL license so that it acts
> like the LGPL license. This allows linking (probably dynamic) against the
> library, but would not cover compiling directly with the code.
>
> 1) If we compile our external backend with the sane-backends source, does it
> cover the exception? or does it mean that our external backend should
> automatically be shipped under GPL license?
>
> 2) Is it possible to compile an external backend without the sane-backends
> source?
>
> 3) Is there a developers guide for SANE external backends that says that you
> should compile directly with the sane-backends source?
>
> Thank you for your support.
>
> --
> 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



-- 
"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] Canon DR-C125: Wrong colors when scanning Duplex

[m. allan noah]

You have installed both sane-backends, and canon's driver? Which one
are you using? Assuming you are actually using sane-backends, we will
have to modify the code to control the color descrambling.

allan

On Tue, Mar 15, 2016 at 6:08 AM, el-ti  wrote:
> Hello,
>
> I have an appendix to make – maybe someone has a hint for me, why the
> scanner behaves really strange:
>
> Depending on the scanning resolution, the shifting on the color range is
> different! I used the following command to test this:
>
> scanimage --batch --source "ADF Duplex" --page-width 210
> --page-height=297 -l 0 -t 0 -x 210 -y 297 --mode Color --resolution 300
>
> Then I tried all available resolutions: 100, 150, 200, 240, 300, 400,
> 600. The results are strange:
>
> Scanning with 100,150,200 gives me:
> Blue -> Red
> Red -> Green
> Green -> Blue
>
> Scanning with 300 and 400 gives me:
> Blue -> Green
> Green -> Red
> Red -> Blue
>
> And scanning with 240 and 600 shows the RIGHT colors.
>
> How is that possible? And how can this problem be solved?
>
>
> I installed Rolf Bensch’s PPA
> (https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-git), because it
> solved the back page cutting problem when scanning Duplex. (see
> http://permalink.gmane.org/gmane.comp.graphics.scanning.sane.devel/24903)
>
> Other than that, I only installed the Canon "DR-C125 Driver for Linux
> V1.0 (v1.0)".
>
> Any hint is appreciated!
> el-ti
>
> Am 04.03.2016 um 10:59 schrieb el-ti:
>> Dear Sane-developers and users,
>>
>> through this very helpful discussion
>> (http://permalink.gmane.org/gmane.comp.graphics.scanning.sane.devel/24903),
>> I managed to get my Canon Scanner working in Duplex without cutting 1 cm
>> of the back page.
>>
>> Everything seems to work fine. However, I discovered a very strange
>> behaviour regarding the colour management: When scanning in simplex
>> mode, everything works fine. There is no page cutting and colours are as
>> they should be. But in duplex mode, the colours are somehow shifted on
>> the colour range: Blue is scanned as green, green is scanned as red, red
>> is scanned as blue (for both back and front page).
>>
>> Is there an easy solution for this? Or did I forget to install something?
>>
>> Thank you very much!
>> el-ti
>>
>
>
> --
> 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



-- 
"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] sane_read() parameters

[m. allan noah]

Yes- the value of maxlen is determined by the frontend. You cannot
change it, and you certainly cannot re-alloc. You should have your own
buffer in the backend, and read bytes from it into the buffer provided
by the frontend. This type of double buffering will allow you to read
from the scanner in whatever block size is best, and then respond to
the frontend however it wants. I recommend that you not make your
backend buffer very large (to save memory), but you then have to be
careful not to overflow it when the frontend is draining it slowly.

allan

On Wed, Mar 9, 2016 at 1:14 AM, ky gcp <kygcpsam...@gmail.com> wrote:
> Thank you for such quick response, allan. Do you mean to say that the value
> of maxlen is determined by the frontend? On xsane application, maxlen value
> is 8192 when using acquire preview and then value of maxlen is 65536 when
> using scan function. Our external backend currently reads images by row on
> sane_read(). Issue occurs when using acquire preview on colored A3 original
> because the number of bytes per row is more than the value of maxlen. If I
> reallocate the argument buf to a much bigger size, xsane closes and I get
> this error message below:
> *** stack smashing detected ***: xsane terminated
> Aborted (core dumped)
>
> Since our external backend currently reads images by row on sane_read(), is
> it better to just change our implementation on sane_read() ?
>
> On Wed, Mar 9, 2016 at 9:39 AM, m. allan noah <kitno...@gmail.com> wrote:
>>
>> Because different frontends have different requirements. Some try to
>> save memory, some try to maximize speed by using large buffers, some
>> try to fill a network packet exactly. You can (and should expect) to
>> get any value of maxlen from 1 byte to perhaps a 1M, maybe more.
>>
>> allan
>>
>> On Tue, Mar 8, 2016 at 8:23 PM, ky gcp <kygcpsam...@gmail.com> wrote:
>> > why does the value of maxlen vary from various frontends?
>> >
>> > On Tue, Mar 8, 2016 at 9:06 PM, m. allan noah <kitno...@gmail.com>
>> > wrote:
>> >>
>> >> maxlen is provided by the caller of the function, to tell the backend
>> >> how much memory the caller has allocated for image data.
>> >>
>> >> allan
>> >>
>> >> On Tue, Mar 8, 2016 at 3:09 AM, ky gcp <kygcpsam...@gmail.com> wrote:
>> >> > hi,
>> >> >
>> >> > how is the argument maxlen determined in sane_read() function?
>> >> >
>> >> > SANE_Status sane_read (SANE_Handle h, SANE_Byte * buf, SANE_Int
>> >> > maxlen,
>> >> > SANE_Int * len);
>> >> >
>> >> > Thanks for your help.
>> >> >
>> >> > --
>> >> > 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
>> >>
>> >>
>> >>
>> >> --
>> >> "well, I stand up next to a mountain- and I chop it down with the edge
>> >> of my hand"
>> >
>> >
>>
>>
>>
>> --
>> "well, I stand up next to a mountain- and I chop it down with the edge
>> of my hand"
>
>



-- 
"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