[sane-devel] Canon PIXMA MG6350

[Rolf Bensch]

Hi Theo,

Please test the same issue with scanimage.

(1) search your scanner: 'scanimage -L'
(2) scan via each interface with option '-d', e.g. 'scanimage -d
"pixma:04A91908" > test.pnm' (this is my scanner's usb-id, replace it
with one by one you found in (1)).

If you'll find problems with scanimage, these come from SANE. Please
mention that XSANE is 3rd party software and report problems there.

You can also check the behaviour of your scanner's push buttons with (1)
push any button and (2) 'scanimage -A'.

If you'll have problems here, please enable debug output with 'export
SANE_DEBUG_PIXMA=11' and provide the output here. The debug output can
look like this, inlined in the respond from scanimage:

  Buttons:
    --button-update
        Update button state
[pixma] INTR T=1.661 len=32
[pixma]  00000000:00 20 00 00 00 00 00 00  00 00 00 00 00 00 00 00
[pixma]  00000010:00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
[pixma]
    --button-1 <int> [1] [read-only]
        Button 1
    --button-2 <int> [0] [read-only]
        Button 2
    --original <int> [0] [read-only]
        Type of original to scan
    --target <int> [2] [read-only]
        Target operation type

If your push buttons are detected by SANE, you can also use scanbd:
http://lists.alioth.debian.org/pipermail/sane-devel/2013-January/030828.html.

Cheers,
Rolf



Am 18.03.2013 23:20, schrieb Theo:
> Hi Rolf,
> 
> I assumed xsane keeps an 'open connection' once the device is selected.
> To get the scanner to work I:
> 1 stopped xsane
> 2 unplugged the network cable from the scanner
> 3 tried to scan via USB without result
> 4 turned the scanner off and on again
> 5 did a successful scan via USB
> 
> After this I plugged in the network cable, stopped & started xsane and
> was still able to scan via USB.
> 
> I then rebooted my PC (while the scanner had both USB & network
> connected) and the scan via USB failed again.
> 
> For some reason, right now, both scanning via USB and the network work fine.
> 
> Do you know if there is an open bug for this issue?
> 
> 
> -- 
> Kind regards, /Theo van Rijn/