Re: [sane-devel] daily git snapshots

[Rolf Bensch]

Hi Olaf,

The cron job seems running. I can download the daily git snapshots.

I just pushed some commits to gitlab. But I cannot find the immediately
builds on the website.

Cheers,
Rolf

Am 06.03.2018 um 13:20 schrieb Olaf Meeuwissen:
> Hi Rolf,
> 
> Rolf Bensch writes:
> 
>> Hi Olaf
>>
>> Am 04.03.2018 um 02:52 schrieb Olaf Meeuwissen:
>>> ...
>>>
>>> Sorry about that.  Should be fixed now.
>>
>> The last file on the website is from 28-Feb-2018 00:05
> 
> Should be fixed now.  Looks like something is wrong with the changes I
> made to the script and/or permission issues with me running the script
> manually and Allan's cron job running it.  Will have a look.
> 
>>> # Not quite sure why that happened but I suspect I made a mistake with
>>> # the ln command.  It doesn't seem to be caused by the update-htdocs.sh
>>> # script.  IIUC, that script runs daily.
>>>
>>> Anyway, given the (in)frequency with which our repositories are pushed
>>> to I wonder if it makes sense to drop the daily git snapshots in favour
>>> of the source tarballs created by our CI setup on every push.
>>>
>>> # Sometimes weeks go by without a commit ;-)
>>>
>>> The git snapshots are *not* the same as the source tarballs.  The former
>>> are the result of
>>>
>>>   git archive --format=tar --prefix=sane-backends-$(date +%Y%m%d) master
>>>
>>> whereas the latter are the result of
>>>
>>>   make dist
>>
>> This is exactly what I need.
> 
> If that's the case, you may want to take a look at changing the URL you
> fetch your source tarballs from.  The details[1] are on GitLab, but you
> basically want to grab
> 
>  
> https://gitlab.com/sane-project/$project/builds/artifacts/master/download?job=archive
> 
> and use the sane-$project-*.tar.gz that's in the zip'd archive that that
> URL provides.  This works for $project values of backends and frontends.
> There may be other files in the zip'd archive but those are intended for
> the website so you can safely ignore those.
> 
>  [1]: https://docs.gitlab.com/ce/user/project/pipelines/job_artifacts.html
> 
> You can also take a peek at
> 
>  alioth.debian.org:/home/groups/sane/bin/make-git-snapshots.sh
> 
> which does something similar for the Alioth hosted website.
> 
>>> So the latter are equivalent to what we eventually release.
>>>
>>> How easy/hard would it be to change things on your end to use the CI
>>> source tarballs?  Should I submit an issue for that on GitLab?
>>>
>>> ...
>>
>> On my point of view, daily git snapshots without any changes make no sense.
> 
> That's exactly why I asked.  We now have CI builds with every push.
> These are guaranteed to have a change.  It doesn't really matter how
> often they happen, once a month or every five minutes ;-)
> A new source tarball will be created for *every* push unless the build
> fails.  Even so, the last successfull source tarball will be available
> from the URL above.
> 
> 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

Re: [sane-devel] How can I help with Canon Maxify MB2000 series testing?

[Rolf Bensch]

Hi Patrick,

I just added button support for your scanner.

If you're fetching the sources from git you can start testing now.
Otherwise you must wait 'til tomorrow to get the update from my ppa.

Button support is basicly implemented in standard frontends. You should
use gscan2pdf to get best results. Or if you're familiar programming
bash scripts, you can use scanbd
(https://sourceforge.net/projects/scanbd/). If you like I can provide my
pixma scripts.

Hope this helps.

Cheers,
Rolf

Am 05.02.2018 um 12:44 schrieb Patrick Roncagliolo:
> Feedback on MB2350 button support:
> 
>> SANE_DEBUG_PIXMA=11 scanimage -A
> 
> Buttons:
>     --button-update
>         Update button state
>     --button-1  [0] [read-only]
>         Button 1
>     --button-2  [0] [read-only]
>         Button 2
>     --original  [0] [read-only]
>         Type of original to scan
>     --target  [0] [read-only]
>         Target operation type
>     --scan-resolution  [0] [read-only]
>         Scan resolution
> 
> I noticed that when scanimage is listening for button control, if I go
> Home->Scan->PC on the scanner touch panel, I see as available target of
> the scan:
> - "patrick patrick-desktop"  (if connected by lan)
> - "Locale (USB)" (if connected by USB)
>  
> Then, If I press the green color scan button, the pixma backend behaves
> differently:
> LAN: logs four rows of data
> USB: among a low-rate burst of most-zeros logs and warnings, a different
> line appears when i press the button
> 
> Note that the two rows "00 00 00 00 01 01 01 01  01 00 01 01 01 01 02
> 02" appear when I press SCAN in both USB and LAN mode.
> 
> After pressing the scan button, the scanner displays the message
> "scanning..." for approx 20 seconds, without any sign of flatbed
> activity, then returns to the scan UI page without any errors. scanimage
> continues to listen.
> 
>> SANE_DEBUG_PIXMA=11 scanimage -d "pixma:MB2300_192.168.1.5"
> --format=jpeg -p --mode Color --resolution 75 --button-controlled=yes
> 
> [pixma]  Button-controlled scan mode is enabled.
> [pixma]  To proceed, press 'SCAN' or 'COLOR' button. To cancel,
> press 'GRAY' or 'END' button.
> [pixma] INTR T=4.634 len=64                                             
>      <<< I PRESSED THE BUTTON >>>
> [pixma]  :00 00 00 00 01 01 01 01  01 00 01 01 01 01 02 02 
> [pixma]  0010:00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 
> [pixma]  0020:00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 
> [pixma]  0030:00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
> 
>> SANE_DEBUG_PIXMA=11 scanimage -d "pixma:04A91779_21CEAB" --format=jpeg
> -p --mode Color --resolution 75 --button-controlled=yes
> 
> [pixma]  Button-controlled scan mode is enabled.
> [pixma]  To proceed, press 'SCAN' or 'COLOR' button. To cancel,
> press 'GRAY' or 'END' button.
> [pixma] INTR T=0.768 len=32
> [pixma]  :00 00 00 01 00 00 00 00  00 00 00 00 00 00 00 00 
> [pixma]  0010:00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 
> [pixma] 
> [pixma] WARNING:send_time() disabled!
> [pixma] INTR T=1.024 len=32
> [pixma]  :00 00 00 01 00 00 00 00  00 00 00 00 00 00 00 00 
> [pixma]  0010:00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 
> [pixma] 
> [pixma] WARNING:send_time() disabled!
> [pixma] INTR T=2.688 len=32
> [pixma]  :00 00 00 01 00 00 00 00  00 00 00 00 00 00 00 00 
> [pixma]  0010:00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 
> [pixma] 
> [pixma] WARNING:send_time() disabled!
> [pixma] INTR T=11.136 len=32                                           
>       <<< I PRESSED THE BUTTON >>>
> [pixma]  :00 00 00 00 01 01 01 01  01 00 01 01 01 01 02 02    
> [pixma]  0010:00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 
> [pixma] 
> [pixma] INTR T=13.696 len=32
> [pixma]  :00 00 00 01 00 00 00 00  00 00 00 00 00 00 00 00 
> [pixma]  0010:00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00 
> 
> 
> 
> 
> Il giorno dom 4 feb 2018 alle ore 18:54 Patrick Roncagliolo
> <ronca@gmail.com <mailto:ronca@gmail.com>> ha scritto:
> 
> Hi Rolf, 
> MB2350 supports only one-side scan ADF. I used USBPcapCMD.exe to get
> a USB log from windows (Wireshark on Windows do not support direct
> USB port capturing AFAIK). 
> I sent you .pcap files of one-sheet and two-sheets scans from Win. 
> 
> Il giorno dom 4 feb 2018 alle ore 13:14 Patrick Roncagliolo
> <ronca@gmail.com <mailto:ronca@gmail.com>> ha scritto:
> 
> Oh I see, thank you so much. I'll give you USB logfiles ASAP.

Re: [sane-devel] How can I help with Canon Maxify MB2000 series testing?

[Rolf Bensch]

Hi Patrick,

Many thanks for the log file.

I found some differences to the implemented settings. For comparison
please send a logfile from a normal flatbed scan.

Cheers,
Rolf

Am 04.02.2018 um 19:45 schrieb Patrick Roncagliolo:
> Hi Rolf, 
> MB2350 supports only one-side scan ADF. I used USBPcapCMD.exe to get a
> USB log from windows (Wireshark on Windows do not support direct USB
> port capturing AFAIK).
> I attach to this message the two dumps, that represent an ADF scan with
> a single page, and an ADF scan with two pages in the ADF. 
> 
> Il giorno dom 4 feb 2018 alle ore 13:14 Patrick Roncagliolo
> <ronca@gmail.com <mailto:ronca@gmail.com>> ha scritto:
> 
> Oh I see, thank you so much. I'll give you USB logfiles ASAP.
> 
> 
> Il dom 4 feb 2018, 13:10 Rolf Bensch <r...@bensch-online.de
> <mailto:r...@bensch-online.de>> ha scritto:
> 
> Hi Patrick,
> 
> Here you can find further infos:
> https://wiki.wireshark.org/CaptureSetup/USB
> 
> You need to connect your scanner via USB and disconnect
> Ethernet|WiFi.
> 
> Hope this helps.
> 
> Cheers,
> Rolf
> 
> 
> Am 04.02.2018 um 12:50 schrieb Patrick Roncagliolo:
> > Hi Rolf,
> >
> > Can you point to a short guide for getting proper USB logfiles?
> >
> > Meanwhile, I noticed that wireshark do not have full support
> for BJNP. I
> > browsed SANE and CUPS sources, and the BJNP dissector, and
> maybe in my
> > spare time I'd like to improve the dissector. If you have any
> unofficial
> > doc or article/analysis about BJNP outside what's already in C
> sources,
> > I'd like to get some links.
> >
> >
> > Il dom 4 feb 2018, 12:44 Rolf Bensch <r...@bensch-online.de
> <mailto:r...@bensch-online.de>
> > <mailto:r...@bensch-online.de <mailto:r...@bensch-online.de>>>
> ha scritto:
> >
> >     Hi Patrick,
> >
> >     It seems that we have a general problem with ADF scanning
> from all
> >     Maxify scanners.
> >
> >     If possible, please provide USB logfiles from a Windows
> machine scanning
> >     from ADF and duplex ADF, one page and two pages, using
> Wireshark. Then I
> >     can try to fix this.
> >
> >     In the meantime I'll update the doc files.
> >
> >     Many thanks for your help.
> >
> >     Cheers,
> >     Rolf
> >
> >     Am 28.01.2018 um 15:26 schrieb Patrick Roncagliolo:
> >     > Hi Rolf,
> >     >
> >     > I tested scanimage with different options today. In
> particular, I
> >     tested
> >     > all the combinations of connection/resolution/color
> available with
> >     > flatbed mode:
> >     >
> >     >  --Connection: usb/net
> >     >  --Resolution: 75/150/300/600/1200
> >     >  --Color: color/gray/lineart
> >     >
> >     > ...for a total of 30 tests. I can confirm that all the
> combinations
> >     > work, I have a folder with all the scans and a script,
> so I can
> >     > replicate the operation while collecting debug info by
> >     > setting SANE_DEBUG_PIXMA if necessary, and share all the
> results
> >     > somewhere (eg. Google Drive). 
> >     >
> >     > But ADF _do not_ work for me using scanimage or scanadf.
> Here's a
> >     sample
> >     > output (SANE_DEBUG_PIXMA=3 PIXMA_EXPERIMENT=1):
> >     >
> >     > [pixma] pixma is compiled with pthread support.
> >     > [pixma] pixma version 0.17.45
> >     > [pixma] pixma_collect_devices() found Canon MAXIFY
> MB2300 Series at
> >     > libusb:003:005
> >     > [pixma] Scanner model found: Name MB2300(Canon MAXIFY
> MB2300 Series)
> >     > matches MB2300 series
> >     > [pixma] pixma_collect_devices() found Canon MAXIFY
> MB2300 Series at
> >     > bjnp://192.168.1.5:8612/timeout=1000
> <http://192.168.1.5:8612/timeout=1000&g

Re: [sane-devel] daily git snapshots

[Rolf Bensch]

Hi Olaf

Am 04.03.2018 um 02:52 schrieb Olaf Meeuwissen:
> ...
> 
> Sorry about that.  Should be fixed now.
> 

The last file on the website is from 28-Feb-2018 00:05

> # Not quite sure why that happened but I suspect I made a mistake with
> # the ln command.  It doesn't seem to be caused by the update-htdocs.sh
> # script.  IIUC, that script runs daily.
> 
> Anyway, given the (in)frequency with which our repositories are pushed
> to I wonder if it makes sense to drop the daily git snapshots in favour
> of the source tarballs created by our CI setup on every push.
> 
> # Sometimes weeks go by without a commit ;-)
> 
> The git snapshots are *not* the same as the source tarballs.  The former
> are the result of
> 
>   git archive --format=tar --prefix=sane-backends-$(date +%Y%m%d) master
> 
> whereas the latter are the result of
> 
>   make dist
> 

This is exactly what I need.

> So the latter are equivalent to what we eventually release.
> 
> How easy/hard would it be to change things on your end to use the CI
> source tarballs?  Should I submit an issue for that on GitLab?
> 
> ...

On my point of view, daily git snapshots without any changes make no sense.

Thanks.
Rolf

-- 
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] daily git snapshots

[Rolf Bensch]

Hi Olaf,

There are no daily git snapshots available on the wesite anymore. I can
only find a folder, which goes into itself.

Cheers,
Rolf


-- 
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] How can I help with Canon Maxify MB2000 series testing?

[Rolf Bensch]

Hi Patrick,

Here you can find further infos:
https://wiki.wireshark.org/CaptureSetup/USB

You need to connect your scanner via USB and disconnect Ethernet|WiFi.

Hope this helps.

Cheers,
Rolf


Am 04.02.2018 um 12:50 schrieb Patrick Roncagliolo:
> Hi Rolf,
> 
> Can you point to a short guide for getting proper USB logfiles?
> 
> Meanwhile, I noticed that wireshark do not have full support for BJNP. I
> browsed SANE and CUPS sources, and the BJNP dissector, and maybe in my
> spare time I'd like to improve the dissector. If you have any unofficial
> doc or article/analysis about BJNP outside what's already in C sources,
> I'd like to get some links.
> 
> 
> Il dom 4 feb 2018, 12:44 Rolf Bensch <r...@bensch-online.de
> <mailto:r...@bensch-online.de>> ha scritto:
> 
> Hi Patrick,
> 
> It seems that we have a general problem with ADF scanning from all
> Maxify scanners.
> 
> If possible, please provide USB logfiles from a Windows machine scanning
> from ADF and duplex ADF, one page and two pages, using Wireshark. Then I
> can try to fix this.
> 
> In the meantime I'll update the doc files.
> 
> Many thanks for your help.
> 
> Cheers,
> Rolf
> 
> Am 28.01.2018 um 15:26 schrieb Patrick Roncagliolo:
> > Hi Rolf,
> >
> > I tested scanimage with different options today. In particular, I
> tested
> > all the combinations of connection/resolution/color available with
> > flatbed mode:
> >
> >  --Connection: usb/net
> >  --Resolution: 75/150/300/600/1200
> >  --Color: color/gray/lineart
> >
> > ...for a total of 30 tests. I can confirm that all the combinations
> > work, I have a folder with all the scans and a script, so I can
> > replicate the operation while collecting debug info by
> > setting SANE_DEBUG_PIXMA if necessary, and share all the results
> > somewhere (eg. Google Drive). 
> >
> > But ADF _do not_ work for me using scanimage or scanadf. Here's a
> sample
> > output (SANE_DEBUG_PIXMA=3 PIXMA_EXPERIMENT=1):
> >
> > [pixma] pixma is compiled with pthread support.
> > [pixma] pixma version 0.17.45
> > [pixma] pixma_collect_devices() found Canon MAXIFY MB2300 Series at
> > libusb:003:005
> > [pixma] Scanner model found: Name MB2300(Canon MAXIFY MB2300 Series)
> > matches MB2300 series
> > [pixma] pixma_collect_devices() found Canon MAXIFY MB2300 Series at
> > bjnp://192.168.1.5:8612/timeout=1000
> <http://192.168.1.5:8612/timeout=1000>
> <http://192.168.1.5:8612/timeout=1000>
> > [pixma] pixma_open(): Canon MAXIFY MB2300 Series
> > [pixma] *mp150_open* This is a generation 5 scanner.  *
> > [pixma] Reader task started
> > [pixma] 
> > [pixma] [pixma] Reader task id=139915254597376 (threaded)
> > scanimage: scanning image of size 638x1050 pixels at 24 bits/pixel
> > scanimage: acquiring RGB frame
> > pixma_scan(): start
> > [pixma]   line_size=1914 image_size=2009700 channels=3 depth=8
> > [pixma]   dpi=75x75 offset=(0,0) dimension=638x1050
> > [pixma]   gamma_table=0x704fc8 source=1
> > [pixma]   threshold=127 threshold_curve=0
> > [pixma]   adf-wait=0
> > [pixma]   ADF page count: 0
> > [pixma] WARNING:send_time() disabled!
> > [pixma] Current status: paper=0 cal=0 lamp=0 busy=0
> > [pixma] pixma_scan() failed ECANCELED
> > [pixma] read_image():reader task closed the pipe:0 bytes received,
> > 2009700 bytes expected
> > [pixma] Reader task terminated: ECANCELED
> > scanimage: min/max graylevel value = 255/0
> > scanimage: sane_read: Operation was cancelled
> > [pixma] pixma_close(): Canon MAXIFY MB2300 Series
> >
> > Seems that pages in the ADF are not recognised: see "ADF page
> count=0".
> >
> >
> > Il giorno sab 27 gen 2018 alle ore 18:05 Rolf Bensch
> > <r...@bensch-online.de <mailto:r...@bensch-online.de>
> <mailto:r...@bensch-online.de <mailto:r...@bensch-online.de>>> ha
> scritto:
> >
> >     Hi Patrick,
> >
> >     Please scan all scan options (color, grayscale, lineart, 75...600
> >     dpi) from flatbed.
> >
> >     Then test the document feeder with your preferred settings
> (e.g. A4,
> >     300 dpi) and the whole sheet size. With a single sheet and
> multiple
> >     sh

Re: [sane-devel] Canon MG3050

[Rolf Bensch]

Hi,

Your scanner should work. Please try the scanner connected via USB and
report your results.

Hope this helps.

Cheers,
Rolf


Am 29.01.2018 um 16:23 schrieb kamp0...@arcor.de:
> Hi,
>
>
> can I check if the MG3050 is still supported without inserting cartridges?
>
> I need a sane supported scanner, otherwise I still can return the device.
>
>
> http://www.sane-project.org/sane-mfgs.html
>
> Current sane status:
>
> PIXMA MG3000 Series     USB WiFi     0x04a9/0x180b     Untested    
> Testers needed!
>
>
> Thanks.
>
> Regards,
> Kamp
>
>
>


-- 
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] How can I help with Canon Maxify MB2000 series testing?

[Rolf Bensch]

Hi Louis,

Please try to fix this issue. The main problem are special needed
settings in function send_scan_param() (command 0xde20) from
pixma_mp150.c. You can fetch correct settings from reference scans from
a Windows machine.

To check button support, you can use this simple test:

1. push any button

2. $ SANE_DEBUG_PIXMA=11 scanimage -A

If you scanner has button support, you should get a similar response:

[...]
  Buttons:
    --button-update
    Update button state
[pixma] INTR T=1.165 len=32
[pixma]  :00 20 00 00 00 00 00 00  00 00 00 00 00 00 00 00
[pixma]  0010:00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
[pixma]
    --button-1  [1] [read-only]
    Button 1
    --button-2  [0] [read-only]
    Button 2
    --original  [0] [read-only]
    Type of original to scan
    --target  [2] [read-only]
    Target operation type
    --scan-resolution  [0] [read-only]
    Scan resolution
[...]

Important are existing lines starting with [pixma]. With this info it's
simple to enable button support.

Hope this helps.

Cheers,
Rolf


Am 29.01.2018 um 20:40 schrieb Louis Lagendijk:
> On Sun, 2018-01-28 at 14:26 +, Patrick Roncagliolo wrote:
>> Hi Rolf,
>>
>> I tested scanimage with different options today. In particular, I
>> tested all the combinations of connection/resolution/color available
>> with flatbed mode:
>>
>>  --Connection: usb/net
>>  --Resolution: 75/150/300/600/1200
>>  --Color: color/gray/lineart
>>
>> ...for a total of 30 tests. I can confirm that all the combinations
>> work, I have a folder with all the scans and a script, so I can
>> replicate the operation while collecting debug info by
>> setting SANE_DEBUG_PIXMA if necessary, and share all the results
>> somewhere (eg. Google Drive). 
>>
>> But ADF _do not_ work for me using scanimage or scanadf. Here's a
>> sample output (SANE_DEBUG_PIXMA=3 PIXMA_EXPERIMENT=1):
> This sounds the same as the status on my MB5050. You may also want to
> test the button support: that probably does not work either.
>
> BR, 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

Re: [sane-devel] How can I help with Canon Maxify MB2000 series testing?

[Rolf Bensch]

Hi Patrick,

It seems that we have a general problem with ADF scanning from all
Maxify scanners.

If possible, please provide USB logfiles from a Windows machine scanning
from ADF and duplex ADF, one page and two pages, using Wireshark. Then I
can try to fix this.

In the meantime I'll update the doc files.

Many thanks for your help.

Cheers,
Rolf

Am 28.01.2018 um 15:26 schrieb Patrick Roncagliolo:
> Hi Rolf,
> 
> I tested scanimage with different options today. In particular, I tested
> all the combinations of connection/resolution/color available with
> flatbed mode:
> 
>  --Connection: usb/net
>  --Resolution: 75/150/300/600/1200
>  --Color: color/gray/lineart
> 
> ...for a total of 30 tests. I can confirm that all the combinations
> work, I have a folder with all the scans and a script, so I can
> replicate the operation while collecting debug info by
> setting SANE_DEBUG_PIXMA if necessary, and share all the results
> somewhere (eg. Google Drive). 
> 
> But ADF _do not_ work for me using scanimage or scanadf. Here's a sample
> output (SANE_DEBUG_PIXMA=3 PIXMA_EXPERIMENT=1):
> 
> [pixma] pixma is compiled with pthread support.
> [pixma] pixma version 0.17.45
> [pixma] pixma_collect_devices() found Canon MAXIFY MB2300 Series at
> libusb:003:005
> [pixma] Scanner model found: Name MB2300(Canon MAXIFY MB2300 Series)
> matches MB2300 series
> [pixma] pixma_collect_devices() found Canon MAXIFY MB2300 Series at
> bjnp://192.168.1.5:8612/timeout=1000 <http://192.168.1.5:8612/timeout=1000>
> [pixma] pixma_open(): Canon MAXIFY MB2300 Series
> [pixma] *mp150_open* This is a generation 5 scanner.  *
> [pixma] Reader task started
> [pixma] 
> [pixma] [pixma] Reader task id=139915254597376 (threaded)
> scanimage: scanning image of size 638x1050 pixels at 24 bits/pixel
> scanimage: acquiring RGB frame
> pixma_scan(): start
> [pixma]   line_size=1914 image_size=2009700 channels=3 depth=8
> [pixma]   dpi=75x75 offset=(0,0) dimension=638x1050
> [pixma]   gamma_table=0x704fc8 source=1
> [pixma]   threshold=127 threshold_curve=0
> [pixma]   adf-wait=0
> [pixma]   ADF page count: 0
> [pixma] WARNING:send_time() disabled!
> [pixma] Current status: paper=0 cal=0 lamp=0 busy=0
> [pixma] pixma_scan() failed ECANCELED
> [pixma] read_image():reader task closed the pipe:0 bytes received,
> 2009700 bytes expected
> [pixma] Reader task terminated: ECANCELED
> scanimage: min/max graylevel value = 255/0
> scanimage: sane_read: Operation was cancelled
> [pixma] pixma_close(): Canon MAXIFY MB2300 Series
> 
> Seems that pages in the ADF are not recognised: see "ADF page count=0".
> 
> 
> Il giorno sab 27 gen 2018 alle ore 18:05 Rolf Bensch
> <r...@bensch-online.de <mailto:r...@bensch-online.de>> ha scritto:
> 
> Hi Patrick,
> 
> Please scan all scan options (color, grayscale, lineart, 75...600
> dpi) from flatbed.
> 
> Then test the document feeder with your preferred settings (e.g. A4,
> 300 dpi) and the whole sheet size. With a single sheet and multiple
> sheets. At least test duplex scanning from ADF, single sheet and
> multiple sheets.
> 
> I'm getting the best ADF scan results with gscan2pdf (I really never
> got best results using scanimage or xsane). For scanning single
> sheets from flatbed or ADF (one side only) you can use your favorite
> frontend, e.g. xsane.
> 
> If you might have problems, please test also connected with USB only.
> 
> Many thanks for report.
> 
> Cheers,
> Rolf
> 
> 
> Am 26.01.2018 um 00:33 schrieb Patrick Roncagliolo:
>> I forgot to specify that obviously SANE driver worked and allowed
>> me to do some scans with Xsane and ScanImage.
>> My reference to ScanGearMP is simply for completeness, but does
>> not relate with the main point of my previous mail.
>>
>> So, rephrasing:  "I can say LibSane works with MB2350 via LAN
>> connection".
>>
>> Il giorno ven 26 gen 2018 alle ore 00:27 Patrick Roncagliolo
>> <ronca@gmail.com <mailto:ronca@gmail.com>> ha scritto:
>>
>> Hello, 
>> I saw testers are needed for this series of scanners.
>>
>> I have a Canon Maxify MB2350 scanner, connected through LAN. 
>> I can detect the scanner from Canon ScanGearMP 3.40 from
>> Ubuntu Linux 16.04. 
>> I added "bjnp://192.168.1.5 <http://192.168.1.5>" to my
>> pixma.conf file, where 192.168.1.5 is my scanner IP address.
>> LibSane is taken from the daily git snapshots from
>> RolfBensch's PPA (now: 1.0.27+git201

Re: [sane-devel] How can I help with Canon Maxify MB2000 series testing?

[Rolf Bensch]

Hi Patrick,

Please scan all scan options (color, grayscale, lineart, 75...600 dpi)
from flatbed.

Then test the document feeder with your preferred settings (e.g. A4, 300
dpi) and the whole sheet size. With a single sheet and multiple sheets.
At least test duplex scanning from ADF, single sheet and multiple sheets.

I'm getting the best ADF scan results with gscan2pdf (I really never got
best results using scanimage or xsane). For scanning single sheets from
flatbed or ADF (one side only) you can use your favorite frontend, e.g.
xsane.

If you might have problems, please test also connected with USB only.

Many thanks for report.

Cheers,
Rolf


Am 26.01.2018 um 00:33 schrieb Patrick Roncagliolo:
> I forgot to specify that obviously SANE driver worked and allowed me
> to do some scans with Xsane and ScanImage.
> My reference to ScanGearMP is simply for completeness, but does not
> relate with the main point of my previous mail.
>
> So, rephrasing:  "I can say LibSane works with MB2350 via LAN connection".
>
> Il giorno ven 26 gen 2018 alle ore 00:27 Patrick Roncagliolo
> > ha scritto:
>
> Hello, 
> I saw testers are needed for this series of scanners.
>
> I have a Canon Maxify MB2350 scanner, connected through LAN. 
> I can detect the scanner from Canon ScanGearMP 3.40 from Ubuntu
> Linux 16.04. 
> I added "bjnp://192.168.1.5 " to my pixma.conf
> file, where 192.168.1.5 is my scanner IP address.
> LibSane is taken from the daily git snapshots from RolfBensch's
> PPA (now: 1.0.27+git20180122).
>
> _I can say it works._ But I hope to help more if I can. So: is
> there a way to do something useful other than scanning a random
> sheet of paper? Do you have standard tests or data collection
> procedure that could help you to improve support or verify that
> all is working great? Do you need some packet sniffing or
> something like that?
>
> Best regards,
> Patrick Roncagliolo
>

-- 
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 Canon i-SENSYS MF633cdw Support

[Rolf Bensch]

Hi Wojciech,

Please check the version of SANE you are using:
$ scanimage -V

How did you connect your scanner? For testing it should connected on an
USB port.

A remark to your installation: Please remove your self compiled SANE
from your system and follow the install description from the file
INSTALL.linux, which comes with the sources.

Hope this helps.

Cheers,
Rolf


Am 23.01.2018 um 12:46 schrieb Wojciech Teichert:
> pixma.log have one line: scanimage: no SANE devices found
>
> 2018-01-22 19:34 GMT+01:00 Rolf Bensch <r...@bensch-online.de
> <mailto:r...@bensch-online.de>>:
>
> Hi Wojciech,
>
> Please provide a logfile created with:
>
> $ SANE_DEBUG_PIXMA=4 scanimage 2> pixma.log > pixma.pnm
>
> Please zip, tar.gz or 7zip pixma.log and send it to me.
>
> Cheers,
> Rolf
>
>
> Am 22.01.2018 um 03:29 schrieb Wojciech Teichert:
>>  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).
>> root@### sane-find-scanner
>>
>>   # sane-find-scanner will now attempt to detect your scanner. If the
>>   # result is different from what you expected, first make sure your
>>   # scanner is powered up and properly connected to your computer.
>>
>>   # No SCSI scanners found. If you expected something different,
>> make sure that
>>   # you have loaded a kernel SCSI driver for your SCSI adapter.
>>
>> found USB scanner (vendor=0x04a9 [Canon], product=0x27e1
>> [MF633C/635C]) at libusb:001:005
>>   # Your USB scanner was (probably) detected. It may or may not
>> be supported by
>>   # SANE. Try scanimage -L and read the backend's manpage.
>>
>>   # Not checking for parallel port scanners.
>>
>>   # Most Scanners connected to the parallel port or other
>> proprietary ports
>>   # can't be detected by this program.
>> root@### 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)
>>
>> This is new version
>> from git://git.debian.org/sane/sane-backends.git
>> <http://git.debian.org/sane/sane-backends.git> using ./configure
>> --prefix=/usr --libdir=/usr/lib/x86_64-linux-gnu
>> --sysconfdir=/etc --localstatedir=/var --enable-avahi && make -j4
>>
>> 2018-01-03 21:09 GMT+01:00 Rolf Bensch <r...@bensch-online.de
>> <mailto:r...@bensch-online.de>>:
>>
>> Hi Wojtek,
>>
>> I just added your scanner to SANE. Please check out the
>> recent version
>> from git or you can use the daily git snapshot tomorrow.
>>
>> Please report if all scanning features (75-600dpi, simple and
>> duplex
>> document feeder) are running with USB. After this you can try
>> the bjnp
>> interface.
>>
>> Hope this helps.
>>
>> Cheers,
>> Rolf
>>
>>
>> Am 13.12.2017 um 09:58 schrieb Wojtek Teichert:
>> >  Can you add support for Canon i-SENSYS MF633cdw 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

Re: [sane-devel] PIXMA backend Canon i-SENSYS MF633cdw Support

[Rolf Bensch]

Hi Wojciech,

Please provide a logfile created with:

$ SANE_DEBUG_PIXMA=4 scanimage 2> pixma.log > pixma.pnm

Please zip, tar.gz or 7zip pixma.log and send it to me.

Cheers,
Rolf


Am 22.01.2018 um 03:29 schrieb Wojciech Teichert:
>  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).
> root@### sane-find-scanner
>
>   # sane-find-scanner will now attempt to detect your scanner. If the
>   # result is different from what you expected, first make sure your
>   # scanner is powered up and properly connected to your computer.
>
>   # No SCSI scanners found. If you expected something different, make
> sure that
>   # you have loaded a kernel SCSI driver for your SCSI adapter.
>
> found USB scanner (vendor=0x04a9 [Canon], product=0x27e1
> [MF633C/635C]) at libusb:001:005
>   # Your USB scanner was (probably) detected. It may or may not be
> supported by
>   # SANE. Try scanimage -L and read the backend's manpage.
>
>   # Not checking for parallel port scanners.
>
>   # Most Scanners connected to the parallel port or other proprietary
> ports
>   # can't be detected by this program.
> root@### 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)
>
> This is new version from git://git.debian.org/sane/sane-backends.git
> <http://git.debian.org/sane/sane-backends.git> using ./configure
> --prefix=/usr --libdir=/usr/lib/x86_64-linux-gnu --sysconfdir=/etc
> --localstatedir=/var --enable-avahi && make -j4
>
> 2018-01-03 21:09 GMT+01:00 Rolf Bensch <r...@bensch-online.de
> <mailto:r...@bensch-online.de>>:
>
> Hi Wojtek,
>
> I just added your scanner to SANE. Please check out the recent version
> from git or you can use the daily git snapshot tomorrow.
>
> Please report if all scanning features (75-600dpi, simple and duplex
> document feeder) are running with USB. After this you can try the bjnp
> interface.
>
> Hope this helps.
>
> Cheers,
> Rolf
>
>
> Am 13.12.2017 um 09:58 schrieb Wojtek Teichert:
> >  Can you add support for Canon i-SENSYS MF633cdw 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

Re: [sane-devel] ask for adding support of Canon's i-SENSYS MF620 series

[Rolf Bensch]

Hi Markus,

I just changed the doc files
(http://www.sane-project.org/lists/sane-backends-cvs.html#S-PIXMA).

Many thanks for your help.

Cheers,
Rolf


Am 04.01.2018 um 14:03 schrieb Markus Heiser:
> Hi Rolf,
> 
>> Am 03.01.2018 um 20:09 schrieb Rolf Bensch <r...@bensch-online.de>:
>>
>> Hi Markus,
>>
>> I just added your scanner to SANE sources.
> 
> great :) .. thanks a lot!
> 
> What I have tested while connected via USB:
> 
>   $ sudo sane-find-scanner 
>   ...
>   found USB scanner (vendor=0x0bda [Generic], product=0x0129 [USB2.0-CRW]) at 
> libusb:003:002
>   found USB scanner (vendor=0x04a9 [Canon,Inc.], product=0x27b4 [MF620C 
> Series]) at libusb:003:003  ...
>   ...
>   $ sudo scanimage -vL
>   device `pixma:04A927B4_f48139e3ba8e' is a CANON Canon i-SENSYS MF620 Series 
> multi-function peripheral
> 
>> I set max. page width to 216mm.
>>
>> Please check scans with max. page width and the document feeder.
> 
> $ sudo scanimage -l 216 --source "Automatic Document Feeder" > test.pnm
> scanimage: rounded value of tl-x from 216 to 215.731
> 
> .. is this what you asking for?
> 
> From my POV: scan works like a charm / Thanks again.
> 
> -- Markus --
> 
> 

-- 
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 Canon i-SENSYS MF633cdw Support

[Rolf Bensch]

Hi Wojtek,

I just added your scanner to SANE. Please check out the recent version
from git or you can use the daily git snapshot tomorrow.

Please report if all scanning features (75-600dpi, simple and duplex
document feeder) are running with USB. After this you can try the bjnp
interface.

Hope this helps.

Cheers,
Rolf


Am 13.12.2017 um 09:58 schrieb Wojtek Teichert:
>  Can you add support for Canon i-SENSYS MF633cdw 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

Re: [sane-devel] ask for adding support of Canon's i-SENSYS MF620 series

[Rolf Bensch]

Hi Markus,

I just added your scanner to SANE sources. I set max. page width to 216mm.

Please check scans with max. page width and the document feeder.

Please ask the mailing list again for your bjnp problem.

Many thanks reporting this scanner.

Cheers,
Rolf


Am 02.01.2018 um 19:24 schrieb Markus Heiser:
>> Am 02.01.2018 um 12:52 schrieb Markus Heiser :
>>
>> Hi SANE developers,
>>
>> I'am trying to scan from a Canon MF623Cn which is a AIO device
>> from Canon's i-SENSYS MF620 series. It can be connected by USB
>> or LAN.
>>
>> First I tried USB // MF620 series is not yet listed in:
>>
>> - http://www.sane-project.org/lists/sane-backends-cvs.html nor in
>> - 
>> https://anonscm.debian.org/git/sane/sane-backends.git/tree/doc/descriptions/pixma.desc
>>
>> I'am a bit confused by the naming 'i-SENSYS' and 'PIXMA' from
>> SANE's POV. What is the difference (or is there a difference)
>> between i-SENSYS and PIXMA? Especially, can we use the bjnp
>> protocol (bjnp://myscanner.my.domain:8612) for Canon's i-SENSYS
>> devices when connected via IP?
>>
>> Back to USB, I test the device on Ubuntu's 16.04 LTS // sane-find-scanner
>> from sane-backends 1.0.25git gives me::
>>
>> found USB scanner (vendor=0x04a9 [Canon,Inc.], product=0x27b4 [MF620C 
>> Series]) at libusb:003:003
>>
>> For the full output see below.
>>
>> Now I ask you SANE developer's for adding support of Canon's i-SENSYS
>> MF620 series. If you needed testers, I can test USB & LAN scenarios
>> with my MF623Cn.
>>
>> Thanks!
>>
>> Sidenote, I looked at commit 879565 [1]:
>>
>>  "new scanners Canon i-SENSYS MF230 and MF240 Series
>>
>> is this all we need, adding a define MF620_PID (with 0x27b4)
>> to backend/pixma_imageclass.c?
> I applied the following naive patch:
>
> --
> modified   backend/pixma_imageclass.c
> @@ -105,6 +105,7 @@
>  #define MF210_PID  0x27a9
>  #define MF230_PID  0x27d1
>  #define MF240_PID  0x27d2
> +#define MF620_PID  0x27b4
>  
>  
>  enum iclass_state_t
> @@ -944,5 +945,6 @@ const pixma_config_t pixma_iclass_devices[] = {
>DEV ("Canon i-SENSYS MF230 Series", "MF230", MF230_PID, 600, 0, 637, 1050, 
> PIXMA_CAP_ADF), /* max. w = 216mm */
>DEV ("Canon i-SENSYS MF240 Series", "MF240", MF240_PID, 600, 300, 634, 
> 1050, PIXMA_CAP_ADF),   /* max. w = 215mm, */
>   
> /* TODO: fix black stripes for 216mm @ 600dpi 
> */
> +  DEV ("Canon i-SENSYS MF620 Series", "MF620", MF620_PID, 600, 0, 634, 1050, 
> PIXMA_CAP_ADF),
>DEV (NULL, NULL, 0, 0, 0, 0, 0, 0)
>  };
> ---
>
> Here are the results:
>
>   $ sudo scanimage -v -L
>   device `pixma:04A927B4_f48139e3ba8e' is a CANON Canon i-SENSYS MF620 Series 
> multi-function peripheral
>
>   $ sudo ./tstbackend 
>   tstbackend, Copyright (C) 2002 Frank Zago
>   tstbackend comes with ABSOLUTELY NO WARRANTY
>   This is free software, and you are welcome to redistribute it
>   under certain conditions. See COPYING file for details
>
>   This is tstbackend build 19
>
> TEST: init/exit
>   ERROR   : no SANE devices found
>   warnings: 0  error: 1  checks: 83
>
> But scanning via USB seems to work fine, I tested:
>
>   $ sudo scanimage -v > test.pnm
>   scanimage: scanning image of size 637x877 pixels at 24 bits/pixel
>   scanimage: acquiring RGB frame
>   scanimage: min/max graylevel value = 255/0
>   scanimage: sane_read: Operation was cancelled
>
> I also tried LAN, by adding device's IP (bjnp://192.168.1.119) to 
>
>   /usr/local/etc/sane.d/pixma.conf
>
> But this results in:
>
>   $ sudo scanimage -v -L
>   [bjnp] udp_command: ERROR - no data received (timeout = 1000)
>   [bjnp] bjnp_init_device_structure: Cannot read mac address, skipping this 
> scanner
>   [bjnp] udp_command: ERROR - no data received (timeout = 1000)
>   [bjnp] add_scanner: ERROR - Cannot read scanner make & model: 
> bjnp://192.168.1.119:8612/timeout=1000
>
> I am grateful for any help / Thanks
>
> --Markus--
>
>
>
>
>> [1] 
>> https://anonscm.debian.org/git/sane/sane-backends.git/commit/?id=879565cefcac61e371581d09696ef6d738c2a720
>>
>> -- Markus --
>>
>>
>>
>>
>> This is sane-find-scanner from sane-backends 1.0.25git
>>
>> # sane-find-scanner will now attempt to detect your scanner. If the
>> # result is different from what you expected, first make sure your
>> # scanner is powered up and properly connected to your computer.
>>
>> searching for SCSI scanners:
>> ...
>> searching for USB scanners:
>> checking /dev/usb/scanner... failed to open (Invalid argument)
>> checking /dev/usb/scanner0... failed to open (Invalid argument)
>> checking /dev/usb/scanner1... failed to open (Invalid argument)
>> ...
>> checking /dev/usb/scanner15... failed to open (Invalid argument)
>> checking /dev/usbscanner... failed to open (Invalid argument)
>> checking /dev/usbscanner0... failed to open (Invalid argument)
>> checking 

Re: [sane-devel] CANON Canoscan 9000F - FAIL Error: Error during device I/O

[Rolf Bensch]

Hi Ales,

You can install SANE from my ppa
(https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-git). Then
everything should work well.

Hope this helps.

Cheers,
Rolf


Am 07.12.2017 um 15:35 schrieb Ales Mateju:
> Hi, I try to install scanner *CANON Canoscan 9000F Mark II* via *USB
> *under OS linux *Ubuntu 12.04.LTS 64k*. After *scanimage -T* I get 
> error *FAIL Error: Error during device I/O*. Other frontends ( xsane,
> gimp) says that I/O error appeared as well. Can somebody help me what
> to do next? Thanks Ales.
>
> _*I did this steps:
> *_- uninstall old version
> - install new version 1.0.27
> - create link
> BACKENDS=pixma ./configure --prefix=/usr  --localstatedir=/var
> --sysconfdir=/etc
> sudo make instal
> sudo ln -i -s /usr/lib/sane/libsane-pixma.so.1.0.27
> /usr/lib/x86_64-linux-gnu/sane/libsane-pixma.so.1
> - after sudo find / -name "libsane-pixma.*" I get
> /usr/lib/x86_64-linux-gnu/sane/libsane-pixma.so
> /usr/lib/x86_64-linux-gnu/sane/libsane-pixma.so.1
> /usr/lib/x86_64-linux-gnu/sane/libsane-pixma.la
> /usr/lib/sane/libsane-pixma.so
> /usr/lib/sane/libsane-pixma.so.1
> /usr/lib/sane/libsane-pixma.so.1.0.27
> /usr/lib/sane/libsane-pixma.la
> /home/ales/sane/sane-backends-latest/sane-backends-1.0.27/backend/libsane-pixma.la
> /home/ales/sane/sane-backends-latest/sane-backends-1.0.27/backend/.libs/libsane-pixma.so
> /home/ales/sane/sane-backends-latest/sane-backends-1.0.27/backend/.libs/libsane-pixma.so.1
> /home/ales/sane/sane-backends-latest/sane-backends-1.0.27/backend/.libs/libsane-pixma.lai
> /home/ales/sane/sane-backends-latest/sane-backends-1.0.27/backend/.libs/libsane-pixma.so.1.0.27
> /home/ales/sane/sane-backends-latest/sane-backends-1.0.27/backend/.libs/libsane-pixma.la
> and
> lrwxrwxrwx 1 root root 30 pro  6 23:53
> /usr/lib/x86_64-linux-gnu/sane/libsane-pixma.la ->
> /usr/lib/sane/libsane-pixma.la
> lrwxrwxrwx 1 root root 37 pro  6 23:51
> /usr/lib/x86_64-linux-gnu/sane/libsane-pixma.so ->
> /usr/lib/sane/libsane-pixma.so.1.0.27
> lrwxrwxrwx 1 root root 37 pro  6 22:23
> /usr/lib/x86_64-linux-gnu/sane/libsane-pixma.so.1 ->
> /usr/lib/sane/libsane-pixma.so.1.0.27
>
> _*I get this results:
> *_- sane-find-scanner can find my scanner - the second one
> found USB scanner (vendor=0x08ff, product=0x2580) at libusb:005:002
> found USB scanner (vendor=0x04a9 [Canon], product=0x190d [CanoScan])
> at libusb:002:003
> - scanimage -L can find my scanner
> device `pixma:04A9190D' is a CANON Canoscan 9000F Mark II
> multi-function peripheral
> - scanimage -T  get I/O error
> scanimage: scanning image of size 638x877 pixels at 24 bits/pixel
> scanimage: acquiring RGB frame, 8 bits/sample
> scanimage: reading one scanline, 1914 bytes...    FAIL Error: Error
> during device I/O
> - scanimage -V get mismatch of versions
> scanimage (sane-backends) 1.0.27; backend version 1.0.22
> - other frontends ( xsane, gimp) can find scanner but get I/O error
>
> _*from debugger lists it looks like ...
> *_- from SANE_DEBUG_DLL=255 scanimage -L it looks that system can find
> correct version of backends at right place and can load it
> [dll] load: searching backend `pixma' in
> `/usr/lib/x86_64-linux-gnu/sane:/usr/lib/sane'
> [dll] load: trying to load
> `/usr/lib/x86_64-linux-gnu/sane/libsane-pixma.so.1'
> [dll] load: dlopen()ing
> `/usr/lib/x86_64-linux-gnu/sane/libsane-pixma.so.1'
> [dll] init: initializing backend `pixma'
> [dll] init: backend `pixma' is version 1.0.17
>
> [dll] sane_get_devices: found 1 devices
> device `pixma:04A9190D' is a CANON Canoscan 9000F Mark II
> multi-function peripheral
> [dll] sane_exit: exiting
> [dll] sane_exit: calling backend `pixma's exit function
> [dll] sane_exit: finished
> - from SANE_DEBUG_DLL=1 scanimage -T, looks like the scanimage at this
> case finds and uses wrong version and stops by I/O error
> [sanei_debug] Setting debug level of dll to 1.
> [dll] sane_init: SANE dll backend version 1.0.13 from sane-backends 1.0.22
>
> scanimage: scanning image of size 638x877 pixels at 24 bits/pixel
> scanimage: acquiring RGB frame, 8 bits/sample
> scanimage: reading one scanline, 1914 bytes...    FAIL Error: Error
> during device I/O
>
> - SANE_DEBUG_DLL=3 scanimage -T gives more information about
> sane_init. I am not sure that it is important for loading of wrong
> backends version 
> [dll] sane_init: SANE dll backend version 1.0.13 from sane-backends 1.0.22
> [dll] sane_init/read_dlld: using config directory `/etc/sane.d/dll.d'
>
> _*at the end
> *_1/ I am not sure I understood well the current state
> 2/ I don't know what to do next. Try to looking for mistake in my
> instalation of backends or try to check instalation and configuration
> of frontends and how, ...
> 3/ ... or looking for other mistake
>

-- 
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] Code read

[Rolf Bensch]

Hi Ralph,

Please post your patches (compressed with tar.gz or zip) to the mailing
list, to Louis and me. Then we can review them and everybody who is also
interested can follow this on the ml.

Cheers,
Rolf


Am 21.10.2017 um 22:00 schrieb littlesincanada:
> Hi,
> I have started to do a code read of the pixma backend prior to doing
> some modifications to fix the ADF support for my canon multi-function.
> I have noticed a few things that I think are bugs and some small changes
> popped up from a quick scan with cppcheck.
> 
> I can assemble some patches from git head.
> 
> Should I just post them to the list or would someone like to get them
> directly for review?
> 
> Cheers,
> Ralph
> 
> 
> 

-- 
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 PIXMA MX925 - scan process now broken (does not end)

[Rolf Bensch]

Hi Jörn-Ingo,

Please test ADF with gscan2pdf.

I know that ADF scanning is faulty for scanners from the mp150 sub backend.

I'm sorry, but I cannot fix this issue because I have no access to such
scanners. I stopped remote fixing issues because I don't have much time
for maintaining SANE anymore.

@List: I can support software developers with ADF scanners fixing this
issue and I can commit patches to git. Affected scanners are all Canon
Maxify and PIXMA types with simple and duplex ADF.

Hope this helps.

Cheers,
Rolf


Am 01.09.2017 um 22:35 schrieb Jörn-Ingo Weigert:
> Hello Rolf,
> 
> the Scanner works fluently local in all resolutions now without problems
> using latest 1.0.27git01092017 version.
> 
> Great!
> What's not working:
> - ADF (tested with simple-scan), neither locally nor remote via net-backend.
> 
> Is there any special setting for this?
> 
> - interrupting (stopping) a remote scan from connected clients causes
> Scanner infinite scanning and scanline not moving or resetting, only off
> and on switching of printer help.
> 
> Model is by the way a Canon Maxify MX 2050, my fault. 
> 
> Great work so far Rolf! 
> 
> Kind regards,
> 
> Jörn-Ingo Weigert
> 
> Am 01.09.2017 10:01 vorm. schrieb "Rolf Bensch" <r...@bensch-online.de
> <mailto:r...@bensch-online.de>>:
> 
> The >600dpi should also be solved with the new version from my ppa.
> 
> Cheers,
> Rolf
> 
> Am 31.08.2017 um 21:15 schrieb Jörn-Ingo Weigert:
> > I will wait for it, thanks!
> >
> > Meanwhile, i would like to remind you of a still existing problem, we
> > talked about in the past, that scans over 600dpi are possible, but end
> > result are a overlapping, doubled image, which were also stored as
> a non
> > valid jpeg file..
> >
> > If you have time to research on it, that would be great. Just drop a
> > note on that, when.
> >
> > Kind regards,
> >
> > Jörn-Ingo Weigert
> >
> > Am 31.08.2017 9:05 nachm. schrieb "Rolf Bensch"
> <r...@bensch-online.de <mailto:r...@bensch-online.de>
> > <mailto:r...@bensch-online.de <mailto:r...@bensch-online.de>>>:
> >
> > Please try the next version which will be provided tomorrow,
> or just try
> > the recent one from my test ppa.
> >
> > Hope this helps.
> >
> > Cheers,
> > Rolf
> >
> >
> > Am 31.08.2017 um 16:35 schrieb Jörn-Ingo Weigert:
> > > Could this be a general problem for Pixma aio scanners?
> > >
> > > I had to switch back to 1.0.25 after latest update from your
> ppa (
> > sane
> > > 1.0.27git20170707¿?) The scan process was interruptive,
> stopping,
> > moving
> > > a bit until reaching ca. 75% of flatbed area the scanner neither
> > respond
> > > and stalled with a enabled scanline until switch off and on
> again.
> > >
> > > Happens on a Canon pixma MP350 connected through USB to a
> Ubuntu 17.04
> > > x64 system
> > > Kind regarded,
> > >
> > > Jörn-Ingo Weigert
> > >
> > > Am 31.08.2017 14:49 schrieb "Rolf Bensch"
> <r...@bensch-online.de <mailto:r...@bensch-online.de>
> > <mailto:r...@bensch-online.de <mailto:r...@bensch-online.de>>
> > > <mailto:r...@bensch-online.de <mailto:r...@bensch-online.de>
> <mailto:r...@bensch-online.de <mailto:r...@bensch-online.de>>>>:
> > >
> > > Hi Stephen,
> > >
> > > Sounds great ... and I found a bug in the mp150 code.
> Your scanner
> > > hasn't received the XML end of scan dialog. So you
> couldn't be
> > able to
> > > start a new scan...
> > >
> > > Please test the version +git20170823 from my test ppa.
> This is
> > the most
> > > recent SANE version from git *with* the bug fix.
> > >
> > > Many thanks for your help.
> > >
> > > Cheers,
> > > Rolf
> > >
> > > Am 30.08.2017 um 17:28 schrieb Stephen Weston:
> > > > Rolf,
> > > >
> > &g

Re: [sane-devel] Canon TS8050 not working correctly

[Rolf Bensch]

Hi Martin,

please test the scanner with the most recent version from my ppa. I
fixed a bug yesterday which had the same issue.

Hope this helps.

Cheers,
Rolf


Am 12.08.2017 um 21:47 schrieb Martin Gubser:
> Hi Rolf
> 
> Hopefully that's what you need.
> 
> Cheers,
> Martin
> 
> 
> 
> 
> Am 02.08.2017 um 19:27 schrieb Rolf Bensch:
>> Hi Martin,
>>
>> You can use wireshark with usb extensions:
>> https://wiki.wireshark.org/CaptureSetup/USB . You don't need to install
>> Windows in a VM.
>>
>> Please provide a complete Windows USB scan session as compressed file
>> (e.g. zip or 7z) and a new linux logfile created with
>> SANE_DEBUG_PIXMA=21 xsane &> pixma.log.
>>
>> Hope this helps.
>>
>> Cheers,
>> Rolf
>>
>>
>> Am 02.08.2017 um 00:13 schrieb Martin Gubser:
>>> Hi,
>>>
>>> I installed my new Canon TS8050 on Ubuntu 16.4 LTS with the PPA
>>> ppa:rolfbensch/sane-git
>>>
>>> The scanner is connected by USB. It is correctly detected. The command
>>> SANE_DEBUG_BJNP=4 scanimage -L 2>log
>>> detects the scanner as well.
>>>
>>> The command scanimage -T passes all tests.
>>>
>>> A first pre-scan with XSane works, but afterward the scanner does not
>>> respond any more. The display says “scanning”.
>>> A scan without a pre-scan results in the same error.
>>> Simple Scan produces this same error on the first scan.
>>>
>>> SANE_DEBUG_PIXMA=11 xsane &> pixma.log
>>> shows
>>> pixma is compiled with pthread support.
>>> [pixma] pixma version 0.17.42
>>> [pixma] pixma_collect_devices() found Canon PIXMA TS8000 Series at
>>> libusb:001:005
>>> [pixma] pixma_find_scanners() found 1 devices
>>> [pixma] pixma_collect_devices() found Canon PIXMA TS8000 Series at
>>> libusb:001:005
>>> [pixma] pixma_open(): Canon PIXMA TS8000 Series
>>> [pixma] *mp150_open* This is a generation 5 scanner.  *
>>> [pixma] INTR T=5.782 len=32
>>> [pixma]  :00 00 00 01 00 00 00 00  00 00 00 00 00 00 00 00
>>> [pixma]  0010:00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
>>> [pixma]
>>> [pixma] WARNING:send_time() disabled!
>>> ...
>>> [pixma] pixma_scan(): start
>>> [pixma]   line_size=3828 image_size=6714312 channels=3 depth=8
>>> [pixma]   dpi=150x150 offset=(0,0) dimension=1276x1754
>>> [pixma]   gamma_table=0x56123178b848 source=0
>>> [pixma]   threshold=127 threshold_curve=0
>>> [pixma]   adf-wait=0
>>> [pixma]   ADF page count: 0
>>> [pixma] OUT  T=24.435 len=288
>>> ...
>>> >> xmlns:ivec="http://www.canon.com/ns/cmd/2008/07/common/;>StartJob>>
>>> servicetype="scan">00011
>>>
>>>
>>> [pixma] XML response back from scanner:
>>> 
>>> http://www.canon.com/ns/cmd/2008/07/common/;>
>>> 
>>> StartJobResponse
>>> 
>>> NG
>>> PCScanning
>>> 
>>> 
>>> 
>>> 
>>> [pixma] pixma_scan() failed EPROTO
>>> [pixma] Reader task terminated: EPROTO
>>> [pixma] Setting non-blocking mode
>>> [pixma] read_image():reader task closed the pipe:0 bytes received,
>>> 6714312 bytes expected
>>> [pixma] pixma_close(): Canon PIXMA TS8000 Series
>>>
>>> If it helps I could analyze the communication in a Windows-system. Do
>>> you know a good and safe analyzer? I had used USB-lyzer some years ago
>>> and can’t use the new version any more without buying it.
>>>
>>> Any help is appreciated
>>> Martin
>>>
>>>
>>>
>>
>>

-- 
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 Pixma G2000 support

[Rolf Bensch]

Hi,

I just added your scanner to SANEs code.

You need to use my ppa:
https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-git . But please
be patient, the ppa will support your scanner with the next version
tomorrow (1.0.27+git20170902).

Hope this helps.

Cheers,
Rolf


Am 07.08.2017 um 19:55 schrieb Thierry HUCHARD:
> Le 2017-08-07 18:28, Iam Droidzone a écrit :
>> I've been trying to get the Canon Pixma G2000 to work with Ubuntu
>> 16.04.
>>
>> I tried:
>>
>> 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 fetch string descriptor: Pipe error
>> could not fetch string descriptor: Pipe error
>> found USB scanner (vendor=0x04a9 [Canon], product=0x1795 [G2000
>> series]) at libusb:001:010
>> could not fetch string descriptor: Pipe error
>> could not fetch string descriptor: Pipe error
>>   # 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.
>>
>> On trying 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).
>> root@hp:/etc/sane.d# gedit /usr/local/etc/sane.d/dll.conf
>>
>> systemctl status saned.socket:
>> ● saned.socket - saned incoming socket
>>Loaded: loaded (/lib/systemd/system/saned.socket; enabled; vendor
>> preset: enabled)
>>Active: active (listening) since Mon 2017-08-07 21:16:38 IST; 28min
>> ago
>>Listen: [::]:6566 (Stream)
>>  Accepted: 0; Connected: 0
>> Aug 07 21:16:38 hp systemd[1]: Listening on saned incoming socket.
>>
>> Aug 07 21:34:26 hp systemd[1]: Listening on saned incoming socket.
>>
>> The printing function is working with gutenprint. If only scanning too
>> worked, I could finally get Windows off the partition!
>>
>> Could anyone tell me if it's possible to tweak up support for this
>> printer? I can provide logs for anything needed. It's a simple flatbed
>> usb scanner on a multifunction printer.
>>
>> -Droidzone
>
>
> You may want to try the following line in /etc/sane.d/pixma.conf: usb
> 0x04a9 0x1795
>
>


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

[Rolf Bensch]

Hi Peter,


Am 27.08.2017 um 22:24 schrieb Peter Saunderson:
> Hi,
>
> Commit 62fcf80 in sane-backends is marked as TS5000 Series working but
> WiFi not working.
This issue is documented in the pixma.desc file.

I'm sorry for the unclear description for this commit. It's just a copy
and paste error.

>
>
> A few questions:
>
> 1/ I have build main latest 9b95970.. am I likely to damage my new
> TS5050 by exceeding the physical scan area height.. I would not like
> to damage my new printer / scanner!
The code should restrict scan commands to the maximum allowed scan area.

>
> 2/ I have the scanner connected via wifi on a different subnet in a
> different room.. will this work or do I have to connect locally with USB?
Please contact Olaf for Wifi issues.

>
> 3/ What is stopping wifi from working?  Is there something I could do
> to update the software to support wifi or is this a big job?
>
> 4/ What is a good way to test this sane version with the TS5050 so
> that we can mark the version tested with TS5050?
>
Hope this helps.

Cheers,
Rolf


-- 
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 PIXMA MX925 - scan process now broken (doesnot end)

[Rolf Bensch]

Hi Stephen,

Many thanks for your fast response. I just committed the bug fix into
the master branch. It will be available in my SANE repository tomorrow.

Many thanks again for your help making SANE more stable.

Cheers,
Rolf

Am 31.08.2017 um 18:48 schrieb Stephen Weston:
> Rolf,
> 
>  
> 
> Thanks. Tested +git20170823 and it worked perfectly.
> 
>  
> 
> I appreciate the work you’ve done in correcting the bug and it certainly
> helps me to be able to use the scanner!
> 
>  
> 
> Kind regards,
> 
> Stephen
> 
>  
> 
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
> Windows 10
> 
>  
> 
> *From: *Rolf Bensch <mailto:r...@bensch-online.de>
> *Sent: *31 August 2017 13:48
> *To: *Stephen Weston <mailto:stephencwes...@gmail.com>
> *Cc: *Sane Development <mailto:sane-devel@lists.alioth.debian.org>
> *Subject: *Re: [sane-devel] Canon PIXMA MX925 - scan process now broken
> (doesnot end)
> 
>  
> 
> Hi Stephen,
> 
>  
> 
> Sounds great ... and I found a bug in the mp150 code. Your scanner
> 
> hasn't received the XML end of scan dialog. So you couldn't be able to
> 
> start a new scan...
> 
>  
> 
> Please test the version +git20170823 from my test ppa. This is the most
> 
> recent SANE version from git *with* the bug fix.
> 
>  
> 
> Many thanks for your help.
> 
>  
> 
> Cheers,
> 
> Rolf
> 
>  
> 
> Am 30.08.2017 um 17:28 schrieb Stephen Weston:
> 
>> Rolf,
> 
>>
> 
>> I have tried it out with the '$SANE_USB_WORKAROUND=1 scanimage -T'
> 
>> command on a none-working system and it has not made any difference. The
> 
>> scanner continues to look busy after the initial scan and a second scan
> 
>> fails as before.
> 
>>
> 
>> I had much more success with the git+20170627 version as that worked
> 
>> okay as you suggested it might.
> 
>>
> 
>> I am keen to help, test and do what I can to help get the scanner
> 
>> working correctly, but just to let you know I will be unable to do much
> 
>> until the 15th September. I am moving home and my ISP won't be
> 
>> connecting my new place to the internet until then (and thats assuming
> 
>> no hiccups). I will have mobile internet, so I can receive and send
> 
>> emails at least, but nothing data heavy.
> 
>>
> 
>> Kind regards,
> 
>> Stephen
> 
>>
> 
>> On 29 August 2017 at 11:52, Rolf Bensch <r...@bensch-online.de
> 
>> <mailto:r...@bensch-online.de>> wrote:
> 
>>
> 
>> Hi Stephen,
> 
>>
> 
>> Please test an older version from my test ppa: git20170627. I hope
> that
> 
>> this version is running.
> 
>>
> 
>> On a not working system, please test this:
> 
>> $ SANE_USB_WORKAROUND=1 scanimage -T
> 
>>
> 
>> I still cannot reproduce this problem on my system, even in a
> VirtualBox
> 
>> VM with installed Ubuntu 17.04.
> 
>>
> 
>> Many thanks for your help.
> 
>>
> 
>> Cheers,
> 
>> Rolf
> 
>>
> 
>>
> 
>> Am 26.08.2017 um 14:57 schrieb Stephen Weston:
> 
>> > Hi,
> 
>> >
> 
>> > Had a go with the Ubuntu test ppa after a fresh install of Ubuntu
> 
>> 17.04
> 
>> > in VirtualBox. The terminal output is as below. As you can see the
> 
>> > scanner was successfully detected and the initial scan worked,
> but the
> 
>> > scanner was left in a busy 'scanning...' state and a second
> attempt at
> 
>> > scanning did not work.
> 
>> >
> 
>> > stephen@stephen-VirtualBox:~$ scanimage --version
> 
>> > scanimage (sane-backends) 1.0.27git; backend version 1.0.27
> 
>> >
> 
>> >
> 
>> >
> 
>> > stephen@stephen-VirtualBox:~$ scanimage -L
> 
>> > device `pixma:MX530_192.168.1.68' is a CANON Canon PIXMA MX530
> 
>> > Series multi-function peripheral
> 
>> >
> 
>> >
> 
>> >
> 
>> > stephen@stephen-VirtualBox:~$ scanimage -T
> 
>> > scanimage: scanning image of size 638x877 pixels at 24
> bits/pixel
> 
>> > scanimage: acquiring RGB frame, 8 bits/sample
> 
>> > scanimage: reading one scanline, 1914 bytes...PASS
> 
>> > scanimage: reading one byte...PASS
> 
>> > scanimag

Re: [sane-devel] Canon PIXMA MX925 - scan process now broken (does not end)

[Rolf Bensch]

Hi Stephen,

Sounds great ... and I found a bug in the mp150 code. Your scanner
hasn't received the XML end of scan dialog. So you couldn't be able to
start a new scan...

Please test the version +git20170823 from my test ppa. This is the most
recent SANE version from git *with* the bug fix.

Many thanks for your help.

Cheers,
Rolf

Am 30.08.2017 um 17:28 schrieb Stephen Weston:
> Rolf,
> 
> I have tried it out with the '$SANE_USB_WORKAROUND=1 scanimage -T'
> command on a none-working system and it has not made any difference. The
> scanner continues to look busy after the initial scan and a second scan
> fails as before.
> 
> I had much more success with the git+20170627 version as that worked
> okay as you suggested it might.
> 
> I am keen to help, test and do what I can to help get the scanner
> working correctly, but just to let you know I will be unable to do much
> until the 15th September. I am moving home and my ISP won't be
> connecting my new place to the internet until then (and thats assuming
> no hiccups). I will have mobile internet, so I can receive and send
> emails at least, but nothing data heavy.
> 
> Kind regards,
> Stephen
> 
> On 29 August 2017 at 11:52, Rolf Bensch <r...@bensch-online.de
> <mailto:r...@bensch-online.de>> wrote:
> 
> Hi Stephen,
> 
> Please test an older version from my test ppa: git20170627. I hope that
> this version is running.
> 
> On a not working system, please test this:
> $ SANE_USB_WORKAROUND=1 scanimage -T
> 
> I still cannot reproduce this problem on my system, even in a VirtualBox
> VM with installed Ubuntu 17.04.
> 
> Many thanks for your help.
> 
> Cheers,
> Rolf
> 
> 
> Am 26.08.2017 um 14:57 schrieb Stephen Weston:
> > Hi,
> >
> > Had a go with the Ubuntu test ppa after a fresh install of Ubuntu
> 17.04
> > in VirtualBox. The terminal output is as below. As you can see the
> > scanner was successfully detected and the initial scan worked, but the
> > scanner was left in a busy 'scanning...' state and a second attempt at
> > scanning did not work.
> >
> > stephen@stephen-VirtualBox:~$ scanimage --version
> > scanimage (sane-backends) 1.0.27git; backend version 1.0.27
> >
> >
> >
> > stephen@stephen-VirtualBox:~$ scanimage -L
> > device `pixma:MX530_192.168.1.68' is a CANON Canon PIXMA MX530
> > Series multi-function peripheral
> >
> >
> >
> > stephen@stephen-VirtualBox:~$ scanimage -T
> > scanimage: scanning image of size 638x877 pixels at 24 bits/pixel
> > scanimage: acquiring RGB frame, 8 bits/sample
> > scanimage: reading one scanline, 1914 bytes...PASS
> > scanimage: reading one byte...PASS
> > scanimage: stepped read, 2 bytes... PASS
> > scanimage: stepped read, 4 bytes... PASS
> > scanimage: stepped read, 8 bytes... PASS
> > scanimage: stepped read, 16 bytes... PASS
> > scanimage: stepped read, 32 bytes... PASS
> > scanimage: stepped read, 64 bytes... PASS
> > scanimage: stepped read, 128 bytes... PASS
> > scanimage: stepped read, 256 bytes... PASS
> > scanimage: stepped read, 512 bytes... PASS
> > scanimage: stepped read, 1024 bytes... PASS
> > scanimage: stepped read, 2048 bytes... PASS
> > scanimage: stepped read, 2047 bytes... PASS
> > scanimage: stepped read, 1023 bytes... PASS
> > scanimage: stepped read, 511 bytes... PASS
> > scanimage: stepped read, 255 bytes... PASS
> > scanimage: stepped read, 127 bytes... PASS
> > scanimage: stepped read, 63 bytes... PASS
> > scanimage: stepped read, 31 bytes... PASS
> > scanimage: stepped read, 15 bytes... PASS
> > scanimage: stepped read, 7 bytes... PASS
> > scanimage: stepped read, 3 bytes... PASS
> >
> >
> >
> > stephen@stephen-VirtualBox:~$ scanimage -T
>     > scanimage: scanning image of size 638x877 pixels at 24 bits/pixel
> > scanimage: acquiring RGB frame, 8 bits/sample
> > scanimage: reading one scanline, 1914 bytes...FAIL Error:
> Error
> > during device I/O
> >
> >
> >
> > Thanks. I appreciate your work in getting the scanner sorted.
> > Kind regards,
> > Stephen
> >

Re: [sane-devel] Canon PIXMA MX925 - scan process now broken (does not end)

[Rolf Bensch]

Hi Stephen,

Please test an older version from my test ppa: git20170627. I hope that
this version is running.

On a not working system, please test this:
$ SANE_USB_WORKAROUND=1 scanimage -T

I still cannot reproduce this problem on my system, even in a VirtualBox
VM with installed Ubuntu 17.04.

Many thanks for your help.

Cheers,
Rolf


Am 26.08.2017 um 14:57 schrieb Stephen Weston:
> Hi,
> 
> Had a go with the Ubuntu test ppa after a fresh install of Ubuntu 17.04
> in VirtualBox. The terminal output is as below. As you can see the
> scanner was successfully detected and the initial scan worked, but the
> scanner was left in a busy 'scanning...' state and a second attempt at
> scanning did not work.
> 
> stephen@stephen-VirtualBox:~$ scanimage --version
> scanimage (sane-backends) 1.0.27git; backend version 1.0.27
> 
>  
> 
> stephen@stephen-VirtualBox:~$ scanimage -L
> device `pixma:MX530_192.168.1.68' is a CANON Canon PIXMA MX530
> Series multi-function peripheral
> 
>  
> 
> stephen@stephen-VirtualBox:~$ scanimage -T
> scanimage: scanning image of size 638x877 pixels at 24 bits/pixel
> scanimage: acquiring RGB frame, 8 bits/sample
> scanimage: reading one scanline, 1914 bytes...PASS
> scanimage: reading one byte...PASS
> scanimage: stepped read, 2 bytes... PASS
> scanimage: stepped read, 4 bytes... PASS
> scanimage: stepped read, 8 bytes... PASS
> scanimage: stepped read, 16 bytes... PASS
> scanimage: stepped read, 32 bytes... PASS
> scanimage: stepped read, 64 bytes... PASS
> scanimage: stepped read, 128 bytes... PASS
> scanimage: stepped read, 256 bytes... PASS
> scanimage: stepped read, 512 bytes... PASS
> scanimage: stepped read, 1024 bytes... PASS
> scanimage: stepped read, 2048 bytes... PASS
> scanimage: stepped read, 2047 bytes... PASS
> scanimage: stepped read, 1023 bytes... PASS
> scanimage: stepped read, 511 bytes... PASS
> scanimage: stepped read, 255 bytes... PASS
> scanimage: stepped read, 127 bytes... PASS
> scanimage: stepped read, 63 bytes... PASS
> scanimage: stepped read, 31 bytes... PASS
> scanimage: stepped read, 15 bytes... PASS
> scanimage: stepped read, 7 bytes... PASS
> scanimage: stepped read, 3 bytes... PASS
> 
>  
> 
> stephen@stephen-VirtualBox:~$ scanimage -T
> scanimage: scanning image of size 638x877 pixels at 24 bits/pixel
> scanimage: acquiring RGB frame, 8 bits/sample
> scanimage: reading one scanline, 1914 bytes...FAIL Error: Error
> during device I/O
> 
> 
> 
> Thanks. I appreciate your work in getting the scanner sorted.
> Kind regards,
> Stephen
> 
> On 26 August 2017 at 10:50, Rolf Bensch <r...@bensch-online.de
> <mailto:r...@bensch-online.de>> wrote:
> 
> Hi,
> 
> I just uploaded a version without the sanei threading changes to my
> Ubuntu test ppa
> (https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-test
> <https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-test>). Please
> test this version and report your results.
> 
> Many thanks for your help.
> 
> Cheers,
> Rolf
> 
> Am 12.08.2017 um 05:32 schrieb Olaf Meeuwissen:
> > Hi Kay,
> >
> > Kay Drangmeister writes:
> >
> >> Hi,
> >>
> >> I am using the sane libs (Ubuntu 16.04) with a Canon Pixma MX925
> >> successfully for years now. Since some time (days, maybe weeks), the
> >> scan process does not terminate well.
> >
> > There were two recent threads about similar issues that may be of
> > interest
> >
> > 
> https://lists.alioth.debian.org/pipermail/sane-devel/2017-July/035481.html
> 
> <https://lists.alioth.debian.org/pipermail/sane-devel/2017-July/035481.html>
> > 
> https://lists.alioth.debian.org/pipermail/sane-devel/2017-July/035520.html
> 
> <https://lists.alioth.debian.org/pipermail/sane-devel/2017-July/035520.html>
> >
> > Note, both threads continue on
> >
> > 
> 
> https://lists.alioth.debian.org/pipermail/sane-devel/2017-August/thread.html
> 
> <https://lists.alioth.debian.org/pipermail/sane-devel/2017-August/thread.html>
> >
> > You could try reverting to 1.0.25+git20150528
> >
> > @Rolf> I hope these recent problem don't have anything to do with my
> >sanei threading changes.
> >
> >> [...]
&

Re: [sane-devel] Canon PIXMA MX925 - scan process now broken (does not end)

[Rolf Bensch]

Hi,

I just uploaded a version without the sanei threading changes to my
Ubuntu test ppa
(https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-test). Please
test this version and report your results.

Many thanks for your help.

Cheers,
Rolf

Am 12.08.2017 um 05:32 schrieb Olaf Meeuwissen:
> Hi Kay,
> 
> Kay Drangmeister writes:
> 
>> Hi,
>>
>> I am using the sane libs (Ubuntu 16.04) with a Canon Pixma MX925
>> successfully for years now. Since some time (days, maybe weeks), the
>> scan process does not terminate well.
> 
> There were two recent threads about similar issues that may be of
> interest
> 
>  https://lists.alioth.debian.org/pipermail/sane-devel/2017-July/035481.html
>  https://lists.alioth.debian.org/pipermail/sane-devel/2017-July/035520.html
> 
> Note, both threads continue on
> 
>  https://lists.alioth.debian.org/pipermail/sane-devel/2017-August/thread.html
> 
> You could try reverting to 1.0.25+git20150528
> 
> @Rolf> I hope these recent problem don't have anything to do with my
>sanei threading changes.
> 
>> [...]
> 
> 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

Re: [sane-devel] Canon MX530 - Error during device I/O

[Rolf Bensch]

Hi Stephen,

I would like to know which build fails. Please test the recent version
from my test ppa.

The problem is that on my system I cannot reproduce the problem with
your scanner.

Many thanks for your help in advance.

Cheers,
Rolf

Am 23.08.2017 um 20:11 schrieb Stephen Weston:
> Rolf,
> 
> Thanks for your help. The scanner appears to work with the SANE release
> PPA and your test PPA. Terminal output below:-
> 
> stephen@stephen-VirtualBox:~$ scanimage --version
> scanimage (sane-backends) 1.0.27; backend version 1.0.27
> 
>  
> 
> stephen@stephen-VirtualBox:~$ scanimage -L
> device `pixma:MX530_192.168.1.68' is a CANON Canon PIXMA MX530
> Series multi-function peripheral
> 
>  
> 
> stephen@stephen-VirtualBox:~$ scanimage -T
> scanimage: scanning image of size 638x877 pixels at 24 bits/pixel
> scanimage: acquiring RGB frame, 8 bits/sample
> scanimage: reading one scanline, 1914 bytes...PASS
> scanimage: reading one byte...PASS
> scanimage: stepped read, 2 bytes... PASS
> scanimage: stepped read, 4 bytes... PASS
> scanimage: stepped read, 8 bytes... PASS
> scanimage: stepped read, 16 bytes... PASS
> scanimage: stepped read, 32 bytes... PASS
> scanimage: stepped read, 64 bytes... PASS
> scanimage: stepped read, 128 bytes... PASS
> scanimage: stepped read, 256 bytes... PASS
> scanimage: stepped read, 512 bytes... PASS
> scanimage: stepped read, 1024 bytes... PASS
> scanimage: stepped read, 2048 bytes... PASS
> scanimage: stepped read, 2047 bytes... PASS
> scanimage: stepped read, 1023 bytes... PASS
> scanimage: stepped read, 511 bytes... PASS
> scanimage: stepped read, 255 bytes... PASS
> scanimage: stepped read, 127 bytes... PASS
> scanimage: stepped read, 63 bytes... PASS
> scanimage: stepped read, 31 bytes... PASS
> scanimage: stepped read, 15 bytes... PASS
> scanimage: stepped read, 7 bytes... PASS
> scanimage: stepped read, 3 bytes... PASS
> 
>  
> 
> stephen@stephen-VirtualBox:~$ scanimage -T
> scanimage: scanning image of size 638x877 pixels at 24 bits/pixel
> scanimage: acquiring RGB frame, 8 bits/sample
> scanimage: reading one scanline, 1914 bytes...PASS
> scanimage: reading one byte...PASS
> scanimage: stepped read, 2 bytes... PASS
> scanimage: stepped read, 4 bytes... PASS
> scanimage: stepped read, 8 bytes... PASS
> scanimage: stepped read, 16 bytes... PASS
> scanimage: stepped read, 32 bytes... PASS
> scanimage: stepped read, 64 bytes... PASS
> scanimage: stepped read, 128 bytes... PASS
> scanimage: stepped read, 256 bytes... PASS
> scanimage: stepped read, 512 bytes... PASS
> scanimage: stepped read, 1024 bytes... PASS
> scanimage: stepped read, 2048 bytes... PASS
> scanimage: stepped read, 2047 bytes... PASS
> scanimage: stepped read, 1023 bytes... PASS
> scanimage: stepped read, 511 bytes... PASS
> scanimage: stepped read, 255 bytes... PASS
> scanimage: stepped read, 127 bytes... PASS
> scanimage: stepped read, 63 bytes... PASS
> scanimage: stepped read, 31 bytes... PASS
> scanimage: stepped read, 15 bytes... PASS
> scanimage: stepped read, 7 bytes... PASS
> scanimage: stepped read, 3 bytes... PASS
> 
> 
> However, a relatively less serious issue, if I leave the scanner for a
> more extended period of time (for it to go into standby), when I attempt
> use it I get the following output. It appears that SANE is unable to
> wake the scanner up out of standby.
> 
> stephen@stephen-VirtualBox:~$ scanimage -T
> scanimage: scanning image of size 638x877 pixels at 24 bits/pixel
> scanimage: acquiring RGB frame, 8 bits/sample
> scanimage: reading one scanline, 1914 bytes...[bjnp]
> bjnp_open_tcp: ERROR - Can not connect to scanner: Connection refused
> FAIL Error: Invalid argument
> 
> 
> After pressing a button on the device to wake it up out of standby it
> works fine again. Not  a serious issue as pressing a button on the
> scanner to wake it up isn't too problematic.
> 
> 
> Kind regards,
> Stephen
> 
> 
> 
> On 23 August 2017 at 09:00, Rolf Bensch <r...@bensch-online.de
> <mailto:r...@bensch-online.de>> wrote:
> 
> Hi Stephen,
> 
> Please try my SANE Release PPA:
> https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-release
> <https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-release> .
> 
>  

Re: [sane-devel] Canon MX530 - Error during device I/O

[Rolf Bensch]

Hi Stephen,

Please try my SANE Release PPA:
https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-release .

If your scanner is working with this, please try my inofficial test ppa:
https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-test .

Other users reported similar problems with their scanners. I suppose a
problem with one of the recent commits to the git repository.

Hope this helps.

Cheers,
Rolf


Am 20.08.2017 um 12:49 schrieb Stephen Weston:
> Dear all,
>
> I am hoping to get some help to get the scanner on my Canon MX535
> multi-function device working. In the past it has worked no problems,
> but trying it recently it has not been so successful. The printer
> function works perfectly. I am using Ubuntu Gnome 17.04 fully updated
> and with the sane-git repository. I am using the scanner over wifi.
>  
> After testing the scanner as much as I know how it appears that the
> scanner works initially, but then fails after trying to use it a
> second time. So, on the standard work flow in xsane of doing a preview
> first, then selecting the scan area and clicking scan, the scanner
> will do the preview fine, but fail with 'Error during device I/O" on
> clicking scan. After the initial scan appears to have completed the
> scanner is left in a 'busy' state with 'Scanning...' displayed on its
> screen and a blue LED flashing as if its still trying to work away
> (although the light bar looks parked and is not lit up). Switching the
> scanner off and on again allows me to scan again, but only once before
> the same happens.
>
> I include the output from using scanimage to test the device below. I
> have run scanimage -T twice, the second time shortly after the first
> 'successful' attempt.
>
> stephen@stephen-VirtualBox:~$ scanimage --version
> scanimage (sane-backends) 1.0.27git; backend version 1.0.27
>
>  
>
> stephen@stephen-VirtualBox:~$ scanimage -L
> device `pixma:MX530_192.168.1.68' is a CANON Canon PIXMA MX530
> Series multi-function peripheral
>
>  
>
> stephen@stephen-VirtualBox:~$ scanimage -T
> scanimage: scanning image of size 638x877 pixels at 24 bits/pixel
> scanimage: acquiring RGB frame, 8 bits/sample
> scanimage: reading one scanline, 1914 bytes...PASS
> scanimage: reading one byte...PASS
> scanimage: stepped read, 2 bytes... PASS
> scanimage: stepped read, 4 bytes... PASS
> scanimage: stepped read, 8 bytes... PASS
> scanimage: stepped read, 16 bytes... PASS
> scanimage: stepped read, 32 bytes... PASS
> scanimage: stepped read, 64 bytes... PASS
> scanimage: stepped read, 128 bytes... PASS
> scanimage: stepped read, 256 bytes... PASS
> scanimage: stepped read, 512 bytes... PASS
> scanimage: stepped read, 1024 bytes... PASS
> scanimage: stepped read, 2048 bytes... PASS
> scanimage: stepped read, 2047 bytes... PASS
> scanimage: stepped read, 1023 bytes... PASS
> scanimage: stepped read, 511 bytes... PASS
> scanimage: stepped read, 255 bytes... PASS
> scanimage: stepped read, 127 bytes... PASS
> scanimage: stepped read, 63 bytes... PASS
> scanimage: stepped read, 31 bytes... PASS
> scanimage: stepped read, 15 bytes... PASS
> scanimage: stepped read, 7 bytes... PASS
> scanimage: stepped read, 3 bytes... PASS
>
>
> (After this the scanner appears to still be 'busy' as described above)
>  
>
> stephen@stephen-VirtualBox:~$ scanimage -T
> scanimage: scanning image of size 638x877 pixels at 24 bits/pixel
> scanimage: acquiring RGB frame, 8 bits/sample
> scanimage: reading one scanline, 1914 bytes...FAIL Error:
> Error during device I/O
>
>
> Any help would be appreciated and I am willing to do any testing as
> required, but will need instructions.
>
> Kind regards,
>
> Stephen
>
> P.S. sorry, this is my second post on to this mailing list. Not sure
> if my first email got through or not, but unfortunately I did not get
> a reply. I'm hoping with this extra information someone may be able to
> 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

Re: [sane-devel] Canon PIXMA MX725: ADF scan duplex and automatic recognition of number of pages

[Rolf Bensch]

Hi Timo,

First, we should enable your Ubuntu system to scan via flatbed, adf
simple and adf duplex. Sorry, I have no experiences scanning adf pages
from scanimage in batch mode. Therefore we should start using gsan2pdf.

Maybe somebody on the list can provide running scanimage batch mode
calls for pixma scanners using adf simple and adf duplex.

To make sure using the most recent version you should install SANE from
my ppa: https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-git . OK,
you can stay using your self compiled version on Ubuntu, if you followed
the installation instructions from INSTALL.linux.

The ppa should also provide the recent SANE version for your rasp pi
(armhf or arm64; the packet manager should select the correct version).

OK, after installing (and removing a cruddy self compiled version: $
sudo make uninstall) the most recent version of SANE, you can create a
logfile on a console with, e.g.:

$ SANE_DEBUG_PIXMA=11 gscan2pdf &> pixma.log

On your raspberry pi (and Ubuntu) you can use this corresponding command
for scanimage:

$ SANE_DEBUG_PIXMA=11 scanimage [options] &> pixma.log

Maybe we need to debug and fix some issues on your Ubuntu machine first.

Second, if all scan types are running with gscan2pdf we can find a
working scanimage command which then can be simply adapted into your
raspberry pi.

Please provide the logfile of a failed scan in an archive, e.g. tar.gz,
zip or 7z.

Hope this helps.

Cheers,
Rolf




Am 01.08.2017 um 22:07 schrieb Timo Ziegler:
> Hi Rolf,
>
> thanks for your answer.
>
> I am using scanimage on my raspberry pi without any GUI.
> Now I tried scanning via my ubuntu desktop system, but the document is
> just stopping in the ADF and the MX725 wants that I press OK to get
> the document back. I already tried to reinstall sane and the pixma
> backend (sane via apt-get remove and the pixma backend by checking out
> via git and compiling again). Same result.
>
> Is there maybe a way to debug my problem via console on the raspberry
> pi, since the scanning there is working, just no ADF Duplex and batch
> without providing the number of pages?
>
> Best regards
> Timo
>
>  Original-Nachricht 
> *Betreff:* Re: [sane-devel] Canon PIXMA MX725: ADF scan duplex and
> automatic recognition of number of pages
> *Datum:* Tue, 1 Aug 2017 20:47:11 +0200
> *Von:* Rolf Bensch
> *An:* Timo Ziegler
>> Hi Timo,
>>
>> I prefer gscan2pdf for multi page adf scans.
>>
>> Please report if your problem also occurs with gscan2pdf.
>>
>> Many thanks for your help.
>>
>> Cheers,
>> Rolf
>>
>>
>> Am 29.07.2017 um 12:49 schrieb Timo Ziegler:
>>> Hi,
>>>
>>> I got my MX725 running with scanimage on sane-pixma backend.
>>>
>>> My last problems are that I can't scan in duplex mode via ADF and that
>>> a ADF batch scan tries to scan another page after all pages are gone
>>> from the ADF and then just gets stuck (need to use Ctrl + C once or
>>> twice).
>>>
>>> To scan in duplex mode, I tried the following options:
>>> --ScanMode=Duplex => unrecognized option "--ScanMode"
>>> --source="ADFDUP"
>>> --source="Automatic Document Feeder(left align,duplex)
>>> --source="Automatic Document Feeder(left align,Duplex)
>>> and maybe some variations more => setting of option --source failed
>>> (Invalid argument)
>>>
>>>
>>> To scan "infinity pages, incrementing by 1, numbering from 1", I just
>>> used --batch and scanned.
>>> It's successfully scanning all the pages + tried to scan a next one
>>> after the ADF runs out of pages to scan.
>>> // Scanning page 1
>>> // Scanned page 1. (scanner status = 5)
>>> // Scanning page 2
>>>
>>> Then nothing happens anymore. When I press Ctrl + C, it tries to
>>> // scanimage: received signal 2
>>> // scanimage: trying to stop scanner
>>>
>>> Nothing happens, so I press Ctrl + C again
>>> // scanimage: received signal 2
>>> // scanimage: aborting
>>>
>>> Scanning via --batch --batch-number=2 works fine, but I want to use
>>> scanbuttond later so I don't want to set the number of pages every time.
>>>
>>> I tried using --adf-wait=3 but this option is not recognized. It's not
>>> listed in scanimage -A, but I found it in the online pixma-backend
>>> documentation.
>>>
>>>
>>> I hope, somebody can give a hint.
>>>
>>> Thanks in advance
>>>
>>> Timo
>

-- 
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 TS8050 not working correctly

[Rolf Bensch]

Hi Martin,

You can use wireshark with usb extensions:
https://wiki.wireshark.org/CaptureSetup/USB . You don't need to install
Windows in a VM.

Please provide a complete Windows USB scan session as compressed file
(e.g. zip or 7z) and a new linux logfile created with
SANE_DEBUG_PIXMA=21 xsane &> pixma.log.

Hope this helps.

Cheers,
Rolf


Am 02.08.2017 um 00:13 schrieb Martin Gubser:
> Hi,
>
> I installed my new Canon TS8050 on Ubuntu 16.4 LTS with the PPA
> ppa:rolfbensch/sane-git
>
> The scanner is connected by USB. It is correctly detected. The command
> SANE_DEBUG_BJNP=4 scanimage -L 2>log
> detects the scanner as well.
>
> The command scanimage -T passes all tests.
>
> A first pre-scan with XSane works, but afterward the scanner does not
> respond any more. The display says “scanning”.
> A scan without a pre-scan results in the same error.
> Simple Scan produces this same error on the first scan.
>
> SANE_DEBUG_PIXMA=11 xsane &> pixma.log
> shows
> pixma is compiled with pthread support.
> [pixma] pixma version 0.17.42
> [pixma] pixma_collect_devices() found Canon PIXMA TS8000 Series at
> libusb:001:005
> [pixma] pixma_find_scanners() found 1 devices
> [pixma] pixma_collect_devices() found Canon PIXMA TS8000 Series at
> libusb:001:005
> [pixma] pixma_open(): Canon PIXMA TS8000 Series
> [pixma] *mp150_open* This is a generation 5 scanner.  *
> [pixma] INTR T=5.782 len=32
> [pixma]  :00 00 00 01 00 00 00 00  00 00 00 00 00 00 00 00
> [pixma]  0010:00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
> [pixma]
> [pixma] WARNING:send_time() disabled!
> ...
> [pixma] pixma_scan(): start
> [pixma]   line_size=3828 image_size=6714312 channels=3 depth=8
> [pixma]   dpi=150x150 offset=(0,0) dimension=1276x1754
> [pixma]   gamma_table=0x56123178b848 source=0
> [pixma]   threshold=127 threshold_curve=0
> [pixma]   adf-wait=0
> [pixma]   ADF page count: 0
> [pixma] OUT  T=24.435 len=288
> ...
>  xmlns:ivec="http://www.canon.com/ns/cmd/2008/07/common/;>StartJob servicetype="scan">00011
>
> [pixma] XML response back from scanner:
> 
> http://www.canon.com/ns/cmd/2008/07/common/;>
> 
> StartJobResponse
> 
> NG
> PCScanning
> 
> 
> 
> 
> [pixma] pixma_scan() failed EPROTO
> [pixma] Reader task terminated: EPROTO
> [pixma] Setting non-blocking mode
> [pixma] read_image():reader task closed the pipe:0 bytes received,
> 6714312 bytes expected
> [pixma] pixma_close(): Canon PIXMA TS8000 Series
>
> If it helps I could analyze the communication in a Windows-system. Do
> you know a good and safe analyzer? I had used USB-lyzer some years ago
> and can’t use the new version any more without buying it.
>
> Any help is appreciated
> Martin
>
>
>


-- 
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] Issue with libsane 1.0.27+git20170719-xenial0 and Canon PIXMA MX495

[Rolf Bensch]

Hi Jean,

If you like, you can install SANE from the git repository as described
in INSTALL.linux (http://sane-project.org/docs.html) to find the problem
in the source code.

Most interesting are the commits from the master branch containing
changes for files starting with pixma after 27.05.2017. Usually these
commits come from Olaf Meeuwissen or from me. Please checkout these
commits, compile and test them. Easy to use git frontends are git-gui,
gitk or gitg. But you must checkout a commit with its sha1-id from the
command line (the 1st 6 to 7 characters of the sha1-id are enough to
identify the commit), e.g.: 

$ git checkout  c2594e
Note: checking out 'c2594e'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b 

HEAD ist jetzt bei c2594e9... Revert "pixma_imageclass.c: MF240 Series
supports only 300dpi for adf scans"

Please report the branch which 1st produces the problems you've reported
before.

Otherwise we must wait some weeks finding the problem commit.

Hope this helps.

Cheers,
Rolf


Am 25.07.2017 um 23:03 schrieb Jean Cérien:
>
> Hi Rolf, 
>
> First, thank you for looking into this.
> Second, there is no rush, as I have a workaround reverting to 1.0.25,
>
>
> I've tried with sane-release ppa, 
> scanimage (sane-backends) 1.0.27git; backend version 1.0.27
> and it works fine
>
> same with sane-test, which is ok,
>
> I've reverted to sane-git, and it fails again.
>
> Let me know if you need more info, 
>
> J.
>
>
> On Tue, Jul 25, 2017 at 3:59 AM, Rolf Bensch <r...@fam-bensch.de
> <mailto:r...@fam-bensch.de>> wrote:
>
> Hi Jean,
>
> Please try my other ppa's (SANE Release and SANE Test) with older
> versions of SANE: https://launchpad.net/~rolfbensch
> <https://launchpad.net/%7Erolfbensch> and report the
> results. Then I'll have an idea where to search for the issue you
> reported.
>
> Please be patient. I'm on the move until end of August and I have less
> time to work on SANE.
>
> Hope this helps.
>
> Cheers,
> Rolf
>
>
> Am 19.07.2017 um 23:22 schrieb Jean Cérien:
> >
> > Hello
> > I have a multifunction canon pixma mx 495. Up
> > to 1.0.25+git20150528-1ubuntu2, I only had one small issue, the ADF
> > wasnt working, but flatbed was ok.
> >
> > Since 1.0.27+git20170719-xenial0, in flatbed mode, I can only
> scan on
> > page and then I get an error:
> > scanimage: sane_read: Error during device I/O
> >
> > after scaning one page, trying to scan a second.
> >
> > Reverting to 1.0.25 restore the previous way of working and
> allows me
> > to scan multiple pages via flatbed.
> >
> > scanimage -L gives:
> > device `pixma:04A91787' is a CANON Canon PIXMA MX490 Series
> > multi-function peripheral
> >
> > I've tried 1.0.27 with  /etc/sane.d/pixma.conf from 1.0.25, but
> > unfortunately, that does not work.
> >
> > As an FYI, the ADF reports 'Operation was cancelled' in 1.0.25
> and .27
> >
> > Thanks for any help to have this scanner keep on working,
> >
> > Rgds
> > J.
> >
> >
>
>
>

-- 
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 PIXMA MX725: ADF scan duplex and automatic recognition of number of pages

[Rolf Bensch]

Hi Timo,

I prefer gscan2pdf for multi page adf scans.

Please report if your problem also occurs with gscan2pdf.

Many thanks for your help.

Cheers,
Rolf


Am 29.07.2017 um 12:49 schrieb Timo Ziegler:
> Hi,
>
> I got my MX725 running with scanimage on sane-pixma backend.
>
> My last problems are that I can't scan in duplex mode via ADF and that
> a ADF batch scan tries to scan another page after all pages are gone
> from the ADF and then just gets stuck (need to use Ctrl + C once or
> twice).
>
> To scan in duplex mode, I tried the following options:
> --ScanMode=Duplex => unrecognized option "--ScanMode"
> --source="ADFDUP"
> --source="Automatic Document Feeder(left align,duplex)
> --source="Automatic Document Feeder(left align,Duplex)
> and maybe some variations more => setting of option --source failed
> (Invalid argument)
>
>
> To scan "infinity pages, incrementing by 1, numbering from 1", I just
> used --batch and scanned.
> It's successfully scanning all the pages + tried to scan a next one
> after the ADF runs out of pages to scan.
> // Scanning page 1
> // Scanned page 1. (scanner status = 5)
> // Scanning page 2
>
> Then nothing happens anymore. When I press Ctrl + C, it tries to
> // scanimage: received signal 2
> // scanimage: trying to stop scanner
>
> Nothing happens, so I press Ctrl + C again
> // scanimage: received signal 2
> // scanimage: aborting
>
> Scanning via --batch --batch-number=2 works fine, but I want to use
> scanbuttond later so I don't want to set the number of pages every time.
>
> I tried using --adf-wait=3 but this option is not recognized. It's not
> listed in scanimage -A, but I found it in the online pixma-backend
> documentation.
>
>
> I hope, somebody can give a hint.
>
> Thanks in advance
>
> Timo


-- 
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] Issue with libsane 1.0.27+git20170719-xenial0 and Canon PIXMA MX495

[Rolf Bensch]

Hi Jean,

Please try my other ppa's (SANE Release and SANE Test) with older
versions of SANE: https://launchpad.net/~rolfbensch and report the
results. Then I'll have an idea where to search for the issue you reported.

Please be patient. I'm on the move until end of August and I have less
time to work on SANE.

Hope this helps.

Cheers,
Rolf


Am 19.07.2017 um 23:22 schrieb Jean Cérien:
>
> Hello
> I have a multifunction canon pixma mx 495. Up
> to 1.0.25+git20150528-1ubuntu2, I only had one small issue, the ADF
> wasnt working, but flatbed was ok.
>
> Since 1.0.27+git20170719-xenial0, in flatbed mode, I can only scan on
> page and then I get an error: 
> scanimage: sane_read: Error during device I/O
>
> after scaning one page, trying to scan a second. 
>
> Reverting to 1.0.25 restore the previous way of working and allows me
> to scan multiple pages via flatbed.
>
> scanimage -L gives:
> device `pixma:04A91787' is a CANON Canon PIXMA MX490 Series
> multi-function peripheral
>
> I've tried 1.0.27 with  /etc/sane.d/pixma.conf from 1.0.25, but
> unfortunately, that does not work.
>
> As an FYI, the ADF reports 'Operation was cancelled' in 1.0.25 and .27
>
> Thanks for any help to have this scanner keep on working, 
>
> Rgds
> J.
>
>



-- 
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] [janitorial] Error @ git push

[Rolf Bensch]

Hi Olaf,

My last git push produced this output:

Versende nach
git+ssh://roben-gu...@git.debian.org/git/sane/sane-backends.git
remote: Sending notification emails to:
sane-com...@lists.alioth.debian.org   
remote: Aktualisiere d94c29a..3258b70   
remote: Fast-forward   
remote:  backend/hp3500.c| 2 ++   
remote:  backend/plustek-pp_scan.h   | 6 +-   
remote:  configure   | 2 +-   
remote:  configure.ac| 2 +-   
remote:  doc/descriptions/pixma.desc | 4 ++--   
remote:  include/sane/config.h.in| 3 ---   
remote:  6 files changed, 7 insertions(+), 12 deletions(-)   
remote: cd .. && make  am--refresh   
remote: make[1]: Entering directory
`/var/lib/gforge/chroot/home/groups/sane/sane-backends-lists-git'   
remote: /bin/bash ./config.status --recheck   
remote: running CONFIG_SHELL=/bin/bash /bin/bash ./configure --no-create
--no-recursion   
remote: checking for a BSD-compatible install... /usr/bin/install -c   
remote: checking whether build environment is sane... yes   
remote: checking for a thread-safe mkdir -p... /bin/mkdir -p   
remote: checking for gawk... gawk   
remote: checking whether make sets $(MAKE)... yes   
remote: checking whether make supports nested variables... yes   
remote: checking whether make supports nested variables... (cached)
yes   
remote: checking whether to enable maintainer-specific portions of
Makefiles... no   
remote: checking for gcc... gcc   
remote: checking whether the C compiler works... yes   
remote: checking for C compiler default output file name... a.out   
remote: checking for suffix of executables...
remote: checking whether we are cross compiling... no   
remote: checking for suffix of object files... o   
remote: checking whether we are using the GNU C compiler... yes   
remote: checking whether gcc accepts -g... yes   
remote: checking for gcc option to accept ISO C89... none needed   
remote: checking whether gcc understands -c and -o together... yes   
remote: checking for style of include used by make... GNU   
remote: checking dependency style of gcc... gcc3   
remote: checking for gcc option to accept ISO C99... -std=gnu99   
remote: checking for gcc option for ISO C99 w/o extensions...
-std=c99   
remote: checking how to run the C preprocessor... gcc -std=c99 -E   
remote: checking for grep that handles long lines and -e...
/bin/grep   
remote: checking for egrep... /bin/grep -E   
remote: checking whether gcc -std=c99 needs -traditional... no   
remote: checking for ANSI C header files... yes   
remote: checking for sys/types.h... yes   
remote: checking for sys/stat.h... yes   
remote: checking for stdlib.h... yes   
remote: checking for string.h... yes   
remote: checking for memory.h... yes   
remote: checking for strings.h... yes   
remote: checking for inttypes.h... yes   
remote: checking for stdint.h... yes   
remote: checking for unistd.h... yes   
remote: checking minix/config.h usability... no   
remote: checking minix/config.h presence... no   
remote: checking for minix/config.h... no   
remote: checking whether it is safe to define __EXTENSIONS__... yes   
remote: checking for ar... ar   
remote: checking the archiver (ar) interface... ar   
remote: checking build system type... x86_64-pc-linux-gnu   
remote: checking host system type... x86_64-pc-linux-gnu   
remote: checking how to print strings... printf   
remote: checking for a sed that does not truncate output... /bin/sed   
remote: checking for fgrep... /bin/grep -F   
remote: checking for ld used by gcc -std=c99... /usr/bin/ld   
remote: checking if the linker (/usr/bin/ld) is GNU ld... yes   
remote: checking for BSD- or MS-compatible name lister (nm)...
/usr/bin/nm -B   
remote: checking the name lister (/usr/bin/nm -B) interface... BSD
nm   
remote: checking whether ln -s works... yes   
remote: checking the maximum length of command line arguments...
3458764513820540925   
remote: checking whether the shell understands some XSI constructs...
yes   
remote: checking whether the shell understands "+="... yes   
remote: checking how to convert x86_64-pc-linux-gnu file names to
x86_64-pc-linux-gnu format... func_convert_file_noop   
remote: checking how to convert x86_64-pc-linux-gnu file names to
toolchain format... func_convert_file_noop   
remote: checking for /usr/bin/ld option to reload object files... -r   
remote: checking for objdump... objdump   
remote: checking how to recognize dependent libraries... pass_all   
remote: checking for dlltool... no   
remote: checking how to associate runtime and link libraries... printf
%s\n   
remote: checking for archiver @FILE support... @   
remote: checking for strip... 

Re: [sane-devel] [janitorial] sanei_thread "fixes" and Fedora 26 CI builds

[Rolf Bensch]

Hi Olaf,


Am 15.07.2017 um 10:21 schrieb Olaf Meeuwissen:
> @Rolf> Can you take a look at 73861ea, please?  It affects the pixma
>backend.  I think it's fine but I'd like an extra pair of eyes
>on that.
>
>
Everthing looks fine. My scanner is still working. :-)

Cheers,
Rolf

-- 
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 1.0.27 has been released

[Rolf Bensch]

Hi,

My PPA provides the post release versions (1.0.27+git{date}) now!

If somebody needs the recent SANE release instead of the version from
SANE daily git snapshot, she|he can use my new PPA[2].


Am 23.05.2017 um 11:44 schrieb Olaf Meeuwissen:
> Hi,
>
> csola48 writes:
>
>> Dear Sir!
>>
>> Big-big thanks the sane-backend 1.0.27...
>> Cheeky question: when will be *.deb version? ;)
> Unless you're using Rolf's PPA[1], that's up to your distribution's
> sane-backends package maintainer.
>
>  [1] https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-git
[2] https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-release
>
> If you do use Rolf's PPA, packages should be there in a day (or two).

This comes while I'm using the daily git snapshot, which is built every
night and provided on SANE's project website.

>
> 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
>
>
Hope this helps.

Cheers,
Rolf



-- 
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 is open for development

[Rolf Bensch]

Hi Allan,

If I'm checking the version with scanimage, I get this back:

$ scanimage -V
scanimage (sane-backends) 1.0.27git; backend version 1.0.27

Maybe the backend version should also show 1.0.27git?

Hope this helps.

Cheers,
Rolf


Am 23.05.2017 um 04:02 schrieb 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


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

[Rolf Bensch]

Hi,

I see, the other work flows are pretty much easier for sane than git flow.

Am 20.05.2017 um 03:45 schrieb Olaf Meeuwissen:
> Hi,
> 
> Rolf Bensch writes:
> 
>> Hi,
>>
>>
>> Am 19.05.2017 um 15:02 schrieb Olaf Meeuwissen:
>>> Hi All(an),
>>>
>>> m. allan noah writes:
>>>
>>>> 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?
>>>
>>> Here's where git branches come in nice.  Rolf creates a branch, commits
>>> his bug fix and pushes the branch.  Next, he informs the project admins
>>> of the bug fix branch and that he would like to see it included in the
>>> upcoming releases.  The project admins have a look at the code changes
>>> and can decide for themselves and/or ask for more information as needs
>>> be.
>>>
>>> Right now, everything goes straight to master and I am not sure that is
>>> the best way to proceed when using git (Subversion and CVS are different
>>> beasts).  I also realize that forcing everything through some sort of
>>> review process is unrealistic for sane-backends where most developers
>>> are rather focussed on their own backend(s) only.  Maybe we should try
>>> to write up some kind of policy for pushing to master.
>>>
>>> Something like
>>>
>>>  - pushing changes to master for a backend you maintain is okay (unless
>>>in code freeze)
>>>  - pushing changes for code that affects multiple backends, something in
>>>sanei/ for example or the build system, should go to a branch and get
>>>reviewed before merging to master

I just pushed an doc update to master and created and pushed the branch
'pixma/mf240_adf_only_300dpi' with the corresponding bug fix. Outside
code freeze I'd have pushed the fix directly into master.

@Allan: You can decide if the branch can be merged into master before or
after the next release. If you won't merge it, I'll do it by myself
after the next release.
Background for this patch: The MF240 scanner supports only 300dpi for
adf scans. For this scanner I set the max. allowed value for adf scans
to 300dpi and activated and set the counterpart variable to 300dpi (min.
allowed value for adf scans). The activated variable is already in use
within other pixma sub-backends. This fix only affects the MF240 scanner.


>>>  - anything you like to have an extra pair of eyes on goes to a branch
>>>and you ask/assign someone for review (uh-oh, Alioth doesn't support
>>>merge requests ... :-(, mail and/or mailing list for now?)
>>>  - ... and some more for non-SANE developers that I'll skip for now
>>>

If I wanted to ask someone to review the new branch, I'd named it as
'pixma/review/mf240_adf_only_300dpi'.

According to gitlab flow and github flow I would add these items:

- master is always 'stable'
  then the 'daily git snapshots' on the website can be renamed from
  'Unstable (Development) Source' to something like 'Stable Post Release
  source', I suppose that sane won't provide unstable sources in
  tarballs anymore
- releases, feature freeze and code freeze are tagged on master, e.g.
  RELEASE_1_0_27, FEATURE_FREEZE_PRE_1_0_27, CODE_FREEZE_PRE_1_0_27
  the restrictions for the freeze tags should be written into the tag
  message

>>
>> In real life my company is using the gitflow structure to organize the
>> projects in git:
>> https://datasift.github.io/gitflow/IntroducingGitFlow.html . The
>> developer is free installing gitflow or not, but he|she must always
>> stick to the gitflow structure on the gitlab server.
> 
> I'm aware of Git Flow.  It has its good points but I tend to find it a
> bit over-engineered.  Maybe for a big corporate project, yes, but for
> something like sane-backends I think it too complex.  Something like
> GitLab Flow[1,2] (or GitHub Flow[3]) would be more suitable, IMHO, but
> with a few reasonably well-defined exceptions for the "no direct commits
> to master" rule (as I mentioned above).
> 
>  [1] https://docs.gitlab.com/ce/workflow/gitlab_flow.html
>  [2] https://about.gitlab.com/2016/07/27/the-11-rules-of-gitlab-flow/
>  [3] https://guides.github.com/introduction/flow/
> 

>From my point of view, the new branch is a trial balloon for working
with and|or reviewing branches. Please feel free to define any naming
standard as you like.

Cheers,
Rolf

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

[Rolf Bensch]

Hi,


Am 19.05.2017 um 15:02 schrieb Olaf Meeuwissen:
> Hi All(an),
> 
> m. allan noah writes:
> 
>> 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?
> 
> Here's where git branches come in nice.  Rolf creates a branch, commits
> his bug fix and pushes the branch.  Next, he informs the project admins
> of the bug fix branch and that he would like to see it included in the
> upcoming releases.  The project admins have a look at the code changes
> and can decide for themselves and/or ask for more information as needs
> be.
> 
> Right now, everything goes straight to master and I am not sure that is
> the best way to proceed when using git (Subversion and CVS are different
> beasts).  I also realize that forcing everything through some sort of
> review process is unrealistic for sane-backends where most developers
> are rather focussed on their own backend(s) only.  Maybe we should try
> to write up some kind of policy for pushing to master.
> 
> Something like
> 
>  - pushing changes to master for a backend you maintain is okay (unless
>in code freeze)
>  - pushing changes for code that affects multiple backends, something in
>sanei/ for example or the build system, should go to a branch and get
>reviewed before merging to master
>  - anything you like to have an extra pair of eyes on goes to a branch
>and you ask/assign someone for review (uh-oh, Alioth doesn't support
>merge requests ... :-(, mail and/or mailing list for now?)
>  - ... and some more for non-SANE developers that I'll skip for now
> 

In real life my company is using the gitflow structure to organize the
projects in git:
https://datasift.github.io/gitflow/IntroducingGitFlow.html . The
developer is free installing gitflow or not, but he|she must always
stick to the gitflow structure on the gitlab server.

Hope this helps.

Cheers,
Rolf

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

[Rolf Bensch]

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



-- 
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] [PATCH] Add Canon MF230 Series

[Rolf Bensch]

Hello,

I just got a report from a MF240 Series scanner that only 300dpi is
possible (allowed) scanning from the document feeder. Please test this
and report your results.

Many thanks for your help in advance.

Cheers,
Rolf


Am 26.04.2017 um 11:51 schrieb Rolf Bensch:
>
> Hello,
>
> I just committed the patch to the git repository (pixma backend
> version >= 0.17.36) and updated the doc files. I also added the new
> scanners i-SENSYS MF240 Series
>
> Many thanks for your help.
>
> Cheers,
> Rolf
>
> Am 19.04.2017 um 21:47 schrieb Peter Talbott:
>>
>> Hello,
>>
>> I also have a Canon ImageClass MF232.
>>
>> I added that patch into the pixma_imageclass.c file, recompiled the
>> sane backeneds and it seems to work perfectly.
>>
>> Thank You!
>>
>>
>> On 04/17/2017 01:54 PM, thierry wrote:
>>> Hello,
>>>
>>> This little patch add support to Canon MF230 Series scanner.
>>> Tested OK (network only) on my MF232w :
>>> [bjnp] get_scanner_id: Scanner identity string =
>>> MFG:CANON;CMD:MFNP1,MultiPASS 2.1;MDL:Canon MF230
>>> Series;CLS:IMG;DES:Canon MF230 Series; - length = 88
>>> [bjnp] get_scanner_id: Scanner model = Canon MF230 Series
>>>
>>> Please commit.
>>> Best regards
>>>
>>>
>>>
>>>
>

-- 
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 ImageClass mf244dw

[Rolf Bensch]

Hi Curtis,

Please install recent SANE version from my Ubuntu PPA and report your
test results:

$ sudo add-apt-repository ppa:rolfbensch/sane-git

Hope this helps.

Cheers,
Rolf


Am 14.05.2017 um 15:43 schrieb Curtis Graham:
> Needing a little help getting the scanner working on this all-in-one
> from Canon.
> I am kinda a linux noob so hopefully I'm requesting this correctly. I
> originally posted for help in the Ubuntu help forums and one of the
> guys over there suggested I talked to you guys about this.
> Here is the original post I had over there
>
> https://ubuntuforums.org/showthread.php?t=2361040=13644030#post13644030
>
> If you need any other information just let me know
>
> 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

Re: [sane-devel] Version numbering (was Re: Fix PPA build)

[Rolf Bensch]

Hi All,

After reactivating my Ubuntu ppa it uses for the recent version
1.0.26~ppa[date].

OK, this breaks the old version from last July (1.0.26+git[date]), but I
communicated 2 instructions how the users can jump onto the new versions.

Don't worry about the Ubuntu distribution versions. They're still using
1.0.25+git20150528.

Using 'git describe' is an good idea. But please don't forget that we
must be able to compile the tarballs provided from sane's website and
alioth *without* installed git packages or with the correct version.

A header file (e.g. git-describe.h) could be a solution, which holds the
git version and has been created before creating the tarballs. If we're
compiling against a git repository, this file can be rewritten from
'make' and must be excluded from the git repository.

Hope this helps.

Cheers,
Rolf


Am 13.05.2017 um 05:10 schrieb Olaf Meeuwissen:
> Hi Allan,
> 
> m. allan noah writes:
> 
>> 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).
> 
> Most of the cases I've seen use a date for the xxx part.  If so, there'd
> be no problem as the git snapshots after the 1.0.26 release will have a
> later date.
> 
> Distributions can also work around with an "epoch", so you get something
> like "1:1.0.26+git", but that's a bit ugly.
> 
> But we could also just admit that we've more or less goofed up on the
> versioning for our master branch, skip 1.0.26 and release as 1.0.27.
> Doing so will bypass any of the scenarios you worry about.
> 
> I'd go with 1.0.27 but am fine with 1.0.26 for the release and add a
> +git on master (for now while we investigate using `git describe`).
> 
> 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

Re: [sane-devel] Fix PPA build

[Rolf Bensch]

Hi James,

I just found the problem in the build control file. Please test the
recent version from my ppa again.

Many thanks for your help.

Cheers,
Rolf

Am 09.05.2017 um 22:06 schrieb James Duvall:
> Rolf,
> 
> OK, now it makes more sense to me.  I saw that the last released version
> was 1.0.25, but I didn't fully comprehend that your ppa is a pre-release
> for 1.0.26.  When 1.0.26 is released, of course you would want these
> builds to compare earlier than the released version.
> 
> One thing I still don't fully comprehend.  libsane=1.0.26~preXXX depends
> on libsane-common=1.0.26~preXXX, but libsane=1.0.26~preXXX also breaks
> libsane-common<<1.0.26
> 
> This seems like a conflict.  Isn't this saying that libsane breaks the
> same version that it depends on?
> 
> Sorry if I am being frustrating or dense on this topic.  As I
> understand, apt and dpkg won't allow 2 different versions of the same
> package to be simultaneously installed.  If the pre-release libsane
> requires a specific version of libsane-common, doesn't that
> automatically imply that it breaks/conflicts with any other version? 
> libsane=1.0.26~preXXX will also break 1.0.27 or 1.1 or anything else
> that is released in the future, right?
> 
> Using your instructions, I still can't install using apt, dpkg.  I
> installed synaptic, but I get the same error and refusal to install (). 
> I am running yakkety, so maybe there is some difference from trusty.
> 
> However, this is not a big problem for me.  I am able to automatically
> build from the sane-backends package on your ppa, so I can test my
> MG5420 with the latest fixes.  I'll send another email once I have
> verified all functions and the scanbd script you sent me.
> 
> Many thanks,
> James
> On Tuesday, May 9, 2017 11:36 AM, Rolf Bensch <r...@bensch-online.de> wrote:
> 
> 
> 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
>>
> 
> I used synaptic for Trusty and it's working.
> 
> You can use an alternative more complex procedure to get the updates
> from my ppa:
> 
> (1) search for installed SANE packages:
> $ dpkg -l *sane*
> 
> (2) purge all SANE packages with the version '1.0.26[-+]ppa{date}
> *without* removing dependent packages:
> $ sudo dpkg --force-all -P libsane libsane-common sane-utils [other
> installed packages]
> 
> (3) reinstall SANE:
> $ apt-get -f install
> 
> (4) reinstall all other removed packages, e.g.:
> $ sudo apt-get install libsane-dev
> 
>> Apt complains that
>>
>> The following packages have unmet dependencies:
>>  libsane : Breaks: libsane-common (< 1.0.26)
>>Breaks: libsane-common:i386 (< 1.0.26)
>> E: Unable to correct problems, you have held broken packages.
>>
>> I think the issue is that version 1.0.26~ppa20170508-yakkety0 compares
>> less than 1.0.26 due to special rules for handling ~ in version
>> numbers.  The following shows this:
>>
>> dpkg --compare-versions 1.0.26~ppa20170508-yakkety0 lt 1.0.26 && echo true
>> true
>>
> 
> This is correct. SANE 1.0.26 isn't released yet.
> Inspired from your comment I renamed the version in my ppa to
> '1.0.26~pre{date}'. This makes it more transparent that this is a
> pre-release.
> 
>> I created a local repository and re-packaged as version
>> 1.0.26+ppa20170508-yakkety0 and was able to install with no problems, so
>> maybe change the ~ for + or some other separator?  I am not experienced
>> with debian package management, so please disregard if I am missing
>> something.
>>
> 
> Then you'll get the next update after we started the development of SANE
> version 1.0.27, then AKA version 1.0.27~pre{date} from my ppa repository
> 
> Many thanks for your report.
> 
> Hope this helps.
> 
> Cheers,
> 
> Rolf
> 
> 

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

[Rolf Bensch]

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
> 

I used synaptic for Trusty and it's working.

You can use an alternative more complex procedure to get the updates
from my ppa:

(1) search for installed SANE packages:
$ dpkg -l *sane*

(2) purge all SANE packages with the version '1.0.26[-+]ppa{date}
*without* removing dependent packages:
$ sudo dpkg --force-all -P libsane libsane-common sane-utils [other
installed packages]

(3) reinstall SANE:
$ apt-get -f install

(4) reinstall all other removed packages, e.g.:
$ sudo apt-get install libsane-dev

> Apt complains that
> 
> The following packages have unmet dependencies:
>  libsane : Breaks: libsane-common (< 1.0.26)
>Breaks: libsane-common:i386 (< 1.0.26)
> E: Unable to correct problems, you have held broken packages.
> 
> I think the issue is that version 1.0.26~ppa20170508-yakkety0 compares
> less than 1.0.26 due to special rules for handling ~ in version
> numbers.  The following shows this:
> 
> dpkg --compare-versions 1.0.26~ppa20170508-yakkety0 lt 1.0.26 && echo true
> true
> 

This is correct. SANE 1.0.26 isn't released yet.
Inspired from your comment I renamed the version in my ppa to
'1.0.26~pre{date}'. This makes it more transparent that this is a
pre-release.

> I created a local repository and re-packaged as version
> 1.0.26+ppa20170508-yakkety0 and was able to install with no problems, so
> maybe change the ~ for + or some other separator?  I am not experienced
> with debian package management, so please disregard if I am missing
> something.
> 

Then you'll get the next update after we started the development of SANE
version 1.0.27, then AKA version 1.0.27~pre{date} from my ppa repository

Many thanks for your report.

Hope this helps.

Cheers,
Rolf

-- 
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 (was Re: sane-backends release 1.0.26 schedule)

[Rolf Bensch]

Hello All,

My Ubuntu ppa (ppa:rolfbensch/sane-git
<https://launchpad.net/%7Erolfbensch/+archive/ubuntu/sane-git>) is
working again. It distributes pre-built packages for all supported
Ubuntu distributions (amd64, i386 and armhf architectures).

I changed the package names to fit the packages version convention a
little bit more. I hope that this helps to change the package names
provided from Ubuntu.

If you are already using my ppa, you must use the "Force Version"
function of your package manager once to get the updates.

Please report if you may have any problems.

Hope this helps.

Cheers,
Rolf


Am 07.05.2017 um 13:15 schrieb Rolf Bensch:
> Hi,
>
> @Olaf: Thanks for your patch. It's working with the ppa.
>
> Please have a look at the attached patches. Maybe there are additional
> fixes for SANE (fix_avahi_error_paths.patch) or there are needful
> additional options for configure possible or just keep them inside the ppa?
>
> Many thanks for your help.
>
> Cheers,
> Rolf
>
>
> Am 06.05.2017 um 14:00 schrieb Olaf Meeuwissen:
>> Hi Rolf,
>>
>> Rolf Bensch writes:
>>
>>> Hi Olaf,
>>>
>>> I tried to build a recent version for zesty some weeks ago with my test
>>> ppa: https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-test/+packages .
>> Thanks for the link!  Now I can see the build failures.
>> BTW, it looks like the build does not apply the debian/patches/.  Don't
>> know if that's intentional or not.
>>
>>> I'll try to investigate this issue next week. If you can provide a patch
>>> before, I can merge it into the build system very quickly.
>> See the attached.
>>  - debian/rules: modified a few configure flags and added one for the
>>API spec (BTW, 6ffeb909 fixed a brain fart for that option)
>>  - debian/control: add transfig as a build dependency for the spec (BTW,
>>we do PDF now too but that requires pdflatex and gs as well)
>>  - debian/patches/multiarch_dll_searc_path.patch: adjust to upstream
>>changes
>>
>> Note that this only aims to fix the xenial build but the other builds
>> should be mostly identical if not exactly.
>>
>> I've checked
>>
>>   debian/rules binary
>>   dpkg-buildpackage -b
>>
>> and both complete without a hitch, on xenial (in a Docker container).
>>
>> 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

Re: [sane-devel] Fix PPA build (was Re: sane-backends release 1.0.26 schedule)

[Rolf Bensch]

Hi,

@Olaf: Thanks for your patch. It's working with the ppa.

Please have a look at the attached patches. Maybe there are additional
fixes for SANE (fix_avahi_error_paths.patch) or there are needful
additional options for configure possible or just keep them inside the ppa?

Many thanks for your help.

Cheers,
Rolf


Am 06.05.2017 um 14:00 schrieb Olaf Meeuwissen:
> Hi Rolf,
> 
> Rolf Bensch writes:
> 
>> Hi Olaf,
>>
>> I tried to build a recent version for zesty some weeks ago with my test
>> ppa: https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-test/+packages .
> 
> Thanks for the link!  Now I can see the build failures.
> BTW, it looks like the build does not apply the debian/patches/.  Don't
> know if that's intentional or not.
> 
>> I'll try to investigate this issue next week. If you can provide a patch
>> before, I can merge it into the build system very quickly.
> 
> See the attached.
>  - debian/rules: modified a few configure flags and added one for the
>API spec (BTW, 6ffeb909 fixed a brain fart for that option)
>  - debian/control: add transfig as a build dependency for the spec (BTW,
>we do PDF now too but that requires pdflatex and gs as well)
>  - debian/patches/multiarch_dll_searc_path.patch: adjust to upstream
>changes
> 
> Note that this only aims to fix the xenial build but the other builds
> should be mostly identical if not exactly.
> 
> I've checked
> 
>   debian/rules binary
>   dpkg-buildpackage -b
> 
> and both complete without a hitch, on xenial (in a Docker container).
> 
> 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
> 



patches.tar.gz
Description: application/gzip
-- 
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

[Rolf Bensch]

Hi Olaf,

I tried to build a recent version for zesty some weeks ago with my test
ppa: https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-test/+packages .

I'll try to investigate this issue next week. If you can provide a patch
before, I can merge it into the build system very quickly.

Hope this helps.

Cheers,
Rolf


Am 06.05.2017 um 08:32 schrieb Olaf Meeuwissen:
> Hi again,
> 
> Olaf Meeuwissen writes:
> 
>> Hi Allan,
>>
>> m. allan noah writes:
>>
>>> Ok folks, it's time to get another sane-backends release out the door.
>>
>> [snip]
>>> However, there are a handful of patches in
>>> the bug tracker that could still be applied, once they are reviewed.
>>
>> I'm working through the recent patches to the mailing list.
> 
> I'm done with the patches to the mailing list as well as any in the bug
> tracker.  I've gone back all the way to September 2015.  There are still
> a few patches in the bug tracker for issues that have been assigned and
> seen follow-up from assignees.  Those I haven't touched.  I'll leave
> these to the respective assignees.
> 
> # Going through all open bugs looking for patches is *no* fun.  I had to
> # open every single bug report :-(  Is there no way to flag bug reports
> # with a patch so I can query on that?
> 
>> I also have some concerns about Wilhelm's report (from 2017-04-05)
>> that looping over
>>
>>   sane_init()
>>   sane_get_devices()
>>   sane_exit()
>>
>> crashes on Debian (not on Arch Linux or Gentoo).  It appears to be an
>> issue with threading.  I know the sanei_thread API has issues but
>> haven't gotten around to testing this.  I hope to take a look before
>> the release.
> 
> This seems to have been fixed in git.  See the mailing list for details.
> 
>> [snip]
>> Do you need a hand writing or an eye reviewing the release notes?  If
>> yes, just say so.
>>
>> Please mention that the USB support's configure option has changed, that
>> libusb-0.1 is deprecated and that libusb-1.0 is the default now (if both
>> are available).  This may hit unsuspecting binary package maintainers.
>>
>> @Rolf> Could the changed configure option be why your PPAs no longer
>>build?  See a9c81394 for details.  You want --with-usb (or just
>>default if a libusb*-dev package is in the Build-Depends).  If
>>it's something else, let us know what's preventing your builds
>>from succeeding.
> 
> I've started looking at Rolf's PPA build issue.  It doesn't seem to be
> the --with-usb flag that's causing the trouble.  There's a couple of
> things that need fixing but I'll have a look at that later today or
> tomorrow.
> 
>> As there have been some changes in configure.ac and friends, I'll check
>> if the doc/backend-writing.txt file needs updating.
> 
> This is still on my 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

Re: [sane-devel] [sane-commit] [sane-backends] 02/02: fix 1200 dpi scanning for MB5000 series

[Rolf Bensch]

Hello Louis,

Please don't forget to increment the pixma backend version in pixma.h
(PIXMA_VERSION_BUILD) and in pixma.desc (version) after patching the code.

Many thanks.

Cheers,
Rolf


Am 03.05.2017 um 16:35 schrieb Louis Lagendijk:
> This is an automated email from the git hooks/post-receive script.
>
> llagendijk-guest pushed a commit to branch master
> in repository sane-backends.
>
> commit 0ca2fc46136dbaa30da25f4b79b67871c7e2d39b
> Author: Louis Lagendijk 
> Date:   Wed May 3 13:52:06 2017 +0200
>
> fix 1200 dpi scanning for MB5000 series
> ---
>  backend/pixma_mp150.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/backend/pixma_mp150.c b/backend/pixma_mp150.c
> index 74fc8e8..dca0965 100644
> --- a/backend/pixma_mp150.c
> +++ b/backend/pixma_mp150.c
> @@ -1178,7 +1178,8 @@ post_process_image_data (pixma_t * s, pixma_imagebuf_t 
> * ib)
>&& s->cfg->pid != MG6400_PID
>&& s->cfg->pid != MG7100_PID
>&& s->cfg->pid != MG7500_PID
> -  && s->cfg->pid != MG7700_PID)
> +  && s->cfg->pid != MG7700_PID
> +  && s->cfg->pid != MB5000_PID)
>reorder_pixels (mp->linebuf, sptr, c, n, m, s->param->wx, 
> line_size);
>
>/* Crop line to selected borders */
>



-- 
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] Typo in pixma.desc

[Rolf Bensch]

Hi Olaf,

I just fixed the typo. Many thanks for your hint.

Cheers,
Rolf

Am 27.04.2017 um 13:32 schrieb Olaf Meeuwissen:
> Hi Rolf,
> 
> I just noticed
> 
>   pixma.desc: Warning: `pixma's USB product id of `PIXMA TS5000 Series' is 
> not a lowercase 4-digit hex number: `0x18022'
> 
> in the make output for the tools/ directory.  I think you meant 0x1802
> but can you check and fix this?
> 
> Thanks in advance,
> --
> 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

Re: [sane-devel] [PATCH] Add Canon MF230 Series

[Rolf Bensch]

Hello,

I just committed the patch to the git repository (pixma backend version
>= 0.17.36) and updated the doc files. I also added the new scanners
i-SENSYS MF240 Series

Many thanks for your help.

Cheers,
Rolf

Am 19.04.2017 um 21:47 schrieb Peter Talbott:
>
> Hello,
>
> I also have a Canon ImageClass MF232.
>
> I added that patch into the pixma_imageclass.c file, recompiled the
> sane backeneds and it seems to work perfectly.
>
> Thank You!
>
>
> On 04/17/2017 01:54 PM, thierry wrote:
>> Hello,
>>
>> This little patch add support to Canon MF230 Series scanner.
>> Tested OK (network only) on my MF232w :
>> [bjnp] get_scanner_id: Scanner identity string =
>> MFG:CANON;CMD:MFNP1,MultiPASS 2.1;MDL:Canon MF230
>> Series;CLS:IMG;DES:Canon MF230 Series; - length = 88
>> [bjnp] get_scanner_id: Scanner model = Canon MF230 Series
>>
>> Please commit.
>> Best regards
>>
>>
>>
>>

-- 
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 PIXMA MX320 0x04a9/0x1736 UNTESTED

[Rolf Bensch]

Please test all options, e.g. with scan2pdf.

Cheers,
Rolf


Am 14.01.2017 um 06:57 schrieb Two Spirit:
> I have this printer. I can test, but I need to know what the criteria is.
> scanimage > file.pnm works for me.


-- 
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] [Scanbd] Set up for Canon PIXMA multifunction scanner - no button response

[Rolf Bensch]

Hi Matt,

Sorry for the late response.

The command line must run without
'SANE_CONFIG_DIR=/usr/local/etc/scanbd/sane.d'. Maybe you don't have the
user rights to access your scanner via USB. Please try following:
(1) push any button
(2) sudo su -c "SANE_DEBUG_PIXMA=11 scanimage -A"

Please send me the complete log response.

Cheers,
Rolf

Am 13.10.2016 um 23:29 schrieb matt clark:
> Hi Rolf, the "buttons" section in the code shows this:
> 
>   Buttons:
> --button-update
> Update button state
> --button-1  [0] [read-only]
> Button 1
> --button-2  [0] [read-only]
> Button 2
> --original  [0] [read-only]
> Type of original to scan
> --target  [0] [read-only]
> Target operation type
> --scan-resolution  [0] [read-only]
> Scan resolution
> 
> None of the binary code you mentioned.  Does this mean there is no
> sane support for the buttons?  Note that I had to use the command
> SANE_CONFIG_DIR=/usr/local/etc/scanbd/sane.d SANE_DEBUG_PIXMA=11
> scanimage -A to make it work.  I pushing both buttons, and sending it
> via USB (yes it's connected) and the "localhost saned" option which is
> I assume sending via network.
> 
> On Fri, Oct 14, 2016 at 7:16 AM, Rolf Bensch <r...@bensch-online.de> wrote:
>> Hi Matt,
>>
>> Have you tested that your scanner resp. the backend sends data @ a push
>> button event?
>>
>> Please test on the console:
>> (1) push any button
>> (2) $ SANE_DEBUG_PIXMA=11 scanimage -A
>> (3) check the response; I'm especially interested in following lines:
>>
>>   Buttons:
>> --button-update
>> Update button state
>> [pixma] INTR T=1.343 len=32
>> [pixma]  :00 20 00 00 00 00 00 00  00 00 00 00 00 00 00 00
>> [pixma]  0010:00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
>> [pixma]
>> --button-1  [1] [read-only]
>> Button 1
>> --button-2  [0] [read-only]
>> Button 2
>> --original  [0] [read-only]
>> Type of original to scan
>> --target  [2] [read-only]
>> Target operation type
>> --scan-resolution  [0] [read-only]
>> Scan resolution
>>
>> Please repeat (1) ... (3) for all scan buttons.
>>
>> Maybe you need to test your scanner USB connected to the pc. I haven't
>> tested push buttons wireless yet.
>>
>> If you don't get lines starting with [pixma], your scanner has no button
>> support from SANE.
>>
>> If you get lines starting with [pixma] with more data as shown above (I
>> have a different scanner) and without data output below at the
>> parameters --button-1 ... --scan-resolution, what I suppose, then please
>> send me your "Buttons:" logs and I'll fix the backend code.
>>
>> Hope this helps.
>>
>> Cheers,
>> Rolf
>>
>> Am 13.10.2016 um 13:23 schrieb Wilhelm:
>>> Oh, mixed the values ...
>>>
>>>  action btest {
>>>  filter = "^button.*"
>>>  numerical-trigger {
>>>  from-value = 0
>>>  to-value   = 1
>>>  }
>>>  desc   = "Scan to file"
>>>  script = "test.script"
>>>  }
>>>
>>>
>>> Am 13.10.2016 um 11:16 schrieb Wilhelm:
>>>> Matt, you need something like this in your config:
>>>>
>>>> action btest {
>>>> filter = "^button.*"
>>>> numerical-trigger {
>>>> from-value = 1
>>>> to-value   = 0
>>>> }
>>>> desc   = "Scan to file"
>>>> script = "test.script"
>>>> }
>>>>
>>>> --
>>>>  Wilhelm
>>>>
>>>> Am 13.10.2016 um 09:09 schrieb matt clark:
>>>>> Thanks Wilhelm.  I had changed that while trying to debug the problem,
>>>>> not sure why this would be a problem.  Have reverted to the
>>>>> scanbd.conf from source, with modifications to sane.d directory and
>>>>> comment out the unnecessary manufacturer scanner.d profiles.  revised
>>>>> config is attached - apologies for the length of code.
>>>>>
>>>>> ---
>>>>>
>>>>> /*
>>>>>  * $Id: scanbd.conf 213 201

Re: [sane-devel] [Scanbd] Set up for Canon PIXMA multifunction scanner - no button response

[Rolf Bensch]

Hi Matt,

Have you tested that your scanner resp. the backend sends data @ a push
button event?

Please test on the console:
(1) push any button
(2) $ SANE_DEBUG_PIXMA=11 scanimage -A
(3) check the response; I'm especially interested in following lines:

  Buttons:
--button-update
Update button state
[pixma] INTR T=1.343 len=32
[pixma]  :00 20 00 00 00 00 00 00  00 00 00 00 00 00 00 00
[pixma]  0010:00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
[pixma]
--button-1  [1] [read-only]
Button 1
--button-2  [0] [read-only]
Button 2
--original  [0] [read-only]
Type of original to scan
--target  [2] [read-only]
Target operation type
--scan-resolution  [0] [read-only]
Scan resolution

Please repeat (1) ... (3) for all scan buttons.

Maybe you need to test your scanner USB connected to the pc. I haven't
tested push buttons wireless yet.

If you don't get lines starting with [pixma], your scanner has no button
support from SANE.

If you get lines starting with [pixma] with more data as shown above (I
have a different scanner) and without data output below at the
parameters --button-1 ... --scan-resolution, what I suppose, then please
send me your "Buttons:" logs and I'll fix the backend code.

Hope this helps.

Cheers,
Rolf

Am 13.10.2016 um 13:23 schrieb Wilhelm:
> Oh, mixed the values ...
>
>  action btest {
>  filter = "^button.*"
>  numerical-trigger {
>  from-value = 0
>  to-value   = 1
>  }
>  desc   = "Scan to file"
>  script = "test.script"
>  }
>
>
> Am 13.10.2016 um 11:16 schrieb Wilhelm:
>> Matt, you need something like this in your config:
>>
>> action btest {
>> filter = "^button.*"
>> numerical-trigger {
>> from-value = 1
>> to-value   = 0
>> }
>> desc   = "Scan to file"
>> script = "test.script"
>> }
>>
>> --
>>  Wilhelm
>>
>> Am 13.10.2016 um 09:09 schrieb matt clark:
>>> Thanks Wilhelm.  I had changed that while trying to debug the problem,
>>> not sure why this would be a problem.  Have reverted to the
>>> scanbd.conf from source, with modifications to sane.d directory and
>>> comment out the unnecessary manufacturer scanner.d profiles.  revised
>>> config is attached - apologies for the length of code.
>>>
>>> ---
>>>
>>> /*
>>>  * $Id: scanbd.conf 213 2015-10-05 06:52:50Z wimalopaan $
>>>  *
>>>  *  scanbd - KMUX scanner button daemon
>>>  *
>>>  *  Copyright (C) 2008 - 2015  Wilhelm Meier (wilhelm.me...@fh-kl.de)
>>>  *
>>>  *  This program is free software; you can redistribute it and/or modify
>>>  *  it under the terms of the GNU General Public License as published by
>>>  *  the Free Software Foundation; either version 2 of the License, or
>>>  *  (at your option) any later version.
>>>  *
>>>  *  This program is distributed in the hope that it will be useful,
>>>  *  but WITHOUT ANY WARRANTY; without even the implied warranty of
>>>  *  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
>>>  *  GNU General Public License for more details.
>>>  *
>>>  *  You should have received a copy of the GNU General Public License
>>>  *  along with this program; if not, write to the Free Software
>>>  *  Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
>>> 02110-1301, USA.
>>>  */
>>>
>>>
>>> # global settings
>>> global {
>>> # turn on debugging
>>>
>>> # log to console
>>> debug   = true
>>>
>>> # debug logging
>>> # 1=error, 2=warn, 3=info, 4-7=debug
>>> debug-level = 7
>>>
>>> # drop priviliges to this user
>>> #=
>>> # Linux (most distributions use the saned user):
>>> # user= saned
>>> # ArchLinux (ArchLinux doesn't have saned user)
>>> # user= daemon
>>> # *BSD
>>> # user= root
>>> user= saned
>>>
>>> # Group to be used
>>> #=
>>> # Linux (most distributions use the lp group to access scanners)
>>> # group   = lp
>>> # ArchLinux (ArchLinux uses the scanner group)
>>> # group = scanner
>>> #
>>> # *BSD (no group lp here, use daemon instead)
>>> # group   = daemon # root
>>> #
>>> group   = lp
>>>
>>> # the saned executable for manager-mode
>>> saned   = "/usr/sbin/saned"
>>> saned_opt  = {} # string-list
>>> saned_env  = { "SANE_CONFIG_DIR=/etc/scanbd/sane.d" } # list of
>>> environment vars for saned
>>>
>>> # Scriptdir specifies where scanbd normally looks for scripts.
>>> # The scriptdir option can be defined as:
>>> #   - a path relative to the configuations (/etc/scanbd) 
>>> directory
>>>   

Re: [sane-devel] [PATCH] Fix ADF scanning for Canon MF57x0 devices

[Rolf Bensch]

Hello Dmitry,

I just pushed your patch to SANEs git repository.

The MF5750 still has the status untested. Have you also tested this
device or can you confirm that this device is working?

Many thanks for your help.

Cheers,
Rolf

Am 30.09.2016 um 15:38 schrieb Dmitry Deshevoy:
> Canon MF57x0 devices require abort_session() after each page except
> the last one.
> The result from calibrate() should be ignored, so that scanning is not
> interrupted with PIXMA_STATUS_BUSY.
> ---
>  backend/pixma_mp730.c | 31 ++-
>  1 file changed, 18 insertions(+), 13 deletions(-)
>
> diff --git a/backend/pixma_mp730.c b/backend/pixma_mp730.c
> index 06bc9ee..b0692e4 100644
> --- a/backend/pixma_mp730.c
> +++ b/backend/pixma_mp730.c
> @@ -459,6 +459,8 @@ step1 (pixma_t * s)
>default:
>  break;
>  }
> +
> +  error = 0;
>  }
>if (error >= 0)
>  error = activate (s, 0);
> @@ -747,19 +749,22 @@ mp730_finish_scan (pixma_t * s)
>query_status (s);
>activate (s, 0);
>
> -  if (! aborted && s->cfg->pid == IR1020_PID)
> - {
> -  error = abort_session (s);
> -  if (error < 0)
> -{
> -  PDBG (pixma_dbg
> -(1, "WARNING:abort_session() failed %s\n",
> - pixma_strerror (error)));
> -  query_status (s);
> -  query_status (s);
> -  activate (s, 0);
> -}
> - }
> +  if (!aborted &&
> +  (s->param->source == PIXMA_SOURCE_ADF ||
> +   s->param->source == PIXMA_SOURCE_ADFDUP) &&
> +  has_paper (s) &&
> +  (s->cfg->pid == MF5730_PID ||
> +   s->cfg->pid == MF5750_PID ||
> +   s->cfg->pid == MF5770_PID ||
> +   s->cfg->pid == IR1020_PID))
> +{
> +  error = abort_session (s);
> +  if (error < 0)
> +PDBG (pixma_dbg
> +  (1, "WARNING:abort_session() failed %s\n",
> +   pixma_strerror (error)));
> +}
> +
>mp->buf = mp->lbuf = mp->imgbuf = NULL;
>mp->state = state_idle;
>/* fall through */



-- 
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] Linux Step by Step Installation Manual

[Rolf Bensch]

Hello List,

With my last commit I created a new file:

INSTALL.linux

and moved the Linux step by step installation manual from README.linux
to it.

I hope this helps new users to find this manual by its filename.

First I planned to move the manual into INSTALL. But this would explode
the size of this document and could confuse other OSs installers.

I already updated the website: http://www.sane-project.org/docs.html .

Cheers,
Rolf


-- 
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 9000f MK2 48bit Color Gamma Too Dark

[Rolf Bensch]

Hello Roger,

Sorry for the late response.

I can still remember that the scanner doesn't accept gamma settings for
48 bits color scans. So you need to post process the images if they are
too dark. This is what you're doing within Gimp.

Cheers,
Rolf


Am 02.04.2016 um 06:39 schrieb Roger:
>> On Thu, Mar 31, 2016 at 09:33:12PM -0400, Roger wrote:
>> I think I've found a bug (when using a Canon 9000f MK2), scanning at 16 bits 
>> color (AKA "Color") produces an apparent proper image gamma of 2.2, while 
>> choosing to scan at "48 bits color" produces an image too dark, or an image 
>> having an approximate gamma of less than or equal to one.
>>
>> Both scanimage and xsane, as well as enabling and disabling Color Managment 
>> exhibit this problem.
>>
>> A temporary work around when scanning at "48 bits color", would be to open 
>> the 
>> scanned image within Gimp, opening Levels and moving the middle slider on 
>> the 
>> first slider to a value of 2.2.  (Hence, first selecting Auto Level, then 
>> adjusting the gamma to 2.2.)
>>
>> Feedback on this issue?
> I think I can answer my own question here, as this appears to be a standard.
>
> VueScan PDF User Manual, page 89, nine paragraphs/sections down.
>
> "The image gamma value is 1.0 when there are two bytes (16-bits) per sample, 
> and 2.2 when there is one byte (8-bits) per sample. Raw files saved with 
> gamma 
> 1.0 will look dark, but this is normal."
>
> Also on page 76, maybe relevant for some situations:
>
> "Note that if you use the Apple RGB, ColorMatch RGB, ProPhoto RGB or ECI RGB 
> color space, the image gamma will be 1.8. If you use any other color space, 
> the 
> image gamma will be 2.2."
>
>
> So I'm guessing in order to work with 16 bit/channel images (ie. 48 bit 
> color), 
> we'll need to bump the gamma to 2.2 when their viewed on our sRGB displays, 
> else they're too dark?
>
>



-- 
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] Feedback Canon MG7750 / PIXMA backend

[Rolf Bensch]

Hi Frank,

I attached a patch for this issue. You need to patch the file
"backend/pixma_mp150.c".

Please report your results.

Many thanks for your help.

Cheers,
Rolf

Am 25.03.2016 um 13:25 schrieb FS:
> Hi all,
> I recently bought a Canon MG7750. And I was rather badly surprised by
> Canons own scanner driver for Linux.
> Hence, first and foremost a big thank you to the SANE developers for
> adding support for this model.
>
> Since you asked for testers I made some scans with different settings.
> All resolutions up to 600DPI work fine (http://susepaste.org/350ec6bf ).
> 1200DPI and 2400DPI work but the result looks rather strange
> (=unusable) (http://susepaste.org/a7dbf6b8 and
> http://susepaste.org/1ac92632 ).
>
> All three files should show exactly the same picture.
> For scanning only the resolution changed. No other setting was changed.
> To reduce file size I compressed the images pretty strongly before
> uploading. The 2400DPI scan is also reduced in resolution.
> Hence, quality is well below the real scan quality.
> But the problem is clearly visible.
>
> SANE backends are from sane-backends-git20160322. OS is openSUSE
> Leap42.1.
>
> I hope this information helps. I will be happy to test newer versions
> or tell you more information.
>
> Cheers
> Frank
>
>
>

--- ./pixma_mp150.c	2016-03-31 11:13:01.730683710 +0200
+++ ../sane-backends/backend/pixma_mp150.c	2016-03-31 11:13:33.432333614 +0200
@@ -1166,7 +1166,8 @@
   && s->cfg->pid != MG6300_PID
   && s->cfg->pid != MG6400_PID
   && s->cfg->pid != MG7100_PID
-  && s->cfg->pid != MG7500_PID)
+  && s->cfg->pid != MG7500_PID
+  && s->cfg->pid != MG7700_PID)
   reorder_pixels (mp->linebuf, sptr, c, n, m, s->param->wx, line_size);
   
   /* Crop line to selected borders */
-- 
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 MG6650 (6600 Series)

[Rolf Bensch]

Hello,

Your scanner is supported since Sane version 1.0.25.

Please check the used Sane version with: "scanimage -V".

As you can see here: http://sane-project.org/sane-backends.html#S-PIXMA
and here: http://sane-project.org/lists/sane-backends-cvs.html#S-PIXMA ,
your scanner has the status "Untested".

This means that it should run out of the box and can scan up to 600 dpi.
I suppose that 1200 dpi scans are shifted (half images are stacked).

If you're using an Ubuntu based distribution, you can install my ppa to
get Sane's recent development version:
$ sudo add-apt-repository ppa:rolfbensch/sane-git

Otherwise you need to install Sane from source as described in chapter
"Step by step install on Linux 2.6.* and 3.*" in README.linux:
http://sane-project.org/docs.html

If the 1200dpi scan is shifted, I can fix it within a few days.

Hope this helps.

Cheers,
Rolf


Am 26.03.2016 um 19:29 schrieb rpk:
> Dear Ladies and Gentlemen,
>
> sending you the result by "sane-find-scanner" below. The Problem is
> that sane does not find the scanner.
> It would be great if you can help.
>
> Yours Sincerely
>
> Rolf-Peter Kraft
> mailto:m...@rolf-peter-kraft.de
>
>
> sudo sane-find-scanner
>
> [sudo] password for rpk:
>
>   # 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=0x0bda [Manufacturer Realtek ],
> product=0x8174 [RTL8192S WLAN Adapter ]) at libusb:004:003
> found USB scanner (vendor=0x04a9 [Canon], product=0x177e [MG6600
> series]) at libusb:001:002
>   # 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.
>
>
>



-- 
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 Maxifiy MB2000 series

[Rolf Bensch]

Hi Jörn-Ingo,

Your new Sane installation is working with the patch, but not the ADF.

Please be patient. I'll have to look deeper into the protocols. Maybe
after Easter.

Cheers,
Rolf


Am 24.03.2016 um 15:32 schrieb Jörn-Ingo Weigert:
> Hi Rolf,
> after a challenge how to compile the source :-P , i could compile the
> source with your patch.
> Is this correct when I check the version of "scanimage" that it reports:
> "scanimage (sane-backends) 1.0.26git; backend version 1.0.26" ?
> 
> This is the output of "sudo ldconfig -v | grep libsane":
> 
> /sbin/ldconfig.real: »stat()« kann nicht für »/lib/i686-linux-gnu«
> aufgerufen werden: Datei oder Verzeichnis nicht gefunden
> /sbin/ldconfig.real: »stat()« kann nicht für »/usr/lib/i686-linux-gnu«
> aufgerufen werden: Datei oder Verzeichnis nicht gefunden
> /sbin/ldconfig.real: Pfad »/lib/x86_64-linux-gnu« mehrfach angegeben
> /sbin/ldconfig.real: Pfad »/usr/lib/x86_64-linux-gnu« mehrfach angegeben
> /sbin/ldconfig.real: /lib/i386-linux-gnu/ld-2.19.so <http://ld-2.19.so>
> is the dynamic linker, ignoring
> 
> libsane.so.1 -> libsane.so.1.0.26
> libsane.so.1 -> libsane.so.1.0.26
> /sbin/ldconfig.real: /lib/x86_64-linux-gnu/ld-2.19.so
> <http://ld-2.19.so> is the dynamic linker, ignoring
> 
> libsane.so.1 -> libsane.so.1.0.26
> /sbin/ldconfig.real: /lib32/ld-2.19.so <http://ld-2.19.so> is the
> dynamic linker, ignoring
> 
> /sbin/ldconfig.real: /lib/ld-lsb.so.3 is the dynamic linker, ignoring
> 
> When I try to test the ADF with your previous command:
> scanimage --source "Automatic Document Feeder" -l 100 -x 10 -y 10
> 2>pixma.log > pixma.pnm
> 
> I still get the attached log.. and no paper feeding nor scanning
> 
> 
> 
> 
> 2016-03-23 22:13 GMT+01:00 Rolf Bensch <r...@bensch-online.de
> <mailto:r...@bensch-online.de>>:
> 
> Hi,
> 
> Based on the wireshark logfile you sent me before, I prepared a 1st
> patch.
> 
> To use this patch you need to install Sane from source as described in
> README.linux in chapter "Step by step install on Linux 2.6.* and 3.*"
> (http://sane-project.org/docs.html).
> 
> Then you need to patch the file "backend/pixma_mp150.c" with the
> attached file "pixma_mp150.c.patch1":
> (1) save attached file to folder backend
> (2) cd into folder backend
> (3) run command:
> $ patch pixma_mp150.c pixma_mp150.c.patch1
> (4) make and install Sane
> $ cd ..
> $ make && sudo make install
> 
> Please try scanning one page from ADF, then 2 pages and after this try
> duplex ADF.
> 
> The scanner may hang anywhere. Please create a log file for this test
> function.
> 
> Many thanks for your help.
> 
> Cheers,
> Rolf
> 
> 
> Am 23.03.2016 um 16:59 schrieb Jörn-Ingo Weigert:
> > Hi Rolf,
> > The scanner reacts on scanimage --source "Automatic Document Feeder" -l
>     > 100 -x 10 -y 10 2>
> > pixma.log > pixma.pnm (wokeup yes, displaying "Progress .. please
> > wait... ")
> >
> > unfortunately it dont feed the paper into the adf nor try to scan.
> >
> > I attached pixma.log and output--test.txt (made with scanimage --test)
> >
> > hope it help.
> >
> > 2016-03-22 14:15 GMT+01:00 Rolf Bensch <r...@bensch-online.de 
> <mailto:r...@bensch-online.de>
> > <mailto:r...@bensch-online.de <mailto:r...@bensch-online.de>>>:
> >
> > Hi,
> >
> > Sorry, there was a copy and paste error inside the command:
> > "Transparency Unit" must be replaced by "Automatic Document
> Feeder". The
> > command for scanning a *single* page is:
> >
> > $ scanimage --source "Automatic Document Feeder" -l 100 -x 10
> -y 10 2>
> > pixma.log > pixma.pnm
> >
> > Maybe the scanner hangs. Then the log file will help debugging
> this
> > issue.
> >
> > If you want to use scanimage or xsane scanning more than one
> page from
> > ADF, you need to enable batch mode. Please read the man pages for
> > details.
> >
> > Therefore I prefer gscan2pdf for ADF scans.
> >
> > You can create log files in a terminal window with:
> >
> > $ SANE_DEBUG_PIXMA=11 gscan2pdf &> pixma.log
> >
> > May

Re: [sane-devel] Canon Maxifiy MB2000 series

[Rolf Bensch]

Hi,

Based on the wireshark logfile you sent me before, I prepared a 1st patch.

To use this patch you need to install Sane from source as described in
README.linux in chapter "Step by step install on Linux 2.6.* and 3.*"
(http://sane-project.org/docs.html).

Then you need to patch the file "backend/pixma_mp150.c" with the
attached file "pixma_mp150.c.patch1":
(1) save attached file to folder backend
(2) cd into folder backend
(3) run command:
$ patch pixma_mp150.c pixma_mp150.c.patch1
(4) make and install Sane
$ cd ..
$ make && sudo make install

Please try scanning one page from ADF, then 2 pages and after this try
duplex ADF.

The scanner may hang anywhere. Please create a log file for this test
function.

Many thanks for your help.

Cheers,
Rolf


Am 23.03.2016 um 16:59 schrieb Jörn-Ingo Weigert:
> Hi Rolf,
> The scanner reacts on scanimage --source "Automatic Document Feeder" -l
> 100 -x 10 -y 10 2>
> pixma.log > pixma.pnm (wokeup yes, displaying "Progress .. please
> wait... ") 
> 
> unfortunately it dont feed the paper into the adf nor try to scan.
> 
> I attached pixma.log and output--test.txt (made with scanimage --test)
> 
> hope it help.
> 
> 2016-03-22 14:15 GMT+01:00 Rolf Bensch <r...@bensch-online.de
> <mailto:r...@bensch-online.de>>:
> 
> Hi,
> 
> Sorry, there was a copy and paste error inside the command:
> "Transparency Unit" must be replaced by "Automatic Document Feeder". The
> command for scanning a *single* page is:
> 
> $ scanimage --source "Automatic Document Feeder" -l 100 -x 10 -y 10 2>
> pixma.log > pixma.pnm
> 
> Maybe the scanner hangs. Then the log file will help debugging this
> issue.
> 
> If you want to use scanimage or xsane scanning more than one page from
> ADF, you need to enable batch mode. Please read the man pages for
> details.
> 
> Therefore I prefer gscan2pdf for ADF scans.
> 
> You can create log files in a terminal window with:
> 
> $ SANE_DEBUG_PIXMA=11 gscan2pdf &> pixma.log
> 
> Maybe you want to check the capabilities of your scanner:
> 
> $ scanimage --help
> 
> The scanner must be switched on for this test.
> 
> Hope this helps.
> 
> Cheers,
> Rolf
> 
> 
> 
> Am 20.03.2016 um 13:05 schrieb Jörn-Ingo Weigert:
> > Here ist a logfile made with scanimage --test because I dont know how to
>     > select the ADF as source,
> >
> > I tried scanimage --source "Automatic Document Feeder" and also
> > scanimage --source "ADF"
> >
> > Any thoughts?
> >
> > Kind regards,
> >
> > Jörn-Ingo Weigert
> >
> > 2015-11-02 22:37 GMT+01:00 Rolf Bensch <r...@bensch-online.de 
> <mailto:r...@bensch-online.de>
> > <mailto:r...@bensch-online.de <mailto:r...@bensch-online.de>>>:
> >
> > Hi,
> >
> > Sorry for my late response.
> >
> > Am 25.10.2015 um 10:55 schrieb Jörn-Ingo Weigert:
> > > I can report that sane does support the rudimentary scanning
> with the
> > > Canon Maxify MB2000 series MFP printer under Ubuntu 14.04 LTS.
> > >
> > > I installed the drivers from Canon Website for Linux.
> > > Configured the appropriate permissions to access the scanner
> device
> > > via USB.
> > >
> > > What works:
> > > - Scanning in 300 / 600dpi works from Flatbed with Ubuntu
> own Simple
> > > Scan and XSane
> > >
> > OK. Many thanks for your report.
> >
> > > What does not work:
> > > - Scanning over / with ADF: The Scanner recognize that there
> comes a
> > > command (display lights up, showing "Process command..." but
> does NOT
> > > activate the feeder or start to scan. :-(
> > > Scanning via Canon own tool scangear works on both flatbed
> and adf scan.
> > >
> > Please sniff the USB protocols from a small scangear adf scan,
> e.g.
> > 10x10mm @ 75dpi with wireshark.
> > And again in a different log file from Sane in a Linux terminal:
> >
> > (1) $ export SANE_DEBUG_PIXMA=11
> > (2) $ scanimage --source "Transparency Unit" -l 100 -x 10 -y 10 2>
> > pixma.log > pixma.pnm
> >
>   

Re: [sane-devel] PIXMA: New Protocol Timeouts

[Rolf Bensch]

Hi Louis,

In the meantime I had time to work a little on the imageclass sub-backend.

Please have a look at these commits:
c41640f
bbd327f

For the 1st possibly failing USB command I chose a reduced timeout
duration of 2 sec.

This code also affects the BJNP communications. But I haven't seen any
problems testing a MF6140 device.

Cheers,
Rolf


Am 27.02.2016 um 18:44 schrieb Louis Lagendijk:
> On 2016-02-18 10:35, Rolf Bensch wrote:
>> Hello Louis,
>>
>> However, some Pixma scanners usually timeout the 1st USB command. I
>> already fixed this in pixma_imageclass.c by simply resending the 1st
>> command (query_status()).
>>
>> To reduce the timeout loop from 8 sec to 1 sec for this 1st particular
>> command, I'd like to load tmo in pixma_cmd_transaction() (->
>> pixma_common.c) from a parameter.
>>
>> I see 2 options:
>> (1) a new parameter in the function call of pixma_cmd_transaction()
>> (2) a new parameter with the default setting for 8 sec, e.g. in s->io
>>
>> Which one is smarter?
>>
>> Many thanks for your idea in advance.
>>
>> Cheers,
>> Rolf
>>
>> Am 18.02.2016 um 08:54 schrieb Rolf Bensch:
>>> Hello List,
>>>
>>> My recent commits to Sane's git repository contain some fixes which
>>> affect USB and BJNP protocol timeouts.
>>>
>>> This affects *ALL* Canon PIXMA, imageCLASS, i-SENSYS and *SOME* CanoScan
>>> scanning devices (please search your scanner here:
>>> http://sanexe-project.org/lists/sane-backends-cvs.html#S-PIXMA).
>>>
>>> Background:
>>>
>>> Many users have reported and my experience was the same while debugging
>>> a new scanner, that the 8 sec receive timeout needed approx. 160 sec to
>>> lapse. This blocked the interface and was very annoying.
>>>
>>> I found out that the protocol timeouts were set to eternal 20 sec. So I
>>> reduced the timeouts down to 1 sec (human immediately), for both
>>> PIXMA_BULKIN_TIMEOUT and PIXMA_BULKOUT_TIMEOUT. Now the 8 sec receive
>>> timeout loop is working again, also with available
>>> sanei_usb_set_timeout().
>>>
>>> Please report any problems caused by this fixes.
>>>
>>> Cheers,
>>> Rolf
>>>
> Hi Rolf
> Myapologies for not responding sooner, but I am on a businesstrip untill
> end of coming week. I hope to be able to get back to you when I get home
> Br, 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

[sane-devel] PIXMA: New Software Lineart for all Canon imageCLASS Scanners

[Rolf Bensch]

Hello List,

I just added a new software lineart (1 bit b/w) scan function for *all*
Canon imageCLASS based scanners to the Pixma backend:

imageCLASS scanners:
D420, D480, D530, MF810/820, MF3240, MF4010, MF4150, MF4270, MF4320,
MF4360,
MF4410, MF4570dw, MF4690, MF5630, MF6500, MF8030, MF8170c
   
i-SENSYS scanners:
MF210, MF220, MF3010, MF4500, MF4700, MF4800, MF5880dn, MF5900, MF6100,
MF6680dn, MF8200C, MF8300, MF8500C
   
imageRUNNER scanners:
iR1133
   
laserBase scanners:
MF5650

To get this function you must update your copy of Sane:

(1) clone your copy of the git repository and remake Sane now
or
(2) download the daily git snapshot of the unstable (development) source
from the website (http://sane-project.org/source.html) and remake or
install Sane tomorrow
or
(3) on an Ubuntu based OS update Sane from my PPA
(https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-git) tomorrow

Please contact the mailing list if you have any problems with your scanner.

Cheers,
Rolf


-- 
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] I want to test the Sane backend for Canon Pixma MG3670 Multi-functional Scanner-Printer (WIFI)

[Rolf Bensch]

Hi Javier,

Sorry for the late response.

You can install the patch file as follows:

(1) save the file into the folder /backend/
(2) open a terminal window
(3) $ cd 
 please replace  by the folder name of your sane sources
(4) $ cd backend
(5) $ patch pixma_mp150.c pixma_mp150.c.patch1
 maybe you need to install the package 'patch' if your system won't
find the program
(6) $ cd ..
(7) $ make && sudo make install

Now your scanner should create proper 1200 dpi scans. Please report your
results.

Cheers,
Rolf


Am 24.02.2016 um 22:38 schrieb Javier Altamirano Poveda:
> Hi Rolf,
>
> I've install Sane from git as described in chapter "Step by step
> install on Linux 2.6.* and 3.* as you recommended and my scanner CANON
> PIXMA MG3650 started working. Thanks!!.
>
> Now, I want to install and test attached patch but I don't know how to
> install it. Could you help me, please?
>
> Cheers,
>
> Javier
>
>
> El 24/02/16 a las 20:11, Rolf Bensch escribió:
>> Hi Javier,
>>
>> Your scanner is supported by the Sane Development (git) Version
>> (http://sane-project.org/lists/sane-backends-cvs.html#S-PIXMA).
>>
>> Everything is working fine, instead of 1200 dpi scans.
>>
>> Please install Sane from git as described in chapter "Step by step
>> install on Linux 2.6.* and 3.*" from README.linux
>> (http://sane-project.org/docs.html) and test attached patch *after*
>> your scanner is working.
>>
>> Please report your results.
>>
>> Many thanks for your help in advance.
>>
>> Cheers,
>> Rolf
>>
>>
>>
>> Am 22.02.2016 um 12:49 schrieb Javier Altamirano Poveda:
>>> Hi all,
>>> Recently I acquired a Canon PIXMA MG3650. I've seen Sane-project is
>>> looking for testers for this model. I can dedicate some time to this
>>> issue. I'm not sure this is the correct way to begin the testing
>>> process. If not please advise.
>>>
>>> Environment:
>>>
>>>   * Ubuntu 15.10 64bits (Kernel 4.2.0-27-generic) (Gnome 3.16.2
>>> (Ubuntu 2015-09-15))
>>>   * Xsane 0.998
>>>   * Original Canon drivers: cnijfilter2-5.20-1-deb (printer) and
>>> scangearmp2-3.20-1-deb (scanner)
>>>
>>> Tests done:
>>>
>>>   * Print function works fine.
>>>   * Scanner function only works if I use scangearmp2 program.
>>>
>>> Other information
>>>
>>>   * Device not found when I execute Xsane
>>>   * scanimage -V result: scanimage (sane-backends) 1.0.26git;
>>> backend version 1.0.25
>>>   * I export SANE_DEBUG_PIXMA=4 and execute Xsane, results are:
>>>   o [sanei_debug] Setting debug level of pixma to 4.
>>> [pixma] pixma is compiled with pthread support.
>>> [pixma] pixma version 0.17.18
>>> [pixma] pixma_find_scanners() found 0 devices
>>>
>>> Best regards
>>> Javier
>>>
>>
>
> -- 
>
> *Un cordial s**aludo,*
>
> *Javier Altamirano Poveda*
> Colaborador Independiente
>
> Móvil : +34 667 70 33 95
> Skype: javier.altamirano.poveda
>
> *El nuevo código penal sobre software ilegal entra en vigor el 1 de
> julio 2015* <http://www.leysoftware.net/>
>

-- 
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] I want to test the Sane backend for Canon Pixma MG3670 Multi-functional Scanner-Printer (WIFI)

[Rolf Bensch]

Hi Javier,

Your scanner is supported by the Sane Development (git) Version
(http://sane-project.org/lists/sane-backends-cvs.html#S-PIXMA).

Everything is working fine, instead of 1200 dpi scans.

Please install Sane from git as described in chapter "Step by step
install on Linux 2.6.* and 3.*" from README.linux
(http://sane-project.org/docs.html) and test attached patch *after* your
scanner is working.

Please report your results.

Many thanks for your help in advance.

Cheers,
Rolf



Am 22.02.2016 um 12:49 schrieb Javier Altamirano Poveda:
> Hi all,
> Recently I acquired a Canon PIXMA MG3650. I've seen Sane-project is
> looking for testers for this model. I can dedicate some time to this
> issue. I'm not sure this is the correct way to begin the testing
> process. If not please advise.
>
> Environment:
>
>   * Ubuntu 15.10 64bits (Kernel 4.2.0-27-generic) (Gnome 3.16.2
> (Ubuntu 2015-09-15))
>   * Xsane 0.998
>   * Original Canon drivers: cnijfilter2-5.20-1-deb (printer) and
> scangearmp2-3.20-1-deb (scanner)
>
> Tests done:
>
>   * Print function works fine.
>   * Scanner function only works if I use scangearmp2 program.
>
> Other information
>
>   * Device not found when I execute Xsane
>   * scanimage -V result: scanimage (sane-backends) 1.0.26git; backend
> version 1.0.25
>   * I export SANE_DEBUG_PIXMA=4 and execute Xsane, results are:
>   o [sanei_debug] Setting debug level of pixma to 4.
> [pixma] pixma is compiled with pthread support.
> [pixma] pixma version 0.17.18
> [pixma] pixma_find_scanners() found 0 devices
>
> Best regards
> Javier
>

--- ./pixma_mp150.c 2016-02-16 16:09:43.264394614 +0100
+++ ../sane-backends/backend/pixma_mp150.c  2016-02-16 16:10:40.800054083 
+0100
@@ -1159,6 +1159,7 @@
   && s->cfg->pid != MX920_PID
   && s->cfg->pid != MG3100_PID
   && s->cfg->pid != MG3500_PID
+  && s->cfg->pid != MG3600_PID
   && s->cfg->pid != MG2100_PID
   && s->cfg->pid != MG5300_PID
   && s->cfg->pid != MG5500_PID
-- 
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: New Protocol Timeouts

[Rolf Bensch]

Hello Louis,

However, some Pixma scanners usually timeout the 1st USB command. I
already fixed this in pixma_imageclass.c by simply resending the 1st
command (query_status()).

To reduce the timeout loop from 8 sec to 1 sec for this 1st particular
command, I'd like to load tmo in pixma_cmd_transaction() (->
pixma_common.c) from a parameter.

I see 2 options:
(1) a new parameter in the function call of pixma_cmd_transaction()
(2) a new parameter with the default setting for 8 sec, e.g. in s->io

Which one is smarter?

Many thanks for your idea in advance.

Cheers,
Rolf

Am 18.02.2016 um 08:54 schrieb Rolf Bensch:
> Hello List,
>
> My recent commits to Sane's git repository contain some fixes which
> affect USB and BJNP protocol timeouts.
>
> This affects *ALL* Canon PIXMA, imageCLASS, i-SENSYS and *SOME* CanoScan
> scanning devices (please search your scanner here:
> http://sane-project.org/lists/sane-backends-cvs.html#S-PIXMA).
>
> Background:
>
> Many users have reported and my experience was the same while debugging
> a new scanner, that the 8 sec receive timeout needed approx. 160 sec to
> lapse. This blocked the interface and was very annoying.
>
> I found out that the protocol timeouts were set to eternal 20 sec. So I
> reduced the timeouts down to 1 sec (human immediately), for both
> PIXMA_BULKIN_TIMEOUT and PIXMA_BULKOUT_TIMEOUT. Now the 8 sec receive
> timeout loop is working again, also with available sanei_usb_set_timeout().
>
> Please report any problems caused by this fixes.
>
> Cheers,
> Rolf
>



-- 
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] PIXMA: New Protocol Timeouts

[Rolf Bensch]

Hello List,

My recent commits to Sane's git repository contain some fixes which
affect USB and BJNP protocol timeouts.

This affects *ALL* Canon PIXMA, imageCLASS, i-SENSYS and *SOME* CanoScan
scanning devices (please search your scanner here:
http://sane-project.org/lists/sane-backends-cvs.html#S-PIXMA).

Background:

Many users have reported and my experience was the same while debugging
a new scanner, that the 8 sec receive timeout needed approx. 160 sec to
lapse. This blocked the interface and was very annoying.

I found out that the protocol timeouts were set to eternal 20 sec. So I
reduced the timeouts down to 1 sec (human immediately), for both
PIXMA_BULKIN_TIMEOUT and PIXMA_BULKOUT_TIMEOUT. Now the 8 sec receive
timeout loop is working again, also with available sanei_usb_set_timeout().

Please report any problems caused by this fixes.

Cheers,
Rolf


-- 
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 laser multi-functional support: MFNP protocol

[Rolf Bensch]

Hi,

I just committed several fixes for the MF6100 Series to Sane's git
repository.

Everything is working now: Flatbed, ADF and ADFDUP.

On a USB connection the scanner usual timeouts the 1st usb command after
a previous scan. I fixed this by resending the failed command. This
doesn't affect ethernet connections. Maybe somebody can find the reason
why the timeout occurs on USB.

My favourite gui for ADF and ADFDUP is gscan2pdf.

Cheers,
Rolf

Am 27.06.2015 um 23:12 schrieb Rolf Bensch:
> Hi,
>
> The MF6100 Series scanner is only working with flatbed scans and with
> single page scans in adf.
>
> Just now, I'm struggling with multiple pages in adf and duplex adf. A
> patch will take a while, because I only have sporadical access to a
> MF6140 scanner.
>
> Everytime the scanner reports an error on the lcd display, I need to
> wait until scanimage ends, or faster I send a ^C to terminate scanimage.
> However, I always need to reconnect the usb cable before scanimage can
> start the next scan.
>
> The status of this scanner still is untested.
>
> Cheers,
> Rolf
>
>
>
> Am 27.06.2015 um 20:02 schrieb Louis Lagendijk:
>> On Mon, 2015-06-22 at 14:58 +0300, Michael Shigorin wrote:
>>> On Wed, Apr 01, 2015 at 06:19:05PM +0200, Louis Lagendijk wrote:
>>>> Before anything: if scanning over USB  does not work, trying to
>>>> scan over the network is bound to fail.
>>> Got that; both devices and a winxp vm are handy today (will be
>>> there next week hopefully too), here's a 15 Mb usbsnoop log:
>>> http://fly.osdn.org.ua/~mike/tmp/sane-pixma/Canon-iR1133-scan-300dpi.usblog.xz
>>>
>>>> for the MF8540 first a question: what did you use to initiate the scan?
>>> xsane and scanimage
>>>
>>> MF8540Cdn and MF6140dn are available for testing/dumping right now,
>>> trying against today's git...
>>>
>>>> It looks as if a scan was not attempted. Please try (over USB):
>>>> scanimage > filename
>>>> and see what happens.
>> Can you please try the fixes I submitted to GIT today to see if they fix
>> the network issue with the MF devices?
>>
>>> Proper sounds but almost completely white image:
>>> http://fly.osdn.org.ua/~mike/tmp/sane-pixma/Canon-MF8540Cdn-scanimage.ppm.xz
>> how did you scan? Please try 
>> scanimage > test.ppm
>> to avoid problems due to settings from xsane etc. 
>>
>>>> As you saw it is not clear whether the device is supported with
>>>> the current pixma backend. Maybe somebody on the list that
>>>> knows the backend better than I do can help you with that (the
>>>> MF8500 series is listed in pixma_imageclass.c, so it is
>>>> probably possible to get it working, I only wrote the
>>>> networking code).
>>> Thank you :-)
>>>> the ImageRunner 1133 is listed too in the same file, so getting
>>>> it to work is probably possible too
>>> It _does_ work for me as of RELEASE_1_0_24-292-g8c51579:
>>> http://fly.osdn.org.ua/~mike/tmp/sane-pixma/Canon-iR1133iF-scanimage.ppm.xz
>>> (the same vendor provided test print)
>>>
>>>> The MF6100 series is not listed, but it again might be quite
>>>> possible to get it to work.
>>> The same almost white image as with 8540:
>>> http://fly.osdn.org.ua/~mike/tmp/sane-pixma/Canon-MF6140dn-scanimage.ppm.xz
>>>
>> As Rolf commented in a mail from April 3 the MF6100 series is added in
>> GIT, so it should work now. 
>> so please try scanning with scanimage and see if that works over USB and
>> if it works over the network after todays fixes.
>>
>> Kind regards, 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

Re: [sane-devel] I want to test the Sane backend for Canon Pixma MG3670 Multi-functional Scanner-Printer I have

[Rolf Bensch]

Hi Rajib,

Your scanner belongs to the pixma backend!

If you want to compile only the Pixma backend, you need to use this command:
$ ./configure BACKENDS="pixma"

You don't need to set an option for PRELOADABLE_BACKENDS for compiling
Sane in Linux. Please ask the mailing list again for detailed
information about this option.

Hope this helps.

Cheers,
Rolf



Am 11.02.2016 um 07:17 schrieb Susmita/Rajib Bandopadhyay:
> Please note that I used:
> 
>   ./configure BACKENDS="canon" PRELOADABLE_BACKENDS="canon" to preload
> backend for canon.
> Yet in output : I don't see preloadable backend.
> 
> What is the logic behind this?
> 

-- 
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] I want to test the Sane backend for Canon Pixma MG3670 Multi-functional Scanner-Printer I have

[Rolf Bensch]

Hi List,

Who has an answer?

Cheers,
Rolf

Am 11.02.2016 um 10:45 schrieb Susmita/Rajib Bandopadhyay:
> Sir,
> 
> I am using the code:
>  ./configure BACKENDS=pixma  PRELOADABLE_BACKENDS="pixma"
> 
> But why isn't the preload backend is being built?
> 
> Want to learn from this issue, Sir!
> 
> Regards,
> Rajib
> 
> 
> -> The following backends will be built:
> pixma
> 
> -> The following preload backends will be built:
> 
> 
> * Please be sure to read file PROBLEMS in this directory   *
> * BEFORE running any of the SANE applications.  Some devices   *
> * may be damaged by improper operation, so please do heed this *
> * advice.  *
> 
> 

-- 
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] I want to test the Sane backend for Canon Pixma MG3670 Multi-functional Scanner-Printer I have

[Rolf Bensch]

Hi Rajib,

The users knoppix and saned are members of the group scanner.

(1) knoopix: It's you, the logged in user.
(2) saned: It's an optional Sane daemon, which can be used from other
programs, e.g. scanbd (https://sourceforge.net/projects/scanbd/).

To use scanbd your scanner must support push button scan. Please read
your scanner's manual if it does.

Cheers,
Rolf

Am 11.02.2016 um 11:03 schrieb Susmita/Rajib Bandopadhyay:
> Sir,
> My terminal shows: knoppix@Microknoppix:~$
> 
> But the code :
> $ cat /etc/group | grep scanner
> 
> Shows:
> scanner:x:113:saned,knoppix
> 
> Why so, Sir?
> 
> Regards
> 

-- 
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] I want to test the Sane backend for Canon Pixma MG3670 Multi-functional Scanner-Printer I have

[Rolf Bensch]

Hi Rajib,

I just updated the scanner's status in the doc files.

You can see the recent status here:
http://sane-project.org/lists/sane-backends-cvs.html#S-PIXMA .

Many thanks for your help.

Cheers,
Rolf

Am 11.02.2016 um 11:17 schrieb Susmita/Rajib Bandopadhyay:
> I found the following outputs: Everything seems okay except the last output.
> knoppix@Microknoppix:~$ scanimage -v
> scanimage: output is not a file, exiting
> knoppix@Microknoppix:~$ scanimage -V
> scanimage (sane-backends) 1.0.26git; backend version 1.0.26
> knoppix@Microknoppix:~$ scanimage -L
> device `pixma:04A9178A_55CF3E' is a CANON Canon PIXMA MG3600 Series
> multi-function peripheral
> knoppix@Microknoppix:~$ scanimage
> scanimage: output is not a file, exiting
> 
> But I am able to scan at all resolutrions and at all brightness and
> contrast settings via xsane.
> 
> So I need to mark this driver as checked successful.
> 
> You change your Sane page for this printer.
> 
> Love you, Sir!
> 

-- 
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] I want to test the Sane backend for Canon Pixma MG3670 Multi-functional Scanner-Printer I have

[Rolf Bensch]

Hi Rajib,

Please follow *all* installation steps described in chapter "Step by
step install on Linux 2.6.* and 3.*" in the file README.linux.

Cheers,
Rolf


Am 10.02.2016 um 06:46 schrieb Susmita/Rajib Bandopadhyay:
> Hello, Sir!
> Hope you won't be irritated of my naivety.
> 
> knoppix@Microknoppix$ scanimage -V
> scanimage (sane-backends) 1.0.22; backend version 1.0.22
> 
> Then I did the following after downloading sane-backend from:
> knoppix@Microknoppix$ git clone git://git.debian.org/sane/sane-backends.git
> 
> Then I did:
> knoppix@Microknoppix$ whereis scanimage
> scanimage: /usr/bin/scanimage /usr/bin/X11/scanimage
> /usr/local/bin/scanimage /usr/share/man/man1/scanimage.1.gz
> 
> Then I went inside of the downloaded sane-backend directory and did:
> knoppix@Microknoppix:~/Downloads/sane-backends$ make && sudo make install
> make: *** No targets specified and no makefile found.  Stop.
> 
> I repeated and found the same result even in su.
> 
> Although there are makefile.in and makefile.am.
> 
> What do I need to do?
> 
> I hope I am not irritating you.
> 
> Regards,
> Rajib
> 
> 
> 
> 
> On 08/02/2016, Rolf Bensch <r...@bensch-online.de> wrote:
>> Hi Rajib,
>>
>> First please check the used Sane version on the command line (in a
>> terminal window):
>> $ scanimage -V
>> scanimage (sane-backends) 1.0.26git; backend version 1.0.26
>>
>> The shown versions must be minimum 1.0.25. Otherwise you must install
>> Sane from git as described in README.linux:
>> http://www.sane-project.org/docs.html , chapter "Step by step install on
>> Linux 2.6.* and 3.*".
>>
>> If you have a suitable Sane version, you can start scanning via the USB
>> interface with a frontend of your choice: scanimage, xsane, ... Please
>> disable all Ethernet and WiFi connections to your printer/scanner device!!!
>>
>> To get some debug information, please enable this on the command line with:
>> $ export SANE_DEBUG_PIXMA=4
>>
>> You may read the man page ($ man sane-pixma) for details.
>>
>> Please also start a gui frontend from the command line (the same
>> terminal window), e.g. xsane:
>> $ xsane
>>
>> Then you'll see the debug output in the terminal window beside the xsane
>> windows.
>>
>> Your scanner should scan pages up to 600dpi out of the box. What's about
>> scanning @ 1200dpi? You may see your image double beside each other.
>>
>> Please report your results.
>>
>> Many thanks for your help.
>>
>> Cheers,
>> Rolf
>>
>>
>> Am 23.01.2016 um 17:00 schrieb Susmita/Rajib Bandopadhyay:
>>> Dear Sirs,
>>>
>>> I have always had a problem with xsane. The only time I had seen xsane
>>> work was with HP multi-functional scanner printer.
>>>
>>> I can volunteer to test the xscane backend for my printer. Information
>>> collected from:
>>> http://www.sane-project.org/sane-backends.html
>>>
>>> Tell me how to go about it.
>>>
>>> Regards,
>>> Rajib
>>> Mysore
>>>
>>>
>>
>>
>>
> 

-- 
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] I want to test the Sane backend for Canon Pixma MG3670 Multi-functional Scanner-Printer I have

[Rolf Bensch]

Hi Rajib,

You don't need to install Sane frontends. You can use scanimage from the
backends installation or any other frontend, e.g. xsane.

Cheers,
Rolf


Am 10.02.2016 um 09:06 schrieb Susmita/Rajib Bandopadhyay:
> according to direction in the file, I went to and downloaded the two
> files from http://www.sane-project.org/snapshots/
> 
> sane-backends-git20160210.tar.gz sane-frontends-git20160210.tar.gz
> I unZipped the files to two separate folders and tried to run:
> /.configure
> make && sudo make install
> 
> These don't work. The frontend says about gtk:
> #
> ##Frontend  ##
> #
> ...
> checking for GTK+ - version >= 2.0.0... no
> *** Could not run GTK+ test program, checking why...
> *** The test program failed to compile or link. See the file
> config.log for the
> *** exact error that occured. This usually means GTK+ is
> incorrectly installed.
> configure: WARNING: *** GIMP 2.0 plugin requested, but GTK+ 2.0
> not found, falling back to GIMP/GTK+ < 2.0 if possible ***
> checking for gtk-config... no
> checking for GTK - version >= 0.99.13... no
> *** The gtk-config script installed by GTK could not be found
> *** If GTK was installed in PREFIX, make sure PREFIX/bin is in
> *** your path, or set the GTK_CONFIG environment variable to the
> *** full path to gtk-config.
> checking for gimp-config... no
> checking for gimptool... no
> checking libgimp/gimp.h usability... no
> checking libgimp/gimp.h presence... no
> checking for libgimp/gimp.h... no
> checking libgimp/gimpfeatures.h usability... no
> checking libgimp/gimpfeatures.h presence... no
> checking for libgimp/gimpfeatures.h... no
> no
> *** Could not run GIMP test program, checking why...
> 
> WARNING: GTK-0.99.13 or newer is needed for compiling the GUI
> frontends. If you installed gtk as rpm make sure
> you also installed gtk-devel.
> ===> GUIs will be deactivated
> 
> 
> You may need to remove /dev/null before you run configure again.
> 
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: WARNING: 'Makefile.in' seems to ignore the
> --datarootdir setting
> config.status: creating lib/Makefile
> config.status: WARNING: 'lib/Makefile.in' seems to ignore the
> --datarootdir setting
> config.status: creating src/Makefile
> config.status: WARNING: 'src/Makefile.in' seems to ignore the
> --datarootdir setting
> config.status: creating sanei/Makefile
> config.status: WARNING: 'sanei/Makefile.in' seems to ignore the
> --datarootdir setting
> config.status: creating doc/Makefile
> config.status: WARNING: 'doc/Makefile.in' seems to ignore the
> --datarootdir setting
> config.status: creating include/Makefile
> config.status: WARNING: 'include/Makefile.in' seems to ignore the
> --datarootdir setting
> config.status: creating include/sane/config.h
> config.status: include/sane/config.h is unchanged
> 
> * *
> * SANE-FRONTENDS configure status: *
> *  *
> * * GTK not found: GUIs deactivated *
> * *
> 
> * *
> * To compile SANE-FRONTENDS: *
> * -- *
> * make *
> * make install *
> * *
> *  *
> * ... PLEASE READ SANE DOCUMENTATION BEFORE STARTING SANE ... *
> *  *
> * *
> * If you experience any problems with sane-frontends please *
> * write to the sane list at sane-devel@lists.alioth.debian.org *
> * *
> 
> 
> I do indeed have libgtk of version 3.4.2-7 in my system.
> #
> ###Backend###
> #
> 
> Then I tried to install sane-backends.
> There, with ./configure I find:
> Avahi support: no
> SNMP support:  no
> -> The following backends will be built:
> abaton agfafocus apple artec artec_eplus48u as6e avision bh canon
> canon630u canon_dr cardscan coolscan coolscan2 coolscan3 dc25 dmc
> epjitsu epson epson2 fujitsu genesys gt68xx hp hp3500 hp3900 hp4200
> hp5400 hp5590 hpljm1005 hs2p ibm kodak kodakaio kvs1025 kvs20xx
> kvs40xx leo lexmark ma1509 magicolor matsushita microtek microtek2
> mustek mustek_usb mustek_usb2 nec net niash pie pieusb pixma plustek
> plustek_pp qcam ricoh rts8891 s9036 

Re: [sane-devel] I want to test the Sane backend for Canon Pixma MG3670 Multi-functional Scanner-Printer I have

[Rolf Bensch]

Hi Rajib,

First please check the used Sane version on the command line (in a
terminal window):
$ scanimage -V
scanimage (sane-backends) 1.0.26git; backend version 1.0.26

The shown versions must be minimum 1.0.25. Otherwise you must install
Sane from git as described in README.linux:
http://www.sane-project.org/docs.html , chapter "Step by step install on
Linux 2.6.* and 3.*".

If you have a suitable Sane version, you can start scanning via the USB
interface with a frontend of your choice: scanimage, xsane, ... Please
disable all Ethernet and WiFi connections to your printer/scanner device!!!

To get some debug information, please enable this on the command line with:
$ export SANE_DEBUG_PIXMA=4

You may read the man page ($ man sane-pixma) for details.

Please also start a gui frontend from the command line (the same
terminal window), e.g. xsane:
$ xsane

Then you'll see the debug output in the terminal window beside the xsane
windows.

Your scanner should scan pages up to 600dpi out of the box. What's about
scanning @ 1200dpi? You may see your image double beside each other.

Please report your results.

Many thanks for your help.

Cheers,
Rolf


Am 23.01.2016 um 17:00 schrieb Susmita/Rajib Bandopadhyay:
> Dear Sirs,
>
> I have always had a problem with xsane. The only time I had seen xsane
> work was with HP multi-functional scanner printer.
>
> I can volunteer to test the xscane backend for my printer. Information
> collected from:
> http://www.sane-project.org/sane-backends.html
>
> Tell me how to go about it.
>
> Regards,
> Rajib
> Mysore
>
>



-- 
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 MF212w Scanner and SANE

[Rolf Bensch]

Hi,

Beside all installation issues, please don't forget that this scanner
has the status "Untested"
(http://www.sane-project.org/sane-backends.html#S-PIXMA).

This means that this scanner may *NOT* work until some bug fixing will
happen.

I'm sorry, but I cannot supply any support for the Pixma backend until
my Chistmas holidays.

In the meantime you can sniff the USB protocols from a Windows machine.
You can use a pysical or a virtual machine. Usually I'm using Wireshark
with USBPcap (https://wiki.wireshark.org/CaptureSetup/USB) for this job.

Please compress the log files. The mailing list rejects large emails.

Hope this helps so far.

Cheers,
Rolf

Am 04.12.2015 um 02:05 schrieb Scott:
> Olaf, thank you for your continued help.  Yes, I am a newbie to this
> driver business among many things.
>
>
> On 12/03/2015 04:52 AM, Olaf Meeuwissen wrote:
>> Hi Scott,
>>
>> monkity writes:
>>
>>> Hi Olaf,
>>>
>>> Olaf writes:
>>>
 [...]
 Have you tried sane-backends-1.0.25.  That versions claims that
 support
 for the MF210 Series was added to the pixma backend.

 Seeing that you are using Linux Mint, I *guess* that you get your SANE
 backends via the Ubuntu package archives.  The version in Ubuntu's
 wily
 (1.0.25+git20150528) appears to be new enough.
 # The Changelog mention the addition on 2015-04-03.
>>>
>>> Unfortunately nothing is that easy.  Mint doesn't download the 1.0.25
>>> backend with SANE; in fact it doesn't seem to do anything with respect
>>> to backends.  I'm afraid I'm going to have to build the backend from
>>> scratch, and I have no experience with this.
>>> I did find a copy of 1.0.25 on
>>> http://www.linuxfromscratch.org/blfs/view/svn/pst/sane.html.
>>> That page, https://help.ubuntu.com/community/sane, and others aren't
>>> really designed for Mint and newbies though.  Where should I start?
>>
>> Uh-oh, newbie alert ;-)
>>
>> First, check that you have the libsane package installed.  From a
>> terminal, run
>>
>>$ dpkg-query -W libsane
>>
>> If that produces something like
>>
>>libsane:amd641.0.25-2
>>
>> things look good.  If, instead you get something like
>>
>>dpkg-query: no packages found matching libsane
>>
>> there is more work to do but I assume for now that libsane is found.
>> # If not, stop here and get back to me via the mailing list.
>>
>> In that case, you can probably get away with downloading the Ubuntu
>> libsane package from
>>
>>http://packages.ubuntu.com/wily/libsane
>>
>> Just make sure to pick the correct architecture.
>>
>> Once downloaded, run
>>
>>$ sudo dpkg -i libsane-1.0.25+git20150528-1ubuntu2_amd64.deb
>>
>> and you should be good to go.
>>
>> Hope this helps,
>>
>
> So I ended up trying to install both i386 and amd64 versions. When I
> updated these, I got errors, and had to fix broken packages. After I
> did that, my SANE installation didn't work and the query you gave me
> gave the following result, even after removing SANE and reinstalling it.
>
> $ dpkg-query -W libsane
> libsane:amd64 1.0.23-3ubuntu3.1
> libsane:i386 1.0.25+git20150528-1ubuntu2
>
> So I then redid the command on the amd64 deb:
>
> $ sudo dpkg -i libsane_1.0.25+git20150528-1ubuntu2_amd64.deb
> [sudo] password for flibberty:
> (Reading database ... 194182 files and directories currently installed.)
> Preparing to unpack libsane_1.0.25+git20150528-1ubuntu2_amd64.deb ...
> Unpacking libsane:amd64 (1.0.25+git20150528-1ubuntu2) over
> (1.0.23-3ubuntu3.1) ...
> dpkg: dependency problems prevent configuration of libsane:amd64:
> libsane:amd64 depends on libsane-common (=
> 1.0.25+git20150528-1ubuntu2); however:
> Version of libsane-common on system is 1.0.23-3ubuntu3.1.
> libsane:amd64 depends on libgphoto2-port12 (>= 2.5.6); however:
> Package libgphoto2-port12 is not installed.
>
> dpkg: error processing package libsane:amd64 (--install):
> dependency problems - leaving unconfigured
> Errors were encountered while processing:
> libsane:amd64
>
> Now my query came out as follows:
> $ dpkg-query -W libsane
> libsane:amd64 1.0.25+git20150528-1ubuntu2
> libsane:i386 1.0.25+git20150528-1ubuntu2
>
> SANE is still not recognizing my Canon.  Do the errors above give you
> any new ideas for me to try?
>
> Thanks again,
> Scott
>
>



-- 
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 MP250, pixma backend

[Rolf Bensch]

Hi Andrey,

Your patch ist the right way to handle this issue.

Please open a bug report. I have no time for any support now and I don't
want to forget this issue.

Many thanks for your report and your help.

Cheers,
Rolf

Am 26.11.2015 um 09:22 schrieb Andrey Kovalev:
> Hi!
>
> I'm trying to run Canon MP250 scanner.
>
> It worked with sane-backend 1.0.23, and is broken since 1.0.24.
>
> I took sane from git. Below I attached a part of sane log. I added
> several "here we are" lines to see source file name and line of code.
>
> Problems started after "sane_control_option(handle=0x8080c00,option=17"
>
> option=17 is opt_button_1.
>
> In 1.0.24 these lines were added to pixma.c control_option() function:
>
> +  case opt_button_1:
> +  case opt_button_2:
> +  case opt_original:
> +  case opt_target:
> +  case opt_scan_resolution:
> +/* poll scanner if option is not cached */
> +if (! ss->button_option_is_cached[ BUTTON_GROUP_INDEX(n) ] )
> +  update_button_state (ss, info);
> +/* mark this option as read */
> +ss->button_option_is_cached[  BUTTON_GROUP_INDEX(n) ] = 0;
>
>
> control_option() form pixma.c call update_button_state(),
> then pixma_wait_event(),
> mp150_wait_event(),
> handle_interrupt() from pixma_mp150.c,
> send_time().
>
> Send a few bytes over USB and wait for device respond.
>
> Device never responds.
>
> If I comment out all these lines marked with '+' in pixma.c
> control_option() function my MP250 works.
>
>
>
>
> On the other hand with this patch to sane git and without any other
> changes:
>
>
> diff --git a/backend/pixma_mp150.c b/backend/pixma_mp150.c
> index 4f8b232..7ab9e0f 100644
> --- a/backend/pixma_mp150.c
> +++ b/backend/pixma_mp150.c
> @@ -967,8 +967,11 @@ handle_interrupt (pixma_t * s, int timeout)
> * target in buf[1] */
>{
>  /* More than one event can be reported at the same time. */
> -if (buf[3] & 1)
> -  send_time (s);
> +if (s->cfg->pid != MP250_PID)
> +{
> +  if (buf[3] & 1)
> +send_time (s);
> +}
>  if (buf[9] & 2)
>query_status (s);
>  if (buf[0] & 2)
>
>
>
> my MP250 works too.
>
>
> In pixma_mp810.c there is a comment:
>
> /* FIXME: some scanners hang here */
>
> near send_time() call. Perhaps, MP250 doesn't need send_time()?
>
>
>
> 
> [bjnp] sanei_bjnp_find_devices, pixma backend version: 0.17.24
> [bjnp] sanei_bjnp_find_devices: No devices specified in configuration
> file.
> [bjnp] sanei_bjnp_find_devices: Added all configured scanners, now do
> auto detection...
> [bjnp] prepare_socket: lo is not a valid IPv4 interface, skipping...
> [bjnp] prepare_socket: eth0 is IPv4 capable, sending broadcast, socket
> = 13
> [bjnp] sanei_find_devices: scanner discovery finished...
> [pixma] pixma_open(): Canon PIXMA MP250
> [sanei_usb] sanei_usb_open: trying to open device `libusb:001:002'
> [sanei_usb] sanei_usb_open: configuration nr: 0
> [sanei_usb] sanei_usb_open: interface nr: 0
> [sanei_usb] sanei_usb_open:   alt_setting nr: 0
> [sanei_usb] sanei_usb_open: endpoint nr: 0
> [sanei_usb] sanei_usb_open: direction: 0
> [sanei_usb] sanei_usb_open: address: 7 transfertype: 2
> [sanei_usb] sanei_usb_open: found bulk-out endpoint (address 0x07)
> [sanei_usb] sanei_usb_open: we already have a bulk-out endpoint
> (address: 0x07), ignoring the new one
> [sanei_usb] sanei_usb_open: endpoint nr: 1
> [sanei_usb] sanei_usb_open: direction: 128
> [sanei_usb] sanei_usb_open: address: 8 transfertype: 2
> [sanei_usb] sanei_usb_open: found bulk-in endpoint (address 0x08)
> [sanei_usb] sanei_usb_open: we already have a bulk-in endpoint
> (address: 0x88), ignoring the new one
> [sanei_usb] sanei_usb_open: endpoint nr: 2
> [sanei_usb] sanei_usb_open: direction: 128
> [sanei_usb] sanei_usb_open: address: 9 transfertype: 3
> [sanei_usb] sanei_usb_open: found interrupt-in endpoint (address 0x09)
> [sanei_usb] sanei_usb_open: we already have a int-in endpoint
> (address: 0x89), ignoring the new one
> [sanei_usb] sanei_usb_open: configuration nr: 0
> [sanei_usb] sanei_usb_open: interface nr: 1
> [sanei_usb] sanei_usb_open:   alt_setting nr: 0
> [sanei_usb] sanei_usb_open: interface 1 not detected as a scanner by
> sanei_usb_init, ignoring.
> [sanei_usb] sanei_usb_open: opened usb device `libusb:001:002' (*dn=0)
> [pixma] *mp150_open* This is a generation 4 scanner.  *
> [pixma] here we are pixma_mp150.c 1231
> [pixma] here we are pixma_mp150.c 1240
> [dll] sane_open: open successful
> [sanei_wire] sanei_w_space: bigger than buffer (8192 bytes), may be
> flush()
> [sanei_wire] sanei_w_space: bigger than buffer (8192 bytes), may be
> flush()
> [sanei_wire] sanei_w_space: bigger than buffer (8192 bytes), may be
> flush()
> [dll] sane_get_parameters(handle=0x8080c00,params=0xbfd71cb4)
> [sanei_wire] sanei_w_space: bigger than buffer (8192 bytes), may be
> flush()
> [sanei_wire] sanei_w_space: bigger than buffer (8192 bytes), may be
> 

Re: [sane-devel] Canoscan 9000F Mark II not working properly for transparency scans on Ubuntu 15.10 and libsane 1.0.26

[Rolf Bensch]

Hi Ronald,

Sorry for my late response.

Please compare your installation procedure with the description in
README.linux.

Please sniff the USB protocols of a transparency scan with your Windows
laptop. Usually I'm using Wireshark with USBPcap
(https://wiki.wireshark.org/CaptureSetup/USB) for this job. You can use
any other USB sniffer for this.

I'm sorry, but I cannot supply any support for the Pixma backend until
my Chistmas holidays.

Cheers,
Rolf



Am 20.11.2015 um 21:50 schrieb Ronald Trask:
> On 11/19/2015 10:59 PM, Ronald Trask wrote:
>> I recently bought a Canoscan 9000 F Mark II scanner, I am running
>> Ubuntu 15.10. using both xsane transparency/slide setting, and the
>> command line options for scanning a transparency it appears that the
>> cover light is not illuminating. I uninstalled libsane that was
>> bundled with 15.10, and built / installed libsane 1.0.26 but it made
>> no difference. I verified proper function of the transparency scan
>> functionality with a windows lap top, so the issue is not with the
>> hardware. I attempted to attach the results of the a scan of some
>> slides, but the message was rejected, so  message me if you think it
>> would be helpful to see the scanner's behavior. The left side of the
>> scan is totally black and gets auto cropped. The right side of the
>> scan is bright white, the actual slides are too dark to see. The
>> xsane frontend detects that cover for the transparency window is off,
>> and will not allow you to scan, I think a lot is working, but I am
>> not sure where to go from here.
>>
>> One thing to note is that after I removed / purged the libsane that
>> is bundled with Ubuntu 15.10, and did a ldconfig -v | grep libsane it
>> showed only the 1.0.26 version of libsane. However, uninstalling
>> libsane also uninstalled xsane. When I did an apt-get install on
>> xsane, it evidently loaded 1.0.25 because running ldconfig shows both
>> versions installed. I really don't think that has any impact on the
>> issue though. I have not attempted it yet, but I assume I can fix
>> that by uninstalling xsane and libsane again and building the front end.
>>
>>
>> root>:/opt/sane/src/sane-backends# ldconfig -v | grep libsane
>> /sbin/ldconfig.real: Path `/lib/x86_64-linux-gnu' given more than once
>> /sbin/ldconfig.real: Path `/usr/lib/x86_64-linux-gnu' given more than
>> once
>> /sbin/ldconfig.real: /lib/x86_64-linux-gnu/ld-2.21.so
>>  is the dynamic linker, ignoring
>>
>> libsane.so.1 -> libsane.so.1.0.26
>> libsane.so.1 -> libsane.so.1.0.25
>>
>> -
>>  
>> Following the instructions I found at multiple locations, I did a git
>> clone and built it / installed it.
>>
>> git clone git://git.debian.org/sane/sane-backends.git
>> root>:/opt/sane/src/sane-backends# export BACKENDS="canon pixma"
>> root>:/opt/sane/src/sane-backends# ./configure
>> root>:/opt/sane/src/sane-backends# make
>> root>:/opt/sane/src/sane-backends# make check
>> ..
>> 
>> Testsuite summary for sane-backends 1.0.26git
>> 
>> # TOTAL: 5
>> # PASS:  5
>> # SKIP:  0
>> # XFAIL: 0
>> # FAIL:  0
>> # XPASS: 0
>> # ERROR: 0
>> 
>> ..
>> 
>> All tests passed
>> 
>>
>> root>:/opt/sane/src/sane-backends# make install
>> ..
>>
>> nothing looked unusual except
>> NOT overwriting canon.conf in /usr/local/etc/sane.d...
>> NOT overwriting pixma.conf in /usr/local/etc/sane.d...
>> NOT overwriting saned.conf in /usr/local/etc/sane.d...
>> NOT overwriting dll.conf in /usr/local/etc/sane.d...
>>
>> 
>>
>>
>>
>> root>:/opt/sane/src/sane-backends# ldconfig -v | grep libsane
>> /sbin/ldconfig.real: Path `/lib/x86_64-linux-gnu' given more than once
>> /sbin/ldconfig.real: Path `/usr/lib/x86_64-linux-gnu' given more than
>> once
>> /sbin/ldconfig.real: /lib/x86_64-linux-gnu/ld-2.21.so
>>  is the dynamic linker, ignoring
>>
>> libsane.so.1 -> libsane.so.1.0.26
>> libsane.so.1 -> libsane.so.1.0.25
>>
>> Which I assume is the problem may be a problem ...
>>
>> A lot seems to work.
>> scanimage -V
>> scanimage (sane-backends) 1.0.26git; backend version 1.0.26
>>
>> scanimage --list-devices
>> device `pixma:04A9190D' is a CANON Canoscan 9000F Mark II
>> multi-function peripheral
>>
>>
>>
>>
>>
>

-- 
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-devel Digest, Vol 124, Issue 35

[Rolf Bensch]

Hi James,

please try my ppa:
https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-git .

This installs Sane's recent development version. I'm interested in if
this is working.

Many thanks for your help in advance.

Cheers,
Rolf


Am 01.11.2015 um 00:33 schrieb James Ring:
> Hi Louis,
>
> On Sat, Oct 31, 2015 at 5:00 AM,
>  wrote:
>> Send sane-devel mailing list submissions to
>> sane-devel@lists.alioth.debian.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
>> or, via email, send a message with subject or body 'help' to
>> sane-devel-requ...@lists.alioth.debian.org
>>
>> You can reach the person managing the list at
>> sane-devel-ow...@lists.alioth.debian.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of sane-devel digest..."
>>
>>
>> Today's Topics:
>>
>>1. Re: issues with sane-pixma and Canon MX7600 (Louis Lagendijk)
>>2. Re: Xsane can't find scanner - again, but this one is USB
>>   (Olaf Meeuwissen)
>>
>>
>> --
>>
>> Message: 1
>> Date: Fri, 30 Oct 2015 22:48:32 +0100
>> From: Louis Lagendijk 
>> To: sane-devel@lists.alioth.debian.org
>> Subject: Re: [sane-devel] issues with sane-pixma and Canon MX7600
>> Message-ID: <1446241712.2904.2.ca...@fazant.net>
>> Content-Type: text/plain; charset="ISO-8859-15"
>>
>> On Thu, 2015-10-29 at 10:26 -0700, James Ring wrote:
>>> One more thing,
>>>
>>> On Thu, Oct 29, 2015 at 10:13 AM, James Ring  wrote:
 Hi all,

 Up until recently, I've been able to scan fine with my Canon Pixma
 MX7600. Then I upgraded to Ubuntu Wily and I've started getting:

 $ scanimage
 scanimage: open of device pixma:MX7600_192.168.2.107 failed:
 Invalid argument

 The device pings and I can get to its HTTP port. Everything appears
 OK.

 If I run

 strace -f -s 256 -o /tmp/trace.txt scanimage

 the relevant output appears to be:

 socket(PF_INET, SOCK_DGRAM, IPPROTO_UDP) = 204
 connect(204, {sa_family=AF_INET, sin_port=htons(8612),
 sin_addr=inet_addr("192.168.2.107")}, 16) = 0
 sendto(204, "BJNP\2\1\0\0\0\0\0\0\0\0\0\0", 16, 0, NULL, 0) = 16
 select(205, [204], NULL, NULL, {4, 0}) = 1 (in [204], left {3,
 998257})
 recvfrom(204,
 "BJNP\202\1\0\0\0\0\0\0\0\0\0\20\0\1\10\0\6\4\0\0\205\316\356\343\3
 00\250\2k",
 2048, 0, NULL, N
 ULL) = 32
 close(204)
 write(2, "scanimage: open of device pixma:MX7600_192.168.2.107
 failed:
 Invalid argument\n", 78) = 78

 It appears to me that the scanner is responding but the driver
 doesn't
 like the response. I'm running sane 1.0.14-11 and sane-utils
 1.0.25+git201505.
>>> I just verified that downgrading to libsane 1.0.24-4ubuntu1 from
>>> 1.0.25+git201505 allows me to scan again, so I definitely there's
>>> some
>>> sort of sane-pixma regression in there.
>> this looks similar to an issue that I fixed some time ago. Please see
>> if you can find a package of the released 1.0.25. that should fix your
>> issue
> I can confirm that building from source resolves the issue, thank you.
> I've raised
>
> https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1512027
>
> with Ubuntu to track the issue.
>
>> Louis
> Thanks,
> James
>
>


-- 
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 Maxifiy MB2000 series

[Rolf Bensch]

Hi,

Sorry for my late response.

Am 25.10.2015 um 10:55 schrieb Jörn-Ingo Weigert:
> I can report that sane does support the rudimentary scanning with the
> Canon Maxify MB2000 series MFP printer under Ubuntu 14.04 LTS.
>
> I installed the drivers from Canon Website for Linux.
> Configured the appropriate permissions to access the scanner device
> via USB.
>
> What works:
> - Scanning in 300 / 600dpi works from Flatbed with Ubuntu own Simple
> Scan and XSane
>
OK. Many thanks for your report.

> What does not work:
> - Scanning over / with ADF: The Scanner recognize that there comes a
> command (display lights up, showing "Process command..." but does NOT
> activate the feeder or start to scan. :-(
> Scanning via Canon own tool scangear works on both flatbed and adf scan.
>
Please sniff the USB protocols from a small scangear adf scan, e.g.
10x10mm @ 75dpi with wireshark.
And again in a different log file from Sane in a Linux terminal:

(1) $ export SANE_DEBUG_PIXMA=11
(2) $ scanimage --source "Transparency Unit" -l 100 -x 10 -y 10 2>
pixma.log > pixma.pnm

Then I can compare both log files and prepare a patch.

> - Scanning in higher resolution like 1200dpi / 2400dpi result in a
> doubled interlaced scanning image, however the scan themself work but
> result in bad image.

OK. I can prepare a Patch for 1200 dpi. XSane shouldn't show the option
for 2400dpi.

Please zip the log files. The mailing list rejects large emails.

Cheers,
Rolf


-- 
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 (canon MG6450)

[Rolf Bensch]

Hi Lovro,

Am 23.09.2015 um 17:59 schrieb lovrolu:
> Hello Rolf,
>
>> Your scanner wasn't fully supported by the backend version 1.0.24. 
>> 1200dpi scans don't work.
> Aha, this is what I wanted to know. Does it work in 1.0.25? If not, any
> plans for when the support will be added?
This scanner is fully supported in 1.0.25. Please have a look here:
http://www.sane-project.org/lists/sane-backends-cvs.html#S-PIXMA .

>> Everthing else should work with scans up to 600 dpi. Please test all 
>> options with your favourite frontend. I prefer xsane.
> I will do that and report back if I find anything unusual. I have
> tinkered with the settings a bit and it all seems be working fine.
>
>> If you might get problems with 1.0.24, you won't get around to 
>> install Sane 1.0.25 from git.
> I'm not quite sure what you mean by "you won't get around to install".
> Was it a typo or did I misunderstand?
I mean that you need to install version 1.0.25 from git if you have
problems with 1.0.24.

>> The brightness of the scan result depends on the scan settings. 
>> Please try the sliders in xsane and watch the results in the preview
>>  window.
> Yup, I've just done this the other day and everything appears to work!

OK. Many thanks for your help.

Cheers,
Rolf

> Lovro
>
> On 09/23/2015 05:18 PM, Rolf Bensch wrote:
>> Hi Lovro,
>>
>> Your scanner wasn't fully supported by the backend version 1.0.24. 
>> 1200dpi scans don't work.
>>
>> Everthing else should work with scans up to 600 dpi. Please test all 
>> options with your favourite frontend. I prefer xsane.
>>
>> If you might get problems with 1.0.24, you won't get around to 
>> install Sane 1.0.25 from git.
>>
>> The brightness of the scan result depends on the scan settings. 
>> Please try the sliders in xsane and watch the results in the preview
>>  window.
>>
>> Hope this helps.
>>
>> Cheers, Rolf
>>
>> Am 19.09.2015 um 21:45 schrieb lovrolu:
>>> I have already installed SANE (through my distribution's package 
>>> manager) and confirmed that it works with my scanner. I'm on Fedora
>>> 22 running GNU/Linux, kernel release 4.1.6-201.fc22.x86_64.
>>>
>>> Running `scanimage -V` from the shell returns
>>>
>>> scanimage (sane-backends) 1.0.24; backend version 1.0.24
>>>
>>> I'm not sure but I think the git version of SANE is 1.0.25. Since 
>>> 1.0.24 works just fine (from the tests I've done -- the reason I 
>>> would like to help out is to confirm that it *fully* works as 
>>> expected on 1.0.24) I'm not sure if upgrading to 1.0.25 is 
>>> worthwhile, at least currently.
>>>
>>> I have also installed the official driver from Canon. Scans 
>>> produced using Canon's driver are a bit brighter but this is 
>>> probably just to different default settings. Since it was just a 
>>> quick test I didn't bother too much customizing the brightness 
>>> level but I might do that if required.
>>>
>>> Anyway, I wanted to know if there's a test suite that SANE offers 
>>> that I could run or some kind of a procedure I could go through to
>>>  verify that SANE *fully* works as expected with my scanner (and 
>>> with this particular version of SANE I have)?
>>>
>>> If you think I should use the latest version of SANE I can probably
>>> do that but most likely not right away. However, I would like to
>>> try out 1.0.24 first, if possible.
>>>
>>> Have a nice day, Lovro
>>>
>>>> Hi Lovro,
>>>>
>>>> The MG6400 Series scanner is supported by the git version of 
>>>> Sane: 
>>>> http://www.sane-project.org/lists/sane-backends-cvs.html#S-PIXMA
>>>>  .
>>>>
>>>> You can check the latest code with your scanner. Please install 
>>>> Sane from git as described in README.linux: 
>>>> http://www.sane-project.org/docs.html .
>>>>
>>>> Many thanks for your help.
>>>>
>>>> Cheers, Rolf
>>>>
>>>> Am 18.09.2015 um 22:55 schrieb lovrolu:
>>>>> Since quite some time has passed and it looks like OP either 
>>>>> gave up or had some difficulties, I thought I would chime in 
>>>>> and help out since I just got mine today.
>>>>>
>>>>> http://www.sane-project.org/sane-backends.html#S-PIXMA lists 
>>>>> PIXMA MG6450's status as "untested". I would like to resolve 
>>>>> this. Could someone point me in the right direction? What am I
>>>>>  to do as a tester?
>>>>>
>>>>> Lovro
>



-- 
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 (canon MG6450)

[Rolf Bensch]

Hi Lovro,

Your scanner wasn't fully supported by the backend version 1.0.24.
1200dpi scans don't work.

Everthing else should work with scans up to 600 dpi. Please test all
options with your favourite frontend. I prefer xsane.

If you might get problems with 1.0.24, you won't get around to install
Sane 1.0.25 from git.

The brightness of the scan result depends on the scan settings. Please
try the sliders in xsane and watch the results in the preview window.

Hope this helps.

Cheers,
Rolf

Am 19.09.2015 um 21:45 schrieb lovrolu:
> I have already installed SANE (through my distribution's package
> manager) and confirmed that it works with my scanner. I'm on Fedora 22
> running GNU/Linux, kernel release 4.1.6-201.fc22.x86_64.
>
> Running `scanimage -V` from the shell returns
>
> scanimage (sane-backends) 1.0.24; backend version 1.0.24
>
> I'm not sure but I think the git version of SANE is 1.0.25. Since 1.0.24
> works just fine (from the tests I've done -- the reason I would like to
> help out is to confirm that it *fully* works as expected on 1.0.24) I'm
> not sure if upgrading to 1.0.25 is worthwhile, at least currently.
>
> I have also installed the official driver from Canon. Scans produced
> using Canon's driver are a bit brighter but this is probably just to
> different default settings. Since it was just a quick test I didn't
> bother too much customizing the brightness level but I might do that if
> required.
>
> Anyway, I wanted to know if there's a test suite that SANE offers that I
> could run or some kind of a procedure I could go through to verify that
> SANE *fully* works as expected with my scanner (and with this particular
> version of SANE I have)?
>
> If you think I should use the latest version of SANE I can probably do
> that but most likely not right away. However, I would like to try out
> 1.0.24 first, if possible.
>
> Have a nice day,
> Lovro
>
>> Hi Lovro,
>>
>> The MG6400 Series scanner is supported by the git version of Sane:
>> http://www.sane-project.org/lists/sane-backends-cvs.html#S-PIXMA .
>>
>> You can check the latest code with your scanner. Please install Sane
> >from git as described in README.linux:
>> http://www.sane-project.org/docs.html .
>>
>> Many thanks for your help.
>>
>> Cheers,
>> Rolf
>>
>> Am 18.09.2015 um 22:55 schrieb lovrolu:
>>> Since quite some time has passed and it looks like OP either gave up or
>>> had some difficulties, I thought I would chime in and help out since I
>>> just got mine today.
>>>
>>> http://www.sane-project.org/sane-backends.html#S-PIXMA lists PIXMA
>>> MG6450's status as "untested". I would like to resolve this. Could
>>> someone point me in the right direction? What am I to do as a tester?
>>>
>>> Lovro
>



-- 
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 (canon MG6450)

[Rolf Bensch]

Hi Lovro,

The MG6400 Series scanner is supported by the git version of Sane:
http://www.sane-project.org/lists/sane-backends-cvs.html#S-PIXMA .

You can check the latest code with your scanner. Please install Sane
from git as described in README.linux:
http://www.sane-project.org/docs.html .

Many thanks for your help.

Cheers,
Rolf

Am 18.09.2015 um 22:55 schrieb lovrolu:
> Since quite some time has passed and it looks like OP either gave up or
> had some difficulties, I thought I would chime in and help out since I
> just got mine today.
>
> http://www.sane-project.org/sane-backends.html#S-PIXMA lists PIXMA
> MG6450's status as "untested". I would like to resolve this. Could
> someone point me in the right direction? What am I to do as a tester?
>
> Lovro
>
>


-- 
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-Bugs][315170] pieusb breaks Ubuntu ppa

[Rolf Bensch]

Hi Stef,

I can confirm that your "patch" is working with my ppa.

@Klaus: Please patch pieusb.c.

Many thanks for your help.

Cheers,
Rolf

Am 15.09.2015 um 06:40 schrieb Stef:
> On 15/09/2015 04:08, m. allan noah wrote:
>> Looks like the pieusb backend needs an update, strdup is not ansi C,
>> AFAIK.
>>
>> allan
>
> Hello,
>
> we need to do this include _first_ to get the correct 'magic':
>
> #include "../include/sane/config.h"
>
> with that pieusb.c compiles with strdup like other backends.
>
> Regards,
> Stef
>
>
>

--- ./pieusb.c	2015-09-16 08:48:31.595901930 +0200
+++ ../sane-backends/backend/pieusb.c	2015-09-16 08:50:44.533149481 +0200
@@ -58,6 +58,9 @@
  *
  * --*/
 
+/* Configuration defines */
+#include "../include/sane/config.h"
+
 /* Standard includes for various utiliy functions */
 #include  /* for FILE */
 #include  /* for strlen */
@@ -65,9 +68,6 @@
 #include 
 #include 
 
-/* Configuration defines */
-#include "../include/sane/config.h"
-
 /* SANE includes */
 #include "../include/sane/sane.h"
 #include "../include/sane/saneopts.h"
-- 
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 Canon MF229DW

[Rolf Bensch]

Hi,

Please install Sane from sources as described in README.linux (Step by
step install on Linux 2.6.* and 3.*, both with udev; you can jump over
item 3.2): http://www.sane-project.org/docs.html and report your test
results. I assume that you're a Linux user.

Cheers,
Rolf

Am 26.08.2015 um 07:35 schrieb nw link:
 Hi!
 
 I'd be happy to testing of a Canon MF229DW (04a9x27a8)
 Please tell me what to do.
 
 Problem: my English is very-very bad 

-- 
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] MF8230 still works

[Rolf Bensch]

Hi Troels,

Please test if USB is working. One simple scan with scanimage is OK.

Many thanks for your help.

Cheers,
Rolf


Am 24.08.2015 um 00:11 schrieb Troels Thomsen:
 
 BJNP scanning is normally harder than USB (?), so I decided to skip
 this, but could be convinced to change my mind, if needed?
 
 That is, I tested everything via network / BJNP!
 
 /Troels
 
 
 2015-08-23 22:28 GMT+02:00 Troels Thomsen troels.pil.thom...@gmail.com
 mailto:troels.pil.thom...@gmail.com:
 
 
 Hi ,
 
 Because of the upcoming release, I decided to re-test Rolf’s
 previous work on the MF8200C (mine is a MF8230), and it (still)
 looks like its working fine.
 
 Details are below.
 
 What else should I do?
 BJNP scanning is normally harder than USB (?), so I decided to skip
 this, but could be convinced to change my mind, if needed?
 
 I desired, I can make a USB live stick and run it on my work-labtop
 which has USB2 + USB3 ports. Please specify if any special distro +
 usb-stack or whatever is desired for testing. Otherwise it will
 probably be newest Ubuntu or Mint
 
 /Troels
 
 
 
 
 Details:
 
 I removed all traces of sane/libsane on computer, and took Rolf’s
 PPA, and installed using Synaptic (apt-get preferred the Ubuntu
 version ...)
 Version was: libsane_1.0.25-git20150822-trusty0_i386
 
 Tested:
 
 Using xsane + bjnp:
 
 Flatbed:
 75 + 150 + 600 dpi works fine
 Scanning again and again: works fine
 
 ADF:
 300 dpi works fine
 Scanning again and again: works fine
 
 scanimage -L
 -scanner is found correctly
 
 sane-find-scanner
 - does not find scanner.
 I think the list is full of trouble-shooting steps for this
 
 
 One minor hickup though:
 I experienced a paper-jam with the ADF (my own fault, really).
 After that I found no other method than to 'killall xsane' - no
 problem - but the scanner was in 'bad-mode'. Going to local-mode ,
 then 'remote-scanner' did not help. Reboot of computer did not
 either. Reboot of scanner did the trick.
 I'm sorry I did not get record the error-message in the terminal
 (printf from pixma driver?).
 It was something like illegal reply length.
 
 I'm very happy with the performance even if this corner-case exist.
 
 /Troels
 
 

-- 
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 help with Canon scanner

[Rolf Bensch]

Hi Alan,

You must install xsane with your package manager. Please check in xsane
the used Sane version (File - Info or CTRL+I). It must be 1.0.25.

If we're talking about scanner devices we don't talk about Linux
devices. They are USB or BJNP or MFNP devices, depending on the selected
interface. You always need a frontend (scanimage, xsane, ...) to talk
with your scanner device, e.g. to scan an image!

Cheers,
Rolf

Am 23.08.2015 um 19:15 schrieb Alan McConnell:
 On Sat, Aug 22, 2015 at 11:31:30PM +0200, Rolf Bensch wrote:
 Hi Alan,

 This time with one 'l'.
   G  Vielen Dank!
 
 
 'scanimage -h' shows all options of your scanner, if you scanner has
 been switched to Remote Scanner mode before. Some options come from
 the backend and are not described in the doc of scanimage. Please read
 the manpage of the Pixma backend: 'man sane-pixma' and note that button
 scan isn't supported for your scanner.
  I checked that already.  That is fine with me.  It is easy
for me to half-rise from my chair, press the Scan button
on the Canon . . . and then issue my scanimage command
 
The sane-pixma man page speaks of the 'device pixma'; but
I have tried  ls /dev/pixma and am told that a device
with such a name doesn't exist.  There is confusion here?
or is 'pixma . . hidden in some subdirectory?
 
 Alternatively to scanimage I'm using xsane as gui frontend.
I would love to try xsane, simple-scan, etc!  But I
think I have to install some front-ends(?) or utils,
and I am fearful of breaking what now seems to work
quite well.  Suggestions?
 
 Hope this helps.
  It does indeed!  This morning I was able to scan
the very colorful Japenese advertisement I wrote of
yesterdeay, but today in Gray scale.
 
 My new desires: what /dev/ is this Canon scanner? and how to
 use other front-ends?  are just that: desires.  They are not
 needs.  Again, I am most grateful!!
 
 Alan
 

-- 
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 help with Canon scanner

[Rolf Bensch]

Hi Alan,

This time with one 'l'.

'scanimage -h' shows all options of your scanner, if you scanner has
been switched to Remote Scanner mode before. Some options come from
the backend and are not described in the doc of scanimage. Please read
the manpage of the Pixma backend: 'man sane-pixma' and note that button
scan isn't supported for your scanner.

Alternatively to scanimage I'm using xsane as gui frontend.

Hope this helps.

Cheers,
Rolf


Am 22.08.2015 um 16:08 schrieb Alan McConnell:
 ! ! ! !
 
 On Fri, Aug 21, 2015 at 10:05:20PM +0200, Rolf Bensch wrote:
 Hi Allan,
   G  You're thinking of Mr Noah.  I'm a one-L Alan.
 
 Did you install Sane from sources before? It seems so. Please remove all
 libsane.so.1.0.24 files from /usr/local/lib/ and reinstall Sane with
 'sudo make install' and go ahead with 3.1.
 All done.
 
 You can jump over 3.2.
There is a symlink pointing nowhere there?  ?  ?
 
 Please check the version with 'scanimage -V'. You should get:
 scanimage (sane-backends) 1.0.25git; backend version 1.0.25
Exactly what I got.
 
 Please read your scanners manual. You need to set your scanner into
 Remote Scanner mode before you can use any PC program to scan.
   I _did_ read it, and discovered that after I toggled to
   Remote Scanner I then had to press the OK button.  That
   was what settled things.  For my scanner now 'works'.
   The command 'scanimge  test ' took a while to execute,
   which is not surprising, since it yielded a 
  Netpbm PPM rawbits image data
   file of size 1683875.  I took several images, a couple of
   elaborately colored ads of the beauties of Japan, and
   the images showed up gorgeously.  The physical
   Canon I have certainly is a fine piece of equipment.
 
 Hope this helps.
  It certainly does/did!   RTFM! and now that I've done
so, and pressed the OK button, things seem to be working.
 
I've got to find out how to do BW scans, which means 
studying the man page for scanimage.  I'll stick around
this E-list for a while, just in case I have further
questions I can't solve by myself.
 
 Herr Bensch, bitte nehme Sie meinen tiefsten Dank an! wegen Ihres
 Wissen und, vor allem, Ihrer Geduld!!
 
 Alan
 

-- 
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] Problems with Canon 9000F Mark II

[Rolf Bensch]

Hi Herbert,

Recently I fixed some issues and maybe your issue should also be fixed.

Please install Sane from source as described in README.linux:
http://www.sane-project.org/docs.html and report your results.

Many thanks for your help.

Cheers,
Rolf

Am 10.07.2015 um 15:33 schrieb m. allan noah:
 The initial problem sounds like a USB3 problem. This should be
 improved by running a development version, which has a workaround for
 a linux kernel bug. I am unfamiliar with the other two issues you
 list.

 allan

 On Fri, Jul 10, 2015 at 5:18 AM, Herbert Poetzl herb...@13thfloor.at wrote:
 Dear SANE Developers!

 I'm having various problems with the Canon Mark II scanner,
 which I bought because it is listed as fully supported
 on the SANE device list.

 The first problem might be distro related (Mageia 5), but
 I'll mention it anyway, because it might give some clues:
 With the mageia 'scanimage' tool (sane-backends-1.0.24-10.mga5)
 I can scan a specific area once, which works perfectly fine,
 but when I repeat the very same command, or try a different
 scan after that, the scanning process doesn't start and the
 command hangs till it times out (which is very long). Once
 that happens, I can again scan another image successfully but
 after that, it will always hang, and timeout with an error.
 I then have to power cycle the scanner to get another image.

 [bertl@newhost]$ scanimage -vp -l 100 -t 150 -x 100 -y 2 --format png 
 out.png
 scanimage: scanning image of size 296x8 pixels at 24 bits/pixel
 scanimage: acquiring RGB frame
 scanimage: min/max graylevel value = 188/246
 scanimage: read 7104 bytes in total

 [bertl@newhost]$ scanimage -vp -l 100 -t 150 -x 100 -y 2 --format png 
 out.png
 scanimage: scanning image of size 296x8 pixels at 24 bits/pixel
 scanimage: acquiring RGB frame
 scanimage: min/max graylevel value = 255/0
 scanimage: sane_read: Operation was cancelled

 [bertl@newhost]$ scanimage -vp -l 100 -t 150 -x 100 -y 2 --format png 
 out.png
 scanimage: scanning image of size 296x8 pixels at 24 bits/pixel
 scanimage: acquiring RGB frame
 scanimage: min/max graylevel value = 188/247
 scanimage: read 7104 bytes in total

 [bertl@newhost]$ scanimage -vp -l 100 -t 150 -x 100 -y 2 --format png 
 out.png
 scanimage: scanning image of size 296x8 pixels at 24 bits/pixel
 scanimage: acquiring RGB frame
 scanimage: min/max graylevel value = 255/0
 scanimage: sane_read: Error during device I/O


 The second problem is with the scanimage built from the
 latest git snapshot to verify if the first problem is
 a distribution specific problem.

 The scanimage runs fine and seems to retrieve an image,
 but then outpus a control character and hangs. When I
 interrupt it with CTRL-C, it outputs two more lines
 claiming to stop the scanner and hangs again, a second
 interrupt finally terminates the scan. Repeating the
 command results in a different behaviour.


 [bertl@newhost]$ ~/SANE/bin/scanimage -vp -l 100 -t 150 -x 100 -y 2 --format 
 png out.png
 scanimage: scanning image of size 296x16 pixels at 24 bits/pixel
 scanimage: acquiring RGB frame
 scanimage: min/max graylevel value = 187/254
 scanimage: read 14208 bytes in total
 SOH
 CTRL-C
 scanimage: received signal 2
 scanimage: trying to stop scanner
 CTRL-C
 scanimage: received signal 2
 scanimage: aborting

 [bertl@newhost SANE]$ ~/SANE/bin/scanimage -vp -l 100 -t 150 -x 100 -y 2 
 --format png out.png
 scanimage: scanning image of size 296x16 pixels at 24 bits/pixel
 scanimage: acquiring RGB frame
 scanimage: min/max graylevel value = 187/254
 scanimage: read 14208 bytes in total
 SOH
 libusb: warning [libusb_close] internal signalling read failed, closing 
 anyway


 The final and original problem is with xsane (not sure this
 is the right place here either) which dies a thousand deaths
 when trying to scan - mostly segfaults after the image data
 was retrieved or when the scaned image is closed.

 Appended are a small bunch of traces acquired during testing.

 I would be very hapy to get some hints how to get this
 scanner working properly and I'm happy to test/debug
 whatever you need to get it done.

 Many thanks in advance,
 Herbert


 Program received signal SIGSEGV, Segmentation fault.
 0x75c816a6 in __memcpy_avx_unaligned () from /lib64/libc.so.6
 Missing separate debuginfos, use: debuginfo-install 
 lib64GConf2_4-3.2.6-8.mga5.x86_64 lib64dbus-glib1_2-0.102-4.mga5.x86_64 
 lib64dbus1_3-1.8.16-1.mga5.x86_64
 (gdb) where
 #0  0x75c816a6 in __memcpy_avx_unaligned () from /lib64/libc.so.6
 #1  0x004339f0 in xsane_viewer_read_image (v=0x10b2610) at 
 xsane-viewer.c:2547
 #2  0x0043744f in xsane_viewer_new (filename=0x8e7a50 \360\231}, 
 selection_filetype=0x88a530 \003,
 allow_reduction_to_lineart=8225568, output_filename=0x10686b0 
 \240\350}, allow_modification=16458496, image_saved=8972480)
 at xsane-viewer.c:3121
 #3  0x00464368 in xsane_scan_done (status=SANE_STATUS_EOF) at 
 xsane-scan.c:1226
 

Re: [sane-devel] Canon laser multi-functional support: MFNP protocol

[Rolf Bensch]

Hi Michael,

My recent commit to Sane sources fixed an issue of scanimage. Please
install recent Sane from source and test if you still need to replug
after each scan.

Cheers,
Rolf


Am 02.07.2015 um 20:18 schrieb Michael Shigorin:
 On Sat, Jun 27, 2015 at 08:02:05PM +0200, Louis Lagendijk wrote:
 for the MF8540 first a question: what did you use to initiate the scan?
 xsane and scanimage

 It looks as if a scan was not attempted. Please try (over USB):
 scanimage  filename
 and see what happens.

 Can you please try the fixes I submitted to GIT today to see if
 they fix the network issue with the MF devices?
 
 Sorry for today's noise on the list, your commits have fixed
 networked scanning with MF8540 indeed: RELEASE_1_0_24-296-g0655b05
 scans over ethernet just as fine as it does over USB now (so it
 probably qualifies as Perfect for me given that I have no clue
 about ADF use anyways but then again I'm not a demanding user).
 
 Proper sounds but almost completely white image:
 http://fly.osdn.org.ua/~mike/tmp/sane-pixma/Canon-MF8540Cdn-scanimage.ppm.xz
 how did you scan?
 
 As mentioned in another today's message, I scanned background!
 
 The MF6100 series is not listed, but it again might be quite
 possible to get it to work.
 The same almost white image as with 8540:
 http://fly.osdn.org.ua/~mike/tmp/sane-pixma/Canon-MF6140dn-scanimage.ppm.xz
 As Rolf commented in a mail from April 3 the MF6100 series is
 added in GIT, so it should work now.  so please try scanning
 with scanimage and see if that works over USB and if it works
 over the network after todays fixes.
 
 The problems with two scanimage/xsane runs in a row are
 still there as of today's git though.
 
 
 On Sat, Jun 27, 2015 at 11:12:22PM +0200, Rolf Bensch wrote:
 The MF6100 Series scanner is only working with flatbed scans
 and with single page scans in adf.
 
 Is ADF facility onboard or an option there?
 
 Just now, I'm struggling with multiple pages in adf and duplex
 adf. A patch will take a while, because I only have sporadical
 access to a MF6140 scanner.

 Everytime the scanner reports an error on the lcd display,
 I need to wait until scanimage ends, or faster I send a ^C to
 terminate scanimage.  However, I always need to reconnect the
 usb cable before scanimage can start the next scan.
 
 Hm, usb cable seems to suffice indeed, that has led to another
 round of iR1133 experiments (will come as yet another message).
 
 The status of this scanner still is untested.
 
 That looks like minimal to me as it's apparently been tested
 and can squeeze at least a scan per replug but oh well :-)
 

-- 
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 help with Canon scanner

[Rolf Bensch]

Hi Allan,

Did you install Sane from sources before? It seems so. Please remove all
libsane.so.1.0.24 files from /usr/local/lib/ and reinstall Sane with
'sudo make install' and go ahead with 3.1.

You can jump over 3.2.

Please check the version with 'scanimage -V'. You should get:
scanimage (sane-backends) 1.0.25git; backend version 1.0.25

Please read your scanners manual. You need to set your scanner into
Remote Scanner mode before you can use any PC program to scan.

Hope this helps.

Cheers,
Rolf


Am 21.08.2015 um 16:19 schrieb Alan McConnell:
 On Thu, Aug 20, 2015 at 10:11:06PM +0200, Rolf Bensch wrote:
 Hi Allan,

 Sorry for my missunderstanding instrunction.
   Perhaps it was I who misunderstood.
 
 Please install latest Sane backend from git (it's the ongoing
 development version) as described under Step by step install on Linux
 2.6.* and 3.*, both with udev in README.linux. Here's the direct link:
 http://www.sane-project.org/README.linux .
   I did this meticulously.  And I feel that I am closer than
   I was.  Whoever wrote up this doc did a good job.
 
   I'll give some results of my step-by-step progress through
   the instructions.  I got the
   sane-backends-git20150821.tar.gz
   and did the standard ./confifure, make, and make install.
   The ldconfig results told me that there were some libs I'd
   never heard of which couldn't be found . . .
   But I now have  libsane.so.1.0.24  and   libsane.so.1.0.25
   in /usr/local/lib/ .
 
   In 3.2 the ln instruction creates a broken symlink.  I
   suspect that the instruction is wrong?
 
   Cutting to the chase, scanimage -L yields
 device `pixma:04A92774_0147O24E997F' is a CANON Canon i-SENSYS
 MF4700 Series multi-function peripheral
 ! !  Of course this cheered me mightilyg.
 
 But when I run scanimage  test.pnm, I get, after a long
 wait, during which time my USB splitter lights blink wildly,
   scanimage: sane_read: Device busy  ? ! ? !
 This even when I press the Scan button on my Canon machine.
 
 And I get a file test.pnd which reads as follows:
 P6
 # SANE data follows
 640 877
 255
   So I am clearly closer, but not there yet.  I hope that 
 this process converges
 without any too many further iterations.
 
 Again, thanks.  I hope that there is a member on this E-list who
 is familiar with Canon three-in-one machines who can give me a tip.
 
 Alan
 

-- 
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] scanimage hangs at shutdown (Preparing for a sane-backends release)

[Rolf Bensch]

Hi Olaf,

I removed atexit() from scanimage and comitted the patch last night.

Now scanimage doesn't hang anymore under OpenSuse with libusb-compat.

Cheers,
Rolf


Am 20.08.2015 um 01:09 schrieb Olaf Meeuwissen:
 Hi Rolf,
 
 Rolf Bensch writes:
 
 Hi Olaf,

 Am 19.08.2015 um 03:27 schrieb Olaf Meeuwissen:

 Rolf Bensch writes:

 Using fork or pthread makes no difference.

 A sleep at the end of main() works wonders.

 But not for the other exit() functions. 'scanimage -h' or 'scanimage -A'
 still hang with the same issue.

 I suggest to replace atexit and all exit() functions by the existing
 scanimage_exit() function.

 Please check if attached patch is running with your installations.

 I had a look at the patch and tripped over the fixme.  Next, I had a
 look at the scanimage_exit() implementation and the timing of adding
 that to the list of functions to call atexit.  Something definitely
 smells there.

  - scanimage_exit() may call sane_close().  That function may need to do
device I/O.
  - scanimage_exit() is register with atexit() *before* sane_init() gets
called.  This means that any functions registered via atexit() in a
backend run *before* scanimage_exit().
  - none of the backends call atexit() directly but any library they use
may register exit handlers

 Is there any chance that the libusb-compat installations that are
 affected register an exit handler?  Say something like libusb_exit()?
 If that is the case, device I/O will be made impossible *before*
 scanimage_exit() gets a chance to sane_close() the device.

 Note that the -h and -A options to scanimage need the device's options
 so that just about guarantees that its backend needs to talk to it.

 Does moving the atexit() call *after* sane_init() fix this issue?

 Good idea, but it doesn't work. Many thanks for your help.
 
 Too bad.  In that case your patch looks fine to me.
 
 Hope this helps,
 

-- 
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: Canon Pixma MG7550 hangs

[Rolf Bensch]

Hi All,

My last commits should have fixed this issue.

Cheers,
Rolf



Am 04.04.2015 um 00:07 schrieb Rolf Bensch:
 Hi All,

 Sorry for my late response. And sorry again, I'm very busy on my new
 job and I can only sometimes look into the mailing list. It's more
 secure to set me on cc, if you want to address me.

 It seems that we have a general problem in the Pixma backend. During
 the past months, several people reported timeouts resp. hang problems
 with their scanners.

 I also had such problems with my new USB3 card, but as I found time to
 solve this problem, it has been gone by itself...

 Now let's start with troubleshooting.

 (1) Please try different frontends, if you have problems with
 scanning. Some users reported problems with scanimage, but xsane is
 working.

 (2) If you're checking USB scanning, always switch off | disable |
 disconnect all ethernet | WiFi connections from your scanner.

 (3) If you're checking ethernet | WiFi connection, always disconnect
 USB from your scanner. And don't mix ethernet and WiFi.

 (4) What's the lastest status of USB only scanning from flatbed? This
 is the base function and should always run without any problems.

 (5) If flatbed scans are running and if you have problems with adf, we
 need to check the usb protocols. Please create log files for single
 page and 2-page scans with 'export SANE_DEBUG_PIXMA=11'. And to reduce
 log files sizes, please scan only small image areas of about 5mm x
 5mm. Background: All pages are scanned in one scan session. We need to
 check if the scan session will be closed after the last page resp.
 after detecting paper empty with 10s timeout.

 I prepared 2 patches for you, if your scanner hangs at the end of a
 scan. Or if your scanner doesn't want to scan a 2nd time without
 repowering. Exclude item (5). Please try only one patch at one time,
 and revoke it before you want to try the other one.

 (6) I found an old patch, I got about 3 years ago as a bug fix
 (3c5cc2a). There is an EOF declared as an error! The original patch
 was for USB only, but has been extended for all protocols with a later
 patch. Attached patch file pixma_io_sanei.c.patch revokes the old patches.

 (7) Due to the reported issue that sometimes xsane is working and
 scanimage doesn't, I found out that the method mp150_finish_scan() in
 pixma_mp150.c will be called twice: (a) At the end of the scan and (b)
 called from scanimage (I didn't investigated other frontends than
 scanimage). Existing code can create communication problems with the
 scanner, if calling (b) is faster than (a) is ready. I'm not sure, if
 this could really happen. Attached patch file pixma_mp150.c.patch
 fixes this issue. I also prepared a patch file for the Pixma CCD
 scanners (pixma_mp810.c.patch).

 Please report your results and|or respond your suggestions.

 Cheers,
 Rolf



 Am 03.03.2015 um 22:49 schrieb Troels Thomsen:
 Hi Martin,

 Good work Martin!
 Any missing commands would be a smoking gun imho.

 Rolf, are you following this thread ?

 /Troels



 2015-02-24 23:09 GMT+01:00 Martin martin...@intergga.ch
 mailto:martin...@intergga.ch:

 Troels

 I don't have access to another computer. But I have installed
 OpenSUSE 13.2
 and the result is the same as on 13.1.
 I did not (yet) test with short delays between the commands, but
 I compared
 the communication of the Canon software scangear on Windows with
 the one of
 SANE:

 At start ScanGear sends the following (linebreaks added by me):
 ?xml version=1.0 encoding=utf-8 ?
 cmd xmlns:ivec=http://www.canon.com/ns/cmd/2008/07/common/;
 xmlns:vcn=http://www.canon.com/ns/cmd/2008/07/canon/;
   ivec:contentsivec:operationVendorCmd/ivec:operation
 ivec:param_set servicetype=scan
   ivec:jobID /ivec:jobID
   vcn:ijoperationModeShift/vcn:ijoperation
   vcn:ijmode1/vcn:ijmode
 /ivec:param_set
   /ivec:contents
 /cmd

 response:
 ?xml version=1.0 encoding=utf-8 ?
 cmd xmlns:ivec=http://www.canon.com/ns/cmd/2008/07/common/;
 xmlns:vcn=http://www.canon.com/ns/cmd/2008/07/canon/;
   ivec:contents
 ivec:operationVendorCmdResponse/ivec:operation
 ivec:param_set servicetype=scan
   ivec:responseOK/ivec:response
   ivec:response_detail/
   vcn:ijoperationModeShiftResponse/vcn:ijoperation
   vcn:ijresponseOK/vcn:ijresponse
   vcn:ijresponse_detail/
 /ivec:param_set
   /ivec:contents
 /cmd

 ScanGear starts a scan with the following command sequece:
 ?xml version=1.0 encoding=utf-8 ?
 cmd xmlns:ivec=http://www.canon.com/ns/cmd/2008/07/common/;
   ivec:contents
 ivec:operationStartJob/ivec:operation
 ivec:param_set servicetype=scan
   ivec:jobID0001/ivec:jobID
   ivec:bidi1/ivec:bidi
 /ivec:param_set
   /ivec:contents
 /cmd

 response:
 ?xml version=1.0 encoding=utf-8

Re: [sane-devel] Need help with Canon scanner

[Rolf Bensch]

Hi Allan,

Sorry for my missunderstanding instrunction.

Please install latest Sane backend from git (it's the ongoing
development version) as described under Step by step install on Linux
2.6.* and 3.*, both with udev in README.linux. Here's the direct link:
http://www.sane-project.org/README.linux .

Cheers,
Rolf


Am 20.08.2015 um 16:23 schrieb Alan McConnell:
 On Wed, Aug 19, 2015 at 10:47:55PM +0200, Rolf Bensch wrote:
 Hi Alan,

 The libsane version from Debian doesn't support your scanner.
   There seems to be a consensus that I must upgrade to
   libsane 1.0.24.  So I have downloaded
 libsane_1.0.24-8_i386.deb
   and run  dpkg -i  libsane_1.0.24-8_i386.deb.
   But this gives me error messages, letting me know that
   the install was not successful.
 
   So, alas, I need further assistance.  Is there a way
   of removing _all_ sane stuff from my computer and
   then downloading from sane-project.org a bunch of the
   latest packages?  This seems cumbersome, but what I
   am doing is not successful.
 
 You need to install Sane Development Version from git as described in
 README.linux (http://www.sane-project.org/docs.html).
   I am guessing that SANE Standard Version 2.0(development)
   is what is being referred to here.  But when I click on this
   I am told that this is currently under development.
 
   I apologize for what must seem like stupidity.  But sinee
   there are front-ends, back-ends, tools, etc for a person
   to cope with, perhaps I may be pardoned, and helped
   further.
 
 Alan
 

-- 
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 help with Canon scanner

[Rolf Bensch]

Hi Alan,

The libsane version from Debian doesn't support your scanner.

You need to install Sane Development Version from git as described in
README.linux (http://www.sane-project.org/docs.html).

Cheers,
Rolf

Am 19.08.2015 um 22:13 schrieb Alan McConnell:
 First of all, thanks for your post, with the helpful hints.  I
 can narrow my questions; see below.

 On Thu, Aug 20, 2015 at 01:38:37AM +0900, Gernot Hassenpflug wrote:
   .  .  .  .

found USB scanner (vendor=0x04a9, product=0x2774) at libusb:001:004
  I can't find where the above line tells _exactly_ what
Canon backend is the appropriate one.  I think the above
tells me what the Canon backend should be, and also tells
me the USB port.

 What version of SANE do you have installed? You can look at the package
 libsane, e.g.
 aptitude show libsane
 (on my Debian unstable installation it is 1.0.24-13, although I also
 install the latest development version in /usr/local)
 The above call to aptitude tells me that I have
 Version: 1.0.22-7.4


 The MF4700 series has been in SANE since before December 2013, so unless
 you are using an ancient version of SANE, it is most likely that you have
 the backend you need in SANE.
   I believe I do.  I remember seeing, back in April, that MF4770n
 was supported.

 The documentation in README.linux that comes with the SANE code should help
 you check the installation and do some debugging, or at least specify to
 the list which steps you managed to succeed in, and where things failed.
  Thank you very much for this tip.  From README.linux, I learned:
The device files used by libusb are located in /proc/bus/usb/
  . . .or in /dev/bus/usb/.  For me, they are in
/dev/bus/usb/, which means, I guess, that I am running udev.
I also put the line   USB_DEVFS_PATH=/dev/bus/usb   into
my .bashrc.  But the call toscanimage image.pnm  still
fails.  My USB socket lights blink furiously, eventually
the call returns withno SANE devices foundand
I am left with an empty file, image.pnm, which I then delete.

 /usr/share/doc/libsane/README.Debian.gz (a Debian-specific file with a
 trouble-shooting section)
This didn't help me.

I think I must be closeg.  But even though I know that
the scanner is seen, and I know the ports in /dev/bus/usb,
I can't get scanimage to work.  I hope for further suggestions.

 Alan




-- 
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] scanimage hangs at shutdown (Preparing for a sane-backends release)

[Rolf Bensch]

Hi Olaf,

Good idea, but it doesn't work. Many thanks for your help.

Cheers,
Rolf

Am 19.08.2015 um 03:27 schrieb Olaf Meeuwissen:
 
 Rolf Bensch writes:
 
 Using fork or pthread makes no difference.

 A sleep at the end of main() works wonders.

 But not for the other exit() functions. 'scanimage -h' or 'scanimage -A'
 still hang with the same issue.

 I suggest to replace atexit and all exit() functions by the existing
 scanimage_exit() function.

 Please check if attached patch is running with your installations.
 
 I had a look at the patch and tripped over the fixme.  Next, I had a
 look at the scanimage_exit() implementation and the timing of adding
 that to the list of functions to call atexit.  Something definitely
 smells there.
 
  - scanimage_exit() may call sane_close().  That function may need to do
device I/O.
  - scanimage_exit() is register with atexit() *before* sane_init() gets
called.  This means that any functions registered via atexit() in a
backend run *before* scanimage_exit().
  - none of the backends call atexit() directly but any library they use
may register exit handlers
 
 Is there any chance that the libusb-compat installations that are
 affected register an exit handler?  Say something like libusb_exit()?
 If that is the case, device I/O will be made impossible *before*
 scanimage_exit() gets a chance to sane_close() the device.
 
 Note that the -h and -A options to scanimage need the device's options
 so that just about guarantees that its backend needs to talk to it.
 
 Does moving the atexit() call *after* sane_init() fix this issue?
 
 Hope this helps,
 

-- 
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 driver for MG7550 produces stripes

[Rolf Bensch]

Addendum:

Xsane sends a gamma table to the scanner, which is responsible for the
quality of the image.

Please correct me if I'm wrong, xsane also manipulates the brightness
and the contrast of the image.

Hope this helps.

Cheers,
Rolf

Am 18.08.2015 um 22:50 schrieb Rolf Bensch:
 Hi Martin,

 The backend isn't responsible for any artefacts, it handles the scanned
 data 1:1 to the saved image colour file. The Pixma backend only
 manipulates the images for grayscale and lineart (1 bit b/w) output formats.

 OK, there is some loss with image compression algorithms. If you have
 trouble with this, you should select lossless image formats.

 Maybe you should test different scan resolutions.

 Hope this helps.

 Cheers,
 Rolf



 Am 18.08.2015 um 13:32 schrieb Martin:
 I noticed diagonal stripes on some scanned pictures.

 In order to verify that it is not on the picture but an artifact of sane
 I scanned the same picture with Canon's scangear-progam on a
 Windows-system. That picture does not have the stripes.

  

 Please find the image scanned with xsane attached.

  

 Cheers,

 Martin

  




-- 
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] scanimage hangs at shutdown (Preparing for a sane-backends release)

[Rolf Bensch]

Using fork or pthread makes no difference.

A sleep at the end of main() works wonders.

But not for the other exit() functions. 'scanimage -h' or 'scanimage -A'
still hang with the same issue.

I suggest to replace atexit and all exit() functions by the existing
scanimage_exit() function.

Please check if attached patch is running with your installations.

Cheers,
Rolf

Am 18.08.2015 um 03:31 schrieb m. allan noah:
 Good point. Rolf- any chance you could insert a sleep at the end of
 main()? Also, does the backend in question use fork() on this distro?
 
 allan
 
 On Mon, Aug 17, 2015 at 8:30 PM, Olaf Meeuwissen
 olaf.meeuwis...@avasys.jp wrote:

 m. allan noah writes:

 I don't understand. Registered atexit handlers should be called when
 main() returns, which is after sane_cancel. What version of
 libusb-compat is in use?

 Please remember that sane_cancel() only *initiates* cancellation.  So
 cancellation may not have finished yet when main() returns.  I'm not
 sure if this is causing the problem but thought I'd mention it anyway.

 Hope this helps,
 --
 Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- EPSON AVASYS CORPORATION
 FSF Associate Member #1962   Help support software freedom
  http://www.fsf.org/jf?referrer=1962
 
 
 
--- ./scanimage.c	2015-08-18 13:02:23.132264339 +0200
+++ ../sane-backends/frontend/scanimage.c	2015-08-18 13:02:39.791040702 +0200
@@ -135,7 +135,7 @@
 static const char *icc_profile = NULL;
 
 static void fetch_options (SANE_Device * device);
-static void scanimage_exit (void);
+static void scanimage_exit (int);
 
 static SANE_Word tl_x = 0;
 static SANE_Word tl_y = 0;
@@ -687,7 +687,7 @@
   fprintf (stderr,
 	   %s: option --%s: bad option value (rest of option: %s)\n,
 	   prog_name, opt-name, str);
-  exit (1);
+  scanimage_exit (1);
 }
   str = end;
 
@@ -796,7 +796,7 @@
 	{
 	  fprintf (stderr, %s: option --%s: closing bracket missing 
 		   (rest of option: %s)\n, prog_name, opt-name, str);
-	  exit (1);
+	  scanimage_exit (1);
 	}
 	  str = end + 1;
 	}
@@ -808,20 +808,20 @@
 	  fprintf (stderr,
 		   %s: option --%s: index %d out of range [0..%ld]\n,
 		   prog_name, opt-name, index, (long) vector_length - 1);
-	  exit (1);
+	  scanimage_exit (1);
 	}
 
   /* read value */
   str = parse_scalar (opt, str, value);
   if (!str)
-	exit (1);
+scanimage_exit (1);
 
   if (*str  *str != '-'  *str != ',')
 	{
 	  fprintf (stderr,
 		   %s: option --%s: illegal separator (rest of option: %s)\n,
 		   prog_name, opt-name, str);
-	  exit (1);
+	  scanimage_exit (1);
 	}
 
   /* store value: */
@@ -874,7 +874,7 @@
   if (opt == NULL)
 {
   fprintf (stderr, Could not get option descriptor for option 0\n);
-  exit (1);
+  scanimage_exit (1);
 }
 
   status = sane_control_option (device, 0, SANE_ACTION_GET_VALUE,
@@ -883,7 +883,7 @@
 {
   fprintf (stderr, Could not get value for option 0: %s\n,
sane_strstatus (status));
-  exit (1);
+  scanimage_exit (1);
 }
 
   /* build the full table of long options */
@@ -894,7 +894,7 @@
   if (opt == NULL)
 	{
 	  fprintf (stderr, Could not get option descriptor for option %d\n,i);
-	  exit (1);
+	  scanimage_exit (1);
 	}
 
   /* create command line option only for settable options */
@@ -1013,7 +1013,7 @@
 {
   fprintf (stderr, %s: setting of option --%s failed (%s)\n,
 	   prog_name, opt-name, sane_strstatus (status));
-  exit (1);
+  scanimage_exit (1);
 }
 
   if ((info  SANE_INFO_INEXACT)  opt-size == sizeof (SANE_Word))
@@ -1048,7 +1048,7 @@
 {
   fprintf (stderr, %s: attempted to set inactive option %s\n,
 	   prog_name, opt-name);
-  exit (1);
+  scanimage_exit (1);
 }
 
   if ((opt-cap  SANE_CAP_AUTOMATIC)  optarg 
@@ -1061,7 +1061,7 @@
 	  fprintf (stderr,
 		   %s: failed to set option --%s to automatic (%s)\n,
 		   prog_name, opt-name, sane_strstatus (status));
-	  exit (1);
+	  scanimage_exit (1);
 	}
   return;
 }
@@ -1081,7 +1081,7 @@
 	{
 	  fprintf (stderr, %s: option --%s: bad option value `%s'\n,
 		   prog_name, opt-name, optarg);
-	  exit (1);
+	  scanimage_exit (1);
 	}
 	}
   break;
@@ -1097,7 +1097,7 @@
 	  if (!vector)
 	{
 	  fprintf (stderr, %s: out of memory\n, prog_name);
-	  exit (1);
+	  scanimage_exit (1);
 	}
 	}
   parse_vector (opt, optarg, vector, vector_length);
@@ -1109,7 +1109,7 @@
   if (!valuep)
 	{
 	  fprintf (stderr, %s: out of memory\n, prog_name);
-	  exit (1);
+	  scanimage_exit (1);
 	}
   strncpy (valuep, optarg, opt-size);
   ((char *) valuep)[opt-size - 1] = 0;
@@ -1648,7 +1648,7 @@
 }
 
 static void
-scanimage_exit (void)
+scanimage_exit (int status)
 {
   if (device)
 {
@@ -1666,6 +1666,7 @@
 free (option_number);
   if (verbose  1)
 fprintf (stderr, scanimage: finished\n);
+  exit (status);
 }
 
 

Re: [sane-devel] Missing Resolution for Canon MG7550

[Rolf Bensch]

Hi Martin,

Gernot is right. The scanner provides only 75, 150, 300, 600, 1200 and
2400 dpi.

If you need other resolutions, you need to post process your images with
e.g. imagemagick or gimp.

Cheers,
Rolf


Am 18.08.2015 um 17:11 schrieb Gernot Hassenpflug:
 On Tue, Aug 18, 2015 at 9:06 PM, Martin martin...@intergga.ch
 mailto:martin...@intergga.ch wrote:
 
 Hi Rolf,
 
 The sane backend does not provide all resolutions of the scanner:
 
 Xsane offers 75, 150, 300, 600, 1200 and 2400 ppi.
 
 Canon's scangear however offers 75, 100, 150, 200, 300, 400, 600 and
 1200 ppi.
 
 
 Hello Martin,
 There is infact no such physical resolution as 200 and 400.
 All the physical scans use resolutions which are multiples of 75.
 A 200dpi scan will be done at 300dpi and scangear simply filters it down
 to 200.
 Likewise, 400 is done at 600dpi and filtered down.
 SANE implements the physical scanning capability. Since the 200 and 400
 are done in software, it would be a filter in the front-end, not the
 backend.
 At least, that is my understanding.
 Regards,
 Gernot Hassenpflug

-- 
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] scanimage hangs at shutdown (Preparing for a sane-backends release)

[Rolf Bensch]

It's not the described bug in libusb-compat.

However, atexit() isn't working as desired in OpenSuse.

scanimage closes the usb interface from atexit() *before* sane_cancel()
is ready at the end of main().

Is this a problem of OpenSuse or should somebody rewrite the shutdown
sequence of scanimage?

Cheers,
Rolf


Am 11.08.2015 um 14:37 schrieb m. allan noah:
 Yes- this sounds like the bug in libusb-compat mentioned in my last
 email. According to the manpage for atexit, registered functions
 should be called in reverse order. So, if we can call atexit in
 scanimage, after libusb's call to atexit, that might help. You could
 try moving scanimage atexit call to after its sane_init call? I'm not
 sure that is where libusb registers, or if this is even a valid
 long-term solution, but it is worth a try.
 
 allan
 
 On Tue, Aug 11, 2015 at 6:42 AM, Rolf Bensch r...@bensch-online.de wrote:
 Hi Allan,

 I compared scanimage and xsane logs, and I found a difference after
 Reader task terminated.

 It seems that scanimage has a problem closing the scanner.

 I removed scanned data in the log files for better reading.

 Hope this helps.

 Cheers,
 Rolf



 Am 08.08.2015 um 00:29 schrieb m. allan noah:
 After a bit of searching, this looks like a bug in libusb-compat:
 http://sourceforge.net/p/libusbx/mailman/libusbx-devel/thread/522af646.7060...@redhat.com/

 allan

 On Fri, Aug 7, 2015 at 6:21 PM, m. allan noah kitno...@gmail.com wrote:
 Rolf- can you get a log of the scanimage and xsane shutdown sequences,
 and see if they call something in a different order? I had one report
 of this same error with the Fujitsu iX500, but I never reproduced.

 allan

 On Fri, Aug 7, 2015 at 5:40 PM, Rolf Bensch r...@bensch-online.de wrote:
 Hello,

 I just fixed an usb communication problem with OpenSuse and the Pixma
 backend.

 Scanning with xsane is working with my CS9000F scanner. But if I'm
 scanning with scanimage, I always get this message at the end of each 
 scan:
 libusb: warning [libusb_close] internal signalling read failed, closing
 anyway

 Then I need to terminate scanimage with 2x CTRL C. And sometimes the USB
 bus is blocked for my scanner until I reboot the machine. The scanned
 image is OK.

 I'm testing OpenSuse 13.2 in VirtualBox 5.0 on Ubuntu 14.04.1, both 
 x86_64.

 Maybe you can give me a hint where to look to fix this issue or Allan
 can fix this for me. I'm not very familiar with the usb library.

 Many thanks for your help.

 Cheers,
 Rolf

 Am 04.08.2015 um 13:11 schrieb Johannes Meixner:

 Hello,

 On Aug 3 14:08 m. allan noah wrote (excerpt):
 ... I know that Gentoo has some systemd compilation fixes.

 Everey Linux distribution should submit their patches to SANE
 upstream (provided their changes make sense for upstream).

 Here our (i.e. openSUSE) patches that we still have:


 1)
 Right now I filed
 https://alioth.debian.org/tracker/index.php?group_id=30186atid=410366
 with my fix-buffer-overflow.patch attached
 that fixes a too small array in backend/niash.c


 2)
 My re-add-SANE_CAP_ALWAYS_SETTABLE.patch re-adds SANE_CAP_ALWAYS_SETTABLE
 to sane.h which was erroneously removed in sane-backends-1.0.20 so that
 sane-frontends and xsane can no longer build, see
 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527675

 re-add-SANE_CAP_ALWAYS_SETTABLE.patch
 -

 --- include/sane/sane.h.orig2009-06-12 10:19:19.0 +0200
 +++ include/sane/sane.h 2009-06-12 10:20:12.0 +0200
 @@ -115,6 +115,7 @@ SANE_Device;
  #define SANE_CAP_AUTOMATIC (1  4)
  #define SANE_CAP_INACTIVE  (1  5)
  #define SANE_CAP_ADVANCED  (1  6)
 +#define SANE_CAP_ALWAYS_SETTABLE   (1  7)

  #define SANE_OPTION_IS_ACTIVE(cap) (((cap)  SANE_CAP_INACTIVE)
 == 0)
  #define SANE_OPTION_IS_SETTABLE(cap)   (((cap) 
 SANE_CAP_SOFT_SELECT) != 0)
 -


 The re-add-SANE_CAP_ALWAYS_SETTABLE.patch still applies for
 current sane-backends-git20150804.tar.gz so that I assume
 SANE_CAP_ALWAYS_SETTABLE is still missing in sane-backends.

 I did not verify whether or not meanwhile all SANE frontends
 also no longer use SANE_CAP_ALWAYS_SETTABLE so that it could
 meanwhile be really removed in sane-backends.


 3)
 My fix-mustek_pp_ccd300.c.patch fixes undefined 'foo = ++foo modulo bar'
 operations in mustek_pp_ccd300.c see
 https://bugzilla.opensuse.org/show_bug.cgi?id=498435
 and
 https://alioth.debian.org/tracker/index.php?func=detailaid=311857group_id=30186atid=410366
 where the upstream maintainer did not understand what is wrong and
 closed it  as Wont Fix so that we must keep this patch forever
 to make at least the code somehow valid for the compiler.
 fix-mustek_pp_ccd300.c.patch is attached to the above
 alioth.debian.org bug tracker issue.
 Of course because the result of 'foo = ++foo' is undefined
 I cannot know if my patch

Re: [sane-devel] Announce: Driver for Pacific Image Electronics and Reflecta USB scanners

[Rolf Bensch]

Hi Klaus,

Some functions of your scanner backend are very interesting for the
Pixma backend, too. My scanner (CanoScan 9000F) also has an ir-lamp for
dust removal functions. I'm very happy that you're implementing such
functions to Sane now.

Please move the buffer functions from backend/pieusb_buffer.[ch] to e.g.
sanei/sanei_buffer.[ch]. Then I also can use your buffer functions for
the Pixma backend.

Many thanks,
Rolf

Am 10.08.2015 um 11:57 schrieb Klaus Kaempf:
 Hi Stef,

 * Stef stef@free.fr [Aug 07. 2015 09:13]:
 I have starting to review the backend's code.
 thanks a lot !

 The bug tracker
 has all the details, but there are a couple of things that are worth
 discussing here.

 First sane/sanei_ir.h is used. I don't find it in the pieusb
 branch, and this is not part of current SANE's sources. Where does
 it come from ?
 I forgot to add it to the pieusb branch, fixed now. The scanner comes
 with an infrared lamp for dust detection. sanei_ir.h is the header
 file for the dust removal functions.

 Second, mmap is used. Are we sure it is available on all the
 platforms where SANE is compiled ?
 Uhm, I have no idea, sorry.


 Klaus



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