date:20170415

Re: [sane-devel] [PATCH v3] Swap bytes in 16-bit PNGs, because PNG is big-endian.

2017-04-15 Thread Aaron Muir Hamilton

Sorry about the volume, third time is definitely the charm.
Admittedly I struggled to grasp the style rules.

I noticed the PNG byte order issue fixed by this patch when using
genesys with a CanoScan LiDE 220. I do not have any other supported
scanners close at hand, so I hope somebody can confirm if this is an
issue specific to genesys. The TIFF 16-bit output already worked
correctly since TIFF is happy to be little-endian.

Cheers!

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.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] [PATCH v3] Swap bytes in 16-bit PNGs, because PNG is big-endian.

2017-04-15 Thread Aaron Muir Hamilton

---
 frontend/scanimage.c | 13 +
 1 file changed, 13 insertions(+)

diff --git a/frontend/scanimage.c b/frontend/scanimage.c
index 77c2288..0925039 100644
--- a/frontend/scanimage.c
+++ b/frontend/scanimage.c
@@ -1529,6 +1529,19 @@ scan_it (FILE *ofp)
  for(j = 0; j < parm.bytes_per_line; j++)
pngbuf[j] = ~pngbuf[j];
}
+ /* PNG is big-endian */
+ /* see: 
https://www.w3.org/TR/2003/REC-PNG-20031110/#7Integers-and-byte-order */
+ if (parm.depth == 16)
+   {
+ int j;
+ for (j = 0; j < parm.bytes_per_line; j += 2)
+   {
+ SANE_Byte LSB;
+ LSB = pngbuf[j];
+ pngbuf[j] = pngbuf[j + 1];
+ pngbuf[j + 1] = LSB;
+   }
+   }
  png_write_row(png_ptr, pngbuf);
  i += parm.bytes_per_line - pngrow;
  left -= parm.bytes_per_line - pngrow;
-- 
1.8.3.1


-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.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] [PATCH v2] Swap bytes in 16-bit PNGs, because PNG is big-endian.

2017-04-15 Thread aaron

---
 frontend/scanimage.c | 13 +
 1 file changed, 13 insertions(+)

diff --git a/frontend/scanimage.c b/frontend/scanimage.c
index 77c2288..961ca49 100644
--- a/frontend/scanimage.c
+++ b/frontend/scanimage.c
@@ -1529,6 +1529,19 @@ scan_it (FILE *ofp)
  for(j = 0; j < parm.bytes_per_line; j++)
pngbuf[j] = ~pngbuf[j];
}
+ /* PNG is big-endian, */
+ /* see: 
https://www.w3.org/TR/2003/REC-PNG-20031110/#7Integers-and-byte-order */
+ if (parm.depth == 16)
+   {
+ int j;
+ for (j = 0; j < parm.bytes_per_line; j += 2)
+   {
+ SANE_Byte LSB;
+ LSB = pngbuf[j];
+ pngbuf[j] = pngbuf[j + 1];
+ pngbuf[j + 1] = LSB;
+   }
+   }
  png_write_row(png_ptr, pngbuf);
  i += parm.bytes_per_line - pngrow;
  left -= parm.bytes_per_line - pngrow;
-- 
1.8.3.1


-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.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] [PATCH] Swap bytes in 16-bit PNGs, because PNG is big-endian.

2017-04-15 Thread Aaron Muir Hamilton


---
 frontend/scanimage.c | 13 +
 1 file changed, 13 insertions(+)

diff --git a/frontend/scanimage.c b/frontend/scanimage.c
index 77c2288..d719c4b 100644
--- a/frontend/scanimage.c
+++ b/frontend/scanimage.c
@@ -1529,6 +1529,19 @@ scan_it (FILE *ofp)
  for(j = 0; j < parm.bytes_per_line; j++)
pngbuf[j] = ~pngbuf[j];
}
+  /* PNG is big-endian, */
+  /* see: 
https://www.w3.org/TR/2003/REC-PNG-20031110/#7Integers-and-byte-order */
+  if (parm.depth == 16)
+{
+  int j;
+  for (j = 0; j < parm.bytes_per_line; j += 2)
+{
+  SANE_Byte LSB;
+  LSB = pngbuf[j];
+  pngbuf[j] = pngbuf[j + 1];
+  pngbuf[j + 1] = LSB;
+}
+}
  png_write_row(png_ptr, pngbuf);
  i += parm.bytes_per_line - pngrow;
  left -= parm.bytes_per_line - pngrow;
-- 
1.8.3.1

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

Re: [sane-devel] scanbd and Canon LiDE 60: buttons not recognized ?

2017-04-15 Thread Florian Gagel


Hi Wilhelm,

thanks, your modification made all four buttons work !
This seems somewhat surprising to me at first glance, should  the 
backend not be strcmp'ed using "==0", providing
an own section for each backend :-) ? Anyway, it works, even if the 
buttons are somewhat scrambled:


 (Button press at scanner)  -> (Action)

Email  -> PDF
PDF -> Email
Scan   -> Copy
Copy   -> Scan.

I also used string-triggers only. The buttons may have to be pressed for 
a short period exceeding the polling interval.
Some minor possible pitfalls using the installations defaults of 
scanbd-1.5.0 under Ubuntu 16.04:
- I removed the default package and configured the newer scanbd 1.5.0 as 
described in the previous mail. I also used xinetd instead of the ubuntu 
default
   bsd-inetd for network scanner access although this should be of no 
relevance.
- Wilhelms patch has to be applied to scanbuttond_wrapper.c (removed 
assertion, return strings on any value of "button").
- In scanbd.conf: Group should be "saned". Make sure all paths refer to 
/usr/local/etc/scanbd, scriptdir = /usr/local/etc/scanbd/scripts, ...
- The new path also enters into /lib/systemd/system/scanbd.service, 
after changing that do "systemctl daemon-reload" and restart scanbd.


Now I am happy because of the four programmable buttons for my Odroid-U2 
SoC which has no monitor attached to it :-)


Thanks again Wilhelm and Happy Easter !

  Florian

Am 15.04.2017 um 17:32 schrieb Wilhelm:

Am 15.04.2017 um 16:13 schrieb Florian Gagel:

Hi Wilhelm,

thanks for your reply -  I made some progress in this issue however
still did not fully succeed.

- First step as you told me: make clean, configure --enable-scanbuttond,
make, make install, copy manually the
old backends to /usr/local/lib/scanbd/scanbuttond as described in the
README (this all with the 1.5.0 version of scanbd).
- Starting scanbd -f -d7, I first got a "scanbd: Can't get the scbtn
device list" error.
- I edited /usr/local/lib/scanbd/scanbuttond/backends/meta.conf, making
it contain the single line "genesys" which was missing before.

Yes, per default this was not included - I added it to trunk.


- Then the LiDE-60 was recognized by the old backend, together with its
four buttons !
- However, scanbd finally stumbled on an assertion:/

Looks like you were the first one with an appropriate scanner to test
this ;-)

You can safely remove the mentioned assertion if you return non-null
string-literals in all switch cases including the default case:

--- scanbuttond_wrapper.c   (Revision 236)

+++ scanbuttond_wrapper.c   (Arbeitskopie)

@@ -1063,10 +1063,9 @@

  slog(SLOG_INFO, "scanbtnd_button_name, backend: %s", backend_name);



  if (strcmp("snapscan", backend_name)) {
-assert(button <= 5);
  switch(button) {
  case 0:
-return NULL;
+return "zero";
  break;
  case 1:
  return "scan"; // "web";
@@ -1084,7 +1083,7 @@
  return "stop";
  break;
  default:
-return NULL;
+return "default";
  break;
  }
  }


If you don't mind please test this modification. I you succeed with it
I'll put it into trunk.


root@gandroid:/usr/local/etc/scanbd# scanbd -f -d7
scanbd: reading config file /usr/local/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: drop privileges to gid: 121
scanbd: Running as effective gid 121
scanbd: drop privileges to uid: 120
scanbd: Running as effective uid 120
scanbd: dbus_init
scanbd: dbus match type='signal',interface='org.freedesktop.Hal.Manager'
scanbd: Loading /usr/local/lib/scanbd/scanbuttond/backends/meta.so
scanbd: Loading /usr/local/lib/scanbd/scanbuttond/backends/genesys.so
scanbd: Scanning for local-only devices
scanbd: found device: CanoScan LiDE 60 Canon genesys:libusb:001:016
scanbd: start_scbtn_threads
scanbd: start the threads (1)
scanbd: Starting poll thread for CanoScan LiDE 60
scanbd: Thread started for device CanoScan LiDE 60
scanbd: start dbus thread
scanbd: scbtn_poll
scanbd: udev init
scanbd: get udev monitor
scanbd: udev fd is non-blocking, now setting to blocking mode
scanbd: start udev thread
scanbd: udev thread started
scanbd: timeout: 500 ms
scanbd: Iteration on dbus call
scanbd: found 15 options for device CanoScan LiDE 60
scanbd: sane_find_matching_options
scanbd: found 3 actions in section (null)
scanbd: checking action scan with filter: ^scan.*
scanbd: scanbtnd_button_name (1)
scanbd: scanbtnd_button_name, backend: Genesys USB
scanbd: found active option[0] scan for device CanoScan LiDE 60
scanbd: installing action scan (0) for CanoScan LiDE 60, option[0]: scan
as: test.script
scanbd: multiple actions allowed
scanbd: scanbtnd_button_name (2)
scanbd: scanbtnd_button_name, backend: Genesys USB
scanbd: found active option[1] copy for

Re: [sane-devel] scanbd and Canon LiDE 60: buttons not recognized ?

2017-04-15 Thread Wilhelm

Am 15.04.2017 um 16:13 schrieb Florian Gagel:
> Hi Wilhelm,
> 
> thanks for your reply -  I made some progress in this issue however
> still did not fully succeed.
> 
> - First step as you told me: make clean, configure --enable-scanbuttond,
> make, make install, copy manually the
> old backends to /usr/local/lib/scanbd/scanbuttond as described in the
> README (this all with the 1.5.0 version of scanbd).
> - Starting scanbd -f -d7, I first got a "scanbd: Can't get the scbtn
> device list" error.
> - I edited /usr/local/lib/scanbd/scanbuttond/backends/meta.conf, making
> it contain the single line "genesys" which was missing before.

Yes, per default this was not included - I added it to trunk.

> - Then the LiDE-60 was recognized by the old backend, together with its
> four buttons !
> - However, scanbd finally stumbled on an assertion:/

Looks like you were the first one with an appropriate scanner to test
this ;-)

You can safely remove the mentioned assertion if you return non-null
string-literals in all switch cases including the default case:

--- scanbuttond_wrapper.c   (Revision 236)

+++ scanbuttond_wrapper.c   (Arbeitskopie)

@@ -1063,10 +1063,9 @@

 slog(SLOG_INFO, "scanbtnd_button_name, backend: %s", backend_name);



 if (strcmp("snapscan", backend_name)) {
-assert(button <= 5);
 switch(button) {
 case 0:
-return NULL;
+return "zero";
 break;
 case 1:
 return "scan"; // "web";
@@ -1084,7 +1083,7 @@
 return "stop";
 break;
 default:
-return NULL;
+return "default";
 break;
 }
 }


If you don't mind please test this modification. I you succeed with it
I'll put it into trunk.

> root@gandroid:/usr/local/etc/scanbd# scanbd -f -d7
> scanbd: reading config file /usr/local/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: drop privileges to gid: 121
> scanbd: Running as effective gid 121
> scanbd: drop privileges to uid: 120
> scanbd: Running as effective uid 120
> scanbd: dbus_init
> scanbd: dbus match type='signal',interface='org.freedesktop.Hal.Manager'
> scanbd: Loading /usr/local/lib/scanbd/scanbuttond/backends/meta.so
> scanbd: Loading /usr/local/lib/scanbd/scanbuttond/backends/genesys.so
> scanbd: Scanning for local-only devices
> scanbd: found device: CanoScan LiDE 60 Canon genesys:libusb:001:016
> scanbd: start_scbtn_threads
> scanbd: start the threads (1)
> scanbd: Starting poll thread for CanoScan LiDE 60
> scanbd: Thread started for device CanoScan LiDE 60
> scanbd: start dbus thread
> scanbd: scbtn_poll
> scanbd: udev init
> scanbd: get udev monitor
> scanbd: udev fd is non-blocking, now setting to blocking mode
> scanbd: start udev thread
> scanbd: udev thread started
> scanbd: timeout: 500 ms
> scanbd: Iteration on dbus call
> scanbd: found 15 options for device CanoScan LiDE 60
> scanbd: sane_find_matching_options
> scanbd: found 3 actions in section (null)
> scanbd: checking action scan with filter: ^scan.*
> scanbd: scanbtnd_button_name (1)
> scanbd: scanbtnd_button_name, backend: Genesys USB
> scanbd: found active option[0] scan for device CanoScan LiDE 60
> scanbd: installing action scan (0) for CanoScan LiDE 60, option[0]: scan
> as: test.script
> scanbd: multiple actions allowed
> scanbd: scanbtnd_button_name (2)
> scanbd: scanbtnd_button_name, backend: Genesys USB
> scanbd: found active option[1] copy for device CanoScan LiDE 60
> scanbd: scanbtnd_button_name (3)
> scanbd: scanbtnd_button_name, backend: Genesys USB
> scanbd: found active option[2] email for device CanoScan LiDE 60
> scanbd: scanbtnd_button_name (4)
> scanbd: scanbtnd_button_name, backend: Genesys USB
> scanbd: found active option[3] pdf for device CanoScan LiDE 60
> scanbd: scanbtnd_button_name (5)
> scanbd: scanbtnd_button_name, backend: Genesys USB
> scanbd: found active option[4] stop for device CanoScan LiDE 60
> scanbd: scanbtnd_button_name (6)
> scanbd: scanbtnd_button_name, backend: Genesys USB
> scanbd: scanbuttond_wrapper.c:1066: scanbtnd_button_name: Assertion
> `button <= 5' failed.
> Aborted
> 
> Of course there are only 4 buttons physically, plus one hidden reset
> button. Now i am unsure whether simply to edit the source code in order to
> remove the assertion. My feeling is it might work then.
> 
> Regards,
>  
>   Florian/
> 
> /Am 15.04.2017 um 12:26 schrieb Wilhelm Meier:
>> Hi Florian,
>>
>> scanbd totally relies on libsane to read the option (button) values. It
>> is known, that some backends aren't capable doing this ...
>>
>> For the Lide60 you can try uing the old scanbuttond backends included in
>> the scanbd source tree. See the ReadMe.txt for instructions please.
>>
>>
>>
>> Am 15.04.2017 um 10:44 schrieb Florian Gagel:
>>> Hi,
>>>
>>> my LiDE60 is working well, either

Re: [sane-devel] scanbd and Canon LiDE 60: buttons not recognized ?

2017-04-15 Thread Florian Gagel


Hi Wilhelm,

thanks for your reply -  I made some progress in this issue however 
still did not fully succeed.


- First step as you told me: make clean, configure --enable-scanbuttond, 
make, make install, copy manually the
old backends to /usr/local/lib/scanbd/scanbuttond as described in the 
README (this all with the 1.5.0 version of scanbd).
- Starting scanbd -f -d7, I first got a "scanbd: Can't get the scbtn 
device list" error.
- I edited /usr/local/lib/scanbd/scanbuttond/backends/meta.conf, making 
it contain the single line "genesys" which was missing before.
- Then the LiDE-60 was recognized by the old backend, together with its 
four buttons !

- However, scanbd finally stumbled on an assertion:/
/
root@gandroid:/usr/local/etc/scanbd# scanbd -f -d7
scanbd: reading config file /usr/local/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: drop privileges to gid: 121
scanbd: Running as effective gid 121
scanbd: drop privileges to uid: 120
scanbd: Running as effective uid 120
scanbd: dbus_init
scanbd: dbus match type='signal',interface='org.freedesktop.Hal.Manager'
scanbd: Loading /usr/local/lib/scanbd/scanbuttond/backends/meta.so
scanbd: Loading /usr/local/lib/scanbd/scanbuttond/backends/genesys.so
scanbd: Scanning for local-only devices
scanbd: found device: CanoScan LiDE 60 Canon genesys:libusb:001:016
scanbd: start_scbtn_threads
scanbd: start the threads (1)
scanbd: Starting poll thread for CanoScan LiDE 60
scanbd: Thread started for device CanoScan LiDE 60
scanbd: start dbus thread
scanbd: scbtn_poll
scanbd: udev init
scanbd: get udev monitor
scanbd: udev fd is non-blocking, now setting to blocking mode
scanbd: start udev thread
scanbd: udev thread started
scanbd: timeout: 500 ms
scanbd: Iteration on dbus call
scanbd: found 15 options for device CanoScan LiDE 60
scanbd: sane_find_matching_options
scanbd: found 3 actions in section (null)
scanbd: checking action scan with filter: ^scan.*
scanbd: scanbtnd_button_name (1)
scanbd: scanbtnd_button_name, backend: Genesys USB
scanbd: found active option[0] scan for device CanoScan LiDE 60
scanbd: installing action scan (0) for CanoScan LiDE 60, option[0]: scan 
as: test.script

scanbd: multiple actions allowed
scanbd: scanbtnd_button_name (2)
scanbd: scanbtnd_button_name, backend: Genesys USB
scanbd: found active option[1] copy for device CanoScan LiDE 60
scanbd: scanbtnd_button_name (3)
scanbd: scanbtnd_button_name, backend: Genesys USB
scanbd: found active option[2] email for device CanoScan LiDE 60
scanbd: scanbtnd_button_name (4)
scanbd: scanbtnd_button_name, backend: Genesys USB
scanbd: found active option[3] pdf for device CanoScan LiDE 60
scanbd: scanbtnd_button_name (5)
scanbd: scanbtnd_button_name, backend: Genesys USB
scanbd: found active option[4] stop for device CanoScan LiDE 60
scanbd: scanbtnd_button_name (6)
scanbd: scanbtnd_button_name, backend: Genesys USB
scanbd: scanbuttond_wrapper.c:1066: scanbtnd_button_name: Assertion 
`button <= 5' failed.

Aborted

Of course there are only 4 buttons physically, plus one hidden reset 
button. Now i am unsure whether simply to edit the source code in order to

remove the assertion. My feeling is it might work then.

Regards,

  Florian/

/Am 15.04.2017 um 12:26 schrieb Wilhelm Meier:

Hi Florian,

scanbd totally relies on libsane to read the option (button) values. It
is known, that some backends aren't capable doing this ...

For the Lide60 you can try uing the old scanbuttond backends included in
the scanbd source tree. See the ReadMe.txt for instructions please.



Am 15.04.2017 um 10:44 schrieb Florian Gagel:

Hi,

my LiDE60 is working well, either directly using scanimage with scanbd
not running, as "genesys:libusb:001:016" or with running scanbd using
xinetd as"net:localhost:genesys:libusb:001:016".
However, none of the four buttons seem to be recognized:

root@gandroid:/usr/local/etc/scanbd# scanbd -f -d7
scanbd: reading config file /usr/local/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: drop privileges to gid: 121
scanbd: Running as effective gid 121
scanbd: drop privileges to uid: 120
scanbd: Running as effective uid 120
scanbd: dbus_init
scanbd: dbus match type='signal',interface='org.freedesktop.Hal.Manager'
scanbd: SANE_CONFIG_DIR=/usr/local/etc/scanbd
scanbd: sane version 1.0
scanbd: Scanning for local-only devices
scanbd: found device: genesys:libusb:001:016 Canon LiDE 60 flatbed scanner
scanbd: start_sane_threads
scanbd: Starting poll thread for genesys:libusb:001:016
scanbd: Thread started for device genesys:libusb:001:016
scanbd: sane_poll
scanbd: start dbus thread
scanbd: udev init
scanbd: get udev monitor
scanbd: udev fd is non-blocking, now setting to blocking mode
scanbd: start udev thread
scanbd: udev thread

Re: [sane-devel] Xerox WorkCentre 6027

2017-04-15 Thread Torfinn Ingolfsen

On Fri, Apr 14, 2017 at 9:41 PM, Mayer Landau
 wrote:
> Hi Torfinn,
> That Xerox download only supports the printer part.
>
> I have no problem trying to help the developers with the xerox backend.
> You mention turning on all the debug info.
> At this moment in time, I don't know how to do that.

Well, general info about helping is in the sane(7) man page. You might
know this already.
The section "problems" lists the generic environment variables you can use.
the sane-xerox_mfp(5) man page list the options specific to the
xerox_mfp backend.
example
$ SANE_DEBUG_XEROX_MFP=4 scanimage -L
or a higher value.

> When you say, send to the mailing list, do you mean
> < sane-devel@lists.alioth.debian.org >?

Yes, I do.

HTH
-- 
Regards,
Torfinn Ingolfsen

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

Re: [sane-devel] scanbd and Canon LiDE 60: buttons not recognized ?

2017-04-15 Thread Wilhelm Meier

Hi Florian,

scanbd totally relies on libsane to read the option (button) values. It
is known, that some backends aren't capable doing this ...

For the Lide60 you can try uing the old scanbuttond backends included in
the scanbd source tree. See the ReadMe.txt for instructions please.



Am 15.04.2017 um 10:44 schrieb Florian Gagel:
> Hi,
> 
> my LiDE60 is working well, either directly using scanimage with scanbd
> not running, as "genesys:libusb:001:016" or with running scanbd using
> xinetd as "net:localhost:genesys:libusb:001:016".
> However, none of the four buttons seem to be recognized:
> 
> root@gandroid:/usr/local/etc/scanbd# scanbd -f -d7
> scanbd: reading config file /usr/local/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: drop privileges to gid: 121
> scanbd: Running as effective gid 121
> scanbd: drop privileges to uid: 120
> scanbd: Running as effective uid 120
> scanbd: dbus_init
> scanbd: dbus match type='signal',interface='org.freedesktop.Hal.Manager'
> scanbd: SANE_CONFIG_DIR=/usr/local/etc/scanbd
> scanbd: sane version 1.0
> scanbd: Scanning for local-only devices
> scanbd: found device: genesys:libusb:001:016 Canon LiDE 60 flatbed scanner
> scanbd: start_sane_threads
> scanbd: Starting poll thread for genesys:libusb:001:016
> scanbd: Thread started for device genesys:libusb:001:016
> scanbd: sane_poll
> scanbd: start dbus thread
> scanbd: udev init
> scanbd: get udev monitor
> scanbd: udev fd is non-blocking, now setting to blocking mode
> scanbd: start udev thread
> scanbd: udev thread started
> scanbd: timeout: 500 ms
> scanbd: Iteration on dbus call
> scanbd: Iteration on dbus call
> scanbd: found 49 options for device genesys:libusb:001:016
> scanbd: sane_find_matching_options
> scanbd: found 5 actions in section (null)
> scanbd: checking action scan with filter: ^scan.*
> scanbd: found active option[2] mode (type: 3) for device
> genesys:libusb:001:016
> scanbd: found active option[4] preview (type: 0) for device
> genesys:libusb:001:016
> scanbd: found active option[5] depth (type: 1) for device
> genesys:libusb:001:016
> scanbd: found active option[6] resolution (type: 1) for device
> genesys:libusb:001:016
> scanbd: found active option[8] tl-x (type: 2) for device
> genesys:libusb:001:016
> scanbd: found active option[9] tl-y (type: 2) for device
> genesys:libusb:001:016
> scanbd: found active option[10] br-x (type: 2) for device
> genesys:libusb:001:016
> scanbd: found active option[11] br-y (type: 2) for device
> genesys:libusb:001:016
> scanbd: found active option[13] custom-gamma (type: 0) for device
> genesys:libusb:001:016
> scanbd: found active option[18] swdeskew (type: 0) for device
> genesys:libusb:001:016
> scanbd: found active option[19] swcrop (type: 0) for device
> genesys:libusb:001:016
> scanbd: found active option[20] swdespeck (type: 0) for device
> genesys:libusb:001:016
> scanbd: found active option[21] despeck (type: 1) for device
> genesys:libusb:001:016
> scanbd: found active option[22] swskip (type: 2) for device
> genesys:libusb:001:016
> scanbd: found active option[23] swderotate (type: 0) for device
> genesys:libusb:001:016
> scanbd: found active option[24] brightness (type: 1) for device
> genesys:libusb:001:016
> scanbd: found active option[25] contrast (type: 1) for device
> genesys:libusb:001:016
> scanbd: found active option[27] lamp-off-time (type: 1) for device
> genesys:libusb:001:016
> scanbd: found active option[28] lamp-off-scan (type: 0) for device
> genesys:libusb:001:016
> scanbd: found active option[29] threshold (type: 2) for device
> genesys:libusb:001:016
> scanbd: found active option[30] threshold-curve (type: 1) for device
> genesys:libusb:001:016
> scanbd: found active option[31] disable-dynamic-lineart (type: 0) for
> device genesys:libusb:001:016
> scanbd: found active option[32] disable-interpolation (type: 0) for
> device genesys:libusb:001:016
> scanbd: found active option[33] color-filter (type: 3) for device
> genesys:libusb:001:016
> scanbd: found active option[34] calibration-file (type: 3) for device
> genesys:libusb:001:016
> scanbd: found active option[35] expiration-time (type: 1) for device
> genesys:libusb:001:016
> scanbd: found active option[48] clear-calibration (type: 4) for device
> genesys:libusb:001:016
> scanbd: checking action email with filter: ^email$
> scanbd: found active option[2] mode (type: 3) for device
> genesys:libusb:001:016
> scanbd: found active option[4] preview (type: 0) for device
> genesys:libusb:001:016
> scanbd: found active option[5] depth (type: 1) for device
> genesys:libusb:001:016
> scanbd: found active option[6] resolution (type: 1) for device
> genesys:libusb:001:016
> scanbd: found active option[8] tl-x (type: 2) for device
> genesys:libusb:001:016
> scanbd: found active option[9] tl-y (type: 2) for device
> genesys:libusb:001:016
>

[sane-devel] scanbd and Canon LiDE 60: buttons not recognized ?

2017-04-15 Thread Florian Gagel


Hi,

my LiDE60 is working well, either directly using scanimage with scanbd 
not running, as "genesys:libusb:001:016" or with running scanbd using 
xinetd as "net:localhost:genesys:libusb:001:016".

However, none of the four buttons seem to be recognized:

root@gandroid:/usr/local/etc/scanbd# scanbd -f -d7
scanbd: reading config file /usr/local/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: drop privileges to gid: 121
scanbd: Running as effective gid 121
scanbd: drop privileges to uid: 120
scanbd: Running as effective uid 120
scanbd: dbus_init
scanbd: dbus match type='signal',interface='org.freedesktop.Hal.Manager'
scanbd: SANE_CONFIG_DIR=/usr/local/etc/scanbd
scanbd: sane version 1.0
scanbd: Scanning for local-only devices
scanbd: found device: genesys:libusb:001:016 Canon LiDE 60 flatbed scanner
scanbd: start_sane_threads
scanbd: Starting poll thread for genesys:libusb:001:016
scanbd: Thread started for device genesys:libusb:001:016
scanbd: sane_poll
scanbd: start dbus thread
scanbd: udev init
scanbd: get udev monitor
scanbd: udev fd is non-blocking, now setting to blocking mode
scanbd: start udev thread
scanbd: udev thread started
scanbd: timeout: 500 ms
scanbd: Iteration on dbus call
scanbd: Iteration on dbus call
scanbd: found 49 options for device genesys:libusb:001:016
scanbd: sane_find_matching_options
scanbd: found 5 actions in section (null)
scanbd: checking action scan with filter: ^scan.*
scanbd: found active option[2] mode (type: 3) for device 
genesys:libusb:001:016
scanbd: found active option[4] preview (type: 0) for device 
genesys:libusb:001:016
scanbd: found active option[5] depth (type: 1) for device 
genesys:libusb:001:016
scanbd: found active option[6] resolution (type: 1) for device 
genesys:libusb:001:016
scanbd: found active option[8] tl-x (type: 2) for device 
genesys:libusb:001:016
scanbd: found active option[9] tl-y (type: 2) for device 
genesys:libusb:001:016
scanbd: found active option[10] br-x (type: 2) for device 
genesys:libusb:001:016
scanbd: found active option[11] br-y (type: 2) for device 
genesys:libusb:001:016
scanbd: found active option[13] custom-gamma (type: 0) for device 
genesys:libusb:001:016
scanbd: found active option[18] swdeskew (type: 0) for device 
genesys:libusb:001:016
scanbd: found active option[19] swcrop (type: 0) for device 
genesys:libusb:001:016
scanbd: found active option[20] swdespeck (type: 0) for device 
genesys:libusb:001:016
scanbd: found active option[21] despeck (type: 1) for device 
genesys:libusb:001:016
scanbd: found active option[22] swskip (type: 2) for device 
genesys:libusb:001:016
scanbd: found active option[23] swderotate (type: 0) for device 
genesys:libusb:001:016
scanbd: found active option[24] brightness (type: 1) for device 
genesys:libusb:001:016
scanbd: found active option[25] contrast (type: 1) for device 
genesys:libusb:001:016
scanbd: found active option[27] lamp-off-time (type: 1) for device 
genesys:libusb:001:016
scanbd: found active option[28] lamp-off-scan (type: 0) for device 
genesys:libusb:001:016
scanbd: found active option[29] threshold (type: 2) for device 
genesys:libusb:001:016
scanbd: found active option[30] threshold-curve (type: 1) for device 
genesys:libusb:001:016
scanbd: found active option[31] disable-dynamic-lineart (type: 0) for 
device genesys:libusb:001:016
scanbd: found active option[32] disable-interpolation (type: 0) for 
device genesys:libusb:001:016
scanbd: found active option[33] color-filter (type: 3) for device 
genesys:libusb:001:016
scanbd: found active option[34] calibration-file (type: 3) for device 
genesys:libusb:001:016
scanbd: found active option[35] expiration-time (type: 1) for device 
genesys:libusb:001:016
scanbd: found active option[48] clear-calibration (type: 4) for device 
genesys:libusb:001:016

scanbd: checking action email with filter: ^email$
scanbd: found active option[2] mode (type: 3) for device 
genesys:libusb:001:016
scanbd: found active option[4] preview (type: 0) for device 
genesys:libusb:001:016
scanbd: found active option[5] depth (type: 1) for device 
genesys:libusb:001:016
scanbd: found active option[6] resolution (type: 1) for device 
genesys:libusb:001:016
scanbd: found active option[8] tl-x (type: 2) for device 
genesys:libusb:001:016
scanbd: found active option[9] tl-y (type: 2) for device 
genesys:libusb:001:016
scanbd: found active option[10] br-x (type: 2) for device 
genesys:libusb:001:016
scanbd: found active option[11] br-y (type: 2) for device 
genesys:libusb:001:016
scanbd: found active option[13] custom-gamma (type: 0) for device 
genesys:libusb:001:016
scanbd: found active option[18] swdeskew (type: 0) for device 
genesys:libusb:001:016
scanbd: found active option[19] swcrop (type: 0) for device 
genesys:libusb:001:016
scanbd: found active option[20] swdespeck (type: 0) for device 
genesys:libusb:001:016
scanbd:

Re: [sane-devel] [PATCH v3] Swap bytes in 16-bit PNGs, because PNG is big-endian.

[sane-devel] [PATCH v3] Swap bytes in 16-bit PNGs, because PNG is big-endian.

[sane-devel] [PATCH v2] Swap bytes in 16-bit PNGs, because PNG is big-endian.

[sane-devel] [PATCH] Swap bytes in 16-bit PNGs, because PNG is big-endian.

Re: [sane-devel] scanbd and Canon LiDE 60: buttons not recognized ?

Re: [sane-devel] scanbd and Canon LiDE 60: buttons not recognized ?

Re: [sane-devel] scanbd and Canon LiDE 60: buttons not recognized ?

Re: [sane-devel] Xerox WorkCentre 6027

Re: [sane-devel] scanbd and Canon LiDE 60: buttons not recognized ?

[sane-devel] scanbd and Canon LiDE 60: buttons not recognized ?

10 matches

Site Navigation

Mail list logo

Footer information