Re: [sane-devel] HP5590 and scanbd button recognition

[Ilia Sotnikov]

Damiano,
apologies for a delay on my side - had just a quick look over the patch and it 
seems ok to me overall, just had no time to apply it. Sorry for that. Hopefully 
would be able to make it on coming weekend.

---
 Ilia Sotnikov

> On Apr 9, 2018, at 2:01 PM, Cesello  
>  wrote:
> 
> Hi Ilia,
> some news about my patch on hp5590.c ? Was usefull ? Un-usefull ? Very 
> Bad thing ? :)
> 
> Let me know
> Damiano
> 
> 
>> On 13/03/2018 20:56, Ilia Sotnikov wrote:
>> Excellent, thanks Damiano! As a quick step you could send the patch over to 
>> the DL and I’ll adapt it if needed. Or you could create a merge request, 
>> which would be more elegant though require additional steps.
>> ---
>> Ilia Sotnikov
>> 
>>> On Mar 13, 2018, at 21:29, Cesello  wrote:
>>> 
>>> Hi Ilia and Jared
>>> I'm just registered to this ML to propose my patch to this back end
>>> driver made in the past weekend.
>>> And I see someone have my same problem :)
>>> I've used hp5590 scanner with scanbuttond for years. Some week ago I've
>>> upgraded my system to debian 9 and
>>> discovered that scanbd does not works anymore with my scanner. I really
>>> need this functionality so I've made
>>> modifications to hp5590.c code to export the options .
>>> Is a first attempt and the backend called by scanbd threads makes
>>> buttons quite  responsive
>>> without using a self polling thread.
>>> I've made a patch file for debian 9  stable version package (yes but the
>>> real patch is for hp5590.c only)
>>> If you are interested I can send it (or tell me if I have to release
>>> into the repo directly I'm new user here :))
>>> 
>>> Damiano
>>> 
 On 07/03/2018 14:01, hostcc at gmail.com (Ilia Sotnikov) wrote:
 Hi,
 backend author here - it shouldn't be too much of effort to expose
 button status so scanbd can use it. Though haven't gone thru its
 documentation to understand requirements. As a technical insight -
 there is hp5590_read_buttons() function in hp5590_cmds.c that reads
 button status.
 However, I'll seek for a volunteer to test a change as I don't have
 access to HW currently.
 
 On Wed, Mar 7, 2018 at 12:40 AM, Wilhelm Meier
  wrote:
> Please try the old scanbuttond-backend for this type of scanner - it
> should work. The HP sane backend sadly doesn't support the buttons on
> this scanner.
> 
> Am 06.03.2018 um 15:46 schrieb Jared Hedegaard:
>>> Main question: does the HP 5590 support button presses or am I just 
>>> setting this up incorrectly?
>>> 
>>> I'm been successful using scanbd with SANE backends to get scanning 
>>> working over my network and locally on the host machine, but I can't 
>>> seem to get it to recognize button presses, either running scanbd in 
>>> foreground or background.
>>> 
>>> For past testing, it seems that actions defined in scanbd.conf are used 
>>> to tie to the backend options? From searching /var/log/syslog, I 
>>> expected to track button presses or get some sort of trigger feedback, 
>>> and I didn't think I needed an action set up for it.
>>> 
>>> Any help on this one would be much appreciated. Thanks.
>>> 
>>> Jared H
>>> 
>> After a bit more research, it looks like doing this with the SANE 
>> backend for HP 5590 is not possible. scanbd is used to tie custom 
>> actions to the options available on the scanner. In this case, none of 
>> the 10 options seem to return values. They all look to be ones that I 
>> designate from some client software.
>> 
>> scanbd: found active option[1] tl-x (type: 2) for device 
>> hp5590:libusb:001:008
>> scanbd: found active option[2] tl-y (type: 2) for device 
>> hp5590:libusb:001:008
>> scanbd: found active option[3] br-x (type: 2) for device 
>> hp5590:libusb:001:008
>> scanbd: found active option[4] br-y (type: 2) for device 
>> hp5590:libusb:001:008
>> scanbd: found active option[5] mode (type: 3) for device 
>> hp5590:libusb:001:008
>> scanbd: found active option[6] source (type: 3) for device 
>> hp5590:libusb:001:008
>> scanbd: found active option[7] resolution (type: 1) for device 
>> hp5590:libusb:001:008 scanbd: found active option[8] extend-lamp-timeout 
>> (type: 0) for device hp5590:libusb:001:008
>> scanbd: found active option[9] wait-for-button (type: 0) for device 
>> hp5590:libusb:001:008
>> scanbd: found active option[10] preview (type: 0) for device 
>> hp5590:libusb:001:008
>> 
>> In this case, it looks like I will have to try the old scanbuttond 
>> backends for this, or see if there are optional enhancements for the 
>> SANE hp5590 backend.
>> 
>> Jared
>> 
> --
> sane-devel mailing list: sane-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
> Unsubscribe: Send mail 

[sane-devel] canon d570

[Steve Marx]

Hello,

I have a canon d570 scanner which is not on the list.  It seems to
be working ok with the sane_pixma driver using the same parameters
as canon d530.  System is up-to-date archlinux, using usb interface.

i rebuilt the libsane-pixma.so using the source from a recent
sane-git, and replaced the installed lib/libsane-pixma.so.1.0.27 file in
the currently installed sane (backends) version 1.0.27-1.

not sure how much help i can be, please feel free to contact me via
email.

 steve




-- 
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] Lexmark CX510de printer / scanner

[Pierre THOMAS]

  
  
Bonjour,
  
  When I use xane with
my HP Scanjet G4050 scanner, it is possible to define a frame (dot lines) in the
preview window
before scanning.
  
When I use xane with my Lexmark CX510de
scanner, it is impossible to select a frame in
the preview window (no
  dot lines), I
  am obliged to scan the
full image.
  How
can I solve this problem
?

 Regards,

Pierre

  


-- 
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] Offset problem

[Pierre THOMAS]

  
  
Bonjour,
  
  I use HP Scanjet G4050 scanner with
Mageia Linux 6 / xsane version 0.999.
When I select a frame in the preview
  window, the resulting image is
correct for a 100 dpi resolution.
For a 200 dpi resolution there is
  a negative vertical offset, I mean about 2 mm are
  missing at the bottom of the picture (about 2 mm added
  at the top).
  For 200, 400 and 600 dpi
resolution there is a positive offset, I mean about
2 mm are missing at the top of the image (about 2 mm
added at the bottom)

What can I do to solve this
  problem which is very annoying. I do
  not want to have to reboot to Windows ...
  
  When I use the scanner
with Windows (in the same PC), with the HP
software or with the Windows scanning
software the result is correct.
  
  Regards,

Pierre

  


-- 
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] Adding support for scanner

[John Oliver]

I have a Canon imageCLASS MF416dw that does not appear to be supported
by sane.  How can we get it added?  I'm happy to do whatever legwork I
can.

-- 
***
* John Oliver, RHCE, LFCS http://www.john-oliver.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] What does basic support mean on the supported devices page for Plustek Opticbook 3600?

[Alex ARNAUD]

Le 09/04/2018 à 14:50, Olaf Meeuwissen a écrit :

The meaning of "basic" and other status classifiers are explained in the
Legend at the bottom of the page.  There's a link near the top, BTW.


Thank you very much.


for the latest information.  FWIW, the support status of the scanner you
mentioned has *not* changed.


What is the reason that make a device support to basic? The lack of time 
or the lack of documentation? In another word, if I tell to my user that 
his scanner works, if some feature is missing, could we collaborate 
together to implement them or is it impossible?


Best regards,
Alex.

--
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] What does basic support mean on the supported devices page for Plustek Opticbook 3600?

[Olaf Meeuwissen]

Hi Alex,

Alex ARNAUD writes:

> Hello all,
>
> I'm trying to help a visual-impaired person that wants to switch to
> GNU/Linux.
>
> He has a Plustek Opticbook 3600 and I found on this page:
> https://www.chiark.greenend.org.uk/doc/libsane/supported.html that the
> support of this device is noted as basic but honestly I don't understand
> what this mean.

The meaning of "basic" and other status classifiers are explained in the
Legend at the bottom of the page.  There's a link near the top, BTW.

> What does basic support for such device mean ?

  basic means it works at least in the most important modes but quality
  is not perfect.

> Is the page I've found correct to check if an hardware is compatible
> with Sane?

The page is not wrong but a bit out-of-date.  Have a look at

  https://sane-project.org/sane-backends.html

for the latest information.  FWIW, the support status of the scanner you
mentioned has *not* changed.

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

[sane-devel] What does basic support mean on the supported devices page for Plustek Opticbook 3600?

[Alex ARNAUD]

Hello all,

I'm trying to help a visual-impaired person that wants to switch to 
GNU/Linux.


He has a Plustek Opticbook 3600 and I found on this page: 
https://www.chiark.greenend.org.uk/doc/libsane/supported.html that the 
support of this device is noted as basic but honestly I don't understand 
what this mean.


What does basic support for such device mean ?

Is the page I've found correct to check if an hardware is compatible 
with Sane?


Best regards.
--
Alex ARNAUD
Visual-Impairment Project Manager
Hypra - "Humanizing technology"

--
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] Scan with Canon i-SENSYS MF211

[gonzo-rapid-eye-movem...@web.de]

Hello there,

i want to get the scanner of my Canon i-SENSYS MF 211 running. My OS is
ubuntu release 16.04. With simple scan the device starts to scan but
cancels in the middle of the process.

I read on sane-project.org that i shall use the sane-pixma.5 backend
(http://www.sane-project.org/man/sane-pixma.5.html). But I just don't
have the vaguest notion of how to make this work.

Can anybody help me? Thanks a lot.

Best

Torte



-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] Canon Lide 90 support

[Andre Wagner]

On Tue, Apr 3, 2018 at 10:24 PM,   wrote:






Hi,






I' m just switch a PC system from Windows to Linux including an old Canon Lide 
90 Scanner. I saw in Tour mailing list an old thread from 2008. Guillaume 
Gastebois and Pierre Willenbrock started at this time the development but did 
not finished it. I want to start a new attempt but all external links are in 
meanwhile invalid, so i got no base to start. Can somebody provide my the code 
written so far?






Thank you in advance














I actually also have a LiDE 90 I bought cheaply just to help development 
several years ago, but the hurdle was too much for me back then.






It would be nice to have another try though, so I will see if I can check out 
the git code and have a look to see the current status of the genesys backend.






Best regards,






Gernot Hassenpflug









Hi Gernot,
I also did so research on latest git version of sane backends. It seems that 
their code wasn't merged at all. Only a few snippets for an old thread 
(http://sane.10972.n7.nabble.com/Canon-LiDE-90-td11628.html) are available. 
They wrote that the GL842 chip used in the Canon Lide 90 is almost the same 
like then GL841 chip used in Canon Lide 35 and other older Canon Lide Models. 
As motor they assume it is the same like the motor in Canon LIDE 35, the analog 
frontend seams to be a Wolfson WM8192 (extracted from GL842 datasheet) or 
compatible. They assumed  CIS sensor used seams to be a compatible to the one 
used used in Canon Lide 35, but this model got only half of the resolution, so 
I think this assumption is perhaps not correct. I think Guillaume and Pierre 
developed an almost working code, but they have to give up on parametrisation 
of the AFE and black/white threshold, gamma correction, denoising etc. Since 
I'm working for an company which manufactures optical components I can use some 
test patterns for calibrating and can get perhaps some help of experts in 
optics.


Greetings,
André 


P.S.: I will do some USB traces with wireshark2 tomorrow, for figuring out the 
differences compared to the gl841 chip.



-- 
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] Canon Lide 220 problems?

[kamp000x]

Hi,


I have a new Canon Lide 220.


If I try to scan a 150 dpi grey file, the output is unreadable.

150dpi color is ok

300 dpi grey is ok


an example:

https://www.dropbox.com/sh/xmd5axjxn0n07z7/AADMt_fuQ98i6m3aZbSKPNbJa?dl=0


The scanner is doing on any scan a calibration (?) or something, by
driving a few centimeters backwards and forwards before scan.

Sometimes I am hearing some rattle or scratching while scanning, I think
the rail is running too far.


I am REALLY worried about this, but I did not notice these problems on
windows.

Are these known problems on sane?



Thanks in anticipation





Scanner

usb 1-2: New USB device found, idVendor=04a9, idProduct=190f
usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-2: Product: CanoScan
usb 1-2: Manufacturer: Canon

Xubuntu 17.10 64Bit

 dpkg -l | grep sane
ii  libsane-common   
1.0.27-1~experimental2ubuntu2.1  all  API library for
scanners -- documentation and support files
ii  libsane-hpaio:amd64  
3.17.7+repack0-3 amd64    HP SANE backend
for multi-function peripherals
ii  libsane1:amd64   
1.0.27-1~experimental2ubuntu2.1  amd64    API library for
scanners
ii  sane-utils   
1.0.27-1~experimental2ubuntu2.1  amd64    API library for
scanners -- utilities
ii  xsane
0.999-5ubuntu2   amd64    featureful
graphical frontend for SANE (Scanner Access Now Easy)
ii  xsane-common 
0.999-5ubuntu2   all  xsane architecture
independent files


-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] Canon Lide 90 support

[Gernot Hassenpflug]

On Tue, Apr 3, 2018 at 10:24 PM,  wrote:

> Hi,
> I' m just switch a PC system from Windows to Linux including an old Canon
> Lide 90 Scanner. I saw in Tour mailing list an old thread from 2008.
> Guillaume Gastebois and Pierre Willenbrock started at this time the
> development but did not finished it. I want to start a new attempt but all
> external links are in meanwhile invalid, so i got no base to start. Can
> somebody provide my the code written so far?
> Thank you in advance
>

I actually also have a LiDE 90 I bought cheaply just to help development
several years ago, but the hurdle was too much for me back then.
It would be nice to have another try though, so I will see if I can check
out the git code and have a look to see the current status of the genesys
backend.
Best 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

[sane-devel] Canon Lide 90 support

[wagnerandre85]

Hi,
I' m just switch a PC system from Windows to Linux including an old Canon Lide 
90 Scanner. I saw in Tour mailing list an old thread from 2008. Guillaume 
Gastebois and Pierre Willenbrock started at this time the development but did 
not finished it. I want to start a new attempt but all external links are in 
meanwhile invalid, so i got no base to start. Can somebody provide my the code 
written so far?
Thank you in advance
-- 
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] Canoscan Lide scanners are broken using sane-backends_1.0.27

[Alec Bickerton]

Hi,

Could somebody here provide an update for the bug #315752 "Sane 1.0.27 breaks
canoscan lide 100"

Ubuntu is also tracking the same issue here :
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1731459

As described in the above link, the culprit appears to be patch below, when the
change is reverted the issue is resolved.

https://alioth.debian.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=sane/sane-backends.git;a=commitdiff;h=bd0b0cd218504868f32962a5558449956c8ce242

Can anyone comment?

Regards,
Alec

-- 
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] gscan2pdf v2.0.3 released

[Jeff]

gscan2pdf - A GUI to produce a multipage PDF or DjVu from a scan.

http://gscan2pdf.sourceforge.net/

Five clicks are required to scan several pages and then save all or
a selection as a PDF or DjVu file, including metadata if required.

gscan2pdf can control regular or sheet-fed (ADF) scanners with SANE via
libimage-sane-perl, scanimage or scanadf, and can scan multiple pages at
once. It presents a thumbnail view of scanned pages, and permits simple
operations such as cropping, rotating and deleting pages.

OCR can be used to recognise text in the scans, and the output
embedded in the PDF or DjVu.

PDF conversion is done by PDF::API2.

The resulting document may be saved as a PDF, DjVu, multipage TIFF file,
or single page image file.

Changelog for 2.0.3:
* Always update image viewer if page selection changes
  Closes Debian bug #893026 (Preview pane does not update)
* Fixed manually typing date in metadata dialog (again)
  Closes Debian bug #893024 (Manual entry into UI date widget is broken)
* If image is zoomed to fit viewer, update zoom when the size of the
  viewer changes
* Update cursor depending on selected tool and position
* Build corrupt session file by hand rather than storing binary file
  that is not universally compatible. Closes bug #293
  (t/175_open_session2.t fails on i686: Long integer size is not
  compatible)
* Convert all scans to PNG to allow tesseract to extract resolution
* Ignore invalid options in profile
* Ignore options in profile that are already within tolerance
* Update to Hungarian translation (thanks to csola)



signature.asc
Description: OpenPGP digital signature
-- 
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] test backend

[Jeff]

I know about the test backend, and it is very useful.

However, it cannot cover every combination of option type/reload that is
out in the wild.

I often have to spend hours mocking up a backend from a log file to be
able to reproduce a bug in gscan2pdf, in order then to be able to fix it.

It would be really useful to have a SANE option to test a real backend
without the scanner being present. i.e. instead of calling
sane_device_open, to be able to call sane_device_mock_open or similar,
which would still allow sane_set_option, etc., but would not try to pass
the options to the hardware.

Unfortunately, I assume that to implement something like this, every
backend would have to be changed to separate out the hardware calls.

Would anyone else find something like this useful?

Does anyone have any better ideas for supporting hardware for which
there is no access?

Regards

Jeff



signature.asc
Description: OpenPGP digital signature
-- 
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 MF237w ADF

[Louis Lagendijk]

On Wed, 2018-03-28 at 11:28 +, Алтымышев Атилла wrote:
>  Hello!
> Please, i need help.
> We are using Canon MF237w MFP in our organization. We have installed
> Linux Mint 17.3, when i scan on glass its find. But when im using
> ADF, First page going scan, but the second one is stopping. 
> 
> There is simple-scan debug.
> I think that sane losing connect to the MFP when trying scan second
> page.
> May be i need to configure sane-backends? (pixma.conf)
> 
> Best regards, Atilla Altymyshev.
Looking at the logfile you seem to be connected over IP (Wifi?). Does
the scanning work over USB?

/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] Canon MF237w ADF

[Алтымышев Атилла]

Hello!
Please, i need help.
We are using Canon MF237w MFP in our organization. We have installed Linux Mint 
17.3, when i scan on glass its find. But when im using ADF, First page going 
scan, but the second one is stopping. 
There is simple-scan debug.
I think that sane losing connect to the MFP when trying scan second page.
May be i need to configure sane-backends? (pixma.conf)
Best regards, Atilla Altymyshev.


sane_debug
Description: Binary data
-- 
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] Canon D550 imageCLASS

[Steve Longerbeam]

Hi all,

I see that the libsane pixma backend supports the scanner on the
Canon imageCLASS D530.

I'm attempting to get scanning to work on the imageCLASS D550.
From scant specs on Canon's website, the D530 looks similar to the
D550, except that the D550 supports ADF.

After building sane with the following (probably naive) patch to
pixma backend:

$ git diff
diff --git a/backend/pixma_imageclass.c b/backend/pixma_imageclass.c
index 374259e..17b660c 100644
--- a/backend/pixma_imageclass.c
+++ b/backend/pixma_imageclass.c
@@ -98,6 +98,7 @@
 #define IR1133_PID 0x2742
 #define MF5900_PID 0x2743
 #define D530_PID   0x2775
+#define D550_PID   0x2738
 #define MF8500_PID 0x277a
 #define MF6100_PID 0x278e
 #define MF820_PID  0x27a6
@@ -930,6 +931,7 @@ const pixma_config_t pixma_iclass_devices[] = {
   DEV ("Canon i-SENSYS MF8200C Series", "MF8200C", MF8200_PID, 600, 
300, 640, 1050, PIXMA_CAP_ADF),
   DEV ("Canon i-SENSYS MF8300 Series", "MF8300", MF8300_PID, 600, 0, 
640, 1050, PIXMA_CAP_ADF),

   DEV ("Canon imageCLASS D530", "D530", D530_PID, 600, 0, 640, 877, 0),
+  DEV ("Canon imageCLASS D550", "D550", D550_PID, 600, 0, 640, 877, 
PIXMA_CAP_ADF),

   /* FIXME: the following capabilities all need updating/verifying */
   DEV ("Canon imageCLASS MF5630", "MF5630", MF5630_PID, 600, 0, 640, 
877, PIXMA_CAP_ADF),
   DEV ("Canon laserBase MF5650", "MF5650", MF5650_PID, 600, 0, 640, 
877, PIXMA_CAP_ADF),


I can see the scanner is detected:

$ scanimage -L
device `pixma:04A92738_1116D3300178' is a CANON Canon imageCLASS D550 
multi-function peripheral



But actual scanning is failing:

$ sudo scanimage -v > image.pnm
scanimage: scanning image of size 640x877 pixels at 24 bits/pixel
scanimage: acquiring RGB frame
scanimage: min/max graylevel value = 255/0
scanimage: sane_read: Device busy


Does anyone know more about the differences between the D530 and D550? Or
other ideas to get the D550 working?

Thanks!
Steve


--
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] Canon D550 imageCLASS

[Steve Longerbeam]

Hi all,

I see that the libsane pixma backend supports the scanner on the
Canon imageCLASS D530.

I'm attempting to get scanning to work on the imageCLASS D550.
From scant specs on Canon's website, the D530 looks similar to the
D550, except that the D550 supports ADF.

After building sane with the following (probably naive) patch to
pixma backend:

$ git diff
diff --git a/backend/pixma_imageclass.c b/backend/pixma_imageclass.c
index 374259e..17b660c 100644
--- a/backend/pixma_imageclass.c
+++ b/backend/pixma_imageclass.c
@@ -98,6 +98,7 @@
 #define IR1133_PID 0x2742
 #define MF5900_PID 0x2743
 #define D530_PID   0x2775
+#define D550_PID   0x2738
 #define MF8500_PID 0x277a
 #define MF6100_PID 0x278e
 #define MF820_PID  0x27a6
@@ -930,6 +931,7 @@ const pixma_config_t pixma_iclass_devices[] = {
   DEV ("Canon i-SENSYS MF8200C Series", "MF8200C", MF8200_PID, 600, 
300, 640, 1050, PIXMA_CAP_ADF),
   DEV ("Canon i-SENSYS MF8300 Series", "MF8300", MF8300_PID, 600, 0, 
640, 1050, PIXMA_CAP_ADF),

   DEV ("Canon imageCLASS D530", "D530", D530_PID, 600, 0, 640, 877, 0),
+  DEV ("Canon imageCLASS D550", "D550", D550_PID, 600, 0, 640, 877, 
PIXMA_CAP_ADF),

   /* FIXME: the following capabilities all need updating/verifying */
   DEV ("Canon imageCLASS MF5630", "MF5630", MF5630_PID, 600, 0, 640, 
877, PIXMA_CAP_ADF),
   DEV ("Canon laserBase MF5650", "MF5650", MF5650_PID, 600, 0, 640, 
877, PIXMA_CAP_ADF),


I can see the scanner is detected:

$ scanimage -L
device `pixma:04A92738_1116D3300178' is a CANON Canon imageCLASS D550 
multi-function peripheral



But actual scanning is failing:

$ sudo scanimage -v > image.pnm
scanimage: scanning image of size 640x877 pixels at 24 bits/pixel
scanimage: acquiring RGB frame
scanimage: min/max graylevel value = 255/0
scanimage: sane_read: Device busy


Does anyone know more about the differences between the D530 and D550? Or
other ideas to get the D550 working?

Thanks!
Steve



--
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] gscan2pdf v2.0.2 released

[Jeff]

gscan2pdf - A GUI to produce a multipage PDF or DjVu from a scan.

http://gscan2pdf.sourceforge.net/

Five clicks are required to scan several pages and then save all or
a selection as a PDF or DjVu file, including metadata if required.

gscan2pdf can control regular or sheet-fed (ADF) scanners with SANE via
libimage-sane-perl, scanimage or scanadf, and can scan multiple pages at
once. It presents a thumbnail view of scanned pages, and permits simple
operations such as cropping, rotating and deleting pages.

OCR can be used to recognise text in the scans, and the output
embedded in the PDF or DjVu.

PDF conversion is done by PDF::API2.

The resulting document may be saved as a PDF, DjVu, multipage TIFF file,
or single page image file.

Changelog for 2.0.2:
* Clear view if no page selected
* Change boolean scan options to use switch instead of checkbox widget
* Fixed manually typing date in metadata dialog.
  Closes Debian bug #893024
  (Manual entry into UI date widget is broken)
* Take colours for image viewer from theme. Closes Debian bug #893025
  (White UI background makes page borders disappear)
* Support Glib::Object::Introspection < 0.043



signature.asc
Description: OpenPGP digital signature
-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] [janitorial] Alioth Tracker Item → GitLab Issue

[Olaf Meeuwissen]

Hi all,

A couple of days ago on sane-devel, I wrote:

> Today Alioth Tracker Item #315943 was submitted.  We now have 1583 bugs
> and 53 feature requests registered at Alioth.  About a quarter of the
> bugs and half of the feature requests is still open.  When Alioth gets
> discontinued (sometime May 2018 for all I know) *all* that information
> will become inaccessible.
>
> I have been looking[1] at transferring these Tracker Items to GitLab
> issues but things on the Alioth side do not look easy (see the issue
> for details).  Currently, I am looking at scraping Alioth for all of
> the information on our Tracker Items and use that to create issues on
> GitLab.  I haven't made up my mind yet about whether to use a special
> "tracker-items" project for that or try to create the issues on the
> right project, i.e. one of backends, frontends or website.  Whichever
> way I decide, issues can be moved between projects on GitLab anyway so
> it's not such a big deal.
>
>  [1]: https://gitlab.com/sane-project/ops/issues/10

I've been able to pull all but two of the Tracker Items we have at
Alioth with the code I pushed to

  https://gitlab.com/sane-project/tracker-migration

The two issues that I have not been able to pull (so far) are both on
the Bugs tracker (310605 and 311568).  For some reason the connection
resets.

Anyway, I have HTML pages and attachments for all 1634 other items.
Next on the agenda is figuring out how to get this on GitLab ;-)

Oh, I'll be monitoring the Alioth Trackers for changes every now and
then.  There's no way to make them read-only :-(

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] Martin passed away

[m. allan noah]

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

allan

On Sat, Mar 24, 2018 at 5:33 AM, Martin Kho  wrote:
> With deep sadness, I have to inform you that my brother Martin has passed away
> last Saturday. Most of the time, he enjoyed working with you. Keep up the good
> work,
> Rob
>
>
>
> --
> sane-devel mailing list: sane-devel@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>  to sane-devel-requ...@lists.alioth.debian.org



-- 
"well, I stand up next to a mountain- and I chop it down with the edge
of my hand"

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] Martin passed away

[Gernot Hassenpflug]

On Sat, Mar 24, 2018 at 6:33 PM, Martin Kho  wrote:

> With deep sadness, I have to inform you that my brother Martin has passed
> away
> last Saturday. Most of the time, he enjoyed working with you. Keep up the
> good
> work,
> Rob
>

I'm very sorry to hear that. My sincere condolences on your loss Rob.
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

[sane-devel] Martin passed away

[Martin Kho]

With deep sadness, I have to inform you that my brother Martin has passed away 
last Saturday. Most of the time, he enjoyed working with you. Keep up the good 
work,
Rob



-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] Alioth deprecation

[Olaf Meeuwissen]

Hi Laura, list,

Gerhard Jäger writes:

> Dear Laura,
>
> Thank you for the information and thanks to Olaf we're already in the
> process of moving to gitlab: https://gitlab.com/sane-project
>
> Although not all issues we have with the movement are solved, the
> project is on a good way.

And just how good you can see in the burndown chart and issue lists at

  https://gitlab.com/sane-project/ops/milestones/1

The main issue we still have is with issues, pun intended.  Migrating
our Alioth Tracker Items[1] has turned out to be a bit cumbersome but
I'm making good progress with a website scraper to at least fetch all
Tracker Item content before Alioth goes off-line.

 [1]: https://gitlab.com/sane-project/ops/issues/10

Allan has requested our mailing lists to be migrated and I rsync the
project's home directory just in case.

> On 20.03.2018 at 09:38 Laura Arjona Reina wrote:
>> Hello SANE developers
>>
>> (Please CC me, I'm not subscribed).
>>
>> Thanks for working in making scanning easy!
>>
>> Yesterday I happened to be in the need of downloading and compiling
>> sane-backends in a Debian box, and realised that you (upstream
>> project) use Debian's Alioth for the development management (repos,
>> mailing lists, bug tracker, maybe more).

For what it's worth, I did update our website to point to the GitLab
repositories and issues.  If you find anything wrong in that area,
please submit an issue at

  https://gitlab.com/sane-project/website/issues

Anyway, thanks for letting us know!  And 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] Alioth deprecation

[Gerhard Jäger]

Dear Laura,

Thank you for the information and thanks to Olaf we're already in the process of
moving to gitlab: https://gitlab.com/sane-project

Although not all issues we have with the movement are solved, the project is on
a good way.

Best regards,
  Gerhard

On 20.03.2018 at 09:38 Laura Arjona Reina wrote:

Hello SANE developers

(Please CC me, I'm not subscribed).

Thanks for working in making scanning easy!

Yesterday I happened to be in the need of downloading and compiling
sane-backends in a Debian box, and realised that you (upstream project) use
Debian's Alioth for the development management (repos, mailing lists, bug
tracker, maybe more).

I don't know if you are aware that Alioth is deprecated, it will be shutdown in
May 2018 probably, and all the Debian contributors and upstream projects that
use its infrastructure should consider migrating the different services to
another place.

Please have a look at this wiki page:

https://wiki.debian.org/Alioth/

in order to see the alternatives for the different components of Alioth  and
take the corresponding measures.

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

[sane-devel] problem with Canon scanner Canoscan Lide20 under MacOSX 10.11

[oli dobolli]

having problem running Canon scanner Canoscan Lide20 under Mac OSX 10.11 El
Capitan.
scanimage recognises it, but wont work with output, says

scanimage: no SANE devices found

Vuescan software recognises it and scans ok.

here are some logs...

olivers-MacBook-Pro:~ oli$ sane-find-scanner

found USB scanner (vendor=0x05ac [Apple Inc.], product=0x821a [Bluetooth
USB Host Controller]) at libusb:002:007-05ac-821a-ff-01

found USB scanner (vendor=0x04a9 [Canon], product=0x220d [CanoScan],
chip=LM9832/3) at libusb:002:005-04a9-220d-ff-00

  # Your USB scanner was (probably) detected. It may or may not be
supported by

  # SANE. Try scanimage -L and read the backend's manpage.


olivers-MacBook-Pro:~ oli$ scanimage -L

device `plustek:libusb:002:005-04a9-220d-ff-00' is a Canon CanoScan
N670U/N676U/LiDE20 flatbed scanner


olivers-MacBook-Pro:~ oli$ scanimage -vvv > test.pnm

scanimage: no SANE devices found

Calling sane_exit

scanimage: finished

and here is the log debug file

olivers-MacBook-Pro:~ oli$ SANE_DEBUG_PLUSTEK=5 scanimage > test.pnm 2>
logsane.txt

[sanei_debug] Setting debug level of plustek to 5.
[plustek] Plustek backend V0.52-12, part of sane-backends 1.0.25
[plustek] Retrieving all supported and conntected devices
[plustek] Available and supported devices:
[plustek] Device: >libusb:002:005-04a9-220d-ff-00< - 0x04a9x0x220d
[plustek] usbDev_open(auto,) - 0x7fb5c1f01160
[plustek] Vendor ID=0x04A9, Product ID=0x220D
[plustek] usbio_DetectLM983x
[plustek] usbio_DetectLM983x: found LM9832/3
[plustek] Detected vendor & product ID: 0x04A9-0x220D
[plustek] Device description for >0x04A9-0x220D< found.
[plustek] usb_initDev(41,0x04a9,-1)
[plustek] Device WAF  : 0x4002
[plustek] Transferrate: 100 Bytes/s
[plustek] Device Flags: 0x
[plustek] Vendor adjusted to: >Canon<
[plustek] LAMP-STATUS: 0x (off)
[plustek] RESETTING REGISTERS(-1) - 0x80
[plustek] MISC I/O after RESET: 0x66, 0x16, 0x91
[plustek] Calibration file-names set to:
[plustek] >/Users/oli/.sane/Canon_CanoScan_N670U_N676U_LiDE20-coarse.cal<
[plustek] >/Users/oli/.sane/Canon_CanoScan_N670U_N676U_LiDE20-fine.cal<
[plustek] usb_SetScanParameters()
[plustek] usb_GetMCLKDivider()
[plustek] usb_GetMCLKDiv()
[plustek] * PhyBytes   = 6
[plustek] * PhyLines   = 4
[plustek] * TotalBytes = 24
[plustek] * Scansteps=72 (9*1200/150)
[plustek] usb_SetScanParameters() done.
[plustek] usbDev_getCaps()
[plustek] Scanner information:
[plustek] Vendor : Canon
[plustek] Model  : CanoScan N670U/N676U/LiDE20
[plustek] Flags  : 0x
[plustek] drvclose()
[plustek] usbDev_stopScan()
[plustek] usbDev_ScanEnd(), start=0, park=0
[plustek] usbDev_close()
[plustek] Presetting Gamma tables (len=4096)
[plustek] * Channel[0], gamma 2.000
[plustek] * Channel[1], gamma 2.000
[plustek] * Channel[2], gamma 2.000
[plustek] * Channel[3], gamma 2.000
[plustek] --
[plustek] usbDev_open(libusb:002:005-04a9-220d-ff-00,) - 0x0
[plustek] Vendor ID=0x04A9, Product ID=0x220D
[plustek] usbio_DetectLM983x
[plustek]  * could not read version register!
[plustek] sane_start: open failed: 25
scanimage: sane_start: Error during device I/O
[plustek] Shutdown called (dev->fd=-1, libusb:002:005-04a9-220d-ff-00)
[plustek] Function ignored!


thank you for your time.
-- 
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] Alioth deprecation

[Laura Arjona Reina]

Hello SANE developers

(Please CC me, I'm not subscribed).

Thanks for working in making scanning easy!

Yesterday I happened to be in the need of downloading and compiling
sane-backends in a Debian box, and realised that you (upstream project) use
Debian's Alioth for the development management (repos, mailing lists, bug
tracker, maybe more).

I don't know if you are aware that Alioth is deprecated, it will be shutdown in
May 2018 probably, and all the Debian contributors and upstream projects that
use its infrastructure should consider migrating the different services to
another place.

Please have a look at this wiki page:

https://wiki.debian.org/Alioth/

in order to see the alternatives for the different components of Alioth  and
take the corresponding measures.

Best regards
-- 
Laura Arjona Reina
https://wiki.debian.org/LauraArjona

-- 
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] Who do I submit a How To for saned?

[ToddAndMargo]

On 03/22/2018 11:54 AM, John Oliver wrote:

Err... if anything, it's the opposite.  Fedora is the FOSS upstream for
RHEL.  It has a very short, bleeding-edge lifecycle of about six months.
RHEL and CentOS get long in the tooth, sure, but what you can expect
from them is anything but "riddled with bugs and incompatibilities".



I was with RHEL clones since CentOS 5 all the way to Scientific
Linux 7.5.  My choice was based on all the above stuff you stated.

RHEL is "minimally" maintained.  (No flame wars here, I said
"minimally" not "NOT" maintained.)  In order to maintain stability,
RHEL is deliberately "out-of-date".  This means the OS is locked
down and frozen in place.  "Supposedly" this is to keep instabilities
from creeping in.

What sounds wonderful is not always the reality.  I learned this
the EXTREME HARD WAY.  Bugs that are reported are NOT fixed, or
if they are fixed it takes up to SIX YEARS.

The two straws that broke my back were the bug in Osmo
were my business' contacts got wiped when I shutdown.
Mind you Osmo had fixed this, but could do nothing for
me as Scientific Linux was so miserably out of date.

And the other one was that RHEL and Friends no longer
supports modern motherboards (bug 1353423) and has
no intention of remedying the issue, even though
Supermicro has a program to provide Red Hat with all
the hardware they need.  1353423 cost me over $1000
in free consulting to figure out.  I had even tested
the motherboard with a Live USB before install natively.
"Pissed" does not begin to describe it!

Since all my customers are now on the more stable
Fedora servers do to 1353423, I ripped out Scientific
Linux and installed Fedora on my own machines so I
could match my customers.  I did this in December.  It
has been joy ever since to see all the improvements
and bug fixes in the various software package I run
in my business.  And Osmo no longer eats my business
contacts (good thing I am a backup whore).

And my USB2 is now four to five times faster (bugs
1333582, 1333583, 1224498).

So, in my experience, I do not recommend RHEL for anything
other than a set and forget appliance.  And you can
do that with any Linux by turning off the updates.

Now for a Fedora example, the above mentioned motherboard
that RHEL won't even run on (1353423) had a problem
rebooting and shutting down (bug 1537845).

Reported: 2018-01-23
Reported as resolved after a weeks testing: 2018-03-19

Beats the hell out of six years to NEVER.

Fedora is a Kaisen OS (constant improvement); RHEL is
by nature a non-kaisen OS.

RHEL is NOT more stable.  Fedora is a joy to use and work
on.  RHEL ALMOST DROVE ME INSANE !!!

The irony that RHEL could not fix all the various issues
with qemu-kvm because as RHEL was too out of date and kvm
being a Red Hat project is not lost on me (bug 1518387).




--
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] Who do I submit a How To for saned?

[John Oliver]

On Wed, Mar 21, 2018 at 11:56:13PM -0700, ToddAndMargo wrote:
> >>On Sat, Mar 10, 2018 at 4:49 PM, ToddAndMargo  
> RHEL is riddled with bugs and incompatibilities, so the HOWTO
> is specifically written for Fedora (where things work).  But,
> this is close enough to RHEL that you should be able to
> adapt it.  Basically, some of the back end rpms are rolled
> together in RHEL.  Systemd is the same.

Err... if anything, it's the opposite.  Fedora is the FOSS upstream for
RHEL.  It has a very short, bleeding-edge lifecycle of about six months.
RHEL and CentOS get long in the tooth, sure, but what you can expect
from them is anything but "riddled with bugs and incompatibilities".

-- 
***
* John Oliver, RHCE, LFCS http://www.john-oliver.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] Looking for help with scanner

[John Oliver]

On Sat, Mar 17, 2018 at 10:30:05PM +0100, Louis Lagendijk wrote:
> On Sat, 2018-03-17 at 11:20 -0700, John Oliver wrote:
> > > What does lsusb say for the scanner when connected over USB?
> > 
> > Haven't tried yet, I don't have a USB cable handy...
> Please contact the mailing list again and ask Rolf Bensch to have a
> look at the scanner: it is currently not supported. I guess that it
> should be added in the code. That is normally not that complicated. But
> Rolf does normally the management of the code, so he knows what look
> for. @Rolf Bensch: can you please have a look? @John, please find a USB
> cable as Rolf will want to do initial testing over USB

I tried with USB.  No dice :-(

Bus 002 Device 008: ID 04a9:27c0 Canon, Inc. 

I'm happy to do whatever I can to help get support added!

Thanks...

-- 
***
* John Oliver, RHCE, LFCS http://www.john-oliver.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] Who do I submit a How To for saned?

[ToddAndMargo]

On Sat, Mar 10, 2018 at 4:49 PM, ToddAndMargo > wrote:


Hi All,

I wrote up an very in depth How To on saned and Fedora.
It included all the annoying, missing steps you
get when your google how to do this.

Who would I submit it to get get in evaluated for
inclusion to Sane's How To's?

Many thanks,
-T


On 03/21/2018 07:47 PM, Steven Santos wrote:
I am about to install SANE on a fresh CENTOS 7 system.  Any chance I 
could get a copy of this howto?




RHEL is riddled with bugs and incompatibilities, so the HOWTO
is specifically written for Fedora (where things work).  But,
this is close enough to RHEL that you should be able to
adapt it.  Basically, some of the back end rpms are rolled
together in RHEL.  Systemd is the same.

Qoppa took the howto and posted it.  Fedora showed some interest, so
I will eventually posted it with Fedora too.  Other than you,
sane showed no interest.

Good luck!

https://kbpdfstudio.qoppa.com/how-to-set-up-your-scanner-to-work-with-sane-and-pdf-studio-under-fedora-27-linuxs-systemd/

-T


--
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] Alioth Tracker Item → GitLab Issue

[Olaf Meeuwissen]

Hi all,

I just pushed updates to the website that point people to submit issues
against our GitLab projects instead of creating Tracker Items on Alioth.

The GitLab issues have been configured with a wealth of labels:

 - backend/* for every SANE Project supported backend
 - frontend/* for every SANE Project "supported" frontend (that's quoted
   because, sadly?, sane-frontends it all but dead) but please note that
   the scanimage and saned frontends are part of sane-backends (huh?!?)
 - connection/* for network, usb, scsi and parallel connections

In addition there are labels for bugs, feature requests, documentation
and translation issues, build issues, security issues (tick the checkbox
to keep these confidential!), sanei, portability and tools issues,
issues that have a patches and issues needing feedback.  These last two
are colour coordinated with the Doing and To Do labels that are used on
the board(s).  Actually, I have tried to colour coordinate most of the
labels that I think are sort of in the same category.  Of course, any
issue can have more than one label.

# I still would like to add descriptions to the current labels but I
# think that can wait for now.  There's more important stuff to take
# care off!  Read on.

Today Alioth Tracker Item #315943 was submitted.  We now have 1583 bugs
and 53 feature requests registered at Alioth.  About a quarter of the
bugs and half of the feature requests is still open.  When Alioth gets
discontinued (sometime May 2018 for all I know) *all* that information
will become inaccessible.

I have been looking[1] at transferring these Tracker Items to GitLab
issues but things on the Alioth side do not look easy (see the issue
for details).  Currently, I am looking at scraping Alioth for all of
the information on our Tracker Items and use that to create issues on
GitLab.  I haven't made up my mind yet about whether to use a special
"tracker-items" project for that or try to create the issues on the
right project, i.e. one of backends, frontends or website.  Whichever
way I decide, issues can be moved between projects on GitLab anyway so
it's not such a big deal.

 [1]: https://gitlab.com/sane-project/ops/issues/10

# Tomorrow I have the day off, Vernal Equinox Day is a national holiday
# in Japan!, so I hope to make some headway in scraping Alioth.

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] Help Please with Nikon Super Coolscan 4000 ED

[abel deuring]

Am 06.03.2018 um 23:34 schrieb Bob Louden:
> Dear mailing list.  Please excuse me if I am not using this mailing list
> properly.
> 
> I created a request for help a few days ago in the Linux Mint Hardware
> forum but have not had any luck with responses.  
> 
> I have this very nice, albeit old, scanner that I cannot get to work --
> though I feel like I am very close to having it work.  Alas, I am on the
> brink of giving up on it.  I also have this not-as-good Plustek scanner
> that I've started messing with and it was from searching for help with
> it that I found your mailing list.
> 
> Anyway, if there is anyone out there who might be able to help me, here
> is a link to my Linux Mint forum
> post:  https://forums.linuxmint.com/viewtopic.php?f=51=264978
> 
> Please feel free to respond to me via either email or in the forum.

Bob,

after reading the conversation on the Mint forum it seems to me that the
host machine and the scanner have a, let's say, very serious
communication problem: The excerpt from syslog after "UPDATE2" in your
first post there shows the message "scsi host6: scsi scan: INQUIRY
result too short (7), using 36".

The "inquiry" command is the first command sent by a SCSI host to a SCSI
device when the host detects a new SCSI device. (I know, the scanner is
connected via Firewire, not via a physical SCSI interface, but Firewire
uses the SCSI commands for several device types.)

When a SCSI device receives this comamnd, it should send back a
description of itself: What type of device (disk, optical drive, tape
drive, scanner etc) it is, its vendor vendor name, product name and
other stuff. A SCSI device must send at least 36 bytes to the host
computer, and the content of these 36 bytes is well standardized.

You can find a description of the inquiry command for example on pages
90-99 of this file:

https://www.seagate.com/staticfiles/support/disc/manuals/scsi/100293068a.pdf

(it is hard to find a "generic" description of the SCSI commands, so I
just opened the first result of a Google search for "scsi protocol
specification". As already said, the first 36 bytes inquiry command are
well standardized, so it does not matter much that this PDF describes
the wrong device type.)

The type of the device is described in bits 0-4 of byte 0 in the inquiry
data (page 92 of the aforementioned PDF) – and, according to syslog,
they say that the device is a disk which is obviously wrong. Another
oddity in the syslog messages: The scanner has apparently sent only 7
bytes, not the expected 36 bytes. But it seems that the product name
("LS-4000 ED"), stored in bytes 16-31 of the inquiry data, has been sent
to the host anyway.

In other words: The communication between the computer and the scanner
is really messed up. Hence I think that the idea to replace the firewire
controller and driver chips (as you mention in the forum under "NEWS
FLASH") is technically reasonable – but I also understand that doing
this on a "commercial basis" is somewhat unreasonable.

But before you consider this (despite the costs...) you should
double-check that the Firewire interface of your computer works: Try to
connect another Firewire device to the computer and check if it works
better. Similary, you could check if the scanner shows similar symptoms
when it is connected to another computer. Since we suspect a hardware
problem, you could try any other machine that runs under Linux, MacOS or
Windows.

Abel

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

[Louis Lagendijk]

On Sat, 2018-03-17 at 18:51 +, Patrick Roncagliolo wrote:
> Regarding ADF support, I can tell you a difference between two
> situations:
> 
> ADF empty: backend hangs a while, than I can read "scanimage:
> sane_read: Document feeder out of documents"
> ADF with sheets loaded: operation hats instantaneously, and I can
> read "scanimage: sane_read: Operation was cancelled"
> 
> I can send you some files (scanimage logs and wireshark dumps) if you
> want.
Is this over USB as well? If so, it the backend proper. You may want to
talk to Rolf again for that

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?

[Louis Lagendijk]

On Sat, 2018-03-17 at 18:36 +, Patrick Roncagliolo wrote:
> I have empty iptables. By reading manpages, I found that /etc/sane.d
> was not in the $SANE_CONFIG_DIR.
> I put there "bjnp://192.168.1.5", lanched scanimage -L and it finally
> worked.
> 
> One question/curiosity: scangearmp2 (Canon proprietary scan tool for
> linux) sends a discovery probe on port 8611 instead of 8612, and
> behaves differently from the pixma backend. Is there some reverse-
> engineered documentation about the BJNP messages, types, codes? I
> imagine so, given that pixma-backend exists, but I had no success in
> finding it.
> 
Read the source code... NO there was no documentation whatsoever. I
reverse engineered the protocol from PCAP traces from the Windows
driver. But that is only part of the story: the bjnp protocol just
translates the USB protocol to run over TCP/IP. So the actual
processing is still done by the same backend code as used for USB
scanning. Internally in the bjnp code I map the sanner name to the USB-
id as that is used a lot in the backend...
I reverse engineered the protocol using the MP970 I had at that time,
and it still works for recent scanners that use BJNP, even though I
have seen some variations used by Canon (later Windows drivers for the
scanner use more TCP and less UDP. But that may also have been the case
with the BJNP printing part. And if it works, don't touch it...

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] Looking for help with scanner

[Louis Lagendijk]

On Sat, 2018-03-17 at 11:20 -0700, John Oliver wrote:
> On Sat, Mar 17, 2018 at 02:59:09PM +0100, Louis Lagendijk wrote:
> > On Fri, 2018-03-16 at 10:07 -0700, John Oliver wrote:
> > > On Ubuntu 16.04.04, using "Simple Scan" which is, apparently,
> > > SANE.
> > > 
> > > I bought a Canon imageCLASS MF416dw and had to jump through some
> > > hoops
> > > to get it printing.  It's on the network, wired, local
> > > subnet.  I'm
> > > using the PIXMA backend.
> > > 
> > > 
> > > _scanner._tcp.local. [4m15s] PTR Canon MF410
> > > Series._scanner._tcp.local.
> > > ar: Canone585ce.local. (Cache flush) [4m15s] A 192.168.0.20,
> > > Canon
> > > MF410
> > > Series._scanner._tcp.local. (Cache flush) [4m15s] SRV
> > > Canone585ce.local.:8610 0 0, Canon MF410
> > > Series._scanner._tcp.local.
> > > (Cache flush) [4m15s] TXT "txtvers=1" "note="
> > > "adminurl=http://Canone585ce.local/airprint.html; "ty=Canon MF410
> > > Series" "UUID=f48139e585ce" "mfg=Canon" "mdl=MF410 Series"


Sol this is how the device reports itself: Canon MF410 Series
This deviates more from the type number on the label than normal, just
something to take into account when adding the scanner in the code

> > > 
> > Did you try the scanner over USB? If that works we can continue
> > with
> > the network scanning. Network just adds some additional complexity,
> > so
> > lets first ensure that the scanner works over USB.
> > A quick grep on the source code seems to suggest that it is not yet
> > supported.
Well it reports with a different string, so a grep probably would not
have found it anyhow, but it is currently not suported for all I can
see
> > What does lsusb say for the scanner when connected over USB?
> 
> Haven't tried yet, I don't have a USB cable handy...
Please contact the mailing list again and ask Rolf Bensch to have a
look at the scanner: it is currently not supported. I guess that it
should be added in the code. That is normally not that complicated. But
Rolf does normally the management of the code, so he knows what look
for. @Rolf Bensch: can you please have a look? @John, please find a USB
cable as Rolf will want to do initial testing over USB
> 
> > You could also try:
> > export SANE_DEBUG_PIXMA=20
> > export SANE_DEBUG_BJNP=20
> > scanimage -L 2> log
> > and mail me the logfile
> > See espacially the lines starting with 
> > [pixma] Scanner model
> 
> Attached.
> 
And as expected: the scanner is not yet recognized. Lets hope that Rolf
can have a look...
> 
> What does itt ake to get support added?  I'm happy to do some legwork

See above.

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] xsane 0.999

[Richard Ryniker]

Use "Get Preview", and xsane places a rectangular frame around what it
thinks is the relevant portion in the preview image.  The user can drag
the sides of this frame to what he prefers.  "Scan" then captures just
the area defined by this frame.

Every subsequent scan will use this frame, until the user changes it.

Otherwise, use a separate tool to manipulate images after they have been
scanned.  I find the ImageMagick "convert" command useful if I have
multiple images I wish to crop (or otherwise edit) in the same way.

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

[Patrick Roncagliolo]

Regarding ADF support, I can tell you a difference between two situations:

ADF empty: backend hangs a while, than I can read "scanimage: sane_read:
Document feeder out of documents"
ADF with sheets loaded: operation hats instantaneously, and I can read
"scanimage: sane_read: Operation was cancelled"

I can send you some files (scanimage logs and wireshark dumps) if you want.

Il giorno sab 17 mar 2018 alle ore 19:35 Patrick Roncagliolo <
ronca@gmail.com> ha scritto:

> I have empty iptables.
> By reading manpages, I found that /etc/sane.d was not in
> the $SANE_CONFIG_DIR.
> I put there "bjnp://192.168.1.5", lanched scanimage -L and it finally
> worked.
>
> One question/curiosity: scangearmp2 (Canon proprietary scan tool for
> linux) sends a discovery probe on port 8611 instead of 8612, and behaves
> differently from the pixma backend. Is there some reverse-engineered
> documentation about the BJNP messages, types, codes? I imagine so, given
> that pixma-backend exists, but I had no success in finding it.
>
>
>
> Il giorno sab 17 mar 2018 alle ore 14:47 Louis Lagendijk 
> ha scritto:
>
>> On Tue, 2018-03-13 at 21:17 +, Patrick Roncagliolo wrote:
>>
>> Hi,
>>
>> I tested pixma version 0.17.46 thru USB. It works.
>>
>> However, after updating from your PPa, I'm not able to discover my
>> printer on the network. pixma.conf seems to be ignored, no matter if I set
>> the IP and multiple port combinations (8610, 8611, 8612, but whit wireshark
>> I see only requests as broadcast on ports 8610 8612). What could have been
>> changed? Any hints about some dumb things that I can have forgotten since
>> last configuration?
>>
>> Il giorno dom 11 mar 2018 alle ore 12:26 Rolf Bensch <
>> r...@bensch-online.de> ha scritto:
>>
>> 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
>>
>>
>> I have an MB5050 myself and that works pretty well.
>> Can you please (in a shell) do:
>>
>> export SANE_DEBUG_BJNP=20
>> scanimage -L 2> log
>>
>> and mail the resulting log file?
>> Some of the most recent Canon scanners no longer support bjnp, butthe
>> MB2000 is as far as I know of the same generation as my MB5050, so I expect
>> bjnp till to be supported.
>>
>> Please check your firewall settings (see man sane-pixma) to be sure that
>> traffic does not get blocked. There should be no reason to modify the
>> pixma.conf file, unless you are on WIFI: ome users report problems oer WIFI.
>> See the bjnp-timeout settings in pixma.conf. A single line of
>> bjnp-timeout=5000
>> at the beginning of that file should in that case do the trick.
>> I decided against including that by default as it would cause long delays
>> for user using other backends
>>
>> BR, Loujis
>> --
>> sane-devel mailing list: sane-devel@lists.alioth.debian.org
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
>> Unsubscribe: Send mail with subject "unsubscribe your_password"
>>  to sane-devel-requ...@lists.alioth.debian.org
>
>
-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

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

[Patrick Roncagliolo]

I have empty iptables.
By reading manpages, I found that /etc/sane.d was not in
the $SANE_CONFIG_DIR.
I put there "bjnp://192.168.1.5", lanched scanimage -L and it finally
worked.

One question/curiosity: scangearmp2 (Canon proprietary scan tool for linux)
sends a discovery probe on port 8611 instead of 8612, and behaves
differently from the pixma backend. Is there some reverse-engineered
documentation about the BJNP messages, types, codes? I imagine so, given
that pixma-backend exists, but I had no success in finding it.



Il giorno sab 17 mar 2018 alle ore 14:47 Louis Lagendijk 
ha scritto:

> On Tue, 2018-03-13 at 21:17 +, Patrick Roncagliolo wrote:
>
> Hi,
>
> I tested pixma version 0.17.46 thru USB. It works.
>
> However, after updating from your PPa, I'm not able to discover my printer
> on the network. pixma.conf seems to be ignored, no matter if I set the IP
> and multiple port combinations (8610, 8611, 8612, but whit wireshark I see
> only requests as broadcast on ports 8610 8612). What could have been
> changed? Any hints about some dumb things that I can have forgotten since
> last configuration?
>
> Il giorno dom 11 mar 2018 alle ore 12:26 Rolf Bensch <
> r...@bensch-online.de> ha scritto:
>
> 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
>
>
> I have an MB5050 myself and that works pretty well.
> Can you please (in a shell) do:
>
> export SANE_DEBUG_BJNP=20
> scanimage -L 2> log
>
> and mail the resulting log file?
> Some of the most recent Canon scanners no longer support bjnp, butthe
> MB2000 is as far as I know of the same generation as my MB5050, so I expect
> bjnp till to be supported.
>
> Please check your firewall settings (see man sane-pixma) to be sure that
> traffic does not get blocked. There should be no reason to modify the
> pixma.conf file, unless you are on WIFI: ome users report problems oer WIFI.
> See the bjnp-timeout settings in pixma.conf. A single line of
> bjnp-timeout=5000
> at the beginning of that file should in that case do the trick.
> I decided against including that by default as it would cause long delays
> for user using other backends
>
> BR, Loujis
> --
> sane-devel mailing list: sane-devel@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>  to sane-devel-requ...@lists.alioth.debian.org
-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] sane-backends 1.0.27 skips my SnapScan e20 in USB "unconfigured" state (OK with 1.0.25)

[Oliver.Schwartz]

Dominque,

I’m the current maintainer of the SnapScan backend which supports the e20 in 
Sane. Unfortunately I don’t own a e20 myself and don’t have access to one. 
However, I’ve just tried sane-backends 1.0.27 on OS-X Sierra (homebrew) and 
Linux with my scanner (that also needs firmware upload) and found no problem. 
The scanner is detected by sane-find-scanner. On OS-X, homebrew installed 
libusb 1.0.21.

To debug the problem further it may be helpful to see what the backend itself 
reports. Can you please run 

SANE_DEBUG_SANEI_USB=255 sane-find-scanner 2>findscanner.log

and

SANE_DEBUG_SNAPSCAN=255 SANE_DEBUG_SANEI_USB=255 scanimage -L 2>scanimage.log

and send me the (compressed) log files (findscanner.log and scanimage.log)

Kind regards,

Oliver



-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] Looking for help with scanner

[Louis Lagendijk]

On Fri, 2018-03-16 at 10:07 -0700, John Oliver wrote:
> On Ubuntu 16.04.04, using "Simple Scan" which is, apparently, SANE.
> 
> I bought a Canon imageCLASS MF416dw and had to jump through some
> hoops
> to get it printing.  It's on the network, wired, local subnet.  I'm
> using the PIXMA backend.
> 
> joliver@blinky:~$ sudo nmap -sU -p 8610-8612 192.168.0.20
> 
> Starting Nmap 7.01 ( https://nmap.org ) at 2018-03-16 09:56 PDT
> Nmap scan report for 192.168.0.20
> Host is up (0.038s latency).
> PORT STATE SERVICE
> 8610/udp open|filtered unknown
> 8611/udp closedcanon-bjnp1
> 8612/udp closedcanon-bjnp2
> MAC Address: F4:81:39:E5:85:CE (Canon)
> 
> Nmap done: 1 IP address (1 host up) scanned in 1.74 seconds
> joliver@blinky:~$ sudo nmap -sT -p 8610-8612 192.168.0.20
> 
> Starting Nmap 7.01 ( https://nmap.org ) at 2018-03-16 09:56 PDT
> Nmap scan report for 192.168.0.20
> Host is up (0.0017s latency).
> PORT STATE  SERVICE
> 8610/tcp open   unknown
> 8611/tcp closed unknown
> 8612/tcp closed unknown
> MAC Address: F4:81:39:E5:85:CE (Canon)
> 
> Nmap done: 1 IP address (1 host up) scanned in 0.32 seconds
> 
> 
> So, I tried mfnp://192.168.0.20 but simple-scan quickly bombs out
> with
> "No scanners detected"  So I sniffed traffic while starting sane:
> 
> joliver@blinky:~$ sudo tcpdump -vvv host 192.168.0.20
> tcpdump: listening on wlp2s0, link-type EN10MB (Ethernet), capture
> size
> 262144 bytes
> 10:04:03.030738 IP (tos 0x0, ttl 64, id 41990, offset 0, flags [DF],
> proto UDP (17), length 44)
> 192.168.0.15.44468 > 192.168.0.20.8610: [udp sum ok] UDP, length
> 16
> 10:04:03.032672 IP (tos 0x0, ttl 64, id 6518, offset 0, flags [none],
> proto UDP (17), length 60)
> 192.168.0.20.8610 > 192.168.0.15.44468: [udp sum ok] UDP, length
> 32
> 10:04:03.032757 IP (tos 0x0, ttl 64, id 41991, offset 0, flags [DF],
> proto UDP (17), length 44)
> 192.168.0.15.48892 > 192.168.0.20.8610: [udp sum ok] UDP, length
> 16
> 10:04:03.036182 IP (tos 0x0, ttl 64, id 17032, offset 0, flags
> [none],
> proto UDP (17), length 126)
> 192.168.0.20.8610 > 192.168.0.15.48892: [udp sum ok] UDP, length
> 98
> 10:04:03.040416 IP (tos 0x0, ttl 64, id 23405, offset 0, flags
> [none],
> proto UDP (17), length 60)
> 192.168.0.20.8610 > 192.168.0.15.8612: [udp sum ok] UDP, length
> 32
> 10:04:03.050893 IP (tos 0x0, ttl 64, id 11420, offset 0, flags
> [none],
> proto UDP (17), length 60)
> 192.168.0.20.8610 > 192.168.0.15.8612: [udp sum ok] UDP, length
> 32
> 10:04:03.082441 IP (tos 0x0, ttl 64, id 41994, offset 0, flags [DF],
> proto UDP (17), length 44)
> 192.168.0.15.41346 > 192.168.0.20.8610: [udp sum ok] UDP, length
> 16
> 10:04:03.083924 IP (tos 0x0, ttl 64, id 7595, offset 0, flags [none],
> proto UDP (17), length 60)
> 192.168.0.20.8610 > 192.168.0.15.41346: [udp sum ok] UDP, length
> 32
> 10:04:03.104825 IP (tos 0x0, ttl 64, id 41998, offset 0, flags [DF],
> proto UDP (17), length 44)
> 192.168.0.15.42059 > 192.168.0.20.8610: [udp sum ok] UDP, length
> 16
> 10:04:03.106075 IP (tos 0x0, ttl 64, id 46684, offset 0, flags
> [none],
> proto UDP (17), length 60)
> 192.168.0.20.8610 > 192.168.0.15.42059: [udp sum ok] UDP, length
> 32
> 10:04:05.956867 IP (tos 0x0, ttl 255, id 7957, offset 0, flags
> [none],
> proto UDP (17), length 343)
> 192.168.0.20.mdns > 224.0.0.251.mdns: [udp sum ok] 0- [0q] 1/0/5
> _scanner._tcp.local. [4m15s] PTR Canon MF410
> Series._scanner._tcp.local.
> ar: Canone585ce.local. (Cache flush) [4m15s] A 192.168.0.20, Canon
> MF410
> Series._scanner._tcp.local. (Cache flush) [4m15s] SRV
> Canone585ce.local.:8610 0 0, Canon MF410 Series._scanner._tcp.local.
> (Cache flush) [4m15s] TXT "txtvers=1" "note="
> "adminurl=http://Canone585ce.local/airprint.html; "ty=Canon MF410
> Series" "UUID=f48139e585ce" "mfg=Canon" "mdl=MF410 Series"
> "scannerAvailable=0", Canone585ce.local. (Cache flush) [4m15s] NSEC,
> Canon MF410 Series._scanner._tcp.local. (Cache flush) [4m15s] NSEC
> (315)
> 10:04:07.186519 IP (tos 0x0, ttl 64, id 42873, offset 0, flags [DF],
> proto UDP (17), length 44)
> 192.168.0.15.41949 > 192.168.0.20.8610: [udp sum ok] UDP, length
> 16
> 10:04:07.187775 IP (tos 0x0, ttl 64, id 41168, offset 0, flags
> [none],
> proto UDP (17), length 60)
> 192.168.0.20.8610 > 192.168.0.15.41949: [udp sum ok] UDP, length
> 32
> 10:04:07.187834 IP (tos 0x0, ttl 64, id 42874, offset 0, flags [DF],
> proto UDP (17), length 44)
> 192.168.0.15.49897 > 192.168.0.20.8610: [udp sum ok] UDP, length
> 16
> 10:04:07.192040 IP (tos 0x0, ttl 64, id 8611, offset 0, flags [none],
> proto UDP (17), length 126)
> 192.168.0.20.8610 > 192.168.0.15.49897: [udp sum ok] UDP, length
> 98
> 10:04:07.193488 IP (tos 0x0, ttl 64, id 43608, offset 0, flags
> [none],
> proto UDP (17), length 60)
> 192.168.0.20.8610 > 192.168.0.15.8612: [udp sum ok] UDP, length
> 32
> 10:04:07.203582 IP (tos 0x0, ttl 64, id 58366, offset 0, flags
> [none],
> proto UDP (17), length 

Re: [sane-devel] xsane 0.999

[Yuri Chornoivan]

четвер, 15 березня 2018 р. 18:09:40 EET Myke Fynke написано:
> I can't make it work for me. If it's going to work for me it needs the
> ability to crop images. I can't figure out how to make it crop images,
> so it's worthless to me as-is -- unless you know something I don't know
> -- which is a certainy. So tell me: How can I make your software crop
> the images that it scans?
> 
> Let me know, please, and thanks for your trouble.
> 
> Myke.

Hi,

It is easy to split the complex task on the simpler parts. If you are looking 
for a batch solution, just scan with xsane then use free tools to do the rest.

ScanTailor:

https://github.com/scantailor/scantailor/wiki/Quick-Start-Guide

GIMP + Deskew plugin + DivideScannedImages plugin:

https://www.thelacunablog.com/batch-crop-straighten-scanned-photos.html

ImageMagick + Mutlicrop Script:

http://www.fmwconcepts.com/imagemagick/multicrop/index.php

Hope this helps.

Best regards,
Yuri


-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

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

[Louis Lagendijk]

On Tue, 2018-03-13 at 21:17 +, Patrick Roncagliolo wrote:
> Hi,
> 
> I tested pixma version 0.17.46 thru USB. It works. 
> 
> However, after updating from your PPa, I'm not able to discover my
> printer on the network. pixma.conf seems to be ignored, no matter if
> I set the IP and multiple port combinations (8610, 8611, 8612, but
> whit wireshark I see only requests as broadcast on ports 8610 8612).
> What could have been changed? Any hints about some dumb things that I
> can have forgotten since last configuration?
> 
> Il giorno dom 11 mar 2018 alle ore 12:26 Rolf Bensch  ine.de> ha scritto:
> > 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
> > 
> > 

I have an MB5050  myself and that works pretty well.
Can you please (in a shell) do:

export SANE_DEBUG_BJNP=20
scanimage -L 2>  log

and mail the resulting log file?
Some of the most recent Canon scanners no longer support bjnp, butthe
MB2000 is as far as I know of the same generation as my MB5050, so I
expect bjnp till to be supported.

Please check your firewall settings (see man sane-pixma) to be sure
that traffic does not get blocked. There should be no reason to modify
the pixma.conf file, unless you are on WIFI: ome users report problems
oer WIFI.
See the bjnp-timeout settings in pixma.conf. A single line of 
bjnp-timeout=5000 
at the beginning of that file should in that case do the trick.
I decided against including that by default as it would cause long
delays for user using other backends

BR, Loujis-- 
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] xsane 0.999

[Myke Fynke]

I can't make it work for me. If it's going to work for me it needs the
ability to crop images. I can't figure out how to make it crop images,
so it's worthless to me as-is -- unless you know something I don't know
-- which is a certainy. So tell me: How can I make your software crop
the images that it scans?

Let me know, please, and thanks for your trouble.

Myke.

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

[sane-devel] sane-backends 1.0.27 skips my SnapScan e20 in USB "unconfigured" state (OK with 1.0.25)

[Dominique Quatravaux]

Hello list, I am writing to report that my SnapScan e20 broke between
1.0.25_1 and 1.0.27_3 (Mac OS X with Homebrew) and I'm not exactly
sure what is going on, however I experimented a bit and found some
facts that might be of interest.

Mac:~$ /usr/local/Cellar/sane-backends/1.0.25_1/bin/sane-find-scanner -v
This is sane-find-scanner from sane-backends 1.0.25
[...]
searching for USB scanners:
found USB scanner (vendor=0x06bd [AGFA ], product=0x2091 [SNAPSCAN])
at libusb:020:007
[...]


Mac:~$ /usr/local/Cellar/sane-backends/1.0.27_3/bin/sane-find-scanner -v
This is sane-find-scanner from sane-backends 1.0.27
[...]
searching for USB scanners:
device 0x06bd/0x2091 at 020:007 is not configured
[...]

*However,* after xsane (using older sane-backends, copied libjpeg 8
etc.) opens the scanner OK and gets it to warm up — lo and behold, the
mood improves:

Mac:~$ /usr/local/Cellar/sane-backends/1.0.27_3/bin/sane-find-scanner -v
This is sane-find-scanner from sane-backends 1.0.27
[...]
searching for USB scanners:
found USB scanner (vendor=0x06bd [AGFA], product=0x2091 [ SNAPSCAN e20
  ]) at libusb:020:007
[...]

This state of affairs persists if I unplug the scanner, power-cycle it
and and plug it back in, but not if I reboot my Mac (even keeping the
scanner *unplugged* during the reboot). The "good mood" of
sane-find-scanner v1.0.27 therefore appears to be caused by state in
my Mac's operating system (not something scanner-side).

I recompiled from source and using lldb I could establish that the
"device XXX is not configured" message that I get in "cold" state of
the scanner, comes from libusb_get_configuration() returning config ==
0 (tools/sane-find-scanner.c line 867).

Finally, I need to mention that my SnapScan e20 is of the
"firmware-needy" kind, i.e. it requires

firmware /usr/local/sane-firmware/snape20.bin

in /usr/local/Cellar/sane-backends/VERSIONDUJOUR/etc/sane.d/snapscan.conf
, or it won't even move motors much less respond to xsane. (This
explains my line of investigation to figure out whether the "good
mood" state was caused by my scanner having gotten its firmware; which
unfortunately doesn't appear to be the case.)

I cannot help but notice that
https://github.com/javian/homebrew-core/commit/b1b4d38d5f6875d152f50b36c0950f18a9837a3b
falls just inbetween my "working" and "not working" cases, and
introduces libusb-related changes so I am taking the liberty to put
fxcoudert in Cc.

I am in a position to try patches, etc. Thanks in advance for any help
in that matter,

--
 Dominique Quatravaux
 domini...@quatravaux.org

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

[sane-devel] Help Please with Nikon Super Coolscan 4000 ED

[Bob Louden]

Dear mailing list.  Please excuse me if I am not using this mailing list
properly.

I created a request for help a few days ago in the Linux Mint Hardware
forum but have not had any luck with responses.

I have this very nice, albeit old, scanner that I cannot get to work --
though I feel like I am very close to having it work.  Alas, I am on the
brink of giving up on it.  I also have this not-as-good Plustek scanner
that I've started messing with and it was from searching for help with it
that I found your mailing list.

Anyway, if there is anyone out there who might be able to help me, here is
a link to my Linux Mint forum post:
https://forums.linuxmint.com/viewtopic.php?f=51=264978

Please feel free to respond to me via either email or in the forum.

Thank you.

 Bob



-- 

https://www.google.com/+BobLouden


“Simple can be harder than complex: You have to work hard to get your
thinking clean to make it simple. But it’s worth it in the end because once
you get there, you can move mountains.” Steve Jobs [BusinessWeek, May 25,
1998 ]
-- 
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] Version bumps

[Olaf Meeuwissen]

Hi,

I've pushed a number of commits that mostly just update the versions of
"stuff" the SANE Project depends on.  On the CI front, this:

  - adds a Fedora 27 build
  - drops the Fedora 25 build
  - bumps the Alpine build to 3.7
  - bumps the Debian build to 9.4

In terms of "canonical" build environment, CI now uses Debian 9.

# I thinking about dropping the Debian 8 and Fedora 26 builds, BTW.

As for the SANE backends code, I have bumped the autofoo bits to match
the versions in Debian 9.  Specifically,

  - autoconf is unchanged
  - automake went from 1.11.6 to 1.15
  - libtool from 2.4.2 to 2.4.6
  - gettext from 0.18.1 to 0.19.8

If you experience build problems and think they may be due to the above,
try a `make distclean` and re`./configure`.  That said, I don't expect
there to be any :-)

# Here's assuming maintainer-mode rules don't throw a monkey wrench.

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

[sane-devel] Looking for help with scanner

[John Oliver]

On Ubuntu 16.04.04, using "Simple Scan" which is, apparently, SANE.

I bought a Canon imageCLASS MF416dw and had to jump through some hoops
to get it printing.  It's on the network, wired, local subnet.  I'm
using the PIXMA backend.

joliver@blinky:~$ sudo nmap -sU -p 8610-8612 192.168.0.20

Starting Nmap 7.01 ( https://nmap.org ) at 2018-03-16 09:56 PDT
Nmap scan report for 192.168.0.20
Host is up (0.038s latency).
PORT STATE SERVICE
8610/udp open|filtered unknown
8611/udp closedcanon-bjnp1
8612/udp closedcanon-bjnp2
MAC Address: F4:81:39:E5:85:CE (Canon)

Nmap done: 1 IP address (1 host up) scanned in 1.74 seconds
joliver@blinky:~$ sudo nmap -sT -p 8610-8612 192.168.0.20

Starting Nmap 7.01 ( https://nmap.org ) at 2018-03-16 09:56 PDT
Nmap scan report for 192.168.0.20
Host is up (0.0017s latency).
PORT STATE  SERVICE
8610/tcp open   unknown
8611/tcp closed unknown
8612/tcp closed unknown
MAC Address: F4:81:39:E5:85:CE (Canon)

Nmap done: 1 IP address (1 host up) scanned in 0.32 seconds


So, I tried mfnp://192.168.0.20 but simple-scan quickly bombs out with
"No scanners detected"  So I sniffed traffic while starting sane:

joliver@blinky:~$ sudo tcpdump -vvv host 192.168.0.20
tcpdump: listening on wlp2s0, link-type EN10MB (Ethernet), capture size
262144 bytes
10:04:03.030738 IP (tos 0x0, ttl 64, id 41990, offset 0, flags [DF],
proto UDP (17), length 44)
192.168.0.15.44468 > 192.168.0.20.8610: [udp sum ok] UDP, length 16
10:04:03.032672 IP (tos 0x0, ttl 64, id 6518, offset 0, flags [none],
proto UDP (17), length 60)
192.168.0.20.8610 > 192.168.0.15.44468: [udp sum ok] UDP, length 32
10:04:03.032757 IP (tos 0x0, ttl 64, id 41991, offset 0, flags [DF],
proto UDP (17), length 44)
192.168.0.15.48892 > 192.168.0.20.8610: [udp sum ok] UDP, length 16
10:04:03.036182 IP (tos 0x0, ttl 64, id 17032, offset 0, flags [none],
proto UDP (17), length 126)
192.168.0.20.8610 > 192.168.0.15.48892: [udp sum ok] UDP, length 98
10:04:03.040416 IP (tos 0x0, ttl 64, id 23405, offset 0, flags [none],
proto UDP (17), length 60)
192.168.0.20.8610 > 192.168.0.15.8612: [udp sum ok] UDP, length 32
10:04:03.050893 IP (tos 0x0, ttl 64, id 11420, offset 0, flags [none],
proto UDP (17), length 60)
192.168.0.20.8610 > 192.168.0.15.8612: [udp sum ok] UDP, length 32
10:04:03.082441 IP (tos 0x0, ttl 64, id 41994, offset 0, flags [DF],
proto UDP (17), length 44)
192.168.0.15.41346 > 192.168.0.20.8610: [udp sum ok] UDP, length 16
10:04:03.083924 IP (tos 0x0, ttl 64, id 7595, offset 0, flags [none],
proto UDP (17), length 60)
192.168.0.20.8610 > 192.168.0.15.41346: [udp sum ok] UDP, length 32
10:04:03.104825 IP (tos 0x0, ttl 64, id 41998, offset 0, flags [DF],
proto UDP (17), length 44)
192.168.0.15.42059 > 192.168.0.20.8610: [udp sum ok] UDP, length 16
10:04:03.106075 IP (tos 0x0, ttl 64, id 46684, offset 0, flags [none],
proto UDP (17), length 60)
192.168.0.20.8610 > 192.168.0.15.42059: [udp sum ok] UDP, length 32
10:04:05.956867 IP (tos 0x0, ttl 255, id 7957, offset 0, flags [none],
proto UDP (17), length 343)
192.168.0.20.mdns > 224.0.0.251.mdns: [udp sum ok] 0- [0q] 1/0/5
_scanner._tcp.local. [4m15s] PTR Canon MF410 Series._scanner._tcp.local.
ar: Canone585ce.local. (Cache flush) [4m15s] A 192.168.0.20, Canon MF410
Series._scanner._tcp.local. (Cache flush) [4m15s] SRV
Canone585ce.local.:8610 0 0, Canon MF410 Series._scanner._tcp.local.
(Cache flush) [4m15s] TXT "txtvers=1" "note="
"adminurl=http://Canone585ce.local/airprint.html; "ty=Canon MF410
Series" "UUID=f48139e585ce" "mfg=Canon" "mdl=MF410 Series"
"scannerAvailable=0", Canone585ce.local. (Cache flush) [4m15s] NSEC,
Canon MF410 Series._scanner._tcp.local. (Cache flush) [4m15s] NSEC (315)
10:04:07.186519 IP (tos 0x0, ttl 64, id 42873, offset 0, flags [DF],
proto UDP (17), length 44)
192.168.0.15.41949 > 192.168.0.20.8610: [udp sum ok] UDP, length 16
10:04:07.187775 IP (tos 0x0, ttl 64, id 41168, offset 0, flags [none],
proto UDP (17), length 60)
192.168.0.20.8610 > 192.168.0.15.41949: [udp sum ok] UDP, length 32
10:04:07.187834 IP (tos 0x0, ttl 64, id 42874, offset 0, flags [DF],
proto UDP (17), length 44)
192.168.0.15.49897 > 192.168.0.20.8610: [udp sum ok] UDP, length 16
10:04:07.192040 IP (tos 0x0, ttl 64, id 8611, offset 0, flags [none],
proto UDP (17), length 126)
192.168.0.20.8610 > 192.168.0.15.49897: [udp sum ok] UDP, length 98
10:04:07.193488 IP (tos 0x0, ttl 64, id 43608, offset 0, flags [none],
proto UDP (17), length 60)
192.168.0.20.8610 > 192.168.0.15.8612: [udp sum ok] UDP, length 32
10:04:07.203582 IP (tos 0x0, ttl 64, id 58366, offset 0, flags [none],
proto UDP (17), length 60)
192.168.0.20.8610 > 192.168.0.15.8612: [udp sum ok] UDP, length 32
10:04:07.232969 IP (tos 0x0, ttl 64, id 42886, offset 0, flags [DF],
proto UDP (17), length 44)
192.168.0.15.57656 > 192.168.0.20.8610: [udp sum ok] UDP, length 16
10:04:07.238180 IP (tos 0x0, ttl 64, id 38127, offset 0, flags 

[sane-devel] HP5590 and scanbd button recognition

[Cesello]

Ops a missing important info:

The patch is for hp5590.c in the git repo 
https://gitlab.com/sane-project/backends.git
tag RELEASE_1_0_25.
I've choose that version  because is the last in debian stable.

Damiano




On 13/03/2018 20:56, Ilia Sotnikov wrote:
> Excellent, thanks Damiano! As a quick step you could send the patch over to 
> the DL and I’ll adapt it if needed. Or you could create a merge request, 
> which would be more elegant though require additional steps.
> ---
>  Ilia Sotnikov
>
>> On Mar 13, 2018, at 21:29, Cesello  wrote:
>>
>> Hi Ilia and Jared
>> I'm just registered to this ML to propose my patch to this back end
>> driver made in the past weekend.
>> And I see someone have my same problem :)
>> I've used hp5590 scanner with scanbuttond for years. Some week ago I've
>> upgraded my system to debian 9 and
>> discovered that scanbd does not works anymore with my scanner. I really
>> need this functionality so I've made
>> modifications to hp5590.c code to export the options .
>> Is a first attempt and the backend called by scanbd threads makes
>> buttons quite  responsive
>> without using a self polling thread.
>> I've made a patch file for debian 9  stable version package (yes but the
>> real patch is for hp5590.c only)
>> If you are interested I can send it (or tell me if I have to release
>> into the repo directly I'm new user here :))
>>
>> Damiano
>>
>>> On 07/03/2018 14:01, hostcc at gmail.com (Ilia Sotnikov) wrote:
>>> Hi,
>>> backend author here - it shouldn't be too much of effort to expose
>>> button status so scanbd can use it. Though haven't gone thru its
>>> documentation to understand requirements. As a technical insight -
>>> there is hp5590_read_buttons() function in hp5590_cmds.c that reads
>>> button status.
>>> However, I'll seek for a volunteer to test a change as I don't have
>>> access to HW currently.
>>>
>>> On Wed, Mar 7, 2018 at 12:40 AM, Wilhelm Meier
>>>  wrote:
 Please try the old scanbuttond-backend for this type of scanner - it
 should work. The HP sane backend sadly doesn't support the buttons on
 this scanner.

 Am 06.03.2018 um 15:46 schrieb Jared Hedegaard:
>> Main question: does the HP 5590 support button presses or am I just 
>> setting this up incorrectly?
>>
>> I'm been successful using scanbd with SANE backends to get scanning 
>> working over my network and locally on the host machine, but I can't 
>> seem to get it to recognize button presses, either running scanbd in 
>> foreground or background.
>>
>> For past testing, it seems that actions defined in scanbd.conf are used 
>> to tie to the backend options? From searching /var/log/syslog, I 
>> expected to track button presses or get some sort of trigger feedback, 
>> and I didn't think I needed an action set up for it.
>>
>> Any help on this one would be much appreciated. Thanks.
>>
>> Jared H
>>
> After a bit more research, it looks like doing this with the SANE backend 
> for HP 5590 is not possible. scanbd is used to tie custom actions to the 
> options available on the scanner. In this case, none of the 10 options 
> seem to return values. They all look to be ones that I designate from 
> some client software.
>
> scanbd: found active option[1] tl-x (type: 2) for device 
> hp5590:libusb:001:008
> scanbd: found active option[2] tl-y (type: 2) for device 
> hp5590:libusb:001:008
> scanbd: found active option[3] br-x (type: 2) for device 
> hp5590:libusb:001:008
> scanbd: found active option[4] br-y (type: 2) for device 
> hp5590:libusb:001:008
> scanbd: found active option[5] mode (type: 3) for device 
> hp5590:libusb:001:008
> scanbd: found active option[6] source (type: 3) for device 
> hp5590:libusb:001:008
> scanbd: found active option[7] resolution (type: 1) for device 
> hp5590:libusb:001:008 scanbd: found active option[8] extend-lamp-timeout 
> (type: 0) for device hp5590:libusb:001:008
> scanbd: found active option[9] wait-for-button (type: 0) for device 
> hp5590:libusb:001:008
> scanbd: found active option[10] preview (type: 0) for device 
> hp5590:libusb:001:008
>
> In this case, it looks like I will have to try the old scanbuttond 
> backends for this, or see if there are optional enhancements for the SANE 
> hp5590 backend.
>
> Jared
>
 --
 sane-devel mailing list: sane-devel at 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-request at lists.alioth.debian.org
>>>
>>
>> -- 
>> sane-devel mailing list: sane-devel@lists.alioth.debian.org
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
>> Unsubscribe: Send mail with subject "unsubscribe your_password"
>> to 

[sane-devel] HP5590 and scanbd button recognition

[Cesello]

Hi Ilia et all
attached to this message is the patch (hope mailman engine does not
strip it out :))
Basically exports all missing options as buttons and fix a small problem
I've found interacting with scanbd.
I've tested during the weekend and last days (as real user , I missed
this feature for two months after debian upgrade)
and it seems to work.
Sometime the buttons are less responsive (it depends from scheduled
calls to options made by scanbd)
Probably a better approach could be a separate polling thread (maybe a
next version :))
but for now is quite usable.
I've tested with normal sane application too and with scanbm (for
network scanning and desktop shared scanner)
and no problems at all
Sorry for some erratic indentation.. I've used a
"week-end-found-bad-editor" that mixed up tab and blank spaces

Let me know
Happy PI Day ;)

Damiano

On 13/03/2018 20:56, Ilia Sotnikov wrote:
> Excellent, thanks Damiano! As a quick step you could send the patch over to 
> the DL and I’ll adapt it if needed. Or you could create a merge request, 
> which would be more elegant though require additional steps.
> ---
>  Ilia Sotnikov
>
>> On Mar 13, 2018, at 21:29, Cesello  wrote:
>>
>> Hi Ilia and Jared
>> I'm just registered to this ML to propose my patch to this back end
>> driver made in the past weekend.
>> And I see someone have my same problem :)
>> I've used hp5590 scanner with scanbuttond for years. Some week ago I've
>> upgraded my system to debian 9 and
>> discovered that scanbd does not works anymore with my scanner. I really
>> need this functionality so I've made
>> modifications to hp5590.c code to export the options .
>> Is a first attempt and the backend called by scanbd threads makes
>> buttons quite  responsive
>> without using a self polling thread.
>> I've made a patch file for debian 9  stable version package (yes but the
>> real patch is for hp5590.c only)
>> If you are interested I can send it (or tell me if I have to release
>> into the repo directly I'm new user here :))
>>
>> Damiano
>>
>>> On 07/03/2018 14:01, hostcc at gmail.com (Ilia Sotnikov) wrote:
>>> Hi,
>>> backend author here - it shouldn't be too much of effort to expose
>>> button status so scanbd can use it. Though haven't gone thru its
>>> documentation to understand requirements. As a technical insight -
>>> there is hp5590_read_buttons() function in hp5590_cmds.c that reads
>>> button status.
>>> However, I'll seek for a volunteer to test a change as I don't have
>>> access to HW currently.
>>>
>>> On Wed, Mar 7, 2018 at 12:40 AM, Wilhelm Meier
>>>  wrote:
 Please try the old scanbuttond-backend for this type of scanner - it
 should work. The HP sane backend sadly doesn't support the buttons on
 this scanner.

 Am 06.03.2018 um 15:46 schrieb Jared Hedegaard:
>> Main question: does the HP 5590 support button presses or am I just 
>> setting this up incorrectly?
>>
>> I'm been successful using scanbd with SANE backends to get scanning 
>> working over my network and locally on the host machine, but I can't 
>> seem to get it to recognize button presses, either running scanbd in 
>> foreground or background.
>>
>> For past testing, it seems that actions defined in scanbd.conf are used 
>> to tie to the backend options? From searching /var/log/syslog, I 
>> expected to track button presses or get some sort of trigger feedback, 
>> and I didn't think I needed an action set up for it.
>>
>> Any help on this one would be much appreciated. Thanks.
>>
>> Jared H
>>
> After a bit more research, it looks like doing this with the SANE backend 
> for HP 5590 is not possible. scanbd is used to tie custom actions to the 
> options available on the scanner. In this case, none of the 10 options 
> seem to return values. They all look to be ones that I designate from 
> some client software.
>
> scanbd: found active option[1] tl-x (type: 2) for device 
> hp5590:libusb:001:008
> scanbd: found active option[2] tl-y (type: 2) for device 
> hp5590:libusb:001:008
> scanbd: found active option[3] br-x (type: 2) for device 
> hp5590:libusb:001:008
> scanbd: found active option[4] br-y (type: 2) for device 
> hp5590:libusb:001:008
> scanbd: found active option[5] mode (type: 3) for device 
> hp5590:libusb:001:008
> scanbd: found active option[6] source (type: 3) for device 
> hp5590:libusb:001:008
> scanbd: found active option[7] resolution (type: 1) for device 
> hp5590:libusb:001:008 scanbd: found active option[8] extend-lamp-timeout 
> (type: 0) for device hp5590:libusb:001:008
> scanbd: found active option[9] wait-for-button (type: 0) for device 
> hp5590:libusb:001:008
> scanbd: found active option[10] preview (type: 0) for device 
> hp5590:libusb:001:008
>
> In this case, it looks like I will have to try the old scanbuttond 
> 

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

[Patrick Roncagliolo]

Hi,

I tested pixma version 0.17.46 thru USB. It works.

However, after updating from your PPa, I'm not able to discover my printer
on the network. pixma.conf seems to be ignored, no matter if I set the IP
and multiple port combinations (8610, 8611, 8612, but whit wireshark I see
only requests as broadcast on ports 8610 8612). What could have been
changed? Any hints about some dumb things that I can have forgotten since
last configuration?

Il giorno dom 11 mar 2018 alle ore 12:26 Rolf Bensch 
ha scritto:

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

Re: [sane-devel] HP5590 and scanbd button recognition

[Wilhelm Meier]

Hi together,

if this is a patch for scanbd and the old scanbuttond backends included
there, please send the patch to this list. I'll be happy to integrate it
into scanbd.

Thanks,
 Wilhelm

Am 13.03.2018 um 19:29 schrieb Cesello:
> Hi Ilia and Jared
> I'm just registered to this ML to propose my patch to this back end
> driver made in the past weekend.
> And I see someone have my same problem :)
> I've used hp5590 scanner with scanbuttond for years. Some week ago I've
> upgraded my system to debian 9 and
> discovered that scanbd does not works anymore with my scanner. I really
> need this functionality so I've made
> modifications to hp5590.c code to export the options .
> Is a first attempt and the backend called by scanbd threads makes
> buttons quite  responsive
> without using a self polling thread.
> I've made a patch file for debian 9  stable version package (yes but the
> real patch is for hp5590.c only)
> If you are interested I can send it (or tell me if I have to release
> into the repo directly I'm new user here :))
> 
> Damiano
> 
> On 07/03/2018 14:01, hostcc at gmail.com (Ilia Sotnikov) wrote:
>> Hi,
>> backend author here - it shouldn't be too much of effort to expose
>> button status so scanbd can use it. Though haven't gone thru its
>> documentation to understand requirements. As a technical insight -
>> there is hp5590_read_buttons() function in hp5590_cmds.c that reads
>> button status.
>> However, I'll seek for a volunteer to test a change as I don't have
>> access to HW currently.
>>
>> On Wed, Mar 7, 2018 at 12:40 AM, Wilhelm Meier
>>  wrote:
>>> Please try the old scanbuttond-backend for this type of scanner - it
>>> should work. The HP sane backend sadly doesn't support the buttons on
>>> this scanner.
>>>
>>> Am 06.03.2018 um 15:46 schrieb Jared Hedegaard:
> Main question: does the HP 5590 support button presses or am I just 
> setting this up incorrectly?
>
> I'm been successful using scanbd with SANE backends to get scanning 
> working over my network and locally on the host machine, but I can't seem 
> to get it to recognize button presses, either running scanbd in 
> foreground or background.
>
> For past testing, it seems that actions defined in scanbd.conf are used 
> to tie to the backend options? From searching /var/log/syslog, I expected 
> to track button presses or get some sort of trigger feedback, and I 
> didn't think I needed an action set up for it.
>
> Any help on this one would be much appreciated. Thanks.
>
> Jared H
>
 After a bit more research, it looks like doing this with the SANE backend 
 for HP 5590 is not possible. scanbd is used to tie custom actions to the 
 options available on the scanner. In this case, none of the 10 options 
 seem to return values. They all look to be ones that I designate from some 
 client software.

 scanbd: found active option[1] tl-x (type: 2) for device 
 hp5590:libusb:001:008
 scanbd: found active option[2] tl-y (type: 2) for device 
 hp5590:libusb:001:008
 scanbd: found active option[3] br-x (type: 2) for device 
 hp5590:libusb:001:008
 scanbd: found active option[4] br-y (type: 2) for device 
 hp5590:libusb:001:008
 scanbd: found active option[5] mode (type: 3) for device 
 hp5590:libusb:001:008
 scanbd: found active option[6] source (type: 3) for device 
 hp5590:libusb:001:008
 scanbd: found active option[7] resolution (type: 1) for device 
 hp5590:libusb:001:008 scanbd: found active option[8] extend-lamp-timeout 
 (type: 0) for device hp5590:libusb:001:008
 scanbd: found active option[9] wait-for-button (type: 0) for device 
 hp5590:libusb:001:008
 scanbd: found active option[10] preview (type: 0) for device 
 hp5590:libusb:001:008

 In this case, it looks like I will have to try the old scanbuttond 
 backends for this, or see if there are optional enhancements for the SANE 
 hp5590 backend.

 Jared

>>>
>>> --
>>> sane-devel mailing list: sane-devel at 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-request at lists.alioth.debian.org
>>
>>
> 
> 


-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] HP5590 and scanbd button recognition

[Ilia Sotnikov]

Excellent, thanks Damiano! As a quick step you could send the patch over to the 
DL and I’ll adapt it if needed. Or you could create a merge request, which 
would be more elegant though require additional steps.
---
 Ilia Sotnikov

> On Mar 13, 2018, at 21:29, Cesello  wrote:
> 
> Hi Ilia and Jared
> I'm just registered to this ML to propose my patch to this back end
> driver made in the past weekend.
> And I see someone have my same problem :)
> I've used hp5590 scanner with scanbuttond for years. Some week ago I've
> upgraded my system to debian 9 and
> discovered that scanbd does not works anymore with my scanner. I really
> need this functionality so I've made
> modifications to hp5590.c code to export the options .
> Is a first attempt and the backend called by scanbd threads makes
> buttons quite  responsive
> without using a self polling thread.
> I've made a patch file for debian 9  stable version package (yes but the
> real patch is for hp5590.c only)
> If you are interested I can send it (or tell me if I have to release
> into the repo directly I'm new user here :))
> 
> Damiano
> 
>> On 07/03/2018 14:01, hostcc at gmail.com (Ilia Sotnikov) wrote:
>> Hi,
>> backend author here - it shouldn't be too much of effort to expose
>> button status so scanbd can use it. Though haven't gone thru its
>> documentation to understand requirements. As a technical insight -
>> there is hp5590_read_buttons() function in hp5590_cmds.c that reads
>> button status.
>> However, I'll seek for a volunteer to test a change as I don't have
>> access to HW currently.
>> 
>> On Wed, Mar 7, 2018 at 12:40 AM, Wilhelm Meier
>>  wrote:
>>> Please try the old scanbuttond-backend for this type of scanner - it
>>> should work. The HP sane backend sadly doesn't support the buttons on
>>> this scanner.
>>> 
>>> Am 06.03.2018 um 15:46 schrieb Jared Hedegaard:
> Main question: does the HP 5590 support button presses or am I just 
> setting this up incorrectly?
> 
> I'm been successful using scanbd with SANE backends to get scanning 
> working over my network and locally on the host machine, but I can't seem 
> to get it to recognize button presses, either running scanbd in 
> foreground or background.
> 
> For past testing, it seems that actions defined in scanbd.conf are used 
> to tie to the backend options? From searching /var/log/syslog, I expected 
> to track button presses or get some sort of trigger feedback, and I 
> didn't think I needed an action set up for it.
> 
> Any help on this one would be much appreciated. Thanks.
> 
> Jared H
> 
 After a bit more research, it looks like doing this with the SANE backend 
 for HP 5590 is not possible. scanbd is used to tie custom actions to the 
 options available on the scanner. In this case, none of the 10 options 
 seem to return values. They all look to be ones that I designate from some 
 client software.
 
 scanbd: found active option[1] tl-x (type: 2) for device 
 hp5590:libusb:001:008
 scanbd: found active option[2] tl-y (type: 2) for device 
 hp5590:libusb:001:008
 scanbd: found active option[3] br-x (type: 2) for device 
 hp5590:libusb:001:008
 scanbd: found active option[4] br-y (type: 2) for device 
 hp5590:libusb:001:008
 scanbd: found active option[5] mode (type: 3) for device 
 hp5590:libusb:001:008
 scanbd: found active option[6] source (type: 3) for device 
 hp5590:libusb:001:008
 scanbd: found active option[7] resolution (type: 1) for device 
 hp5590:libusb:001:008 scanbd: found active option[8] extend-lamp-timeout 
 (type: 0) for device hp5590:libusb:001:008
 scanbd: found active option[9] wait-for-button (type: 0) for device 
 hp5590:libusb:001:008
 scanbd: found active option[10] preview (type: 0) for device 
 hp5590:libusb:001:008
 
 In this case, it looks like I will have to try the old scanbuttond 
 backends for this, or see if there are optional enhancements for the SANE 
 hp5590 backend.
 
 Jared
 
>>> 
>>> --
>>> sane-devel mailing list: sane-devel at 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-request at lists.alioth.debian.org
>> 
>> 
> 
> 
> -- 
> sane-devel mailing list: sane-devel@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
> to sane-devel-requ...@lists.alioth.debian.org

-- 
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] HP5590 and scanbd button recognition

[Cesello]

Hi Ilia and Jared
I'm just registered to this ML to propose my patch to this back end
driver made in the past weekend.
And I see someone have my same problem :)
I've used hp5590 scanner with scanbuttond for years. Some week ago I've
upgraded my system to debian 9 and
discovered that scanbd does not works anymore with my scanner. I really
need this functionality so I've made
modifications to hp5590.c code to export the options .
Is a first attempt and the backend called by scanbd threads makes
buttons quite  responsive
without using a self polling thread.
I've made a patch file for debian 9  stable version package (yes but the
real patch is for hp5590.c only)
If you are interested I can send it (or tell me if I have to release
into the repo directly I'm new user here :))

Damiano

On 07/03/2018 14:01, hostcc at gmail.com (Ilia Sotnikov) wrote:
> Hi,
> backend author here - it shouldn't be too much of effort to expose
> button status so scanbd can use it. Though haven't gone thru its
> documentation to understand requirements. As a technical insight -
> there is hp5590_read_buttons() function in hp5590_cmds.c that reads
> button status.
> However, I'll seek for a volunteer to test a change as I don't have
> access to HW currently.
>
> On Wed, Mar 7, 2018 at 12:40 AM, Wilhelm Meier
>  wrote:
>> Please try the old scanbuttond-backend for this type of scanner - it
>> should work. The HP sane backend sadly doesn't support the buttons on
>> this scanner.
>>
>> Am 06.03.2018 um 15:46 schrieb Jared Hedegaard:
 Main question: does the HP 5590 support button presses or am I just 
 setting this up incorrectly?

 I'm been successful using scanbd with SANE backends to get scanning 
 working over my network and locally on the host machine, but I can't seem 
 to get it to recognize button presses, either running scanbd in foreground 
 or background.

 For past testing, it seems that actions defined in scanbd.conf are used to 
 tie to the backend options? From searching /var/log/syslog, I expected to 
 track button presses or get some sort of trigger feedback, and I didn't 
 think I needed an action set up for it.

 Any help on this one would be much appreciated. Thanks.

 Jared H

>>> After a bit more research, it looks like doing this with the SANE backend 
>>> for HP 5590 is not possible. scanbd is used to tie custom actions to the 
>>> options available on the scanner. In this case, none of the 10 options seem 
>>> to return values. They all look to be ones that I designate from some 
>>> client software.
>>>
>>> scanbd: found active option[1] tl-x (type: 2) for device 
>>> hp5590:libusb:001:008
>>> scanbd: found active option[2] tl-y (type: 2) for device 
>>> hp5590:libusb:001:008
>>> scanbd: found active option[3] br-x (type: 2) for device 
>>> hp5590:libusb:001:008
>>> scanbd: found active option[4] br-y (type: 2) for device 
>>> hp5590:libusb:001:008
>>> scanbd: found active option[5] mode (type: 3) for device 
>>> hp5590:libusb:001:008
>>> scanbd: found active option[6] source (type: 3) for device 
>>> hp5590:libusb:001:008
>>> scanbd: found active option[7] resolution (type: 1) for device 
>>> hp5590:libusb:001:008 scanbd: found active option[8] extend-lamp-timeout 
>>> (type: 0) for device hp5590:libusb:001:008
>>> scanbd: found active option[9] wait-for-button (type: 0) for device 
>>> hp5590:libusb:001:008
>>> scanbd: found active option[10] preview (type: 0) for device 
>>> hp5590:libusb:001:008
>>>
>>> In this case, it looks like I will have to try the old scanbuttond backends 
>>> for this, or see if there are optional enhancements for the SANE hp5590 
>>> backend.
>>>
>>> Jared
>>>
>>
>> --
>> sane-devel mailing list: sane-devel at 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-request at lists.alioth.debian.org
>
>


-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

[sane-devel] problem to get SANE work with Hewlett Packard HP Scanjet N6310 scanner

[István Ákos Mórocz]

dear SANE developers,

i am trying to get an HP Scanjet N6310 up & running with linux/SANE
and with Vuescan, so far without success for the last couple of years.
i bought the device back in 2014 in the US and i don't know if it
features any special chip, firmware or whatever, but so much for sure:
it doesn't do a beep with SCANIMAGE, SANE or VUESCAN using SANE 1.0.27
under Slackware 14.2, although it is detected with lsusb and scanimage
-L, and even with XSANE if initiated jointly with an operational
Fujitsu ScanSnap scanner; obviously this will still not work for the
N6310, it just makes it show up in the XSANE GUI.

some years ago i got this N6310 running with some combination of
Vuescan/win8/VMware/Slackware but this is not the case anymore since
all the version changes in the past, and meanwhile i anyway try to go
the direct route using linux pure for all software i use.

i recently re-started to discuss this problem here :

  https://www.linuxquestions.org/questions/showthread.php?p=5830512#post5830512


i will be eagerly waiting for your feedback !  bye, pisti

--
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] [janitorial] Alioth → GitLab Migration Update

[Olaf Meeuwissen]

Hi all,

A good month ago, Olaf Meeuwissen wrote:

> Hi all,

So I thought I'd give you an update ;-)

> I have started work on some of the issues on the migration milestone I
> created on GitLab[1].  Of course you can follow what's going on on the
> milestone directly (or the board[2]) but I figured I'd post an update.
>
>   [1]: https://gitlab.com/sane-project/ops/milestones/1
>   [2]: 
> https://gitlab.com/sane-project/ops/boards?milestone_title=Alioth%20%E2%86%92%20GitLab%20Migration

# As for the board, I've been trying out the sane-project *group* board
# as opposed to the ops *project* board so you should now look at
#
#  https://gitlab.com/groups/sane-project/-/boards?milestone_title=%23started
#
# to get a picture of the current state.

> For starters, both the sane-backends and sane-frontends repositories
> on Alioth are now *read-only* and will no longer receive any updates.
> The developers should push to the corresponding repositories at
> GitLab.com from now on.
>
> Pushes to the Alioth repositories will now fail with an error message
> telling you how to switch your local checkout.
>
> # The website project will follow once we have a site set up on the
> # GitLab infra-structure.  In the mean time, all these changes have
> # been reflected in the site's pages.

The website project has followed suit and the Alioth repository is now
read-only.  This completes the transfer of *all* of the SANE project's
git repositories from Alioth to GitLab.com.

> All SANE project members on Alioth have received invitations to join the
> project on GitLab.com and a bit shy of half have already accepted.  The
> rest will get another nudge soon.  Please note that only project members
> can push to GitLab.com.

On this front, close to three quarters of the Alioth members have now
joined (or declined to join) the project on GitLab.com.  The remaining
five have received several nudges by now and any outstanding invitations
will be closed after 2018-03-21 00:00 UTC.

# The initial invitation was issued on 2018-02-01, BTW.

> Release artifacts, [...]

Nothing changed in this department.

> In the mean time, I'm also looking at the possibility of migrating the
> Tracker items we have at Alioth[5].  It doesn't look easy, but someone
> at GitLab.com (the Director of Strategic Partnerships) has contacted me
> with an offer to help.  I'm not holding my breath but any help in this
> area is welcome.
>
>   [5]: https://gitlab.com/sane-project/ops/issues/10

I have been poking around in the FusionForge source code that powers
Alioth and found an interesting commit that may make migrating Alioth
issues a breeze.  Well, almost at least.  I'm waiting for the Alioth
maintainers to apply a patch so I can test.  Details are in the issue
linked to above.

> If there is anything you think that's missing from the milestone[1] or
> find fault with any of the attached release artifacts[3][4], feel free
> to submit a new issue[6].  You don't have to be a SANE Project member.
> Simply login to GitLab.com[7] and create a new issue[6].
>
>   [6]: https://gitlab.com/users/sign_in
>   [7]: https://gitlab.com/sane-project/ops/issues/new

This stands without change.

> Next up on my list is the website[8].
>
>   [8]: https://gitlab.com/sane-project/ops/issues/7

This issue has been closed after a good deal of mucking about with the
links in the webpages so they would work on Alioth and GitLab.  While
working on this and testing stuff, I even got myself black-listed and
could not browse the site on Alioth for a while :-/
There is now a static SANE Project website that you can visit on

  https://sane-project.gitlab.io/website/

It should be identical to the one on Alioth.  The Scanner Search
Engine[9] will break as soon as Alioth goes off-line, though.

 [9]: https://sane.alioth.debian.org/cgi-bin/driver.pl

I have asked[10] Allan to make the project's domain (sane-project.org)
point to the GitLab hosted website.

 [10]: https://gitlab.com/sane-project/ops/boards?=

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

[sane-devel] sane-backends 1.0.27 skips my SnapScan e20 in USB "unconfigured" state (OK with 1.0.25)

[Dominique Quatravaux]

Hello list, I am writing to report that my SnapScan e20 broke between
1.0.25_1 and 1.0.27_3 (Mac OS X with Homebrew) and I'm not exactly
sure what is going on, however I experimented a bit and found some
facts that might be of interest.

Mac:~$ /usr/local/Cellar/sane-backends/1.0.25_1/bin/sane-find-scanner -v
This is sane-find-scanner from sane-backends 1.0.25
[...]
searching for USB scanners:
found USB scanner (vendor=0x06bd [AGFA ], product=0x2091 [SNAPSCAN])
at libusb:020:007
[...]


Mac:~$ /usr/local/Cellar/sane-backends/1.0.27_3/bin/sane-find-scanner -v
This is sane-find-scanner from sane-backends 1.0.27
[...]
searching for USB scanners:
device 0x06bd/0x2091 at 020:007 is not configured
[...]

*However,* after xsane (using older sane-backends, copied libjpeg 8
etc.) opens the scanner OK and gets it to warm up — lo and behold, the
mood improves:

Mac:~$ /usr/local/Cellar/sane-backends/1.0.27_3/bin/sane-find-scanner -v
This is sane-find-scanner from sane-backends 1.0.27
[...]
searching for USB scanners:
found USB scanner (vendor=0x06bd [AGFA], product=0x2091 [ SNAPSCAN e20
  ]) at libusb:020:007
[...]

This state of affairs persists if I unplug the scanner, power-cycle it
and and plug it back in, but not if I reboot my Mac (even keeping the
scanner *unplugged* during the reboot). The "good mood" of
sane-find-scanner v1.0.27 therefore appears to be caused by state in
my Mac's operating system (not something scanner-side).

I recompiled from source and using lldb I could establish that the
"device XXX is not configured" message that I get in "cold" state of
the scanner, comes from libusb_get_configuration() returning config ==
0 (tools/sane-find-scanner.c line 867).

Finally, I need to mention that my SnapScan e20 is of the
"firmware-needy" kind, i.e. it requires

firmware /usr/local/sane-firmware/snape20.bin

in /usr/local/Cellar/sane-backends/VERSIONDUJOUR/etc/sane.d/snapscan.conf
, or it won't even move motors much less respond to xsane. (This
explains my line of investigation to figure out whether the "good
mood" state was caused by my scanner having gotten its firmware; which
unfortunately doesn't appear to be the case.)

I cannot help but notice that
https://github.com/javian/homebrew-core/commit/
b1b4d38d5f6875d152f50b36c0950f18a9837a3b
falls just inbetween my "working" and "not working" cases, and
introduces libusb-related changes so I am taking the liberty to put
fxcoudert in Cc.

I am in a position to try patches, etc. Thanks in advance for any help
in that matter,

[P.S. Sorry for the double post]
-- 
Dominique Quatravaux
domini...@quatravaux.org
-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

[sane-devel] gscan2pdf v2.0.1 released

[Jeff]

gscan2pdf - A GUI to produce a multipage PDF or DjVu from a scan.

http://gscan2pdf.sourceforge.net/

Five clicks are required to scan several pages and then save all or
a selection as a PDF or DjVu file, including metadata if required.

gscan2pdf can control regular or sheet-fed (ADF) scanners with SANE via
libimage-sane-perl, scanimage or scanadf, and can scan multiple pages at
once. It presents a thumbnail view of scanned pages, and permits simple
operations such as cropping, rotating and deleting pages.

OCR can be used to recognise text in the scans, and the output
embedded in the PDF or DjVu.

PDF conversion is done by PDF::API2.

The resulting document may be saved as a PDF, DjVu, multipage TIFF file,
or single page image file.

Changelog for 2.0.1:
* Fixed editing OCR output
* Fixed displaying image after undoing
* Fixed displaying image after deleting page
* Fixed text in progress bars
* Fixed warning message clearing all pages if no scanner detected



signature.asc
Description: OpenPGP digital signature
-- 
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] daily git snapshots

[Olaf Meeuwissen]

Hi Rolf,

Rolf Bensch writes:

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

When you say "immediately", exactly how fast do you think they complete
:-P

Here's the time line of events:

 2018-03-11 11:08UTC: you pushed[1]
 2018-03-11 11:20UTC: archive build finished[2]

 [1]: 
https://gitlab.com/sane-project/backends/commit/a5ae2dad1d4202911be927933b8f8d6a8dde6413
 [2]: https://gitlab.com/sane-project/backends/pipelines/18712000/builds

The builds took a total of 11 minutes and 46 seconds (after a 13 second
wait) to complete.  I'd say give GitLab.com about 15-20 minutes for the
build to complete because it tests the build on *several* setups (as is
clear from [2]) and the archive is only updated when all succeed.

That said, I have experienced some delays occasionally when the updated
"new" website was being deployed, i.e. transferred to storage.  Anyway,
the archive appears to be available for download now.

I'm writing this an hour and five minutes after the build completed ;-)
I'd say that beats those daily snapshots hands down.  But that's not
really the point.  The point is that things happen automatically when
they make sense: build on push and update the archive if all parts of
the build completed successfully (for some definition of success).

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

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

[sane-devel] Who do I submit a How To for saned?

[ToddAndMargo]

Hi All,

I wrote up an very in depth How To on saned and Fedora.
It included all the annoying, missing steps you
get when your google how to do this.

Who would I submit it to get get in evaluated for
inclusion to Sane's How To's?

Many thanks,
-T


--
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] Trying to get up to speed with a "Mustek PageExpress A3 USB 1200 PRO" ...

[Gjermund Skogstad]

(I'm experiencing trouble with my email, so it's non-intentional if this 
message pops up more than once.)

As mentioned in my last post to this list I'm overwhelmed by other tasks for 
time being, but I did actually get the scanner to work on an old 'buntu and 
simply forgot to post a link about the work to this list.
My deepest apologies being a headless sponge, and for all I know someone 
may find it useful, so here's a link:
https://skogstad.org/scanner/

When I get time to take a closer look at this again I'll share whatever I may 
discover with the community. (I've noticed that there's change on the horizon 
regarding this email-list, but I'll try to share with the community regardless 
how the solution presents itself.)


-- 
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] [solved] Re: Saned and root privileges ????

[ToddAndMargo]

On 03/10/2018 01:01 PM, ToddAndMargo wrote:

On 03/10/2018 12:44 PM, ToddAndMargo wrote:

On 03/10/2018 12:23 PM, ToddAndMargo wrote:

On 03/10/2018 09:22 AM, Andrew Goodbody wrote:



On 10/03/18 11:17, ToddAndMargo wrote:

On 03/10/2018 03:06 AM, Andrew Goodbody wrote:

On 10/03/18 04:59, ToddAndMargo wrote:

On 03/09/2018 12:53 PM, ToddAndMargo wrote:

Hi All,

Okay, now this is "scary".

Both xsane and Simple Scan work locally.

I can not get saned to work, UNLESS, I edit /etc/group
and add the following to root

root:x:0:saned

Without it, I get

$ xsane net:localhost:epkowa:interpreter:001:007
Access to resource has been denied

Now what am I doing wrong?  Must saned have root privileges?

Many thanks,
-T


I just caught this:

$ ps -eo pid,user,group,args --sort user | grep cups
  5005 root root /usr/sbin/cupsd -l

CUPS "is" running as root.  So is it okay to add
saned to root's group?


No, of course not, that's a huge security hole. Just because cups 
does it is no indication that saned should.


The problem could well be that the user saned does not have access 
to your scanner. So check that saned is a member of whichever 
group can access your scanner device. This may be 'scanner'.


Andrew


find /dev -iname \*scanner\*



Please keep this on the list.

What do the commands

lsusb -s 001:007

and

ls -l /dev/bus/usb/001/007

return?

Andrew


$ scanimage -L
device `epkowa:interpreter:001:007' is a Epson Perfection V300 
flatbed scanner


$ lsusb -s 001:007
Bus 001 Device 007: ID 04b8:0131 Seiko Epson Corp. GT-F720 
[GT-S620/Perfection V30/V300 Photo]


$ ls -l /dev/bus/usb/001/007
crw-rw-r--+ 1 root root 189, 6 Mar 10 12:03 /dev/bus/usb/001/007

$ ls -l /usr/lib/udev/rules.d | grep -i sane
-rw-r--r--. 1 root root   3934 Mar  9 12:21 65-sane-backends.rules

The following temporarily fixes the issue (saned removed from
root and a test to verify `xsane net:localhost` crashes before
throwing the following):

    # chown saned.saned ls -l /dev/bus/usb/001/007

But the scanner does not always mount on 001:007.
Power it off and back on and it mounts on 001:008, etc.


Does this lead us to a fix?

Many thanks,
-T


Now it has decided to give the list precedence!

Over on

https://bugzilla.redhat.com/show_bug.cgi?id=1091566#c8

   2. Permissions must be given to the saned user to access scanners.
   I don't have any scanners to test, but the following should work:

   # /usr/lib/udev/rules.d/70-saned.rules
   ACTION=="add", ENV{libsane_matched}=="yes", GROUP="saned", 
MODE="0660"



Is this something I should add to
 /usr/lib/udev/rules.d/65-sane-backends.rules
?



And that worked.

# rpm -qf /usr/lib/udev/rules.d/65-sane-backends.rules
sane-backends-1.0.27-12.fc27.x86_64

Ah Ha!

I just opened
https://bugzilla.redhat.com/show_bug.cgi?id=1554032

to fix this.

I have been trouybleshooting this since November
 AAH! 

Thank you all for all your help and patience with this!

-T





Note: you have to reboot to get this to take:

$ scanimage -L
device `epkowa:interpreter:001:003' is a Epson Perfection V300 flatbed 
scanner
device `net:localhost:epkowa:interpreter:001:003' is a Epson Perfection 
V300 flatbed scanner


$ xsane net:localhost
worked

Unplugging and replugging the scanner:
$ scanimage -L
device `epkowa:interpreter:001:008' is a Epson Perfection V300 flatbed 
scanner
device `net:localhost:epkowa:interpreter:001:008' is a Epson Perfection 
V300 flatbed scanner


$ xsane net:localhost
worked


--
~~~
Serious error.
All shortcuts have disappeared.
Screen. Mind. Both are blank.
~~~


--
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] [solved] Re: Saned and root privileges ????

[ToddAndMargo]

On 03/10/2018 12:44 PM, ToddAndMargo wrote:

On 03/10/2018 12:23 PM, ToddAndMargo wrote:

On 03/10/2018 09:22 AM, Andrew Goodbody wrote:



On 10/03/18 11:17, ToddAndMargo wrote:

On 03/10/2018 03:06 AM, Andrew Goodbody wrote:

On 10/03/18 04:59, ToddAndMargo wrote:

On 03/09/2018 12:53 PM, ToddAndMargo wrote:

Hi All,

Okay, now this is "scary".

Both xsane and Simple Scan work locally.

I can not get saned to work, UNLESS, I edit /etc/group
and add the following to root

root:x:0:saned

Without it, I get

$ xsane net:localhost:epkowa:interpreter:001:007
Access to resource has been denied

Now what am I doing wrong?  Must saned have root privileges?

Many thanks,
-T


I just caught this:

$ ps -eo pid,user,group,args --sort user | grep cups
  5005 root root /usr/sbin/cupsd -l

CUPS "is" running as root.  So is it okay to add
saned to root's group?


No, of course not, that's a huge security hole. Just because cups 
does it is no indication that saned should.


The problem could well be that the user saned does not have access 
to your scanner. So check that saned is a member of whichever group 
can access your scanner device. This may be 'scanner'.


Andrew


find /dev -iname \*scanner\*



Please keep this on the list.

What do the commands

lsusb -s 001:007

and

ls -l /dev/bus/usb/001/007

return?

Andrew


$ scanimage -L
device `epkowa:interpreter:001:007' is a Epson Perfection V300 flatbed 
scanner


$ lsusb -s 001:007
Bus 001 Device 007: ID 04b8:0131 Seiko Epson Corp. GT-F720 
[GT-S620/Perfection V30/V300 Photo]


$ ls -l /dev/bus/usb/001/007
crw-rw-r--+ 1 root root 189, 6 Mar 10 12:03 /dev/bus/usb/001/007

$ ls -l /usr/lib/udev/rules.d | grep -i sane
-rw-r--r--. 1 root root   3934 Mar  9 12:21 65-sane-backends.rules

The following temporarily fixes the issue (saned removed from
root and a test to verify `xsane net:localhost` crashes before
throwing the following):

    # chown saned.saned ls -l /dev/bus/usb/001/007

But the scanner does not always mount on 001:007.
Power it off and back on and it mounts on 001:008, etc.


Does this lead us to a fix?

Many thanks,
-T


Now it has decided to give the list precedence!

Over on

https://bugzilla.redhat.com/show_bug.cgi?id=1091566#c8

   2. Permissions must be given to the saned user to access scanners.
   I don't have any scanners to test, but the following should work:

   # /usr/lib/udev/rules.d/70-saned.rules
   ACTION=="add", ENV{libsane_matched}=="yes", GROUP="saned", 
MODE="0660"



Is this something I should add to
     /usr/lib/udev/rules.d/65-sane-backends.rules
?



And that worked.

# rpm -qf /usr/lib/udev/rules.d/65-sane-backends.rules
sane-backends-1.0.27-12.fc27.x86_64

Ah Ha!

I just opened
https://bugzilla.redhat.com/show_bug.cgi?id=1554032

to fix this.

I have been trouybleshooting this since November
 AAH! 

Thank you all for all your help and patience with this!

-T


--
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] bug in mailing list

[ToddAndMargo]

On 03/10/2018 12:04 PM, ToddAndMargo wrote:

On 03/10/2018 09:22 AM, Andrew Goodbody wrote:
 > Please keep this on the list.


This is caused by the following missing header in the eMail message:

Precedence: list

Currently, without this, Thunderbird thinks these messages are
regular conversations and gives the Reply All button precedence.
So, you wind up send out a lot of message to private addresses,
rather than the list's address or both.


Many thanks,
-T


Apparently, sometimes it does and sometimes it does not.


--
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] Saned and root privileges ????

[ToddAndMargo]

On 03/10/2018 12:23 PM, ToddAndMargo wrote:

On 03/10/2018 09:22 AM, Andrew Goodbody wrote:



On 10/03/18 11:17, ToddAndMargo wrote:

On 03/10/2018 03:06 AM, Andrew Goodbody wrote:

On 10/03/18 04:59, ToddAndMargo wrote:

On 03/09/2018 12:53 PM, ToddAndMargo wrote:

Hi All,

Okay, now this is "scary".

Both xsane and Simple Scan work locally.

I can not get saned to work, UNLESS, I edit /etc/group
and add the following to root

root:x:0:saned

Without it, I get

$ xsane net:localhost:epkowa:interpreter:001:007
Access to resource has been denied

Now what am I doing wrong?  Must saned have root privileges?

Many thanks,
-T


I just caught this:

$ ps -eo pid,user,group,args --sort user | grep cups
  5005 root root /usr/sbin/cupsd -l

CUPS "is" running as root.  So is it okay to add
saned to root's group?


No, of course not, that's a huge security hole. Just because cups 
does it is no indication that saned should.


The problem could well be that the user saned does not have access 
to your scanner. So check that saned is a member of whichever group 
can access your scanner device. This may be 'scanner'.


Andrew


find /dev -iname \*scanner\*



Please keep this on the list.

What do the commands

lsusb -s 001:007

and

ls -l /dev/bus/usb/001/007

return?

Andrew


$ scanimage -L
device `epkowa:interpreter:001:007' is a Epson Perfection V300 flatbed 
scanner


$ lsusb -s 001:007
Bus 001 Device 007: ID 04b8:0131 Seiko Epson Corp. GT-F720 
[GT-S620/Perfection V30/V300 Photo]


$ ls -l /dev/bus/usb/001/007
crw-rw-r--+ 1 root root 189, 6 Mar 10 12:03 /dev/bus/usb/001/007

$ ls -l /usr/lib/udev/rules.d | grep -i sane
-rw-r--r--. 1 root root   3934 Mar  9 12:21 65-sane-backends.rules

The following temporarily fixes the issue (saned removed from
root and a test to verify `xsane net:localhost` crashes before
throwing the following):

    # chown saned.saned ls -l /dev/bus/usb/001/007

But the scanner does not always mount on 001:007.
Power it off and back on and it mounts on 001:008, etc.


Does this lead us to a fix?

Many thanks,
-T


Now it has decided to give the list precedence!

Over on

https://bugzilla.redhat.com/show_bug.cgi?id=1091566#c8

  2. Permissions must be given to the saned user to access scanners.
  I don't have any scanners to test, but the following should work:

  # /usr/lib/udev/rules.d/70-saned.rules
  ACTION=="add", ENV{libsane_matched}=="yes", GROUP="saned", 
MODE="0660"



Is this something I should add to
/usr/lib/udev/rules.d/65-sane-backends.rules
?



--
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] Saned and root privileges ????

[ToddAndMargo]

one more:

$ grep lp /etc/group
lp:x:7:saned


--
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] Saned and root privileges ????

[ToddAndMargo]

On 03/10/2018 09:22 AM, Andrew Goodbody wrote:



On 10/03/18 11:17, ToddAndMargo wrote:

On 03/10/2018 03:06 AM, Andrew Goodbody wrote:

On 10/03/18 04:59, ToddAndMargo wrote:

On 03/09/2018 12:53 PM, ToddAndMargo wrote:

Hi All,

Okay, now this is "scary".

Both xsane and Simple Scan work locally.

I can not get saned to work, UNLESS, I edit /etc/group
and add the following to root

root:x:0:saned

Without it, I get

$ xsane net:localhost:epkowa:interpreter:001:007
Access to resource has been denied

Now what am I doing wrong?  Must saned have root privileges?

Many thanks,
-T


I just caught this:

$ ps -eo pid,user,group,args --sort user | grep cups
  5005 root root /usr/sbin/cupsd -l

CUPS "is" running as root.  So is it okay to add
saned to root's group?


No, of course not, that's a huge security hole. Just because cups 
does it is no indication that saned should.


The problem could well be that the user saned does not have access to 
your scanner. So check that saned is a member of whichever group can 
access your scanner device. This may be 'scanner'.


Andrew


find /dev -iname \*scanner\*



Please keep this on the list.

What do the commands

lsusb -s 001:007

and

ls -l /dev/bus/usb/001/007

return?

Andrew


$ scanimage -L
device `epkowa:interpreter:001:007' is a Epson Perfection V300 flatbed 
scanner


$ lsusb -s 001:007
Bus 001 Device 007: ID 04b8:0131 Seiko Epson Corp. GT-F720 
[GT-S620/Perfection V30/V300 Photo]


$ ls -l /dev/bus/usb/001/007
crw-rw-r--+ 1 root root 189, 6 Mar 10 12:03 /dev/bus/usb/001/007

$ ls -l /usr/lib/udev/rules.d | grep -i sane
-rw-r--r--. 1 root root   3934 Mar  9 12:21 65-sane-backends.rules

The following temporarily fixes the issue (saned removed from
root and a test to verify `xsane net:localhost` crashes before
throwing the following):

   # chown saned.saned ls -l /dev/bus/usb/001/007

But the scanner does not always mount on 001:007.
Power it off and back on and it mounts on 001:008, etc.


Does this lead us to a fix?

Many thanks,
-T



--
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] bug in mailing list

[ToddAndMargo]

On 03/10/2018 09:22 AM, Andrew Goodbody wrote:
> Please keep this on the list.


This is caused by the following missing header in the eMail message:

Precedence: list

Currently, without this, Thunderbird thinks these messages are
regular conversations and gives the Reply All button precedence.
So, you wind up send out a lot of message to private addresses,
rather than the list's address or both.


Many thanks,
-T



--
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] Bug in mailing list

[ToddAndMargo]

On 03/10/2018 09:22 AM, Andrew Goodbody wrote:

Please keep this on the list.



This is caused by the following missing header in the eAmil message:

Precedence: list

Currently, without this, Thunderbird thinks these messages are
regular conversations and gives the Reply All button precedence.
So, you wind up send out a lot of message to private addresses,
rather than the list's address or both.


Many thanks,
-T



--
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] Saned and root privileges ????

[Andrew Goodbody]

On 10/03/18 11:17, ToddAndMargo wrote:

On 03/10/2018 03:06 AM, Andrew Goodbody wrote:

On 10/03/18 04:59, ToddAndMargo wrote:

On 03/09/2018 12:53 PM, ToddAndMargo wrote:

Hi All,

Okay, now this is "scary".

Both xsane and Simple Scan work locally.

I can not get saned to work, UNLESS, I edit /etc/group
and add the following to root

root:x:0:saned

Without it, I get

$ xsane net:localhost:epkowa:interpreter:001:007
Access to resource has been denied

Now what am I doing wrong?  Must saned have root privileges?

Many thanks,
-T


I just caught this:

$ ps -eo pid,user,group,args --sort user | grep cups
  5005 root root /usr/sbin/cupsd -l

CUPS "is" running as root.  So is it okay to add
saned to root's group?


No, of course not, that's a huge security hole. Just because cups does 
it is no indication that saned should.


The problem could well be that the user saned does not have access to 
your scanner. So check that saned is a member of whichever group can 
access your scanner device. This may be 'scanner'.


Andrew


find /dev -iname \*scanner\*



Please keep this on the list.

What do the commands

lsusb -s 001:007

and

ls -l /dev/bus/usb/001/007

return?

Andrew

--
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] net.conf bug

[ToddAndMargo]

Hi All,

The comment section of /etc/sane.d/net.conf, state

## saned hosts
# Each line names a host to attach to.

This is confusing, if not inaccurate.  It should say

# List the name or IP of the server that the scanner
# to be shared is attached to

Reference: https://bugzilla.redhat.com/show_bug.cgi?id=1546433#c15

Many thanks,
-T







--
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] Saned and root privileges ????

[ToddAndMargo]

On 03/09/2018 12:53 PM, ToddAndMargo wrote:

Hi All,

Okay, now this is "scary".

Both xsane and Simple Scan work locally.

I can not get saned to work, UNLESS, I edit /etc/group
and add the following to root

root:x:0:saned

Without it, I get

$ xsane net:localhost:epkowa:interpreter:001:007
Access to resource has been denied

Now what am I doing wrong?  Must saned have root privileges?

Many thanks,
-T


I just caught this:

$ ps -eo pid,user,group,args --sort user | grep cups
 5005 root root /usr/sbin/cupsd -l

CUPS "is" running as root.  So is it okay to add
saned to root's group?




--
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] Epson Perfection V300 and the backend

[ToddAndMargo]

On 03/09/2018 02:35 AM, Olaf Meeuwissen wrote:

Hi Todd,

ToddAndMargo writes:


On 03/08/2018 03:09 AM, Olaf Meeuwissen wrote:


# Better quoting would be appreciated :-)


looking at
krarc:/home/CDs/Linux/Epson/iscan-gt-f720-bundle-1.0.1.x64.rpm/data/iscan-data-1.36.0-1.noarch.rpm/usr/share/iscan-data/device/

I only find an XML for the Perfection V800.


The presence of an XML file for your device is not a hard requirement,
IIRC.  The fact that scanimage lists your V300 would be proof of that.
If you can actually scan with scanimage even more so.  If you can scan
with scanimage then the V300 _is_ supported by the epkowa backend.

If, on the same machine and with the same permissions, saned is not able
to detect the device, then there is something wrong with your saned
configuration iself or with the way saned is started by, I presume,
systemd.


Figured it out.  I had to add saned to root in /etc/group.  I
made a separate posting on this to find out the ramifications
and if there is a way around it.


--
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] Saned and root privileges ????

[ToddAndMargo]

Hi All,

Okay, now this is "scary".

Both xsane and Simple Scan work locally.

I can not get saned to work, UNLESS, I edit /etc/group
and add the following to root

root:x:0:saned

Without it, I get

$ xsane net:localhost:epkowa:interpreter:001:007
Access to resource has been denied

Now what am I doing wrong?  Must saned have root privileges?

Many thanks,
-T



--
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] Epson Perfection V300 and the backend

[Olaf Meeuwissen]

Hi Todd,

ToddAndMargo writes:

> On 03/08/2018 03:09 AM, Olaf Meeuwissen wrote:

# Better quoting would be appreciated :-)

> looking at
> krarc:/home/CDs/Linux/Epson/iscan-gt-f720-bundle-1.0.1.x64.rpm/data/iscan-data-1.36.0-1.noarch.rpm/usr/share/iscan-data/device/
>
> I only find an XML for the Perfection V800.

The presence of an XML file for your device is not a hard requirement,
IIRC.  The fact that scanimage lists your V300 would be proof of that.
If you can actually scan with scanimage even more so.  If you can scan
with scanimage then the V300 _is_ supported by the epkowa backend.

If, on the same machine and with the same permissions, saned is not able
to detect the device, then there is something wrong with your saned
configuration iself or with the way saned is started by, I presume,
systemd.

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] Epson Perfection V300 and the backend

[ToddAndMargo]

On 03/08/2018 03:09 AM, Olaf Meeuwissen wrote:

looking at 
krarc:/home/CDs/Linux/Epson/iscan-gt-f720-bundle-1.0.1.x64.rpm/data/iscan-data-1.36.0-1.noarch.rpm/usr/share/iscan-data/device/


I only find an XML for the Perfection V800.


--
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] Epson Perfection V300 and the backend

[ToddAndMargo]

On 03/08/2018 03:09 AM, Olaf Meeuwissen wrote:

You are of course looking at the saned output from a saned that runs on
the machine to which your V300 is connected, right?


yes


--
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] Epson Perfection V300 and the backend

[ToddAndMargo]

On 03/08/2018 03:09 AM, Olaf Meeuwissen wrote:

Hi Todd,

ToddAndMargo writes:


Hi All,

Fedora 27
iscan-gt-f720-bundle-1.0.1.x64.rpm

By change is the Epson Perfection V300 included in
the rpm's front end, but not its back end?


I just remembered I wrote a section about the network configuration for
iscan a decade or so ago.  Have a look at

   http://download.ebz.epson.net/man/linux/iscan_e.html#sec7

and see if some of that helps.


I will look on Friday when I get some more office time.
Thank you!





Scanimage can find it,

$ scanimage -L
device `epkowa:interpreter:001:008' is a Epson Perfection V300 flatbed
scanner

but saned cannot.

saned[16940]: [net] sane_init: done
saned[16940]: [dll] init: backend `net' is version 1.0.27
saned[16940]: [net] sane_get_devices: local_only = 1
saned[16940]: [dll] sane_get_devices: found 0 devices
saned[16940]: saned exiting

If not, how do I get the V300 into the back end?


Does saned's dll load the epkowa backend?  I think you can check by
running it in standalone mode and get the dll backend to output the
debug info with

   sudo SANE_DEBUG_DLL=128 saned -d128

You are of course looking at the saned output from a saned that runs on
the machine to which your V300 is connected, right?


Looking at

   # journalctl -efx -t saned > /home/temp/saned.log.epson4.txt

After running `xsane net:localhost`, it seems like I
have hundreds of "epkowa" entries, but nothing with a
"300" in it.

This is why I am suspicious of the V300 not being
supported in the back end.



--
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] Epson Perfection V300 and the backend

[Olaf Meeuwissen]

Hi Todd,

ToddAndMargo writes:

> Hi All,
>
> Fedora 27
> iscan-gt-f720-bundle-1.0.1.x64.rpm
>
> By change is the Epson Perfection V300 included in
> the rpm's front end, but not its back end?

I just remembered I wrote a section about the network configuration for
iscan a decade or so ago.  Have a look at

  http://download.ebz.epson.net/man/linux/iscan_e.html#sec7

and see if some of that helps.

> Scanimage can find it,
>
> $ scanimage -L
> device `epkowa:interpreter:001:008' is a Epson Perfection V300 flatbed
> scanner
>
> but saned cannot.
>
> saned[16940]: [net] sane_init: done
> saned[16940]: [dll] init: backend `net' is version 1.0.27
> saned[16940]: [net] sane_get_devices: local_only = 1
> saned[16940]: [dll] sane_get_devices: found 0 devices
> saned[16940]: saned exiting
>
> If not, how do I get the V300 into the back end?

Does saned's dll load the epkowa backend?  I think you can check by
running it in standalone mode and get the dll backend to output the
debug info with

  sudo SANE_DEBUG_DLL=128 saned -d128

You are of course looking at the saned output from a saned that runs on
the machine to which your V300 is connected, right?

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

[sane-devel] gscan2pdf v2.0.0 released

[Jeff]

gscan2pdf - A GUI to produce a multipage PDF or DjVu from a scan.

http://gscan2pdf.sourceforge.net/

Five clicks are required to scan several pages and then save all or
a selection as a PDF or DjVu file, including metadata if required.

gscan2pdf can control regular or sheet-fed (ADF) scanners with SANE via
libimage-sane-perl, scanimage or scanadf, and can scan multiple pages at
once. It presents a thumbnail view of scanned pages, and permits simple
operations such as cropping, rotating and deleting pages.

OCR can be used to recognise text in the scans, and the output
embedded in the PDF or DjVu.

PDF conversion is done by PDF::API2.

The resulting document may be saved as a PDF, DjVu, multipage TIFF file,
or single page image file.

Changelog for 2.0.0:
* Switch from gtk+-2 to gtk+-3, requiring the reimplementation of
  GtkImageview in pure Perl, as C library not compatible with gtk+-3.
* Fixed ghosting if flatbed only source option but not set.
  Closes #290 (Page Options -> Pages: scanning only first page of n)
* Fixed setting preferences if frontend not set to libsane-image-perl
  and no scanner available. Closes #291 (Cannot change temporary
  directory)



signature.asc
Description: OpenPGP digital signature
-- 
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] Epson Perfection V300 and the backend

[ToddAndMargo]

Hi All,

Fedora 27
iscan-gt-f720-bundle-1.0.1.x64.rpm


By change is the Epson Perfection V300 included in
the rpm's front end, but not its back end?

Scanimage can find it,

$ scanimage -L
device `epkowa:interpreter:001:008' is a Epson Perfection V300 flatbed 
scanner


but saned cannot.

saned[16940]: [net] sane_init: done
saned[16940]: [dll] init: backend `net' is version 1.0.27
saned[16940]: [net] sane_get_devices: local_only = 1
saned[16940]: [dll] sane_get_devices: found 0 devices
saned[16940]: saned exiting

If not, how do I get the V300 into the back end?

Many thanks,
-T


--
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] HP5590 and scanbd button recognition

[Jared Hedegaard]

Thank you both Ilia and Wilhem.
I'll be testing out scanbuttond backends in the next day or two. 

Ilia, if you need assistance testing any changes, I'd be willing to help if 
need be. I've taken a peek at the backend code, and did see the function you 
mentioned, so I can do a little tinkering on in. Thanks for the insight.

Jared

On March 7, 2018 6:01 AM, Ilia Sotnikov  wrote:

> ​​
> 
> Hi,
> 
> backend author here - it shouldn't be too much of effort to expose
> 
> button status so scanbd can use it. Though haven't gone thru its
> 
> documentation to understand requirements. As a technical insight -
> 
> there is hp5590\_read\_buttons() function in hp5590_cmds.c that reads
> 
> button status.
> 
> However, I'll seek for a volunteer to test a change as I don't have
> 
> access to HW currently.
> 
> On Wed, Mar 7, 2018 at 12:40 AM, Wilhelm Meier
> 
> wilhelm.wm.me...@googlemail.com wrote:
> 
> > Please try the old scanbuttond-backend for this type of scanner - it
> > 
> > should work. The HP sane backend sadly doesn't support the buttons on
> > 
> > this scanner.
> > 
> > Am 06.03.2018 um 15:46 schrieb Jared Hedegaard:
> > 
> > > > Main question: does the HP 5590 support button presses or am I just 
> > > > setting this up incorrectly?
> > > > 
> > > > I'm been successful using scanbd with SANE backends to get scanning 
> > > > working over my network and locally on the host machine, but I can't 
> > > > seem to get it to recognize button presses, either running scanbd in 
> > > > foreground or background.
> > > > 
> > > > For past testing, it seems that actions defined in scanbd.conf are used 
> > > > to tie to the backend options? From searching /var/log/syslog, I 
> > > > expected to track button presses or get some sort of trigger feedback, 
> > > > and I didn't think I needed an action set up for it.
> > > > 
> > > > Any help on this one would be much appreciated. Thanks.
> > > > 
> > > > Jared H
> > > 
> > > After a bit more research, it looks like doing this with the SANE backend 
> > > for HP 5590 is not possible. scanbd is used to tie custom actions to the 
> > > options available on the scanner. In this case, none of the 10 options 
> > > seem to return values. They all look to be ones that I designate from 
> > > some client software.
> > > 
> > > scanbd: found active option\[1\] tl-x (type: 2) for device 
> > > hp5590:libusb:001:008
> > > 
> > > scanbd: found active option\[2\] tl-y (type: 2) for device 
> > > hp5590:libusb:001:008
> > > 
> > > scanbd: found active option\[3\] br-x (type: 2) for device 
> > > hp5590:libusb:001:008
> > > 
> > > scanbd: found active option\[4\] br-y (type: 2) for device 
> > > hp5590:libusb:001:008
> > > 
> > > scanbd: found active option\[5\] mode (type: 3) for device 
> > > hp5590:libusb:001:008
> > > 
> > > scanbd: found active option\[6\] source (type: 3) for device 
> > > hp5590:libusb:001:008
> > > 
> > > scanbd: found active option\[7\] resolution (type: 1) for device 
> > > hp5590:libusb:001:008 scanbd: found active option\[8\] 
> > > extend-lamp-timeout (type: 0) for device hp5590:libusb:001:008
> > > 
> > > scanbd: found active option\[9\] wait-for-button (type: 0) for device 
> > > hp5590:libusb:001:008
> > > 
> > > scanbd: found active option\[10\] preview (type: 0) for device 
> > > hp5590:libusb:001:008
> > > 
> > > In this case, it looks like I will have to try the old scanbuttond 
> > > backends for this, or see if there are optional enhancements for the SANE 
> > > hp5590 backend.
> > > 
> > > Jared
> > 
> > --
> > 
> > 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
> 
> --
> 
> Ilia Sotnikov
> -
> 
> sane-devel mailing list: sane-devel@lists.alioth.debian.org
> 
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
> 
> Unsubscribe: Send mail with subject "unsubscribe your_password"
> 
> to sane-devel-requ...@lists.alioth.debian.org



-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] HP5590 and scanbd button recognition

[Ilia Sotnikov]

Hi,
backend author here - it shouldn't be too much of effort to expose
button status so scanbd can use it. Though haven't gone thru its
documentation to understand requirements. As a technical insight -
there is hp5590_read_buttons() function in hp5590_cmds.c that reads
button status.
However, I'll seek for a volunteer to test a change as I don't have
access to HW currently.

On Wed, Mar 7, 2018 at 12:40 AM, Wilhelm Meier
 wrote:
> Please try the old scanbuttond-backend for this type of scanner - it
> should work. The HP sane backend sadly doesn't support the buttons on
> this scanner.
>
> Am 06.03.2018 um 15:46 schrieb Jared Hedegaard:
>>>
>>> Main question: does the HP 5590 support button presses or am I just setting 
>>> this up incorrectly?
>>>
>>> I'm been successful using scanbd with SANE backends to get scanning working 
>>> over my network and locally on the host machine, but I can't seem to get it 
>>> to recognize button presses, either running scanbd in foreground or 
>>> background.
>>>
>>> For past testing, it seems that actions defined in scanbd.conf are used to 
>>> tie to the backend options? From searching /var/log/syslog, I expected to 
>>> track button presses or get some sort of trigger feedback, and I didn't 
>>> think I needed an action set up for it.
>>>
>>> Any help on this one would be much appreciated. Thanks.
>>>
>>> Jared H
>>>
>>
>> After a bit more research, it looks like doing this with the SANE backend 
>> for HP 5590 is not possible. scanbd is used to tie custom actions to the 
>> options available on the scanner. In this case, none of the 10 options seem 
>> to return values. They all look to be ones that I designate from some client 
>> software.
>>
>> scanbd: found active option[1] tl-x (type: 2) for device 
>> hp5590:libusb:001:008
>> scanbd: found active option[2] tl-y (type: 2) for device 
>> hp5590:libusb:001:008
>> scanbd: found active option[3] br-x (type: 2) for device 
>> hp5590:libusb:001:008
>> scanbd: found active option[4] br-y (type: 2) for device 
>> hp5590:libusb:001:008
>> scanbd: found active option[5] mode (type: 3) for device 
>> hp5590:libusb:001:008
>> scanbd: found active option[6] source (type: 3) for device 
>> hp5590:libusb:001:008
>> scanbd: found active option[7] resolution (type: 1) for device 
>> hp5590:libusb:001:008 scanbd: found active option[8] extend-lamp-timeout 
>> (type: 0) for device hp5590:libusb:001:008
>> scanbd: found active option[9] wait-for-button (type: 0) for device 
>> hp5590:libusb:001:008
>> scanbd: found active option[10] preview (type: 0) for device 
>> hp5590:libusb:001:008
>>
>> In this case, it looks like I will have to try the old scanbuttond backends 
>> for this, or see if there are optional enhancements for the SANE hp5590 
>> backend.
>>
>> Jared
>>
>
>
> --
> 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



-- 
 Ilia Sotnikov

-- 
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] Fwd: Help Please with Nikon Super Coolscan 4000 ED

[Bob Louden]

Please see forwarded note -- I sent it before subscribing to the SANE
mailing list - and so am resending.

Thanks,

   Bob


-- Forwarded message --
From: Bob Louden 
Date: Tue, Mar 6, 2018 at 5:34 PM
Subject: Help Please with Nikon Super Coolscan 4000 ED
To: sane-devel@lists.alioth.debian.org


Dear mailing list.  Please excuse me if I am not using this mailing list
properly.

I created a request for help a few days ago in the Linux Mint Hardware
forum but have not had any luck with responses.

I have this very nice, albeit old, scanner that I cannot get to work --
though I feel like I am very close to having it work.  Alas, I am on the
brink of giving up on it.  I also have this not-as-good Plustek scanner
that I've started messing with and it was from searching for help with it
that I found your mailing list.

Anyway, if there is anyone out there who might be able to help me, here is
a link to my Linux Mint forum post:  https://forums.
linuxmint.com/viewtopic.php?f=51=264978

Please feel free to respond to me via either email or in the forum.

Thank you.

 Bob



-- 

https://www.google.com/+BobLouden


“Simple can be harder than complex: You have to work hard to get your
thinking clean to make it simple. But it’s worth it in the end because once
you get there, you can move mountains.” Steve Jobs [BusinessWeek, May 25,
1998 ]



-- 

https://www.google.com/+BobLouden


“Simple can be harder than complex: You have to work hard to get your
thinking clean to make it simple. But it’s worth it in the end because once
you get there, you can move mountains.” Steve Jobs [BusinessWeek, May 25,
1998 ]
-- 
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] HP5590 and scanbd button recognition

[Wilhelm Meier]

Please try the old scanbuttond-backend for this type of scanner - it
should work. The HP sane backend sadly doesn't support the buttons on
this scanner.

Am 06.03.2018 um 15:46 schrieb Jared Hedegaard:
>>
>> Main question: does the HP 5590 support button presses or am I just setting 
>> this up incorrectly?
>>
>> I'm been successful using scanbd with SANE backends to get scanning working 
>> over my network and locally on the host machine, but I can't seem to get it 
>> to recognize button presses, either running scanbd in foreground or 
>> background.
>>
>> For past testing, it seems that actions defined in scanbd.conf are used to 
>> tie to the backend options? From searching /var/log/syslog, I expected to 
>> track button presses or get some sort of trigger feedback, and I didn't 
>> think I needed an action set up for it.
>>
>> Any help on this one would be much appreciated. Thanks.
>>
>> Jared H
>>
> 
> After a bit more research, it looks like doing this with the SANE backend for 
> HP 5590 is not possible. scanbd is used to tie custom actions to the options 
> available on the scanner. In this case, none of the 10 options seem to return 
> values. They all look to be ones that I designate from some client software.
> 
> scanbd: found active option[1] tl-x (type: 2) for device 
> hp5590:libusb:001:008 
> scanbd: found active option[2] tl-y (type: 2) for device 
> hp5590:libusb:001:008 
> scanbd: found active option[3] br-x (type: 2) for device 
> hp5590:libusb:001:008 
> scanbd: found active option[4] br-y (type: 2) for device 
> hp5590:libusb:001:008 
> scanbd: found active option[5] mode (type: 3) for device 
> hp5590:libusb:001:008 
> scanbd: found active option[6] source (type: 3) for device 
> hp5590:libusb:001:008 
> scanbd: found active option[7] resolution (type: 1) for device 
> hp5590:libusb:001:008 scanbd: found active option[8] extend-lamp-timeout 
> (type: 0) for device hp5590:libusb:001:008 
> scanbd: found active option[9] wait-for-button (type: 0) for device 
> hp5590:libusb:001:008 
> scanbd: found active option[10] preview (type: 0) for device 
> hp5590:libusb:001:008
> 
> In this case, it looks like I will have to try the old scanbuttond backends 
> for this, or see if there are optional enhancements for the SANE hp5590 
> backend.
> 
> Jared
> 


-- 
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] HP5590 and scanbd button recognition

[Jared Hedegaard]

> 
> Main question: does the HP 5590 support button presses or am I just setting 
> this up incorrectly?
> 
> I'm been successful using scanbd with SANE backends to get scanning working 
> over my network and locally on the host machine, but I can't seem to get it 
> to recognize button presses, either running scanbd in foreground or 
> background.
> 
> For past testing, it seems that actions defined in scanbd.conf are used to 
> tie to the backend options? From searching /var/log/syslog, I expected to 
> track button presses or get some sort of trigger feedback, and I didn't think 
> I needed an action set up for it.
> 
> Any help on this one would be much appreciated. Thanks.
> 
> Jared H
> 

After a bit more research, it looks like doing this with the SANE backend for 
HP 5590 is not possible. scanbd is used to tie custom actions to the options 
available on the scanner. In this case, none of the 10 options seem to return 
values. They all look to be ones that I designate from some client software.

scanbd: found active option[1] tl-x (type: 2) for device hp5590:libusb:001:008 
scanbd: found active option[2] tl-y (type: 2) for device hp5590:libusb:001:008 
scanbd: found active option[3] br-x (type: 2) for device hp5590:libusb:001:008 
scanbd: found active option[4] br-y (type: 2) for device hp5590:libusb:001:008 
scanbd: found active option[5] mode (type: 3) for device hp5590:libusb:001:008 
scanbd: found active option[6] source (type: 3) for device 
hp5590:libusb:001:008 
scanbd: found active option[7] resolution (type: 1) for device 
hp5590:libusb:001:008 scanbd: found active option[8] extend-lamp-timeout (type: 
0) for device hp5590:libusb:001:008 
scanbd: found active option[9] wait-for-button (type: 0) for device 
hp5590:libusb:001:008 
scanbd: found active option[10] preview (type: 0) for device 
hp5590:libusb:001:008

In this case, it looks like I will have to try the old scanbuttond backends for 
this, or see if there are optional enhancements for the SANE hp5590 backend.

Jared

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

[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] 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] HP5590 and scanbd button recognition

[Jared Hedegaard]

Main question: does the HP 5590 support button presses or am I just setting 
this up incorrectly? 

I'm been successful using scanbd with SANE backends to get scanning working 
over my network and locally on the host machine, but I can't seem to get it to 
recognize button presses, either running scanbd in foreground or background.

For past testing, it seems that actions defined in scanbd.conf are used to tie 
to the backend options? From searching /var/log/syslog, I expected to track 
button presses or get some sort of trigger feedback, and I didn't think I 
needed an action set up for it.

Any help on this one would be much appreciated. Thanks.

Jared H

Details Below:
==
I've got an HP ScanJet 5590 connected via USB to my raspberry pi with Raspbian 
9 (Stretch).
sane 1.0.14-12 armhf
scanbd 1.4.4-1+b1 armhf
Both provided by the package manager. I've tried to keep it as close to the way 
it is set up by default. I've changed dll.conf and net.conf in the /etc/sane.d 
folder.

$ cat /etc/sane.d/dll.conf
net

$ cat /etc/sane.d/net.conf 
connect_timeout = 5
localhost

I've copied saned.conf from /etc/sane.d and added a soft link to 
/usr/share/scanbd/scripts/ as scripts into /etc/scanbd. Adjusted dll.conf and 
minor edits on scanbd.conf

$ cat /etc/scanbd/dll.conf
hp5590

$ cat /etc/scanbd/saned.conf
localhost
laptop.luthr.net

$ cat /etc/scanbd/scanbd.conf
$ cat /etc/scanbd/scanbd.conf

global {

debug   = true 
debug-level = 7
user= saned
group   = scanner

# the saned executable for manager-mode
saned   = "/usr/sbin/saned"
saned_opt  = { } # string-list
saned_env  = { "SANE_CONFIG_DIR=/etc/scanbd" } # list of environment 
vars for saned

scriptdir = /etc/scanbd/scripts
device_insert_script = "insert.script"

timeout = 500 
pidfile = "/var/run/scanbd.pid"

# env-vars for the scripts
environment {
# pass the device label as below in this env-var
device = "SCANBD_DEVICE"
# pass the action label as below in this env-var
action = "SCANBD_ACTION"
}

function function_knob {
filter = "^message.*"
desc   = "The value of the function knob / wheel / selector"
env= "SCANBD_FUNCTION" 
}
function function_mode {
filter = "^mode.*"
desc   = "Color mode"
env= "SCANBD_FUNCTION_MODE" 
}

multiple_actions = true # allow multiple actions per option (up to the 
total amount of options)

action scan {
filter = "^scan.*"
numerical-trigger {
from-value = 1
to-value   = 0
}
desc   = "Scan to file"
# script must be an relative path starting from scriptdir (see 
above), 
# or an absolute pathname. 
# It must contain the path to the action script without 
arguments
# Absolute path example: script = "/some/path/foo.script 
script = "test.script"
}
action button {
filter = "^but.*"
desc = "Testing a button press"
script = "test.script"
}
}

include(scanner.d/hp.conf)



I can access the scanner from the local client and over the network using the 
the net: backend.

@pi$ pidof scanbd && SANE_CONFIG_DIR=/etc/sane.d scanimage -L
797
device `net:localhost:hp5590:libusb:001:008' is a HP 5590 Workgroup scanner

@pi$ SANE_CONFIG_DIR=/etc/scanbd scanimage -L
device `hp5590:libusb:001:008' is a HP 5590 Workgroup scanner

Running interactively:
$ SANE_CONFIG_DIR=/etc/scanbd scanbd -d7 -f -c /etc/scanbd/scanbd.conf

scanbd: foreground
scanbd: config-file: /etc/scanbd/scanbd.conf
scanbd: reading config file /etc/scanbd/scanbd.conf
scanbd: debug on: level: 7
scanbd: dropping privs to uid saned
scanbd: dropping privs to gid scanner
scanbd: group scanner has member: 
scanbd: saned
scanbd: pi
scanbd: jaredh
scanbd: dispatcher
scanbd: drop privileges to gid: 113
scanbd: Can't set the effective gid to 113
scanbd: drop privileges to uid: 109
scanbd: Can't set the effective uid to 109
scanbd: dbus_init
scanbd: dbus match type='signal',interface='org.freedesktop.Hal.Manager'
scanbd: SANE_CONFIG_DIR=/etc/scanbd
scanbd: sane version 1.0
scanbd: Scanning for local-only devices
scanbd: found device: hp5590:libusb:001:008 HP 5590 Workgroup scanner
scanbd: start_sane_threads
scanbd: Starting poll thread for hp5590:libusb:001:008
scanbd: Thread started for device hp5590:libusb:001:008
scanbd: start dbus thread
scanbd: sane_poll
scanbd: found 11 options for device hp5590:libusb:001:008
scanbd: sane_find_matching_options
scanbd: Not Primary Owner (-1)
scanbd: Name Error (Connection ":1.9" is not allowed to own the service 

Re: [sane-devel] daily git snapshots

[Olaf Meeuwissen]

Hi Rolf,

Rolf Bensch writes:

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

Sorry about that.  Should be fixed now.

# 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

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?

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

[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] Canon MX922 scan error

[Louis Lagendijk]

On Sun, 2018-02-25 at 14:45 -0400, J. Paul Bissonnette wrote:
> On Sat, 24 Feb 2018 15:14:22 +0100
> Louis Lagendijk  wrote:

Can you please do the following (as root):


tcpdump host 
and then in a different window:
scanimage -L


Given the fact that the scanner does not work on USB either, this is
not going to help. @Rolf Bensch: do you have any idea why the MX922
stopped working? 

> I checked the scanner with windows 7, the scanner is functional.
> 
> jpb@maple:~$ sudo tcpdump host 192.168.0.108
> [sudo] password for jpb: 
> tcpdump: verbose output suppressed, use -v or -vv for full protocol
> decode listening on eno1, link-type EN10MB (Ethernet), capture size
> 262144 bytes 08:54:51.457427 IP 192.168.0.108.8612 >
> 192.168.0.5.8612:
> UDP, length 32 08:54:51.457464 IP 192.168.0.108.8612 >
> 192.168.0.5.8612: UDP, length 32 08:54:51.522781 IP 192.168.0.5.58749
> >
> 192.168.0.108.8612: UDP, length 16 08:54:51.524481 IP
> 192.168.0.108.8612 > 192.168.0.5.58749: UDP, length 32
> 08:54:51.524629
> IP 192.168.0.5.58617 > 192.168.0.108.8612: UDP, length 16
> 08:54:51.526334 IP 192.168.0.108.8612 > 192.168.0.5.58617: UDP,
> length
> 117 08:54:51.571296 IP 192.168.0.5.50297 > 192.168.0.108.8612: UDP,
> length 16 08:54:51.573604 IP 192.168.0.108.8612 > 192.168.0.5.50297:
> UDP, length 32 08:54:56.821491 ARP, Request who-has 192.168.0.108
> tell
> 192.168.0.5, length 28 08:54:56.822500 ARP, Reply 192.168.0.108 is-at
> 00:bb:c1:22:e6:97 (oui Unknown), length 46
> 
> jpb@maple:~$  scanimage -L
> device `pixma:MX920_192.168.0.108' is a CANON Canon PIXMA MX920
> Series
> multi-function peripheral
> 
> 
> 1) Connect the scanner using a USB cable. Does it work? No
-> so here is the issue: there is a problem in the backend itself, as
bjnp just changes the interface but the actual scanner handling is
exactly the same as for USB. We need input from Rolf Bensch as he knows
much more about the scanning code then I do

> 
>  xsane -v
> xsane-0.999 (c) 1998-2013 Oliver Rauch
>   E-mail: oliver.ra...@xsane.org
>   package xsane-0.999
>   compiled with GTK-2.24.29
>   with color management function
>   with GIMP support, compiled with GIMP-2.8.16
>   XSane output formats: jpeg, pdf(compr.), png, pnm, ps(compr.),
> tiff,
>  txt jpb@maple:~$ 

Try scanimage before going to xsane. Scanimage is easier to use from
the command line and has some debugging options as well.


> 1st click on scan error
> [bjnp] bjnp_open_tcp: ERROR - Can not connect to scanner: Connection
> refused 2nd click no error
> save number is advanced from 001.jpeg to 002.jpeg
> 1st click on scan error
> [bjnp] bjnp_open_tcp: ERROR - Can not connect to scanner: Connection
> refused 2nd click no error
> the save number is advanced
> 
Please note that you need to power cycle the scanner when you get the
TCP connect error and probably for USB as well.


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] Canon MX922 scan error

[J. Paul Bissonnette]

On Sat, 24 Feb 2018 15:14:22 +0100
Louis Lagendijk  wrote:

> On Fri, 2018-02-23 at 15:20 -0400, J. Paul Bissonnette wrote:
> > 
> > Sanner is discoverable and on the same net
> > 
> > I set the Firewall  
> > BJNP8612-8612   TCP 8612-8612
> > Problem even when firewall is disabled
> >   
> Ok, when the firewall is off and the problem still occurs, that can't
> be the poblem. In any case you will have to allow UDP as well. 
> The protocol uses both TCP and UDP.
> > Man sane-pixma claims the MX920 series is supported
> > output frpm avahi-discover
> > jpb@maple:~$ avahi-discover
> > Browsing domain 'local' on -1.-1 ...
> > 
> > '_canon-bjnp1._tcp' in domain 'local' on 2.0 ... Browsing for
> > services  
> Ok, bjnp is supported, good
> 
> Can you please do the following (as root):
> Z%230
tcpdump host 
> 
> and then in a different window:
> scanimage -L
> 
> and mail me the output of both commands?
> 
> Some things you should try first:
> 1) Connect the scanner usinga USB cable. Does itwork?
> 
> 2) Is the scanner connected over WIFI?
> If so and you have a recent sane version, you could try to define to
> define the scanner using a timeout value (e.g. at the start of the
> file specify
> bjnp-timeout=5000
> See the description in the /etc/sane.d/pixma.conf (or whatever path
> your distribution uses). The timeout parameter is supported since
> sane- backends 1.0.27.
> What OS/distribution are you using?
> 
> /Kind regards, Louis
> 

I checked the scanner with windows 7, the scanner is functional.

jpb@maple:~$ sudo tcpdump host 192.168.0.108
[sudo] password for jpb: 
tcpdump: verbose output suppressed, use -v or -vv for full protocol
decode listening on eno1, link-type EN10MB (Ethernet), capture size
262144 bytes 08:54:51.457427 IP 192.168.0.108.8612 > 192.168.0.5.8612:
UDP, length 32 08:54:51.457464 IP 192.168.0.108.8612 >
192.168.0.5.8612: UDP, length 32 08:54:51.522781 IP 192.168.0.5.58749 >
192.168.0.108.8612: UDP, length 16 08:54:51.524481 IP
192.168.0.108.8612 > 192.168.0.5.58749: UDP, length 32 08:54:51.524629
IP 192.168.0.5.58617 > 192.168.0.108.8612: UDP, length 16
08:54:51.526334 IP 192.168.0.108.8612 > 192.168.0.5.58617: UDP, length
117 08:54:51.571296 IP 192.168.0.5.50297 > 192.168.0.108.8612: UDP,
length 16 08:54:51.573604 IP 192.168.0.108.8612 > 192.168.0.5.50297:
UDP, length 32 08:54:56.821491 ARP, Request who-has 192.168.0.108 tell
192.168.0.5, length 28 08:54:56.822500 ARP, Reply 192.168.0.108 is-at
00:bb:c1:22:e6:97 (oui Unknown), length 46

jpb@maple:~$  scanimage -L
device `pixma:MX920_192.168.0.108' is a CANON Canon PIXMA MX920 Series
multi-function peripheral


1) Connect the scanner using a USB cable. Does it work? No
2) Is the scanner connected over WIFI? Yes

Canon firmware is V 3.031

 uname -a
Linux maple 4.15.5-041505-lowlatency #201802221031 SMP PREEMPT Thu Feb
 22 15:35:41 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

 xsane -v
xsane-0.999 (c) 1998-2013 Oliver Rauch
  E-mail: oliver.ra...@xsane.org
  package xsane-0.999
  compiled with GTK-2.24.29
  with color management function
  with GIMP support, compiled with GIMP-2.8.16
  XSane output formats: jpeg, pdf(compr.), png, pnm, ps(compr.), tiff,
 txt jpb@maple:~$ 


I works sort of now 
by setting bjnp-timeout=5000 
timeout at 5000 seemed too slow of a response time

Save scan
set bjnp-timeout=1000

1st click on scan error
[bjnp] bjnp_open_tcp: ERROR - Can not connect to scanner: Connection
refused 2nd click no error
save number is advanced from 001.jpeg to 002.jpeg
1st click on scan error
[bjnp] bjnp_open_tcp: ERROR - Can not connect to scanner: Connection
refused 2nd click no error
the save number is advanced

I want to thank you for the help
too bad Canon was not a bit more Linux friendly.
This is the first canon scanner I have owned all the others for the
last 20 years were either HP or Epson. They just simply work.
anyways thanks again the scanner limps along now which was more that it
has in a long time.

Has something been changed with the drivers lately this scaner worked
fair when I bought it then it quit. Ubuntu form made a few suggestions,
it worked for a while then recently quit again.
 I have been using the drivers from the
PPA..launchpad.net/rolfbensch/sane-release/ubuntu


-- 
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] Mustek scanner problem

[Olaf Meeuwissen]

Hi Chris,

Chris Widdows writes:

> Made the changes, but it is not recognised. XSane seems to only pickup
> on my webcam. I ran sane-find-scanner as root and this is what I got:
>
>> 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=0x138a, product=0x0011) at libusb:003:005
> found USB scanner (vendor=0x055f, product=0x050c, chip=GL128) at
> libusb:001:003
>  # 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.
>> scanimage -L
> device `v4l:/dev/video0' is a Noname Integrated Camera virtual device

Was that run as root as well?  What does

 $ sudo SANE_DEBUG_DLL=128 scanimage -L

say?  Does the output look like it loaded that third-party backend
correctly?  It could be that the backend was installed someplace where
the dll backend does not look.  Not all third-party backends have been
fixed up to play nice with multiarch.

Before multiarch, backends were installed in

  /usr/lib/sane  (or /usr/lib64/sane)

After multiarch, they usually live in a place that looks like

  /usr/lib/x86_64-linux-gnu/sane

> And this is LMDE2 distro, 64bits, kernel 4.9 (from the jessie
> backports). Essentially LMDE2 is a pimped Debian Jessie, which is
> oldstable. 16GB Ram, core i7, Disk is a 64GB ssd + 1TB HDD and the HDD
> is configured as a bcache-backend, because there's 192GB left on the
> ssd, which I use as the bcache cache device.
>
> Rgds Chris
>
>
> On 15/02/18 13:56, Olaf Meeuwissen wrote:
>> Hi Chris,
>>
>> Chris writes:
>>
>>> Hi,
>>>
>>> My first post here, and whilst I think I've covered the obvious things,
>>> I could have easily missed something. But I can read, so in case I
>>> missed what to read, kindly tell me
>>>
>>> Having said that, I have got a Mustek A3F1200N scanner. It's an usb
>>> scanner and Mustek offers a xsane backend deb file for this scanner at
>>> ftp://ftp2.mustek.com.tw/pub/new/driver/A3F1200N/Linux/ . I run 64 bit
>>> LMDE2, so I downloaded and installed the .deb file. This added a lot of
>>> files to /etc/sane.d, but xsane does not detect the scanner. So I did an
>>> lsusb and found this: Bus 001 Device 010: ID 055f:050c Mustek Systems, Inc.
>> Third party backend binary packages often don't bother with getting the
>> device access permissions right on *your* particular system.  Taking a
>> quick look at Mustek's binaries, it doesn't seem to even do so much as
>> try.
>>
>> # Apart from that, it seems to warp you back in time to sane-backends
>> # 1.0.23 for all other backends and clobber whatever changes you made
>> # to /etc/sane.d.  At least for the i386 deb.
>>
>> You didn't mention the distribution you use but something like the below
>> ought to work for most.
>>
>>  sudo cp /lib/udev/rules.d/*-libsane.rules /etc/udev/rules.d/
>>
>> and replace the whole of the gargatuan list of entries that look like
>>
>>   ATTRS{idVendor}=="055f", ATTRS{idProduct}=="050c", 
>> ENV{libsane_matched}="yes"
>>
>> with that single line.  Replace the line that starts with
>>
>>   ENV{libsane_matched}=="yes"
>>
>> with
>>
>>   ENV{libsane_matched}=="yes", RUN+="chmod 0666 $env{DEVNAME}"
>>
>> Replug your device and things should work, if my recollection of the way
>> udev works still up to snuff.  It's not the most granular and security
>> conscious way of going about this but is good enough for single user
>> machines and most SOHO use.

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] Is there any plan to support Web Devices Services (WDS) protocol?

[Patrick Roncagliolo]

I just wrote the same a minute ago in the other email :) A server-side WSD
library would enable the possibility you mentioned, of course.

Il sab 24 feb 2018, 18:22 Steven Santos  ha
scritto:

> One other thought here:
>
> If it were possible to implement a WDS server in SANE, it would open up
> SANE to be used as a single central scan server for windows as well.  Set
> up all of your scanners on a SANE server, then let youw windows and linux
> boxes connect to that.  That would make life easier for sure...
>
> On Sat, Feb 24, 2018 at 12:08 PM, Steven Santos 
> wrote:
>
>> This is a great project.  If it is successful, you will open up a ton of
>> scanners for use with SANE
>>
>> More importantly, it gives a path for supporting just about ANY
>> windows-only scanner in SANE, as seems windows 10 can export any local
>> scanner via WSD
>>
>> I am assuming you found this documentation?
>>
>>
>> https://docs.microsoft.com/en-us/windows-hardware/design/whitepapers/implementing-web-services-on-devices-for-printing
>>
>> On Tue, Feb 6, 2018 at 11:10 AM, Patrick Roncagliolo > > wrote:
>>
>>> Hi all,
>>>
>>> I found http://ws4d.org/dpws-explorer/ . It has a linux version, it can
>>> help a bit with device detection and browse properties while developing a
>>> proper scan software.
>>> Here  is a java
>>> implementation of the DPWS standard, and here
>>>  a C/C++ one.
>>>
>>> However, I found another batch of documentation of the standard, so
>>> developing a simple working implementation targeted mainly to scan
>>> capabilities isn't going to be difficult.
>>>
>>> The C/C++ library posted above might be not suitable for sane backend
>>> implementation, I don't think sane devs would allow adding such a large
>>> gen-purpose dependency to codebase, and a lightweight implementation is
>>> better IMHO.
>>>
>>>
>>>
>>> Il giorno mar 6 feb 2018 alle ore 00:05 Patrick Roncagliolo <
>>> ronca@gmail.com> ha scritto:
>>>
 Hi,

 you can find a basic implementation of a WSD discovery scanner here:
 https://github.com/roncapat/WSD-python

 Here is a sample output (it detects a response from my MB2350):

 EndPoint Reference Address:
 urn:uuid:--1000-8000-f4813944662e
 Implemented Types:
 wsdp:Device
 wprt:PrintDeviceType
 wscn:ScanDeviceType
 Transport addresses:
 http://192.168.1.5:80/wsd/pnpx-metadata.cgi

 Basically, it retrieves an unique identifier, the capabilities of the
 devices (MB2350 is both printer and scanner), and an HTTP address for later
 use.
 More coming. Understanding the protocol with an easy language as Python
 with no API constraints helps to bootstrap a working implementation, but
 ideally the next step would be a true backend implementation.

 Patrick Roncagliolo


 Il giorno lun 5 feb 2018 alle ore 16:25 Patrick Roncagliolo <
 ronca@gmail.com> ha scritto:

> Hi Till,
> WSD came in with Windows Vista IIRC.
> It is HTTP/XML based, so yeah, it works only on network, in fact my
> canon maxify uses an entirely different protocol on USB (similar, if not
> equal, to the BJNP network protocol used by Canon for basic Linux LAN
> support).
> It defines a discovery protocol, a scan service, a print service, but
> probably there are more, unrelated with the printer/multifunction/scanner
> world (I started today to dig the docs).
>
> By the way, I managed to fix the script found in the github repo I
> linked, and maybe the first step for me to get comfortable with the
> protocol will be to play a bit more from python, extending as much as I 
> can
> the short script as a more complete CLI tool with discovery support and 
> all
> the possible options. Then, I could manage to reimplement the protocol as 
> a
> sane backend, which I think is a bit more hard (I need to study sane api
> first).
>
> Beware I'm a student with not-so-much spare time, but I'm interested
> in learning something new and get my canon working at best, and obviously
> contribute as much as I can. I'd like to add or expand wireshark 
> dissectors
> for WSD and BJNP too. We'll see how much I can do.
>
> NB. if in the coming days I start a github repo for a WSD python
> playground, I'll share here the link.
>
> Here are a few links:
> -WS-Discovery (full spec)
> http://specs.xmlsoap.org/ws/2005/04/discovery/ws-discovery.pdf
> -WS-Print (at the bottom of the page there are links to all print &
> scan XML schemas and tech specifications)
> https://docs.microsoft.com/en-us/windows-hardware/drivers/print/ws-print-v1-1
> -WS-Print 2.0 (only printing? 3d printers? have no time to check)
>