Re: [sane-devel] scanbd on ubuntu

[Herr Oswald]

Am Donnerstag, den 01.06.2017, 22:26 +0200 schrieb Herr Oswald:
> Sorry, this probabely is stupid - but I do not know where to begin.
> This is the core of my question. (Some hints at sourceforge's project
> page could be helpful...)
> 
> You wrote that the old ArchLinux instructions will do. OK - I'll try
> these and report back.

I followed the instructions found here: 
https://wiki.archlinux.org/index.php/Scanner_Button_Daemon

Went nice till this place:
$ systemctl start scanbm.socket
Job for scanbm.socket failed.

This is what 
$ systemctl status scanbm.socket
says:

scanbm.socket - scanbd/saned incoming socket
   Loaded: loaded (/lib/systemd/system/scanbm.socket; enabled; vendor
preset: enabled)
   Active: failed (Result: resources)
   Listen: [::]:6566 (Stream)
 Accepted: 0; Connected: 0

Jun 02 14:13:31 Simux systemd[1]: scanbm.socket: Failed to listen on
sockets: Address already in use
Jun 02 14:13:31 Simux systemd[1]: Failed to listen on scanbd/saned
incoming socket.
Jun 02 14:13:31 Simux systemd[1]: scanbm.socket: Unit entered failed
state.
Jun 02 14:19:13 Simux systemd[1]: scanbm.socket: Failed to listen on
sockets: Address already in use
Jun 02 14:19:13 Simux systemd[1]: Failed to listen on scanbd/saned
incoming socket.
Jun 02 14:25:08 Simux systemd[1]: scanbm.socket: Failed to listen on
sockets: Address already in use
Jun 02 14:25:08 Simux systemd[1]: Failed to listen on scanbd/saned
incoming socket.

The outputs of journalctl -xe are attached to this message.

Cheers,
WolfJun 02 14:21:01 Simux dbus-daemon[1381]: Activating service 
name='com.intel.dleyna-renderer'
Jun 02 14:21:01 Simux dleyna-renderer-service[11889]: dLeyna core version 0.4.0
Jun 02 14:21:01 Simux dleyna-renderer-service[11889]: dleyna-renderer-service 
version 0.4.0
Jun 02 14:21:01 Simux dleyna-renderer-service[11889]: Type[0] Level[0x13] 
Mask[0x4C] Flags[0x4F]
Jun 02 14:21:01 Simux dleyna-renderer-service[11889]: Load file 
[/home/wo/.config/dleyna-renderer-service.conf]
Jun 02 14:21:01 Simux dleyna-renderer-service[11889]: [General settings]
Jun 02 14:21:01 Simux dleyna-renderer-service[11889]: Never Quit: F
Jun 02 14:21:01 Simux dleyna-renderer-service[11889]: Connector Name: dbus
Jun 02 14:21:01 Simux dleyna-renderer-service[11889]: [Logging settings]
Jun 02 14:21:01 Simux dleyna-renderer-service[11889]: Log Type : 0
Jun 02 14:21:01 Simux dleyna-renderer-service[11889]: Log Level: 0x13
Jun 02 14:21:01 Simux dleyna-renderer-service[11889]: [Network filtering 
settings]
Jun 02 14:21:01 Simux dleyna-renderer-service[11889]: Enabled : F
Jun 02 14:21:01 Simux dleyna-renderer-service[11889]: Entries: (null)
Jun 02 14:21:01 Simux dbus-daemon[1381]: Successfully activated service 
'com.intel.dleyna-renderer'
Jun 02 14:21:01 Simux dleyna-renderer-service[11889]: Calling GetRenderers 
method
Jun 02 14:21:02 Simux dleyna-renderer-service[11889]: Client :1.245 lost
Jun 02 14:21:04 Simux dleyna-renderer-service[11889]: dLeyna: Exit
Jun 02 14:21:07 Simux scanbm[11900]: scanbm: dbus match 
type='signal',interface='org.freedesktop.Hal.Manager'
Jun 02 14:21:07 Simux saned[11902]: read_config: could not open config file 
(saned.conf): No such file or directory
Jun 02 14:21:07 Simux saned[11902]: saned (AF-indep+IPv6) from sane-backends 
1.0.27git starting up
Jun 02 14:21:07 Simux saned[11902]: check_host: access by remote host: 127.0.0.1
Jun 02 14:21:07 Simux saned[11902]: init: access granted to saned-user@127.0.0.1
Jun 02 14:21:13 Simux org.gnome.Nautilus[1381]: Server response: 
REGISTER_PATH:/home/wo/owncloud-server-sync
Jun 02 14:21:13 Simux org.gnome.Nautilus[1381]: Server response: 
STATUS:IGNORE:/home/wo/owncloud-server-sync
Jun 02 14:25:03 Simux xsane.desktop[11886]: console.error:
Jun 02 14:25:03 Simux xsane.desktop[11886]:   Message: Error: The state cannot 
be set or get. The object may be not be registered, or may already have been 
unloaded.
Jun 02 14:25:03 Simux xsane.desktop[11886]:   Stack:
Jun 02 14:25:03 Simux xsane.desktop[11886]: 
setStateFor@resource://gre/modules/commonjs/toolkit/loader.js -> 
resource://gre/modules/commonjs/sdk/ui/state.js:109:11
Jun 02 14:25:03 Simux xsane.desktop[11886]: 
set@resource://gre/modules/commonjs/toolkit/loader.js -> 
resource://gre/modules/commonjs/sdk/ui/state.js:164:9
Jun 02 14:25:03 Simux xsane.desktop[11886]: 
updateButtonBadge@resource://gre/modules/commonjs/toolkit/loader.js -> 
resource://cachedisabler/index.js:71:5
Jun 02 14:25:03 Simux xsane.desktop[11886]: 
resetAllPrefs@resource://gre/modules/commonjs/toolkit/loader.js -> 
resource://cachedisabler/index.js:67:5
Jun 02 14:25:03 Simux xsane.desktop[11886]: 
exports.onUnload@resource://gre/modules/commonjs/toolkit/loader.js -> 
resource://cachedisabler/index.js:91:5
Jun 02 14:25:03 Simux xsane.desktop[11886]: 
unload/<@resource://gre/modules/commonjs/toolkit/loader.js -> 
resource://gre/modules/commonjs/sdk/system/unload.js:79:9
Jun 02 14:25:03 Simux xsane.desktop[11886]: 

Re: [sane-devel] scanbd on ubuntu

[Herr Oswald]

Sorry, this probabely is stupid - but I do not know where to begin.
This is the core of my question. (Some hints at sourceforge's project
page could be helpful...)

You wrote that the old ArchLinux instructions will do. OK - I'll try
these and report back.

W

Am Donnerstag, den 01.06.2017, 21:52 +0200 schrieb Wilhelm Meier:
> Well ... what did you test?
> Did you follow some setup guide?
> Did you inspect the log files?
> Did you read the docu of scanbd?
> 
> 
> Am 01.06.2017 um 21:49 schrieb Herr Oswald:
> > I'm using an old 
> > 
> > HP 7400c USB scanner on 
> > ubuntu 16.10, 
> > scanbd 1.4.4-1build1,
> > sane-utils 1.0.27+git20170530-yakkety0
> > 
> > everything as it came - and now I'm a little helpless... ):
> > 
> > W
> > 
> > 
> > Am Donnerstag, den 01.06.2017, 09:35 +0200 schrieb Wilhelm Meier:
> > > Hi Wolf,
> > > 
> > > please provide us with a little bit more information, e.g. what
> > > scanner
> > > type, the contents of your config-files, log-files.
> > > 
> > > Despite from that: you can follow the ArchLinux setup guide.
> > > 
> > > --
> > >  Wilhelm
> > > 
> > > Am 01.06.2017 um 09:14 schrieb Herr Oswald:
> > > > Hello,
> > > > 
> > > > I installed the scanbd package on my ubuntu 16.10 - but could
> > > > not
> > > > find
> > > > a fairly recent set of instructions for the setup.
> > > > 
> > > > There is a very comprehensive one for ArchLinux from 2013,
> > > > there is
> > > > a
> > > > one for ubuntu, but for scanbuttond, which may be outdated as
> > > > well
> > > > -
> > > > and the /etc/scanbd/scanbd.conf does not really speak to me... 
> > > > 
> > > > Does anybody here happen to have a hint? - All I want is the
> > > > scanner to
> > > > make a scan when some button at it is pressed.
> > > > 
> > > > Cheers,
> > > > Wolf 
> > > > 
> > > 
> > > 
> > > 
> 
> 

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

Re: [sane-devel] scanbd on ubuntu

[Wilhelm Meier]

Well ... what did you test?
Did you follow some setup guide?
Did you inspect the log files?
Did you read the docu of scanbd?


Am 01.06.2017 um 21:49 schrieb Herr Oswald:
> I'm using an old 
> 
> HP 7400c USB scanner on 
> ubuntu 16.10, 
> scanbd 1.4.4-1build1,
> sane-utils 1.0.27+git20170530-yakkety0
> 
> everything as it came - and now I'm a little helpless... ):
> 
> W
> 
> 
> Am Donnerstag, den 01.06.2017, 09:35 +0200 schrieb Wilhelm Meier:
>> Hi Wolf,
>>
>> please provide us with a little bit more information, e.g. what
>> scanner
>> type, the contents of your config-files, log-files.
>>
>> Despite from that: you can follow the ArchLinux setup guide.
>>
>> --
>>  Wilhelm
>>
>> Am 01.06.2017 um 09:14 schrieb Herr Oswald:
>>> Hello,
>>>
>>> I installed the scanbd package on my ubuntu 16.10 - but could not
>>> find
>>> a fairly recent set of instructions for the setup.
>>>
>>> There is a very comprehensive one for ArchLinux from 2013, there is
>>> a
>>> one for ubuntu, but for scanbuttond, which may be outdated as well
>>> -
>>> and the /etc/scanbd/scanbd.conf does not really speak to me... 
>>>
>>> Does anybody here happen to have a hint? - All I want is the
>>> scanner to
>>> make a scan when some button at it is pressed.
>>>
>>> Cheers,
>>> Wolf 
>>>
>>
>>
>>
> 


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

Re: [sane-devel] scanbd on ubuntu

[Herr Oswald]

I'm using an old 

HP 7400c USB scanner on 
ubuntu 16.10, 
scanbd 1.4.4-1build1,
sane-utils 1.0.27+git20170530-yakkety0

everything as it came - and now I'm a little helpless... ):

W


Am Donnerstag, den 01.06.2017, 09:35 +0200 schrieb Wilhelm Meier:
> Hi Wolf,
> 
> please provide us with a little bit more information, e.g. what
> scanner
> type, the contents of your config-files, log-files.
> 
> Despite from that: you can follow the ArchLinux setup guide.
> 
> --
>  Wilhelm
> 
> Am 01.06.2017 um 09:14 schrieb Herr Oswald:
> > Hello,
> > 
> > I installed the scanbd package on my ubuntu 16.10 - but could not
> > find
> > a fairly recent set of instructions for the setup.
> > 
> > There is a very comprehensive one for ArchLinux from 2013, there is
> > a
> > one for ubuntu, but for scanbuttond, which may be outdated as well
> > -
> > and the /etc/scanbd/scanbd.conf does not really speak to me... 
> > 
> > Does anybody here happen to have a hint? - All I want is the
> > scanner to
> > make a scan when some button at it is pressed.
> > 
> > Cheers,
> > Wolf 
> > 
> 
> 
> 

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

Re: [sane-devel] scanbd on ubuntu

[Wilhelm Meier]

Hi Wolf,

please provide us with a little bit more information, e.g. what scanner
type, the contents of your config-files, log-files.

Despite from that: you can follow the ArchLinux setup guide.

--
 Wilhelm

Am 01.06.2017 um 09:14 schrieb Herr Oswald:
> Hello,
> 
> I installed the scanbd package on my ubuntu 16.10 - but could not find
> a fairly recent set of instructions for the setup.
> 
> There is a very comprehensive one for ArchLinux from 2013, there is a
> one for ubuntu, but for scanbuttond, which may be outdated as well -
> and the /etc/scanbd/scanbd.conf does not really speak to me... 
> 
> Does anybody here happen to have a hint? - All I want is the scanner to
> make a scan when some button at it is pressed.
> 
> Cheers,
> Wolf 
> 



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

[sane-devel] scanbd on ubuntu

[Herr Oswald]

Hello,

I installed the scanbd package on my ubuntu 16.10 - but could not find
a fairly recent set of instructions for the setup.

There is a very comprehensive one for ArchLinux from 2013, there is a
one for ubuntu, but for scanbuttond, which may be outdated as well -
and the /etc/scanbd/scanbd.conf does not really speak to me... 

Does anybody here happen to have a hint? - All I want is the scanner to
make a scan when some button at it is pressed.

Cheers,
Wolf 

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

Re: [sane-devel] Scanbd, Sane and Samsung SCX-3200

[Wilhelm Meier]

Hi Janne,

Am 26.05.2017 um 14:03 schrieb Janne Paalijarvi:
> Hello,
> 
> I am developing support for scan button for my Samsung SCX-3200 series.
> In fact, I actually already wrote some code at:
> 
> https://github.com/usvi/random/tree/master/c/scanbuttond/samsung
> 
> Funnily, I have had not time before these few days to actually try to
> set everything to work for testing.
> 
> Now, when I installed scanbd for my test Ubuntu from Ubuntu
> repositories, I realized that it uses extensively Sane backends. So, my
> question is: Should I actually try to write a backend extension for the
> Sane backend I am using (xerox_mfp)? Is it the way of the future that
> Scanbd actually polls/queries devices via Sane?

I wrote scanbd in order to use the sane-backend, because at the time of
starting with scanbd, scanbuttond seems quite dead. I incorporated
scanbuttond-backends "as-is" to support scanners that didn't had
querying support in sane-backends.

So - in short - up to my view it would be best to make the snae-backend
for your scanner working ...

HTH,
 Wilhelm

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.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 integration (was Re: sane-backends release 1.0.26 schedule)

[Olaf Meeuwissen]

Hi Louis,

I already commented rather elaborately on your reply to Allan's follow
up.  Here I just pick up on the things specific to this reply of yours.

Louis Lagendijk writes:

> On Sat, 2017-05-06 at 21:20 +0900, Olaf Meeuwissen wrote:
>> Hi Louis,
>>
>> Louis Lagendijk writes:
>>
>> [snip]
>>
>> > I made a patch to dll.c where
>> > - It used the dll.conf with the name pointed out by env. var
>> > SANE_CONFIG_FILE if defined, if not
>> > - it tries to load a dll2.conf if it exists. This is meant to be a
>> > file
>> > dropped in thre sane config dir by scanbd. If that does not exist
>> > - it follows the existing code path.
>>
>> So, if I understand correctly, your patched dll backend tries
>>
>>  $SANE_CONFIG_FILE (if defined)
>>  $SANE_CONFIG_DIR/dll2.conf (if SANE_CONFIG_DIR is defined)
>>  $sysconfdir/dll2.conf
>>  $SANE_CONFIG_DIR/dll.conf (if SANE_CONFIG_DIR is defined)
>>  $sysconfdir/dll.conf
>>
>> where $sysconfdir is set at ./configure time.Is that right?
>>
> Yes, I am indeed using the $sysconfdir (or SANE_CONFIG_DIR) as search
> path for all config files.
>
> I am using the sanei functions for loading the config, so the logic is
> the same as for loading other config files.

As long as you're using sanei_config_open() to get the file you should
be fine.

>> > I added a #include statement in the config file so dll2.conf can
>> > include dll.conf if so required.
>>
>> How does that work when SANE_CONFIG_DIR is defined?
>
> I need to check this, but I am using sanei_config so it SHOULD (famous
> last words) work. do it would follow the normal search path
> (SANE_CONFIG_DIR if set, otherwise $sysconfdir). I actually implemented
> this by a call to read_conf with the new name from within read_config.
> This would allow even allow an include from an include.

What about the possibility of infinite loops in this case?  An a.conf
including b.conf which includes a.conf.  The various directories that
may be visited in order to locate a file makes this even more difficult
to track/detect.

> I however just realized that if a user gets the override dll.conf,
> scanbd could use dll.conf explicitely. This removes the need for the
> #include, so i will remove it.

That would eliminate a few questions ;-)

> alan mailed me about one issue: if there is a dll2.conf but scanbd is
> not started, sane would not find any scanners. I don't know what to do
> about that case. Well start scanbd init scripts or the systemd units
> could place/remove the dll2.conf, but that is to much of an hack.

The init system should not be doing this kind of stuff.  The package's
post-installation and pre-removal scripts could do this instead.

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

[Louis Lagendijk]

On Sat, 2017-05-06 at 21:20 +0900, Olaf Meeuwissen wrote:
> Hi Louis,
> 
> Louis Lagendijk writes:
> 
> > On Fri, 2017-04-28 at 08:04 -0400, m. allan noah wrote:
> > > Ok folks, it's time to get another sane-backends release out the
> > > door.
> > 
> > [snip]
> > 
> > Hi,
> > Yesterday when I had a look at our bug tracker for any issues in my
> > code I found https://alioth.debian.org/tracker/?func=detail_i
> > d=30186=315004=410366
> > This is an issue for scanbd integration that requires more
> > flexibility
> > for configuration of dll-loading: when scanbd is used users need to
> > use
> > the net backend only, but scanbd/saned need to be fed with the
> > "normal" list of backends.
> 
> Thanks for trying to improve scanbd integration.
> 
> > I made a patch to dll.c where
> > - It used the dll.conf with the name pointed out by env. var
> > SANE_CONFIG_FILE if defined, if not
> > - it tries to load a dll2.conf if it exists. This is meant to be a
> > file
> > dropped in thre sane config dir by scanbd. If that does not exist
> > - it follows the existing code path.
> 
> So, if I understand correctly, your patched dll backend tries
> 
>   $SANE_CONFIG_FILE (if defined)
>   $SANE_CONFIG_DIR/dll2.conf (if SANE_CONFIG_DIR is defined)
>   $sysconfdir/dll2.conf
>   $SANE_CONFIG_DIR/dll.conf (if SANE_CONFIG_DIR is defined)
>   $sysconfdir/dll.conf
> 
> where $sysconfdir is set at ./configure time.  Is that right?
> 
Yes, I am indeed using the $sysconfdir (or SANE_CONFIG_DIR) as search
path for all config files. 

I am using the sanei functions for loading the config, so the logic is
the same as for loading other config files.


> If so, I guess that could be okay but I don't like the dll2.conf name
> very much.  It seems to imply there's a dll2 backend.  There isn't
> one,
> not now at least.
Neither do I. I am still looking for something better, right now I am
trying to get a working solution. How about dll-override.conf?

> > I added a #include statement in the config file so dll2.conf can
> > include dll.conf if so required.
> 
> How does that work when SANE_CONFIG_DIR is defined?

I need to check this, but I am using sanei_config so it SHOULD (famous
last words) work. do it would follow the normal search path
(SANE_CONFIG_DIR if set, otherwise $sysconfdir). I actually implemented
this by a call to read_conf with the new name from within read_config.
This would allow even allow an include from an include.

I however just realized that if a user gets the override dll.conf,
scanbd could use dll.conf explicitely. This removes the need for the
#include, so i will remove it.

alan mailed me about one issue: if there is a dll2.conf but scanbd is
not started, sane would not find any scanners. I don't know what to do
about that case. Well start scanbd init scripts or the systemd units
could place/remove the dll2.conf, but that is to much of an hack. Maybe
 add a pidfile parameter on the first line in dll2.conf that if not
present makes sane fallback to dll.conf?

Thanks for the feedback
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] scanbd integration (was Re: sane-backends release 1.0.26 schedule)

[Olaf Meeuwissen]

Hi Louis,

Louis Lagendijk writes:

> On Fri, 2017-04-28 at 08:04 -0400, m. allan noah wrote:
>> Ok folks, it's time to get another sane-backends release out the
>> door.
> [snip]
>
> Hi,
> Yesterday when I had a look at our bug tracker for any issues in my
> code I found 
> https://alioth.debian.org/tracker/?func=detail_id=30186=315004=410366
> This is an issue for scanbd integration that requires more flexibility
> for configuration of dll-loading: when scanbd is used users need to use
> the net backend only, but scanbd/saned need to be fed with the
> "normal" list of backends.

Thanks for trying to improve scanbd integration.

> I made a patch to dll.c where
> - It used the dll.conf with the name pointed out by env. var
> SANE_CONFIG_FILE if defined, if not
> - it tries to load a dll2.conf if it exists. This is meant to be a file
> dropped in thre sane config dir by scanbd. If that does not exist
> - it follows the existing code path.

So, if I understand correctly, your patched dll backend tries

  $SANE_CONFIG_FILE (if defined)
  $SANE_CONFIG_DIR/dll2.conf (if SANE_CONFIG_DIR is defined)
  $sysconfdir/dll2.conf
  $SANE_CONFIG_DIR/dll.conf (if SANE_CONFIG_DIR is defined)
  $sysconfdir/dll.conf

where $sysconfdir is set at ./configure time.  Is that right?

If so, I guess that could be okay but I don't like the dll2.conf name
very much.  It seems to imply there's a dll2 backend.  There isn't one,
not now at least.

> I added a #include statement in the config file so dll2.conf can
> include dll.conf if so required.

How does that work when SANE_CONFIG_DIR is defined?

> I am in the process of testing and cleaningup. but my question is:
> should I commit this change so close to the freeze date?

I prefer you don't.  There still seem to be a few things that need
sorting out and code freeze is tomorrow ;-)  Too risky if you ask me.

> Documentation is still to be done, but I would still have 2 weeks for
> that.  Alan, what do you think?

Allan, can we make improving scanbd integration a priority for the
release after 1.0.26 and schedule that soonish, like say in three months
or so?  Preferably in time for inclusion in the Autumn releases of the
major Linux distributions.

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] scanbd ... next steps / questions ...

[Wilhelm Meier]

Am 03.05.2017 um 19:50 schrieb Dr.-Ing. Dieter Jurzitza:
> Hi Axel,
> thank you very much for your feedback - I hope to have more spare time next 
> weekend to dive again into this issue.
> 
> But in general: I had had thought that there is a "generic" dll.conf having 
> only the net - backend enabled that sits in /etc/saned (after configuration 
> of 
> scanbd). This I took from the README.txt:
> 
> ***
> 6) sane config
> 
> All desktop applications should only get access to the scanners via the net
> backend, so edit /etc/sane.d/dll.conf to only contain the net-backend on the 
> desktop machines. 
> 
> example dll.conf:
> ---
> net
> ---
> ***
> 
> but somewhere there is a need to tell sane which physical device to use, so I 
> thought - maybe erratically - that scanbd "hides" other entries / a different 
> dll.conf in /etc/saned from sane and tells sane itself which scanner to use 
> but depicts to the "outer world" that there is nothing but a network scanner. 
> As readily said, this may be totally wrong. If I read your comments it sounds 
> as if the sane - configuration ought to remain "as is", but this is not what 
> the above mentioned entry in README.txt from scanbd tells me.

Please read the ReadMe.txt carefully ;-)

All local scan-applications like xsane e.g. have to use the net-backend.
This is the only way to intercept a scan-request by scanbd. scanbd in
turn has to start saned to perform the real scan. saned itself use the
normal way for configuration: it normally would use the
/etc/sane/dll.conf, but this would be wrong since it leads to an
infinity recursion via the net backend. Therefore scanbd uses the
SANE_CONFIG_DIR to point saned to another location to find an
alternative dll.conf - and this dll.conf should only contain the local
attached scanners (or remote on other machines).

Sounds a bit complicated, but this is the way it is ...

HTH,
 Wilhelm

> 
> Regards,
> thanks for all the work
> 
> 
> 
> 
> Dieter Jurzitza
> 
> 
> 
> Am Donnerstag, 27. April 2017, 15:29:09 schrieb Axel Schöner:
>> Am Samstag, 22. April 2017, 19:02:57 CEST schrieb Dr.-Ing. Dieter Jurzitza:
>>> Dear listmembers,
>>> probably these questions have readily been asked over and over again, then
>>> my apologies:
>>>
>>> 1.) /etc/scanbd/scripts
>>> which scripts does this refer to? There are some scripts in /etc/scanbd,
>>> those like "scanadf.script" and "test.script" (I am using a spec - file
>>> for
>>> opensuse some other person had had generated)? If I look into
>>> /etc/scanbd/scanbd.conf they ought to reside within /etc/scanbd/scripts,
>>> is
>>> that correct? Is there a configure - option that would print out all
>>> directories in use (or, even better, put this summarizing into config.log
>>> like several other packages do / emacs is a nice example in this regard
>>> ...)?
>>
>> The scripts which are executed while device insertion/removal and by pushing
>> buttons should be located in ${prefix}/etc/scanbd/scripts. We will fix the
>> makefiles... to correct this (in the next days).
>>
>>> 2.) /usr/lib64/scanbd/scanbuttond/backends, is this the directory I should
>>> copy /etc/saned/dll.conf to as well as all the other files from /etc/saned
>>> that are uncommented within *this* dll.conf (except net.conf) in contrast
>>> to /etc/saned/dll.conf that ought to contain no reference but "net"? Is
>>> this what is menat with "backends"?
>>
>> I think these files should be in ${prefix}/etc/saned/. Where do you have
>> this information from?
>>
>>> 3.) SCANBD_DEVICE could be /dev/scanner (if I have such a device?)
>>
>> In most cases there is no such devicenode.
>> It could be something like plustek:libusb:001:003.
>> When you plug in your device it should be detected if there is a supported
>> driver configured. Look at the end of ${prefix}/etc/saned/scanbd.conf
>>
>>> 4.) SCANBD_ACTION - I do not really understand what is about this.
>>
>> This is a variable which represents the actual event (insert, remove, scan,
>> copy, ...) the definitions are in scanbd.conf.
>> It is possible to trigger different scripts based on these events (if you
>> have more then one detected button on your scanner).
>>
>> You can launch scanbd in debug mode to see the values of SCANBD_DEVICE and
>> SCANBD_ACTION: ${prefix}/sbin/scanbd -d7 -f -c
>> ${prefix}/etc/scanbd/scanbd.conf .
>>
>>> From within the "README.txt in the source-directory I did not really
>>> understand what is meant with the variables - would it be too much to
>>> simply ask for an example that would shed some light on the do's and
>>> don'ts of the configuration if the "regular" scanner would be say "hp"
>>> and the
>>> corresponding device would be "/dev/scanner"?
>>>
>>> I am trying to set up a spec - file for a rpm - package, but as of now
>>> there is too much understanding missing on my side to get that tracked
>>> down in such a way that I can be satisfied with the results 

Re: [sane-devel] scanbd ... next steps / questions ...

[Dr.-Ing. Dieter Jurzitza]

Hi Axel,
thank you very much for your feedback - I hope to have more spare time next 
weekend to dive again into this issue.

But in general: I had had thought that there is a "generic" dll.conf having 
only the net - backend enabled that sits in /etc/saned (after configuration of 
scanbd). This I took from the README.txt:

***
6) sane config

All desktop applications should only get access to the scanners via the net
backend, so edit /etc/sane.d/dll.conf to only contain the net-backend on the 
desktop machines. 

example dll.conf:
---
net
---
***

but somewhere there is a need to tell sane which physical device to use, so I 
thought - maybe erratically - that scanbd "hides" other entries / a different 
dll.conf in /etc/saned from sane and tells sane itself which scanner to use 
but depicts to the "outer world" that there is nothing but a network scanner. 
As readily said, this may be totally wrong. If I read your comments it sounds 
as if the sane - configuration ought to remain "as is", but this is not what 
the above mentioned entry in README.txt from scanbd tells me.

Regards,
thanks for all the work




Dieter Jurzitza



Am Donnerstag, 27. April 2017, 15:29:09 schrieb Axel Schöner:
> Am Samstag, 22. April 2017, 19:02:57 CEST schrieb Dr.-Ing. Dieter Jurzitza:
> > Dear listmembers,
> > probably these questions have readily been asked over and over again, then
> > my apologies:
> > 
> > 1.) /etc/scanbd/scripts
> > which scripts does this refer to? There are some scripts in /etc/scanbd,
> > those like "scanadf.script" and "test.script" (I am using a spec - file
> > for
> > opensuse some other person had had generated)? If I look into
> > /etc/scanbd/scanbd.conf they ought to reside within /etc/scanbd/scripts,
> > is
> > that correct? Is there a configure - option that would print out all
> > directories in use (or, even better, put this summarizing into config.log
> > like several other packages do / emacs is a nice example in this regard
> > ...)?
> 
> The scripts which are executed while device insertion/removal and by pushing
> buttons should be located in ${prefix}/etc/scanbd/scripts. We will fix the
> makefiles... to correct this (in the next days).
> 
> > 2.) /usr/lib64/scanbd/scanbuttond/backends, is this the directory I should
> > copy /etc/saned/dll.conf to as well as all the other files from /etc/saned
> > that are uncommented within *this* dll.conf (except net.conf) in contrast
> > to /etc/saned/dll.conf that ought to contain no reference but "net"? Is
> > this what is menat with "backends"?
> 
> I think these files should be in ${prefix}/etc/saned/. Where do you have
> this information from?
> 
> > 3.) SCANBD_DEVICE could be /dev/scanner (if I have such a device?)
> 
> In most cases there is no such devicenode.
> It could be something like plustek:libusb:001:003.
> When you plug in your device it should be detected if there is a supported
> driver configured. Look at the end of ${prefix}/etc/saned/scanbd.conf
> 
> > 4.) SCANBD_ACTION - I do not really understand what is about this.
> 
> This is a variable which represents the actual event (insert, remove, scan,
> copy, ...) the definitions are in scanbd.conf.
> It is possible to trigger different scripts based on these events (if you
> have more then one detected button on your scanner).
> 
> You can launch scanbd in debug mode to see the values of SCANBD_DEVICE and
> SCANBD_ACTION: ${prefix}/sbin/scanbd -d7 -f -c
> ${prefix}/etc/scanbd/scanbd.conf .
> 
> > From within the "README.txt in the source-directory I did not really
> > understand what is meant with the variables - would it be too much to
> > simply ask for an example that would shed some light on the do's and
> > don'ts of the configuration if the "regular" scanner would be say "hp"
> > and the
> > corresponding device would be "/dev/scanner"?
> > 
> > I am trying to set up a spec - file for a rpm - package, but as of now
> > there is too much understanding missing on my side to get that tracked
> > down in such a way that I can be satisfied with the results 
> > 
> > Thank you very much,
> > regards
> > 
> > 
> > 
> > 
> > Dieter Jurzitza

-- 
---
Dr.-Ing. Dieter Jurzitza76131 Karlsruhe


-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.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 ... next steps / questions ...

[Axel Schöner]

Am Donnerstag, 27. April 2017, 15:29:09 CEST schrieben Sie:

> Am Samstag, 22. April 2017, 19:02:57 CEST schrieb Dr.-Ing. Dieter Jurzitza:

> > Dear listmembers,

> > probably these questions have readily been asked over and over again, then

> > my apologies:

> >

> > 1.) /etc/scanbd/scripts

> > which scripts does this refer to? There are some scripts in /etc/scanbd,

> > those like "scanadf.script" and "test.script" (I am using a spec - file

> > for

> > opensuse some other person had had generated)? If I look into

> > /etc/scanbd/scanbd.conf they ought to reside within /etc/scanbd/scripts,

> > is

> > that correct? Is there a configure - option that would print out all

> > directories in use (or, even better, put this summarizing into config.log

> > like several other packages do / emacs is a nice example in this regard

> > ...)?

>

> The scripts which are executed while device insertion/removal and by pushing

> buttons should be located in ${prefix}/etc/scanbd/scripts. We will fix the

> makefiles... to correct this (in the next days).

>

 

The changes are now online in version >= [r243] .

 

 

> > 2.) /usr/lib64/scanbd/scanbuttond/backends, is this the directory I should

> > copy /etc/saned/dll.conf to as well as all the other files from /etc/saned

> > that are uncommented within *this* dll.conf (except net.conf) in contrast

> > to /etc/saned/dll.conf that ought to contain no reference but "net"? Is

> > this what is menat with "backends"?

>

> I think these files should be in ${prefix}/etc/saned/. Where do you have

> this information from?

>

> > 3.) SCANBD_DEVICE could be /dev/scanner (if I have such a device?)

>

> In most cases there is no such devicenode.

> It could be something like plustek:libusb:001:003.

> When you plug in your device it should be detected if there is a supported

> driver configured. Look at the end of ${prefix}/etc/saned/scanbd.conf

>

> > 4.) SCANBD_ACTION - I do not really understand what is about this.

>

> This is a variable which represents the actual event (insert, remove, scan,

> copy, ...) the definitions are in scanbd.conf.

> It is possible to trigger different scripts based on these events (if you

> have more then one detected button on your scanner).

>

> You can launch scanbd in debug mode to see the values of SCANBD_DEVICE and

> SCANBD_ACTION: ${prefix}/sbin/scanbd -d7 -f -c

> ${prefix}/etc/scanbd/scanbd.conf .

>

> > From within the "README.txt in the source-directory I did not really

> > understand what is meant with the variables - would it be too much to

> > simply ask for an example that would shed some light on the do's and

> > don'ts of the configuration if the "regular" scanner would be say "hp"

> > and the

> > corresponding device would be "/dev/scanner"?

> >

> > I am trying to set up a spec - file for a rpm - package, but as of now

> > there is too much understanding missing on my side to get that tracked

> > down in such a way that I can be satisfied with the results 

> >

> > Thank you very much,

> > regards

> >

> >

> >

> >

> > Dieter Jurzitza

 


-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.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] scanbd ... next steps / questions ...

[Dr.-Ing. Dieter Jurzitza]

Dear listmembers,
probably these questions have readily been asked over and over again, then my 
apologies:

1.) /etc/scanbd/scripts
which scripts does this refer to? There are some scripts in /etc/scanbd, those 
like "scanadf.script" and "test.script" (I am using a spec - file for opensuse 
some other person had had generated)? If I look into /etc/scanbd/scanbd.conf 
they ought to reside within /etc/scanbd/scripts, is that correct? Is there a 
configure - option that would print out all directories in use (or, even 
better, put this summarizing into config.log like several other packages do / 
emacs is a nice example in this regard ...)?
2.) /usr/lib64/scanbd/scanbuttond/backends, is this the directory I should 
copy /etc/saned/dll.conf to as well as all the other files from /etc/saned 
that are uncommented within *this* dll.conf (except net.conf) in contrast to 
/etc/saned/dll.conf that ought to contain no reference but "net"? Is this what 
is menat with "backends"?
3.) SCANBD_DEVICE could be /dev/scanner (if I have such a device?)
4.) SCANBD_ACTION - I do not really understand what is about this.

>From within the "README.txt in the source-directory I did not really 
understand what is meant with the variables - would it be too much to simply 
ask for an example that would shed some light on the do's and don'ts of the 
configuration if the "regular" scanner would be say "hp" and the corresponding 
device would be "/dev/scanner"?

I am trying to set up a spec - file for a rpm - package, but as of now there 
is too much understanding missing on my side to get that tracked down in such 
a way that I can be satisfied with the results 

Thank you very much,
regards




Dieter Jurzitza
-- 
---
Dr.-Ing. Dieter Jurzitza76131 Karlsruhe


-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.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 ?

[Wilhelm Meier]

Am 16.04.2017 um 16:15 schrieb Florian Gagel:
> Hi Wilhelm,
> 
> thanks for your patch, works like a charm - I just had to made a small
> modification since
> the backend name inside the wrapper actually is "Genesys USB" (see below).

Thank you, Florian, for checking this once again. Just pushed this into
trunk!

> A minor hint for those who tinker around like me: Do no forget to turn
> debugging off in
> scanbd.conf when finished, otherwise syslog will overflow :-)
> 
> Regards,
> 
>   Florian
> 
> === cut here 
> --- /usr/local/src/tmp/1.5.0/src/scanbd/scanbuttond_wrapper.c   
> 2017-04-05 05:46:59.0 +
> +++ scanbuttond_wrapper.c2017-04-16 13:41:07.140209953 +
> @@ -1062,11 +1062,35 @@
>  assert(backend_name);
>  slog(SLOG_INFO, "scanbtnd_button_name, backend: %s", backend_name);
>  
> -if (strcmp("snapscan", backend_name)) {
> -assert(button <= 5);
> +if (strncmp("Genesys", backend_name,7) == 0) {
>  switch(button) {
>  case 0:
> -return NULL;
> +return "zero";
> +break;
> +case 1:
> +return "copy";
> +break;
> +case 2:
> +return "scan";
> +break;
> +case 3:
> +return "pdf";
> +break;
> +case 4:
> +return "email";
> +break;
> +case 5:
> +return "stop";
> +break;
> +default:
> +return "default";
> +break;
> +}
> +}
> +else {
> +switch(button) {
> +case 0:
> +return "zero";
>  break;
>  case 1:
>  return "scan"; // "web";
> @@ -1084,9 +1108,10 @@
>  return "stop";
>  break;
>  default:
> -return NULL;
> +return "default";
>  break;
>  }
> +   
>  }
>  return NULL;
>  }
> 
> 
> Am 16.04.2017 um 11:59 schrieb Wilhelm:
>> Am 15.04.2017 um 20:38 schrieb Florian Gagel:
>>> Hi Wilhelm,
>>>
>>> thanks, your modification made all four buttons work !
>> Great!
>>
>>> 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:
>> Please backout the last patch I sent and now apply the attached one.
>> This should mark your buttons with the right labels.
>>
>> If thats ok for you, I'll check this into trunk.
>>
>> Please report if teh patch is ok, or make your own modifications and
>> send the patch back to me to be inserted into trunk.
>>
>> Thanks for using scanbd.
>>
>> -- Wilhelm
>>
>>>  (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:/
 

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

[Florian Gagel]

Hi Wilhelm,

thanks for your patch, works like a charm - I just had to made a small 
modification since

the backend name inside the wrapper actually is "Genesys USB" (see below).
A minor hint for those who tinker around like me: Do no forget to turn 
debugging off in

scanbd.conf when finished, otherwise syslog will overflow :-)

Regards,

  Florian

=== cut here 
--- /usr/local/src/tmp/1.5.0/src/scanbd/scanbuttond_wrapper.c 2017-04-05 
05:46:59.0 +

+++ scanbuttond_wrapper.c2017-04-16 13:41:07.140209953 +
@@ -1062,11 +1062,35 @@
 assert(backend_name);
 slog(SLOG_INFO, "scanbtnd_button_name, backend: %s", backend_name);

-if (strcmp("snapscan", backend_name)) {
-assert(button <= 5);
+if (strncmp("Genesys", backend_name,7) == 0) {
 switch(button) {
 case 0:
-return NULL;
+return "zero";
+break;
+case 1:
+return "copy";
+break;
+case 2:
+return "scan";
+break;
+case 3:
+return "pdf";
+break;
+case 4:
+return "email";
+break;
+case 5:
+return "stop";
+break;
+default:
+return "default";
+break;
+}
+}
+else {
+switch(button) {
+case 0:
+return "zero";
 break;
 case 1:
 return "scan"; // "web";
@@ -1084,9 +1108,10 @@
 return "stop";
 break;
 default:
-return NULL;
+return "default";
 break;
 }
+
 }
 return NULL;
 }


Am 16.04.2017 um 11:59 schrieb Wilhelm:

Am 15.04.2017 um 20:38 schrieb Florian Gagel:

Hi Wilhelm,

thanks, your modification made all four buttons work !

Great!


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:

Please backout the last patch I sent and now apply the attached one.
This should mark your buttons with the right labels.

If thats ok for you, I'll check this into trunk.

Please report if teh patch is ok, or make your own modifications and
send the patch back to me to be inserted into trunk.

Thanks for using scanbd.

-- Wilhelm


  (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 

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

[Wilhelm]

Am 15.04.2017 um 20:38 schrieb Florian Gagel:
> Hi Wilhelm,
> 
> thanks, your modification made all four buttons work !

Great!

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

Please backout the last patch I sent and now apply the attached one.
This should mark your buttons with the right labels.

If thats ok for you, I'll check this into trunk.

Please report if teh patch is ok, or make your own modifications and
send the patch back to me to be inserted into trunk.

Thanks for using scanbd.

-- Wilhelm

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

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

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

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

[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] scanbd and Canon LiDE 60: buttons not recognized ?

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

[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] scanbd crashes when turning on all-in-one

[Wilhelm]

Am 11.04.2017 um 16:49 schrieb Manuel Reiter:
> I'm using scanbd with a Pixma MP610 all-in-one on a Raspberry Pi 3 running an 
> up-to-date Rasbian Jessie.
> This works pretty well (with some setup help from this list). However, when I 
> turn on the device, scanbd
> seems to crash:

This is a known bug on debian-based systems. The root cause is due to a
bug in libsane.

However, since scanbd-1.5.0 (or trunk) there is a workaround in scanbd
that should fix the problem.

What is your version?

> 
> Apr 11 07:32:40 hive kernel: [134163.203415] usb 1-1.2: new high-speed USB 
> device number 8 using dwc_otg
> Apr 11 07:32:40 hive kernel: [134163.304688] usb 1-1.2: New USB device found, 
> idVendor=04a9, idProduct=1725
> Apr 11 07:32:40 hive kernel: [134163.304711] usb 1-1.2: New USB device 
> strings: Mfr=1, Product=2, SerialNumber=3
> Apr 11 07:32:40 hive kernel: [134163.304724] usb 1-1.2: Product: MP610 series
> Apr 11 07:32:40 hive kernel: [134163.304736] usb 1-1.2: Manufacturer: Canon
> Apr 11 07:32:40 hive kernel: [134163.304748] usb 1-1.2: SerialNumber: 414EE7
> Apr 11 07:32:40 hive kernel: [134163.310051] usblp 1-1.2:1.1: usblp0: USB 
> Bidirectional printer dev 8 if 1 alt 0 proto 2 vid 0x04A9 pid 0x1725
> Apr 11 07:32:40 hive kernel: [134163.310535] usb-storage 1-1.2:1.2: USB Mass 
> Storage device detected
> Apr 11 07:32:40 hive kernel: [134163.311524] scsi host3: usb-storage 1-1.2:1.2
> Apr 11 07:32:40 hive systemd[1]: Starting Printer.
> Apr 11 07:32:40 hive systemd[1]: Reached target Printer.
> Apr 11 07:32:40 hive systemd[1]: scanbd.service: main process exited, 
> code=killed, status=11/SEGV
> 
> Is this known behaviour? I guess I can get around it by adding a Restart 
> option to the systemd unit file,
> but I'd like to know whether something's possibly wrong first.
> 
> Thanks in advance for your help!
> 
> All the best,
> 
>   Manuel
> 


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

Re: [sane-devel] scanbd crashes when turning on all-in-one

[Wilhelm]

Am 11.04.2017 um 16:49 schrieb Manuel Reiter:
> I'm using scanbd with a Pixma MP610 all-in-one on a Raspberry Pi 3 running an 
> up-to-date Rasbian Jessie.
> This works pretty well (with some setup help from this list). However, when I 
> turn on the device, scanbd
> seems to crash:

This is a known bug on debian-based systems. The root cause is due to a
bug in libsane.

However, since scanbd-1.5.0 (or trunk) there is a workaround in scanbd
that should fix the problem.

What is your version?

> 
> Apr 11 07:32:40 hive kernel: [134163.203415] usb 1-1.2: new high-speed USB 
> device number 8 using dwc_otg
> Apr 11 07:32:40 hive kernel: [134163.304688] usb 1-1.2: New USB device found, 
> idVendor=04a9, idProduct=1725
> Apr 11 07:32:40 hive kernel: [134163.304711] usb 1-1.2: New USB device 
> strings: Mfr=1, Product=2, SerialNumber=3
> Apr 11 07:32:40 hive kernel: [134163.304724] usb 1-1.2: Product: MP610 series
> Apr 11 07:32:40 hive kernel: [134163.304736] usb 1-1.2: Manufacturer: Canon
> Apr 11 07:32:40 hive kernel: [134163.304748] usb 1-1.2: SerialNumber: 414EE7
> Apr 11 07:32:40 hive kernel: [134163.310051] usblp 1-1.2:1.1: usblp0: USB 
> Bidirectional printer dev 8 if 1 alt 0 proto 2 vid 0x04A9 pid 0x1725
> Apr 11 07:32:40 hive kernel: [134163.310535] usb-storage 1-1.2:1.2: USB Mass 
> Storage device detected
> Apr 11 07:32:40 hive kernel: [134163.311524] scsi host3: usb-storage 1-1.2:1.2
> Apr 11 07:32:40 hive systemd[1]: Starting Printer.
> Apr 11 07:32:40 hive systemd[1]: Reached target Printer.
> Apr 11 07:32:40 hive systemd[1]: scanbd.service: main process exited, 
> code=killed, status=11/SEGV
> 
> Is this known behaviour? I guess I can get around it by adding a Restart 
> option to the systemd unit file,
> but I'd like to know whether something's possibly wrong first.
> 
> Thanks in advance for your help!
> 
> All the best,
> 
>   Manuel
> 


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

Re: [sane-devel] scanbd on Raspbian: scanner only sporadically detected

[Wilhelm Meier]

Am 09.04.2017 um 12:23 schrieb Manuel Reiter:
> Hi everybody,
> 
> I'm currently trying to set up saned with a Canon Pixma MP610 on a Raspberry 
> Pi 3 running the latest Raspbian Jessie. Scanning works well, however I have 
> some trouble gettings scanbd to work reliably. Scanbd will only detect the 
> scanner on startup every once in a while. Log from the last successful start 
> is at
> 
>   http://paste.debian.net/926687
> 
> This was a foreground run, unfortunately only on debug level 4. After I 
> terminated this run, I started scanbd via systemd. This did not detect my 
> scanner. All subsequent tries were unsuccessfull as well. Log from one such 
> try at debug level 7 is at
> 
>   http://paste.debian.net/926688

Please check the SANE_CONFIG_DIR env-variable for your foreground runs.


> 
> My config files are
> 
> /etc/scanbd/scanbd.conf:  http://paste.debian.net/926677
> /etc/scanbd/sane.d/saned.conf:http://paste.debian.net/926680
> /etc/scanbd/sane.d/dll.conf:  http://paste.debian.net/926683
> /etc/saned/saned.conf:http://paste.debian.net/926684
> /etc/saned/dll.conf:  http://paste.debian.net/926685
> 
> What seems weird to me is that scanimage -L detects the scanner reliably 
> every time, both local and remote, so scanbm doesn't seem to share the 
> problem.
> 
> Any hints on how to debug this are highly welcome, thanks in advance! If you 
> need any more info, please ask!
> 
> Cheers,
> 
>  Manuel
> 


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

[sane-devel] scanbd on Raspbian: scanner only sporadically detected

[Manuel Reiter]

Hi everybody,

I'm currently trying to set up saned with a Canon Pixma MP610 on a Raspberry Pi 
3 running the latest Raspbian Jessie. Scanning works well, however I have some 
trouble gettings scanbd to work reliably. Scanbd will only detect the scanner 
on startup every once in a while. Log from the last successful start is at

http://paste.debian.net/926687

This was a foreground run, unfortunately only on debug level 4. After I 
terminated this run, I started scanbd via systemd. This did not detect my 
scanner. All subsequent tries were unsuccessfull as well. Log from one such try 
at debug level 7 is at

http://paste.debian.net/926688

My config files are

/etc/scanbd/scanbd.conf:http://paste.debian.net/926677
/etc/scanbd/sane.d/saned.conf:  http://paste.debian.net/926680
/etc/scanbd/sane.d/dll.conf:http://paste.debian.net/926683
/etc/saned/saned.conf:  http://paste.debian.net/926684
/etc/saned/dll.conf:http://paste.debian.net/926685

What seems weird to me is that scanimage -L detects the scanner reliably every 
time, both local and remote, so scanbm doesn't seem to share the problem.

Any hints on how to debug this are highly welcome, thanks in advance! If you 
need any more info, please ask!

Cheers,

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

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

[matt clark]

More testing - checking permissions to the scanner:

[matt@localhost sane.d]$ lsusb
Bus 002 Device 005: ID 04a9:174b Canon, Inc.  (plus others)
[matt@localhost sane.d]$ ls -l /dev/bus/usb/002/005
crw-rw-r-- 1 root lp 189, 132 Oct 25 15:47 /dev/bus/usb/002/005

It looks like root and group "lp" have read write access to the
scanner.  So I added both me and the "saned" user is in the lp group.
But I still can't get scanimage -L to pick up the USB connection
without sudo access.

Don't know if this is useful extra info or not!

On Tue, Oct 25, 2016 at 3:31 PM, matt clark  wrote:
> Hi again, after the last test I reinstalled sane without the scanbd
> bits, want to see if I can get this working without it.  The output
> from the command above is at http://pastebin.com/1h6gDTQV
>
> It looks from that as though sane is picking up both the network
> connection to the scanner/printer and the USB connection.  Not sure if
> that helps diagnose?  If I run the same command without sudo access it
> doesn't pick up the USB version.
>
> Cheers
> Matt
>
> On Tue, Oct 25, 2016 at 3:12 PM, matt clark  wrote:
>> Hi Rolf, thanks for replying - sorry I missed it last week.  The
>> response to that command (running as su) is
>>
>> scanimage: no SANE devices found
>>
>> I am guessing it's something wrong with the scanbd setup since I can
>> see that it's installed using the /usr/local/etc/scanbd/sane.d config
>> file.  The only line that is not commented out in my
>> /etc/sane.d/saned.conf file is
>>
>> localhost
>>
>> Would appreciate your thoughts.
>>

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

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

[matt clark]

Hi again, after the last test I reinstalled sane without the scanbd
bits, want to see if I can get this working without it.  The output
from the command above is at http://pastebin.com/1h6gDTQV

It looks from that as though sane is picking up both the network
connection to the scanner/printer and the USB connection.  Not sure if
that helps diagnose?  If I run the same command without sudo access it
doesn't pick up the USB version.

Cheers
Matt

On Tue, Oct 25, 2016 at 3:12 PM, matt clark  wrote:
> Hi Rolf, thanks for replying - sorry I missed it last week.  The
> response to that command (running as su) is
>
> scanimage: no SANE devices found
>
> I am guessing it's something wrong with the scanbd setup since I can
> see that it's installed using the /usr/local/etc/scanbd/sane.d config
> file.  The only line that is not commented out in my
> /etc/sane.d/saned.conf file is
>
> localhost
>
> Would appreciate your thoughts.
>
> On Wed, Oct 19, 2016 at 9:13 PM, Rolf Bensch  wrote:
>> Hi Matt,
>>
>> Sorry for the late response.
>>
>> The command line must run without
>> 'SANE_CONFIG_DIR=/usr/local/etc/scanbd/sane.d'. Maybe you don't have the
>> user rights to access your scanner via USB. Please try following:
>> (1) push any button
>> (2) sudo su -c "SANE_DEBUG_PIXMA=11 scanimage -A"
>>
>> Please send me the complete log response.
>>
>> Cheers,
>> Rolf
>>
>> Am 13.10.2016 um 23:29 schrieb matt clark:
>>> Hi Rolf, the "buttons" section in the code shows this:
>>>
>>>   Buttons:
>>> --button-update
>>> Update button state
>>> --button-1  [0] [read-only]
>>> Button 1
>>> --button-2  [0] [read-only]
>>> Button 2
>>> --original  [0] [read-only]
>>> Type of original to scan
>>> --target  [0] [read-only]
>>> Target operation type
>>> --scan-resolution  [0] [read-only]
>>> Scan resolution
>>>
>>> None of the binary code you mentioned.  Does this mean there is no
>>> sane support for the buttons?  Note that I had to use the command
>>> SANE_CONFIG_DIR=/usr/local/etc/scanbd/sane.d SANE_DEBUG_PIXMA=11
>>> scanimage -A to make it work.  I pushing both buttons, and sending it
>>> via USB (yes it's connected) and the "localhost saned" option which is
>>> I assume sending via network.
>>>
>>> On Fri, Oct 14, 2016 at 7:16 AM, Rolf Bensch  wrote:
 Hi Matt,

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

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

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

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

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

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

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

 Hope this helps.

 Cheers,
 Rolf

 Am 13.10.2016 um 13:23 schrieb Wilhelm:
> Oh, mixed the values ...
>
>  action btest {
>  filter = "^button.*"
>  numerical-trigger {
>  from-value = 0
>  to-value   = 1
>  }
>  desc   = "Scan to file"
>  script = "test.script"
>  }
>
>
> Am 13.10.2016 um 11:16 schrieb Wilhelm:
>> Matt, you need something like this in your config:
>>
>> action btest {
>> filter = "^button.*"
>> numerical-trigger {
>> from-value = 1
>> to-value   = 0
>> }
>> desc   = "Scan to file"
>> script = "test.script"
>> }
>>
>> --
>>  Wilhelm
>>
>> Am 13.10.2016 um 09:09 schrieb matt clark:
>>> Thanks Wilhelm.  I had changed that while trying to debug the 

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

[matt clark]

Hi Rolf, thanks for replying - sorry I missed it last week.  The
response to that command (running as su) is

scanimage: no SANE devices found

I am guessing it's something wrong with the scanbd setup since I can
see that it's installed using the /usr/local/etc/scanbd/sane.d config
file.  The only line that is not commented out in my
/etc/sane.d/saned.conf file is

localhost

Would appreciate your thoughts.

On Wed, Oct 19, 2016 at 9:13 PM, Rolf Bensch  wrote:
> Hi Matt,
>
> Sorry for the late response.
>
> The command line must run without
> 'SANE_CONFIG_DIR=/usr/local/etc/scanbd/sane.d'. Maybe you don't have the
> user rights to access your scanner via USB. Please try following:
> (1) push any button
> (2) sudo su -c "SANE_DEBUG_PIXMA=11 scanimage -A"
>
> Please send me the complete log response.
>
> Cheers,
> Rolf
>
> Am 13.10.2016 um 23:29 schrieb matt clark:
>> Hi Rolf, the "buttons" section in the code shows this:
>>
>>   Buttons:
>> --button-update
>> Update button state
>> --button-1  [0] [read-only]
>> Button 1
>> --button-2  [0] [read-only]
>> Button 2
>> --original  [0] [read-only]
>> Type of original to scan
>> --target  [0] [read-only]
>> Target operation type
>> --scan-resolution  [0] [read-only]
>> Scan resolution
>>
>> None of the binary code you mentioned.  Does this mean there is no
>> sane support for the buttons?  Note that I had to use the command
>> SANE_CONFIG_DIR=/usr/local/etc/scanbd/sane.d SANE_DEBUG_PIXMA=11
>> scanimage -A to make it work.  I pushing both buttons, and sending it
>> via USB (yes it's connected) and the "localhost saned" option which is
>> I assume sending via network.
>>
>> On Fri, Oct 14, 2016 at 7:16 AM, Rolf Bensch  wrote:
>>> Hi Matt,
>>>
>>> Have you tested that your scanner resp. the backend sends data @ a push
>>> button event?
>>>
>>> Please test on the console:
>>> (1) push any button
>>> (2) $ SANE_DEBUG_PIXMA=11 scanimage -A
>>> (3) check the response; I'm especially interested in following lines:
>>>
>>>   Buttons:
>>> --button-update
>>> Update button state
>>> [pixma] INTR T=1.343 len=32
>>> [pixma]  :00 20 00 00 00 00 00 00  00 00 00 00 00 00 00 00
>>> [pixma]  0010:00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
>>> [pixma]
>>> --button-1  [1] [read-only]
>>> Button 1
>>> --button-2  [0] [read-only]
>>> Button 2
>>> --original  [0] [read-only]
>>> Type of original to scan
>>> --target  [2] [read-only]
>>> Target operation type
>>> --scan-resolution  [0] [read-only]
>>> Scan resolution
>>>
>>> Please repeat (1) ... (3) for all scan buttons.
>>>
>>> Maybe you need to test your scanner USB connected to the pc. I haven't
>>> tested push buttons wireless yet.
>>>
>>> If you don't get lines starting with [pixma], your scanner has no button
>>> support from SANE.
>>>
>>> If you get lines starting with [pixma] with more data as shown above (I
>>> have a different scanner) and without data output below at the
>>> parameters --button-1 ... --scan-resolution, what I suppose, then please
>>> send me your "Buttons:" logs and I'll fix the backend code.
>>>
>>> Hope this helps.
>>>
>>> Cheers,
>>> Rolf
>>>
>>> Am 13.10.2016 um 13:23 schrieb Wilhelm:
 Oh, mixed the values ...

  action btest {
  filter = "^button.*"
  numerical-trigger {
  from-value = 0
  to-value   = 1
  }
  desc   = "Scan to file"
  script = "test.script"
  }


 Am 13.10.2016 um 11:16 schrieb Wilhelm:
> Matt, you need something like this in your config:
>
> action btest {
> filter = "^button.*"
> numerical-trigger {
> from-value = 1
> to-value   = 0
> }
> desc   = "Scan to file"
> script = "test.script"
> }
>
> --
>  Wilhelm
>
> Am 13.10.2016 um 09:09 schrieb matt clark:
>> Thanks Wilhelm.  I had changed that while trying to debug the problem,
>> not sure why this would be a problem.  Have reverted to the
>> scanbd.conf from source, with modifications to sane.d directory and
>> comment out the unnecessary manufacturer scanner.d profiles.  revised
>> config is attached - apologies for the length of code.
>>
>> ---
>>
>> /*
>>  * $Id: scanbd.conf 213 2015-10-05 06:52:50Z wimalopaan $
>>  *
>>  *  scanbd - KMUX scanner button daemon
>>  *
>>  *  Copyright (C) 2008 - 2015  Wilhelm Meier (wilhelm.me...@fh-kl.de)
>>  *
>>  *  This program is free software; you can redistribute it and/or modify
>>  *  it under the terms of the GNU 

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

[Rolf Bensch]

Hi Matt,

Sorry for the late response.

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

Please send me the complete log response.

Cheers,
Rolf

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

 action btest {
 filter = "^button.*"
 numerical-trigger {
 from-value = 1
 to-value   = 0
 }
 desc   = "Scan to file"
 script = "test.script"
 }

 --
  Wilhelm

 Am 13.10.2016 um 09:09 schrieb matt clark:
> Thanks Wilhelm.  I had changed that while trying to debug the problem,
> not sure why this would be a problem.  Have reverted to the
> scanbd.conf from source, with modifications to sane.d directory and
> comment out the unnecessary manufacturer scanner.d profiles.  revised
> config is attached - apologies for the length of code.
>
> ---
>
> /*
>  * $Id: scanbd.conf 213 2015-10-05 06:52:50Z wimalopaan $
>  *
>  *  scanbd - KMUX scanner button daemon
>  *
>  *  Copyright (C) 2008 - 2015  Wilhelm Meier (wilhelm.me...@fh-kl.de)
>  *
>  *  This program is free software; you can redistribute it and/or modify
>  *  it under the terms of the GNU General Public License as published by
>  *  the Free Software Foundation; either version 2 of the License, or
>  *  (at your option) any later version.
>  *
>  *  This program is distributed in the hope that it will be useful,
>  *  but WITHOUT ANY WARRANTY; without even the implied warranty of
>  *  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
>  *  GNU General Public License for more details.
>  *
>  *  You should have received a copy of the GNU General Public License
>  *  along with this program; if not, write to the Free Software
>  *  Foundation, Inc., 51 

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

[matt clark]

Hi Rolf, the "buttons" section in the code shows this:

  Buttons:
--button-update
Update button state
--button-1  [0] [read-only]
Button 1
--button-2  [0] [read-only]
Button 2
--original  [0] [read-only]
Type of original to scan
--target  [0] [read-only]
Target operation type
--scan-resolution  [0] [read-only]
Scan resolution

None of the binary code you mentioned.  Does this mean there is no
sane support for the buttons?  Note that I had to use the command
SANE_CONFIG_DIR=/usr/local/etc/scanbd/sane.d SANE_DEBUG_PIXMA=11
scanimage -A to make it work.  I pushing both buttons, and sending it
via USB (yes it's connected) and the "localhost saned" option which is
I assume sending via network.

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

 ---

 /*
  * $Id: scanbd.conf 213 2015-10-05 06:52:50Z wimalopaan $
  *
  *  scanbd - KMUX scanner button daemon
  *
  *  Copyright (C) 2008 - 2015  Wilhelm Meier (wilhelm.me...@fh-kl.de)
  *
  *  This program is free software; you can redistribute it and/or modify
  *  it under the terms of the GNU General Public License as published by
  *  the Free Software Foundation; either version 2 of the License, or
  *  (at your option) any later version.
  *
  *  This program is distributed in the hope that it will be useful,
  *  but WITHOUT ANY WARRANTY; without even the implied warranty of
  *  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  *  GNU General Public License for more details.
  *
  *  You should have received a copy of the GNU General Public License
  *  along with this program; if not, write to the Free Software
  *  Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
 02110-1301, USA.
  */


 # global settings
 global {
 # turn on debugging

 # log to console
 debug   = true

 # debug logging
 # 1=error, 2=warn, 3=info, 4-7=debug
 debug-level = 7

 # drop priviliges to this user
 #=
 # Linux (most distributions use the saned user):
 # user= saned
 # ArchLinux 

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

[Rolf Bensch]

Hi Matt,

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

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

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

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

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

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

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

Hope this helps.

Cheers,
Rolf

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

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

[Wilhelm]

Oh, mixed the values ...

 action btest {
 filter = "^button.*"
 numerical-trigger {
 from-value = 0
 to-value   = 1
 }
 desc   = "Scan to file"
 script = "test.script"
 }


Am 13.10.2016 um 11:16 schrieb Wilhelm:
> Matt, you need something like this in your config:
> 
> action btest {
> filter = "^button.*"
> numerical-trigger {
> from-value = 1
> to-value   = 0
> }
> desc   = "Scan to file"
> script = "test.script"
> }
> 
> --
>  Wilhelm
> 
> Am 13.10.2016 um 09:09 schrieb matt clark:
>> Thanks Wilhelm.  I had changed that while trying to debug the problem,
>> not sure why this would be a problem.  Have reverted to the
>> scanbd.conf from source, with modifications to sane.d directory and
>> comment out the unnecessary manufacturer scanner.d profiles.  revised
>> config is attached - apologies for the length of code.
>>
>> ---
>>
>> /*
>>  * $Id: scanbd.conf 213 2015-10-05 06:52:50Z wimalopaan $
>>  *
>>  *  scanbd - KMUX scanner button daemon
>>  *
>>  *  Copyright (C) 2008 - 2015  Wilhelm Meier (wilhelm.me...@fh-kl.de)
>>  *
>>  *  This program is free software; you can redistribute it and/or modify
>>  *  it under the terms of the GNU General Public License as published by
>>  *  the Free Software Foundation; either version 2 of the License, or
>>  *  (at your option) any later version.
>>  *
>>  *  This program is distributed in the hope that it will be useful,
>>  *  but WITHOUT ANY WARRANTY; without even the implied warranty of
>>  *  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
>>  *  GNU General Public License for more details.
>>  *
>>  *  You should have received a copy of the GNU General Public License
>>  *  along with this program; if not, write to the Free Software
>>  *  Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
>> 02110-1301, USA.
>>  */
>>
>>
>> # global settings
>> global {
>> # turn on debugging
>>
>> # log to console
>> debug   = true
>>
>> # debug logging
>> # 1=error, 2=warn, 3=info, 4-7=debug
>> debug-level = 7
>>
>> # drop priviliges to this user
>> #=
>> # Linux (most distributions use the saned user):
>> # user= saned
>> # ArchLinux (ArchLinux doesn't have saned user)
>> # user= daemon
>> # *BSD
>> # user= root
>> user= saned
>>
>> # Group to be used
>> #=
>> # Linux (most distributions use the lp group to access scanners)
>> # group   = lp
>> # ArchLinux (ArchLinux uses the scanner group)
>> # group = scanner
>> #
>> # *BSD (no group lp here, use daemon instead)
>> # group   = daemon # root
>> #
>> group   = lp
>>
>> # the saned executable for manager-mode
>> saned   = "/usr/sbin/saned"
>> saned_opt  = {} # string-list
>> saned_env  = { "SANE_CONFIG_DIR=/etc/scanbd/sane.d" } # list of
>> environment vars for saned
>>
>> # Scriptdir specifies where scanbd normally looks for scripts.
>> # The scriptdir option can be defined as:
>> #   - a path relative to the configuations (/etc/scanbd) 
>> directory
>> #   - an abosolute path
>> # Examples:
>> # scriptdir = scripts
>> # sets scriptdir to /etc/scanbd/scripts.
>> # scriptdir = /some/path
>> # sets scriptdir to the specified absolute path
>> # Default scriptdir is /etc/scanbd, this is normally 
>> appropriate
>> scriptdir = /etc/scanbd/scripts
>>
>> # Scripts to execute upon device insertion/removal.
>> # It can be necessary to load firmware into the device when it is 
>> first
>> # inserted. For example, scanbuttond backend does not know how to 
>> load
>> # scanner firmware, and it can be rectified by making a custom 
>> script.
>> # A simple command like "scanimage -L" in an example insert.script
>> # invokes saned and it loads the appropriate firmware if necessary.
>> # These scripts receive environmental variables named in the
>> "environment" subsection:
>> # SCANBD_DEVICE - device name (fixed string "dbus device" for
>> dbus notification)
>> # SCANBD_ACTION - "insert" or "remove", so one script can be used.
>> # device_insert_script = "insert.script"
>> # device_remove_script =
>>
>> # scanbuttond_backends_dir sets the path where scanbd looks
>> for the scanbuttond backends
>> # It can be defined as relative path, starting from the scanbd config
>> directory or
>> # as an absolute path
>> # Default is /scanbd/scanbutond/backends

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

[Wilhelm]

Matt, you need something like this in your config:

action btest {
filter = "^button.*"
numerical-trigger {
from-value = 1
to-value   = 0
}
desc   = "Scan to file"
script = "test.script"
}

--
 Wilhelm

Am 13.10.2016 um 09:09 schrieb matt clark:
> Thanks Wilhelm.  I had changed that while trying to debug the problem,
> not sure why this would be a problem.  Have reverted to the
> scanbd.conf from source, with modifications to sane.d directory and
> comment out the unnecessary manufacturer scanner.d profiles.  revised
> config is attached - apologies for the length of code.
> 
> ---
> 
> /*
>  * $Id: scanbd.conf 213 2015-10-05 06:52:50Z wimalopaan $
>  *
>  *  scanbd - KMUX scanner button daemon
>  *
>  *  Copyright (C) 2008 - 2015  Wilhelm Meier (wilhelm.me...@fh-kl.de)
>  *
>  *  This program is free software; you can redistribute it and/or modify
>  *  it under the terms of the GNU General Public License as published by
>  *  the Free Software Foundation; either version 2 of the License, or
>  *  (at your option) any later version.
>  *
>  *  This program is distributed in the hope that it will be useful,
>  *  but WITHOUT ANY WARRANTY; without even the implied warranty of
>  *  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
>  *  GNU General Public License for more details.
>  *
>  *  You should have received a copy of the GNU General Public License
>  *  along with this program; if not, write to the Free Software
>  *  Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
> 02110-1301, USA.
>  */
> 
> 
> # global settings
> global {
> # turn on debugging
> 
> # log to console
> debug   = true
> 
> # debug logging
> # 1=error, 2=warn, 3=info, 4-7=debug
> debug-level = 7
> 
> # drop priviliges to this user
> #=
> # Linux (most distributions use the saned user):
> # user= saned
> # ArchLinux (ArchLinux doesn't have saned user)
> # user= daemon
> # *BSD
> # user= root
> user= saned
> 
> # Group to be used
> #=
> # Linux (most distributions use the lp group to access scanners)
> # group   = lp
> # ArchLinux (ArchLinux uses the scanner group)
> # group = scanner
> #
> # *BSD (no group lp here, use daemon instead)
> # group   = daemon # root
> #
> group   = lp
> 
> # the saned executable for manager-mode
> saned   = "/usr/sbin/saned"
> saned_opt  = {} # string-list
> saned_env  = { "SANE_CONFIG_DIR=/etc/scanbd/sane.d" } # list of
> environment vars for saned
> 
> # Scriptdir specifies where scanbd normally looks for scripts.
> # The scriptdir option can be defined as:
> #   - a path relative to the configuations (/etc/scanbd) 
> directory
> #   - an abosolute path
> # Examples:
> # scriptdir = scripts
> # sets scriptdir to /etc/scanbd/scripts.
> # scriptdir = /some/path
> # sets scriptdir to the specified absolute path
> # Default scriptdir is /etc/scanbd, this is normally appropriate
> scriptdir = /etc/scanbd/scripts
> 
> # Scripts to execute upon device insertion/removal.
> # It can be necessary to load firmware into the device when it is 
> first
> # inserted. For example, scanbuttond backend does not know how to load
> # scanner firmware, and it can be rectified by making a custom script.
> # A simple command like "scanimage -L" in an example insert.script
> # invokes saned and it loads the appropriate firmware if necessary.
> # These scripts receive environmental variables named in the
> "environment" subsection:
> # SCANBD_DEVICE - device name (fixed string "dbus device" for
> dbus notification)
> # SCANBD_ACTION - "insert" or "remove", so one script can be used.
> # device_insert_script = "insert.script"
> # device_remove_script =
> 
> # scanbuttond_backends_dir sets the path where scanbd looks
> for the scanbuttond backends
> # It can be defined as relative path, starting from the scanbd config
> directory or
> # as an absolute path
> # Default is /scanbd/scanbutond/backends
> # Example
> # scanbuttond_backends_dir = "/usr/local/lib/scanbd/scanbuttond/backends"
> 
> # poll timeout in [ms]
> # (for polling the devices)
> 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
>

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

[matt clark]

Thanks Wilhelm.  I had changed that while trying to debug the problem,
not sure why this would be a problem.  Have reverted to the
scanbd.conf from source, with modifications to sane.d directory and
comment out the unnecessary manufacturer scanner.d profiles.  revised
config is attached - apologies for the length of code.

---

/*
 * $Id: scanbd.conf 213 2015-10-05 06:52:50Z wimalopaan $
 *
 *  scanbd - KMUX scanner button daemon
 *
 *  Copyright (C) 2008 - 2015  Wilhelm Meier (wilhelm.me...@fh-kl.de)
 *
 *  This program is free software; you can redistribute it and/or modify
 *  it under the terms of the GNU General Public License as published by
 *  the Free Software Foundation; either version 2 of the License, or
 *  (at your option) any later version.
 *
 *  This program is distributed in the hope that it will be useful,
 *  but WITHOUT ANY WARRANTY; without even the implied warranty of
 *  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 *  GNU General Public License for more details.
 *
 *  You should have received a copy of the GNU General Public License
 *  along with this program; if not, write to the Free Software
 *  Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
02110-1301, USA.
 */


# global settings
global {
# turn on debugging

# log to console
debug   = true

# debug logging
# 1=error, 2=warn, 3=info, 4-7=debug
debug-level = 7

# drop priviliges to this user
#=
# Linux (most distributions use the saned user):
# user= saned
# ArchLinux (ArchLinux doesn't have saned user)
# user= daemon
# *BSD
# user= root
user= saned

# Group to be used
#=
# Linux (most distributions use the lp group to access scanners)
# group   = lp
# ArchLinux (ArchLinux uses the scanner group)
# group = scanner
#
# *BSD (no group lp here, use daemon instead)
# group   = daemon # root
#
group   = lp

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

# Scriptdir specifies where scanbd normally looks for scripts.
# The scriptdir option can be defined as:
#   - a path relative to the configuations (/etc/scanbd) directory
#   - an abosolute path
# Examples:
# scriptdir = scripts
# sets scriptdir to /etc/scanbd/scripts.
# scriptdir = /some/path
# sets scriptdir to the specified absolute path
# Default scriptdir is /etc/scanbd, this is normally appropriate
scriptdir = /etc/scanbd/scripts

# Scripts to execute upon device insertion/removal.
# It can be necessary to load firmware into the device when it is first
# inserted. For example, scanbuttond backend does not know how to load
# scanner firmware, and it can be rectified by making a custom script.
# A simple command like "scanimage -L" in an example insert.script
# invokes saned and it loads the appropriate firmware if necessary.
# These scripts receive environmental variables named in the
"environment" subsection:
# SCANBD_DEVICE - device name (fixed string "dbus device" for
dbus notification)
# SCANBD_ACTION - "insert" or "remove", so one script can be used.
# device_insert_script = "insert.script"
# device_remove_script =

# scanbuttond_backends_dir sets the path where scanbd looks
for the scanbuttond backends
# It can be defined as relative path, starting from the scanbd config
directory or
# as an absolute path
# Default is /scanbd/scanbutond/backends
# Example
# scanbuttond_backends_dir = "/usr/local/lib/scanbd/scanbuttond/backends"

# poll timeout in [ms]
# (for polling the devices)
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 definitions
# values of the options are simply passed via env-vars

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 definitions

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

[matt clark]

Here's the original message again, removing the formatting from the
original forum website version that didn't seem to work.  Lots of the
original content went missing. Sorry for the double post if it did work for
you originally.  I've also added my config file to the end of this message,
so it's huge.
---
I've had a Canon MG8150 attached to my network for ages and decided to hook
it up to my network box (Fedora 23), basically hoping to automatically save
scans to my network drive when I press the scan button on the machine.

I followed various articles around the place to try and set this up but I
seem to have failed.  Here's a summary of where I'm up to - would love some
help troubleshooting the problem:

- Have installed sane-backends-devel via dnf, and scanbd 1.4.4 from source
(using default configure / gmake approach, no options).
- Copied the /etc/sane.d/* files to /usr/local/etc/scanbd/sane.d/
- added a symbolic link from /etc/scanbd to /usr/local/etc/scanbd just in
case anything refers to that.  I prefer working in usr to etc directly.
- Changed /etc/sane.d/saned.conf to only allow localhost
- Changed /usr/local/etc/scanbd/sane.d/saned.conf to allow all local
network clients
- Changed /etc/sane.d/net.conf to have 2 lines, connect_timeout = 3 and
localhost
- Changed /etc/sane.d/dll.conf to have only net
- Changed /etc/local/etc/scanbd/sane.d/dll.conf to comment out net, and
remove the unnecessary references (just kept pixma)
- Saved scanbd_dbus to /etc/dbus-1/system.d/scandb_dbus.conf
- Create systemd files /usr/lib/systemd/system/scanbd.service and
scanbm.socket.  Only change is to add the revised sane.d config directory.

scanbd.service:

[Unit]
Description=Scanner button polling Service

[Service]
Type=simple
ExecStart=/usr/local/sbin/scanbd -f -c /usr/local/etc/scanbd/scanbd.conf
#ExecReload=?
Environment=SANE_CONFIG_DIR=/usr/local/etc/scanbd/sane.d
StandardInput=null
StandardOutput=syslog
StandardError=syslog
#NotifyAccess=?

[Install]
WantedBy=multi-user.target
Also=scanbm.socket
Alias=dbus-de.kmux.scanbd.server.service

My scanbd.conf file is default, with some minor amendments.  See the bottom
of the message for full copy.


When the scanner is started either manually or via the service, it appears
to work ok but never picks up a button press.  The log always seems to show
a value of zero for the button polling response.

Outputs:
Test printer exists and is connected:
[matt@localhost scanbd]$ lsusb
Bus 002 Device 003: ID 04a9:174b Canon, Inc.

Test scanimage can find printer:
[matt@localhost scanbd]$ SANE_CONFIG_DIR=/usr/local/etc/scanbd/sane.d
scanimage -L
device `pixma:MG8100_192.168.1.49' is a CANON Canon PIXMA MG8100
multi-function peripheral

Scanimage can also send test greyscale.tiff to the network drive.

sane-find-scanner also finds the scanner, albeit only if signed in as root.
[matt@localhost scanbd]$ sudo sane-find-scanner
found USB scanner (vendor=0x04a9 [Canon], product=0x174b [MG8100 series])
at libusb:002:003

I've saved the log from scanbd to pastebin because it's huge.
http://pastebin.com/T6RHVsdV

I dont know if there's anything interesting in all that.  I couldn't find
any errors. At the end of the log you can see that it just repeats a
polling cycle, but the values for the buttons never change no matter how
much I press them.

Has anyone got any thoughts on how I could get this working?

Finally, added conf files as requested by Wilhelm:

[matt@localhost scanbd]$ cat /usr/local/etc/scanbd/scanbd.conf
/*
 * $Id: scanbd.conf 213 2015-10-05 06:52:50Z wimalopaan $
 *
 *  scanbd - KMUX scanner button daemon
 *
 *  Copyright (C) 2008 - 2015  Wilhelm Meier (wilhelm.me...@fh-kl.de)
 *
 *  This program is free software; you can redistribute it and/or modify
 *  it under the terms of the GNU General Public License as published by
 *  the Free Software Foundation; either version 2 of the License, or
 *  (at your option) any later version.
 *
 *  This program is distributed in the hope that it will be useful,
 *  but WITHOUT ANY WARRANTY; without even the implied warranty of
 *  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 *  GNU General Public License for more details.
 *
 *  You should have received a copy of the GNU General Public License
 *  along with this program; if not, write to the Free Software
 *  Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
02110-1301, USA.
 */


# global settings
global {
# turn on debugging

# log to console
debug   = true

# debug logging
# 1=error, 2=warn, 3=info, 4-7=debug
debug-level = 4

# drop priviliges to this user
#=
# Linux (most distributions use the saned user):
# user= saned
# ArchLinux (ArchLinux doesn't have saned user)
# user= daemon
# *BSD
# user= root
user= saned

# Group to be used
#=
# Linux (most 

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

[Wilhelm]

Please post your config-file!


Am 12.10.2016 um 14:13 schrieb Matt:
> I've had a Canon MG8150 attached to my network for ages and decided to hook
> it up to my network box (Fedora 23), basically hoping to automatically save
> scans to my network drive when I press the scan button on the machine.
> 
> I followed various articles around the place to try and set this up but I
> seem to have failed.  Here's a summary of where I'm up to - would love some
> help troubleshooting the problem:
> 
> - Have installed sane-backends-devel via dnf, and scanbd 1.4.4 from source
> (using default configure / gmake approach, no options).
> - Copied the /etc/sane.d/* files to /usr/local/etc/scanbd/sane.d/
> - added a symbolic link from /etc/scanbd to /usr/local/etc/scanbd just in
> case anything refers to that.  I prefer working in usr to etc directly.
> - Changed /etc/sane.d/saned.conf to only allow localhost
> - Changed /usr/local/etc/scanbd/sane.d/saned.conf to allow all local network
> clients
> - Changed /etc/sane.d/net.conf to have 2 lines, connect_timeout = 3 and
> localhost
> - Changed /etc/sane.d/dll.conf to have only net
> - Changed /etc/local/etc/scanbd/sane.d/dll.conf to comment out net, and
> remove the unnecessary references (just kept pixma)
> - Saved scanbd_dbus to /etc/dbus-1/system.d/scandb_dbus.conf
> - Create systemd files /usr/lib/systemd/system/scanbd.service and
> scanbm.socket.  Only change is to add the revised sane.d config directory.
> 
> scanbd.service:
> 
> 
> My scanbd.conf file is default, with some minor amendments:
> - changed the location of the sane.d configs:
> 
> - commented out unused scanner.d device references at the end apart from the
> pixma one.
> - changed the globaltest to refer to button-1 for testing purposes, but it
> didn't seem to do anything:
> 
> - I also changed a few other actions (mostly commenting them out) but didn't
> make any difference to the output.
> 
> When the scanner is started either manually or via the service, it appears
> to work ok but never picks up a button press.  The log always seems to show
> a value of zero for the button polling response.
> 
> Outputs:
> Test printer exists and is connected:
> 
> 
> Test scanimage can find printer:
> 
> 
> Scanimage can also send test greyscale.tiff to the network drive.
> 
> sane-find-scanner also finds the scanner, albeit only if signed in as root.
> 
> 
> I've saved the log from scanbd to pastebin because it's huge. 
> http://pastebin.com/T6RHVsdV
> 
> I dont know if there's anything interesting in all that.  I couldn't find
> any errors. At the end of the log you can see that it just repeats a polling
> cycle, but the values for the buttons never change no matter how much I
> press them.
> 
> Has anyone got any thoughts on how I could get this working?
> 
> 
> 
> --
> View this message in context: 
> http://sane.10972.n7.nabble.com/Scanbd-Set-up-for-Canon-PIXMA-multifunction-scanner-no-button-response-tp20701.html
> Sent from the SANE - Dev mailing list archive at Nabble.com.
> 


-- 
Wilhelm


-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.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] [Scanbd] Set up for Canon PIXMA multifunction scanner - no button response

[Matt]

I've had a Canon MG8150 attached to my network for ages and decided to hook
it up to my network box (Fedora 23), basically hoping to automatically save
scans to my network drive when I press the scan button on the machine.

I followed various articles around the place to try and set this up but I
seem to have failed.  Here's a summary of where I'm up to - would love some
help troubleshooting the problem:

- Have installed sane-backends-devel via dnf, and scanbd 1.4.4 from source
(using default configure / gmake approach, no options).
- Copied the /etc/sane.d/* files to /usr/local/etc/scanbd/sane.d/
- added a symbolic link from /etc/scanbd to /usr/local/etc/scanbd just in
case anything refers to that.  I prefer working in usr to etc directly.
- Changed /etc/sane.d/saned.conf to only allow localhost
- Changed /usr/local/etc/scanbd/sane.d/saned.conf to allow all local network
clients
- Changed /etc/sane.d/net.conf to have 2 lines, connect_timeout = 3 and
localhost
- Changed /etc/sane.d/dll.conf to have only net
- Changed /etc/local/etc/scanbd/sane.d/dll.conf to comment out net, and
remove the unnecessary references (just kept pixma)
- Saved scanbd_dbus to /etc/dbus-1/system.d/scandb_dbus.conf
- Create systemd files /usr/lib/systemd/system/scanbd.service and
scanbm.socket.  Only change is to add the revised sane.d config directory.

scanbd.service:


My scanbd.conf file is default, with some minor amendments:
- changed the location of the sane.d configs:

- commented out unused scanner.d device references at the end apart from the
pixma one.
- changed the globaltest to refer to button-1 for testing purposes, but it
didn't seem to do anything:

- I also changed a few other actions (mostly commenting them out) but didn't
make any difference to the output.

When the scanner is started either manually or via the service, it appears
to work ok but never picks up a button press.  The log always seems to show
a value of zero for the button polling response.

Outputs:
Test printer exists and is connected:


Test scanimage can find printer:


Scanimage can also send test greyscale.tiff to the network drive.

sane-find-scanner also finds the scanner, albeit only if signed in as root.


I've saved the log from scanbd to pastebin because it's huge. 
http://pastebin.com/T6RHVsdV

I dont know if there's anything interesting in all that.  I couldn't find
any errors. At the end of the log you can see that it just repeats a polling
cycle, but the values for the buttons never change no matter how much I
press them.

Has anyone got any thoughts on how I could get this working?



--
View this message in context: 
http://sane.10972.n7.nabble.com/Scanbd-Set-up-for-Canon-PIXMA-multifunction-scanner-no-button-response-tp20701.html
Sent from the SANE - Dev mailing list archive at Nabble.com.

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

Re: [sane-devel] [scanbd] using scanbd and saned over network at the same time

[Wilhelm]

Hi Rolf,

your description looks reasonable.

Please ensure that scanbd (or systemd) really listens on port 6566:

[lmeier:/home/lmeier] $ sudo netstat -ltnp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address   Foreign Address
State   PID/Program name
tcp0  0 0.0.0.0:79  0.0.0.0:*
LISTEN  1/init
tcp0  0 0.0.0.0:80  0.0.0.0:*
LISTEN  1119/httpd
tcp0  0 0.0.0.0:22  0.0.0.0:*
LISTEN  1120/sshd
tcp0  0 0.0.0.0:631 0.0.0.0:*
LISTEN  472/cupsd
tcp0  0 0.0.0.0:65660.0.0.0:*
LISTEN  1/init
tcp0  0 0.0.0.0:90000.0.0.0:*
LISTEN  1139/nginx: master

If thats ok check your scanimage:

[lmeier:/home/lmeier] $ strace scanimage -L 2>&1 | grep dll.conf
open("./dll.conf", O_RDONLY)= -1 ENOENT (No such file or
directory)
open("/usr/local/etc/sane.d/dll.conf", O_RDONLY) = 4

Also you should check if the port is reachable or if some portfilter
sits there in between:

[lmeier:/home/lmeier] $ telnet localhost 6566
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.

Please report your results.

Am 19.02.2016 um 17:29 schrieb Rolf Leggewie:
> Hello Wilhelm,
> 
> thank you for the quick response.
> 
> On 19.02.2016 22:52, Wilhelm wrote:
>> Am 19.02.2016 um 14:38 schrieb Rolf Leggewie:
>>> Hello,
>>>
>>> I'd like to know if it is possible to have a computer that does
>>> button-triggered scanning via scanbd but also exports the scanner over
>>> the network to be accesible via the common. How would one do that?
>>
>> Well, absolutely: thats the whole story of scanbd (see the readme.txt of
>> scanbd).
> 
> Well, I am aware of the general idea how saned and scanbd are supposed
> to interact.  It can be pretty complicated to configure this error-free.
>  Going from one machine back to a real network adds yet another layer of
> complexity (and I was bitching when getting saned over network to run
> for the first and a couple subsequent times).
> 
> As you probably know, I added a couple of checks for common
> configuration errors to the Debian scanbd startup script.  Anything
> detected by
> http://anonscm.debian.org/cgit/collab-maint/scanbd.git/tree/debian/scanbd.init
> is OK on my scanbd server machine.  Button presses are detected fine by
> scanbd.  But with this configuration, the scanner will only be detected
> by sane-find-scanner and not be "scanimage -L".
> 
> $ sane-find-scanner | grep ^found
> found USB scanner (vendor=0x04a9 [Canon], product=0x2213 [CanoScan]) at
> libusb:001:035
> 
> Should this really be libusb?
> 
> Only if I add the genesys backend to /etc/sane.d/dll.conf, shut down
> scanbd and start up saned do I get an output from "scanimage -L".
> 
> $ scanimage -L
> device `genesys:libusb:001:035' is a Canon LiDE 35/40/50 flatbed scanner
> 
> That's when I also get a response from a network-connected client.
> 
> $ scanimage -L
> device `net:himbeere.local:genesys:libusb:001:035' is a Canon LiDE
> 35/40/50 flatbed scanner
> 
> So, what am I likely doing wrong here? Any idea?
> 
> When scanbd is running (and thus scanimage is broken locally as well as
> over the network), the following is the status:
> - scanbd service is running
> - saned service is stopped
> - /etc/sane.d/dll.conf contains only the net backend
> - /etc/scanbd/dll.conf does NOT contain the net backend
> - /etc/scanbd/dll.conf contains the necessary genesys backend
>   (and a few others)
> 
> Regards
> 
> Rolf
> 
> 


-- 
Wilhelm


-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.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] using scanbd and saned over network at the same time

[Wilhelm]

Am 19.02.2016 um 14:38 schrieb Rolf Leggewie:
> Hello,
> 
> I'd like to know if it is possible to have a computer that does
> button-triggered scanning via scanbd but also exports the scanner over
> the network to be accesible via the common. How would one do that?

Well, absolutely: thats the whole story of scanbd (see the readme.txt of
scanbd). With scanbd all scan-request must be via network, even local
applications must use network-scanning instead of local (via usb) access
to the scanner.

>From ReadMe.txt:

0.1) the solution

scanbd (the scanner button daemon) opens and polls the scanner and
therefore
locks the device. So no other application can access the device directly
(open
the /dev/..., or via libusb, etc).

To solve this, we use a second daemon (in the so called "manager-mode" of
scanbd): scanbm is configured as a "proxy" to access the scanner and, if
another
application tries to use the scanner, the polling daemon is ordered to
disable
polling for the time the other scan-application wants to use the scanner.

To make this happen, scanbm is configured instead of saned as the network
scanning daemon. If a scan request arrives to scanbm on the sane-port,
scanbm
stops the polling by sending a dbus-signal (default) or a posix-signal
(SIGUSR1)
(signal-mode) to the polling scanbd-daemon. Then it starts the real
saned which
scans and sends the data back to the requesting application. Afterwards the
scanbd-manager scanbm restarts the polling by sending another
dbus-signal (or the
posix-signal SIGUSR2) to scanbd. scanbd now reenables polling of the
devices.

Scanbm is actually only a symbolic link to scanbd. Manager mode can be
activatied by calling scanbd as scanbm OR as scanbd -m as in previous
version
of scanbd.

So all applications must be enabled to use network-scanning (even if the
scanner is local, see below)!

Hth
-- 
Wilhelm


-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.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 fails to start with multiple scanners (and no paper loaded)

[Wilhelm]

Well, looks like an embarrassing (and weird) error: could you please try
the trunk version of scanbd now?

Am 03.06.2015 um 16:18 schrieb Greg Kontos:
 Thank you, Wilhelm.  I appreciate you looking into this issue.  I tried 
 commenting out the paperload and paperunload actions, which still led to the 
 same behavior where the process dies on startup.  I went an extra step and 
 also commented out the entire scanner specific fujitsu conf file within the 
 main scanbd.conf file.  Unfortunately, I still see the same behavior on 
 startup.
 
 :) I'm pretty lucky to have multiple scanners to test with.  If there are 
 tests you would like me to run, just shout.
 
 Thanks again,
 Greg
 
 
 
 
 
 Greg Kontos
 LIMS Integration Specialist
 
 Innovative Diagnostic Laboratory
 8751 Park Central Drive, Suite 200
 Richmond, VA 23227
 Phone: (804) 261-3340 ext.1846
 Cell Phone:
 Fax: (804) 515-7291
 mailto:gkon...@myinnovativelab.com
 
 Visit our website: http://www.myinnovativelab.com
 
 CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files or 
 previous e-mail messages attached to it contain confidential and/or 
 privileged information meant for the listed recipient(s) only. You may not 
 distribute or share this correspondence without written authorization from 
 the above author.
 
 If you are not the intended recipient, or a person responsible for delivering 
 it to the intended recipient, you are hereby notified that any disclosure, 
 copying, distribution or use of any of the information contained in or 
 attached to this transmission is STRICTLY PROHIBITED. If you have received 
 this transmission in error, please immediately notify me by reply e-mail and 
 destroy the original transmission and its attachments without saving them in 
 any manner.
 
 -Original Message-
 From: Wilhelm [mailto:wilhelm.me...@fh-kl.de]
 Sent: Wednesday, June 03, 2015 1:38 AM
 To: Greg Kontos; sane-devel@lists.alioth.debian.org
 Subject: Re: [sane-devel] Scanbd fails to start with multiple scanners (and 
 no paper loaded)
 
 Hi Greg,
 
 do you need the paperload or paperunload action? If not, please remove 
 them from the config file, if yes, then give them a correct script name.
 
 With this changes, please give me the full startup log with debug level 7.
 
 Thanks,
  Wilhelm
 
 Am 02.06.2015 um 17:31 schrieb Wilhelm:
 Hi Greg,

 thank you for your patience!

 I have some ideas where to look for this type of error, but
 unfortunately not enough time to do so. And I don't have access to
 more than one scanner at the moment :-(

 But please stay tuned ...

 Thanks,
  Wilhelm


 Am 02.06.2015 um 14:35 schrieb Greg Kontos:
 Hi Wilhelm,

 I'm following up to see if you have any thoughts or advice regarding the 
 trouble with running multiple scanners?

 Thanks,
 Greg




 Greg Kontos
 LIMS Integration Specialist

 Innovative Diagnostic Laboratory
 8751 Park Central Drive, Suite 200
 Richmond, VA 23227
 Phone: (804) 261-3340 ext.1846
 Cell Phone:
 Fax: (804) 515-7291
 mailto:gkon...@myinnovativelab.com

 Visit our website: http://www.myinnovativelab.com

 CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files 
 or previous e-mail messages attached to it contain confidential and/or 
 privileged information meant for the listed recipient(s) only. You may not 
 distribute or share this correspondence without written authorization from 
 the above author.

 If you are not the intended recipient, or a person responsible for 
 delivering it to the intended recipient, you are hereby notified that any 
 disclosure, copying, distribution or use of any of the information 
 contained in or attached to this transmission is STRICTLY PROHIBITED. If 
 you have received this transmission in error, please immediately notify me 
 by reply e-mail and destroy the original transmission and its attachments 
 without saving them in any manner.

 -Original Message-
 From: Wilhelm [mailto:wilhelm.me...@fh-kl.de]
 Sent: Friday, May 22, 2015 12:15 AM
 To: Greg Kontos; sane-devel@lists.alioth.debian.org
 Subject: Re: [sane-devel] Scanbd fails to start with multiple
 scanners (and no paper loaded)

 Hi Greg,

 please post the scanbd.conf and all the included config files (e.g.
 fujitsu.conf, ...),


 Am 21.05.2015 um 15:59 schrieb Greg Kontos:
 Thank you, Wilhelm.

 The attached zip contains log files with debug level 7.  The file 
 syslog_20150521 shows the process exiting.  The file syslog_start_20150521 
 shows the process starting properly with paper loaded into the scanners.

 I have also included
 - the *.script files referenced in the scanbd.conf file.
 - scanbd is the config file from /etc/default/scanbd
 - scanbd.service is the systemctl file from
 /lib/systemd/system/scanbd.service

 Let me know if there are any more files or test cases that I can run to 
 help troubleshoot this issue.

 Regards,
 G Kontos




 Greg Kontos
 LIMS Integration Specialist

 Innovative Diagnostic Laboratory
 8751 Park

Re: [sane-devel] Scanbd fails to start with multiple scanners (and no paper loaded)

[Greg Kontos]

Thank you, Wilhelm.  I appreciate you looking into this issue.  I tried 
commenting out the paperload and paperunload actions, which still led to the 
same behavior where the process dies on startup.  I went an extra step and also 
commented out the entire scanner specific fujitsu conf file within the main 
scanbd.conf file.  Unfortunately, I still see the same behavior on startup.

:) I'm pretty lucky to have multiple scanners to test with.  If there are tests 
you would like me to run, just shout.

Thanks again,
Greg




Greg Kontos
LIMS Integration Specialist

Innovative Diagnostic Laboratory
8751 Park Central Drive, Suite 200
Richmond, VA 23227
Phone: (804) 261-3340 ext.1846
Cell Phone:
Fax: (804) 515-7291
mailto:gkon...@myinnovativelab.com

Visit our website: http://www.myinnovativelab.com

CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files or 
previous e-mail messages attached to it contain confidential and/or privileged 
information meant for the listed recipient(s) only. You may not distribute or 
share this correspondence without written authorization from the above author.

If you are not the intended recipient, or a person responsible for delivering 
it to the intended recipient, you are hereby notified that any disclosure, 
copying, distribution or use of any of the information contained in or attached 
to this transmission is STRICTLY PROHIBITED. If you have received this 
transmission in error, please immediately notify me by reply e-mail and destroy 
the original transmission and its attachments without saving them in any manner.

-Original Message-
From: Wilhelm [mailto:wilhelm.me...@fh-kl.de]
Sent: Wednesday, June 03, 2015 1:38 AM
To: Greg Kontos; sane-devel@lists.alioth.debian.org
Subject: Re: [sane-devel] Scanbd fails to start with multiple scanners (and no 
paper loaded)

Hi Greg,

do you need the paperload or paperunload action? If not, please remove them 
from the config file, if yes, then give them a correct script name.

With this changes, please give me the full startup log with debug level 7.

Thanks,
 Wilhelm

Am 02.06.2015 um 17:31 schrieb Wilhelm:
 Hi Greg,

 thank you for your patience!

 I have some ideas where to look for this type of error, but
 unfortunately not enough time to do so. And I don't have access to
 more than one scanner at the moment :-(

 But please stay tuned ...

 Thanks,
  Wilhelm


 Am 02.06.2015 um 14:35 schrieb Greg Kontos:
 Hi Wilhelm,

 I'm following up to see if you have any thoughts or advice regarding the 
 trouble with running multiple scanners?

 Thanks,
 Greg




 Greg Kontos
 LIMS Integration Specialist

 Innovative Diagnostic Laboratory
 8751 Park Central Drive, Suite 200
 Richmond, VA 23227
 Phone: (804) 261-3340 ext.1846
 Cell Phone:
 Fax: (804) 515-7291
 mailto:gkon...@myinnovativelab.com

 Visit our website: http://www.myinnovativelab.com

 CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files 
 or previous e-mail messages attached to it contain confidential and/or 
 privileged information meant for the listed recipient(s) only. You may not 
 distribute or share this correspondence without written authorization from 
 the above author.

 If you are not the intended recipient, or a person responsible for 
 delivering it to the intended recipient, you are hereby notified that any 
 disclosure, copying, distribution or use of any of the information contained 
 in or attached to this transmission is STRICTLY PROHIBITED. If you have 
 received this transmission in error, please immediately notify me by reply 
 e-mail and destroy the original transmission and its attachments without 
 saving them in any manner.

 -Original Message-
 From: Wilhelm [mailto:wilhelm.me...@fh-kl.de]
 Sent: Friday, May 22, 2015 12:15 AM
 To: Greg Kontos; sane-devel@lists.alioth.debian.org
 Subject: Re: [sane-devel] Scanbd fails to start with multiple
 scanners (and no paper loaded)

 Hi Greg,

 please post the scanbd.conf and all the included config files (e.g.
 fujitsu.conf, ...),


 Am 21.05.2015 um 15:59 schrieb Greg Kontos:
 Thank you, Wilhelm.

 The attached zip contains log files with debug level 7.  The file 
 syslog_20150521 shows the process exiting.  The file syslog_start_20150521 
 shows the process starting properly with paper loaded into the scanners.

 I have also included
 - the *.script files referenced in the scanbd.conf file.
 - scanbd is the config file from /etc/default/scanbd
 - scanbd.service is the systemctl file from
 /lib/systemd/system/scanbd.service

 Let me know if there are any more files or test cases that I can run to 
 help troubleshoot this issue.

 Regards,
 G Kontos




 Greg Kontos
 LIMS Integration Specialist

 Innovative Diagnostic Laboratory
 8751 Park Central Drive, Suite 200
 Richmond, VA 23227
 Phone: (804) 261-3340 ext.1846
 Cell Phone:
 Fax: (804) 515-7291
 mailto:gkon...@myinnovativelab.com

 Visit our website: http://www.myinnovativelab.com

 CONFIDENTIALITY

Re: [sane-devel] Scanbd fails to start with multiple scanners (and no paper loaded)

[Wilhelm]

Hi Greg,

do you need the paperload or paperunload action? If not, please
remove them from the config file, if yes, then give them a correct
script name.

With this changes, please give me the full startup log with debug level 7.

Thanks,
 Wilhelm

Am 02.06.2015 um 17:31 schrieb Wilhelm:
 Hi Greg,
 
 thank you for your patience!
 
 I have some ideas where to look for this type of error, but
 unfortunately not enough time to do so. And I don't have access to more
 than one scanner at the moment :-(
 
 But please stay tuned ...
 
 Thanks,
  Wilhelm
 
 
 Am 02.06.2015 um 14:35 schrieb Greg Kontos:
 Hi Wilhelm,

 I'm following up to see if you have any thoughts or advice regarding the 
 trouble with running multiple scanners?

 Thanks,
 Greg




 Greg Kontos
 LIMS Integration Specialist

 Innovative Diagnostic Laboratory
 8751 Park Central Drive, Suite 200
 Richmond, VA 23227
 Phone: (804) 261-3340 ext.1846
 Cell Phone:
 Fax: (804) 515-7291
 mailto:gkon...@myinnovativelab.com

 Visit our website: http://www.myinnovativelab.com

 CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files 
 or previous e-mail messages attached to it contain confidential and/or 
 privileged information meant for the listed recipient(s) only. You may not 
 distribute or share this correspondence without written authorization from 
 the above author.

 If you are not the intended recipient, or a person responsible for 
 delivering it to the intended recipient, you are hereby notified that any 
 disclosure, copying, distribution or use of any of the information contained 
 in or attached to this transmission is STRICTLY PROHIBITED. If you have 
 received this transmission in error, please immediately notify me by reply 
 e-mail and destroy the original transmission and its attachments without 
 saving them in any manner.

 -Original Message-
 From: Wilhelm [mailto:wilhelm.me...@fh-kl.de]
 Sent: Friday, May 22, 2015 12:15 AM
 To: Greg Kontos; sane-devel@lists.alioth.debian.org
 Subject: Re: [sane-devel] Scanbd fails to start with multiple scanners (and 
 no paper loaded)

 Hi Greg,

 please post the scanbd.conf and all the included config files (e.g.
 fujitsu.conf, ...),


 Am 21.05.2015 um 15:59 schrieb Greg Kontos:
 Thank you, Wilhelm.

 The attached zip contains log files with debug level 7.  The file 
 syslog_20150521 shows the process exiting.  The file syslog_start_20150521 
 shows the process starting properly with paper loaded into the scanners.

 I have also included
 - the *.script files referenced in the scanbd.conf file.
 - scanbd is the config file from /etc/default/scanbd
 - scanbd.service is the systemctl file from
 /lib/systemd/system/scanbd.service

 Let me know if there are any more files or test cases that I can run to 
 help troubleshoot this issue.

 Regards,
 G Kontos




 Greg Kontos
 LIMS Integration Specialist

 Innovative Diagnostic Laboratory
 8751 Park Central Drive, Suite 200
 Richmond, VA 23227
 Phone: (804) 261-3340 ext.1846
 Cell Phone:
 Fax: (804) 515-7291
 mailto:gkon...@myinnovativelab.com

 Visit our website: http://www.myinnovativelab.com

 CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files 
 or previous e-mail messages attached to it contain confidential and/or 
 privileged information meant for the listed recipient(s) only. You may not 
 distribute or share this correspondence without written authorization from 
 the above author.

 If you are not the intended recipient, or a person responsible for 
 delivering it to the intended recipient, you are hereby notified that any 
 disclosure, copying, distribution or use of any of the information 
 contained in or attached to this transmission is STRICTLY PROHIBITED. If 
 you have received this transmission in error, please immediately notify me 
 by reply e-mail and destroy the original transmission and its attachments 
 without saving them in any manner.

 -Original Message-
 From: Wilhelm [mailto:wilhelm.me...@fh-kl.de]
 Sent: Wednesday, May 20, 2015 5:24 PM
 To: Greg Kontos; sane-devel@lists.alioth.debian.org
 Subject: Re: [sane-devel] Scanbd fails to start with multiple scanners
 (and no paper loaded)

 Am 20.05.2015 um 21:24 schrieb Greg Kontos:
 Thank you, Wilhelm.  I appreciate you taking the time to look into this.

 I am using version 1.4.0-2 of scanbd.  This problem does not persist with 
 only one scanner.  It seems that the scanner will trigger the page-loaded 
 action after a scan is complete.  So the strange behavior of the scan 
 button happens in other situations.

 In the attached zip file please find the scanbd.conf and log files.  The 
 log file shows two startup sequences.  The first is without paper loaded 
 in the scanner.  The second has paper loaded on startup.

 Sorry, but I need all config files (also the included ones) and please 
 start with debug level = 7.


 Regards,
 G Kontos




 Greg Kontos
 LIMS Integration Specialist

 Innovative Diagnostic Laboratory
 8751

Re: [sane-devel] Scanbd fails to start with multiple scanners (and no paper loaded)

[Greg Kontos]

Hi Wilhelm,

I'm following up to see if you have any thoughts or advice regarding the 
trouble with running multiple scanners?

Thanks,
Greg




Greg Kontos
LIMS Integration Specialist

Innovative Diagnostic Laboratory
8751 Park Central Drive, Suite 200
Richmond, VA 23227
Phone: (804) 261-3340 ext.1846
Cell Phone:
Fax: (804) 515-7291
mailto:gkon...@myinnovativelab.com

Visit our website: http://www.myinnovativelab.com

CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files or 
previous e-mail messages attached to it contain confidential and/or privileged 
information meant for the listed recipient(s) only. You may not distribute or 
share this correspondence without written authorization from the above author.

If you are not the intended recipient, or a person responsible for delivering 
it to the intended recipient, you are hereby notified that any disclosure, 
copying, distribution or use of any of the information contained in or attached 
to this transmission is STRICTLY PROHIBITED. If you have received this 
transmission in error, please immediately notify me by reply e-mail and destroy 
the original transmission and its attachments without saving them in any manner.

-Original Message-
From: Wilhelm [mailto:wilhelm.me...@fh-kl.de]
Sent: Friday, May 22, 2015 12:15 AM
To: Greg Kontos; sane-devel@lists.alioth.debian.org
Subject: Re: [sane-devel] Scanbd fails to start with multiple scanners (and no 
paper loaded)

Hi Greg,

please post the scanbd.conf and all the included config files (e.g.
fujitsu.conf, ...),


Am 21.05.2015 um 15:59 schrieb Greg Kontos:
 Thank you, Wilhelm.

 The attached zip contains log files with debug level 7.  The file 
 syslog_20150521 shows the process exiting.  The file syslog_start_20150521 
 shows the process starting properly with paper loaded into the scanners.

 I have also included
 - the *.script files referenced in the scanbd.conf file.
 - scanbd is the config file from /etc/default/scanbd
 - scanbd.service is the systemctl file from
 /lib/systemd/system/scanbd.service

 Let me know if there are any more files or test cases that I can run to help 
 troubleshoot this issue.

 Regards,
 G Kontos




 Greg Kontos
 LIMS Integration Specialist

 Innovative Diagnostic Laboratory
 8751 Park Central Drive, Suite 200
 Richmond, VA 23227
 Phone: (804) 261-3340 ext.1846
 Cell Phone:
 Fax: (804) 515-7291
 mailto:gkon...@myinnovativelab.com

 Visit our website: http://www.myinnovativelab.com

 CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files or 
 previous e-mail messages attached to it contain confidential and/or 
 privileged information meant for the listed recipient(s) only. You may not 
 distribute or share this correspondence without written authorization from 
 the above author.

 If you are not the intended recipient, or a person responsible for delivering 
 it to the intended recipient, you are hereby notified that any disclosure, 
 copying, distribution or use of any of the information contained in or 
 attached to this transmission is STRICTLY PROHIBITED. If you have received 
 this transmission in error, please immediately notify me by reply e-mail and 
 destroy the original transmission and its attachments without saving them in 
 any manner.

 -Original Message-
 From: Wilhelm [mailto:wilhelm.me...@fh-kl.de]
 Sent: Wednesday, May 20, 2015 5:24 PM
 To: Greg Kontos; sane-devel@lists.alioth.debian.org
 Subject: Re: [sane-devel] Scanbd fails to start with multiple scanners
 (and no paper loaded)

 Am 20.05.2015 um 21:24 schrieb Greg Kontos:
 Thank you, Wilhelm.  I appreciate you taking the time to look into this.

 I am using version 1.4.0-2 of scanbd.  This problem does not persist with 
 only one scanner.  It seems that the scanner will trigger the page-loaded 
 action after a scan is complete.  So the strange behavior of the scan button 
 happens in other situations.

 In the attached zip file please find the scanbd.conf and log files.  The log 
 file shows two startup sequences.  The first is without paper loaded in the 
 scanner.  The second has paper loaded on startup.

 Sorry, but I need all config files (also the included ones) and please start 
 with debug level = 7.


 Regards,
 G Kontos




 Greg Kontos
 LIMS Integration Specialist

 Innovative Diagnostic Laboratory
 8751 Park Central Drive, Suite 200
 Richmond, VA 23227
 Phone: (804) 261-3340 ext.1846
 Cell Phone:
 Fax: (804) 515-7291
 mailto:gkon...@myinnovativelab.com

 Visit our website: http://www.myinnovativelab.com

 CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files 
 or previous e-mail messages attached to it contain confidential and/or 
 privileged information meant for the listed recipient(s) only. You may not 
 distribute or share this correspondence without written authorization from 
 the above author.

 If you are not the intended recipient, or a person responsible for 
 delivering it to the intended recipient

Re: [sane-devel] Scanbd fails to start with multiple scanners (and no paper loaded)

[Wilhelm]

Hi Greg,

thank you for your patience!

I have some ideas where to look for this type of error, but
unfortunately not enough time to do so. And I don't have access to more
than one scanner at the moment :-(

But please stay tuned ...

Thanks,
 Wilhelm


Am 02.06.2015 um 14:35 schrieb Greg Kontos:
 Hi Wilhelm,
 
 I'm following up to see if you have any thoughts or advice regarding the 
 trouble with running multiple scanners?
 
 Thanks,
 Greg
 
 
 
 
 Greg Kontos
 LIMS Integration Specialist
 
 Innovative Diagnostic Laboratory
 8751 Park Central Drive, Suite 200
 Richmond, VA 23227
 Phone: (804) 261-3340 ext.1846
 Cell Phone:
 Fax: (804) 515-7291
 mailto:gkon...@myinnovativelab.com
 
 Visit our website: http://www.myinnovativelab.com
 
 CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files or 
 previous e-mail messages attached to it contain confidential and/or 
 privileged information meant for the listed recipient(s) only. You may not 
 distribute or share this correspondence without written authorization from 
 the above author.
 
 If you are not the intended recipient, or a person responsible for delivering 
 it to the intended recipient, you are hereby notified that any disclosure, 
 copying, distribution or use of any of the information contained in or 
 attached to this transmission is STRICTLY PROHIBITED. If you have received 
 this transmission in error, please immediately notify me by reply e-mail and 
 destroy the original transmission and its attachments without saving them in 
 any manner.
 
 -Original Message-
 From: Wilhelm [mailto:wilhelm.me...@fh-kl.de]
 Sent: Friday, May 22, 2015 12:15 AM
 To: Greg Kontos; sane-devel@lists.alioth.debian.org
 Subject: Re: [sane-devel] Scanbd fails to start with multiple scanners (and 
 no paper loaded)
 
 Hi Greg,
 
 please post the scanbd.conf and all the included config files (e.g.
 fujitsu.conf, ...),
 
 
 Am 21.05.2015 um 15:59 schrieb Greg Kontos:
 Thank you, Wilhelm.

 The attached zip contains log files with debug level 7.  The file 
 syslog_20150521 shows the process exiting.  The file syslog_start_20150521 
 shows the process starting properly with paper loaded into the scanners.

 I have also included
 - the *.script files referenced in the scanbd.conf file.
 - scanbd is the config file from /etc/default/scanbd
 - scanbd.service is the systemctl file from
 /lib/systemd/system/scanbd.service

 Let me know if there are any more files or test cases that I can run to help 
 troubleshoot this issue.

 Regards,
 G Kontos




 Greg Kontos
 LIMS Integration Specialist

 Innovative Diagnostic Laboratory
 8751 Park Central Drive, Suite 200
 Richmond, VA 23227
 Phone: (804) 261-3340 ext.1846
 Cell Phone:
 Fax: (804) 515-7291
 mailto:gkon...@myinnovativelab.com

 Visit our website: http://www.myinnovativelab.com

 CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files 
 or previous e-mail messages attached to it contain confidential and/or 
 privileged information meant for the listed recipient(s) only. You may not 
 distribute or share this correspondence without written authorization from 
 the above author.

 If you are not the intended recipient, or a person responsible for 
 delivering it to the intended recipient, you are hereby notified that any 
 disclosure, copying, distribution or use of any of the information contained 
 in or attached to this transmission is STRICTLY PROHIBITED. If you have 
 received this transmission in error, please immediately notify me by reply 
 e-mail and destroy the original transmission and its attachments without 
 saving them in any manner.

 -Original Message-
 From: Wilhelm [mailto:wilhelm.me...@fh-kl.de]
 Sent: Wednesday, May 20, 2015 5:24 PM
 To: Greg Kontos; sane-devel@lists.alioth.debian.org
 Subject: Re: [sane-devel] Scanbd fails to start with multiple scanners
 (and no paper loaded)

 Am 20.05.2015 um 21:24 schrieb Greg Kontos:
 Thank you, Wilhelm.  I appreciate you taking the time to look into this.

 I am using version 1.4.0-2 of scanbd.  This problem does not persist with 
 only one scanner.  It seems that the scanner will trigger the page-loaded 
 action after a scan is complete.  So the strange behavior of the scan 
 button happens in other situations.

 In the attached zip file please find the scanbd.conf and log files.  The 
 log file shows two startup sequences.  The first is without paper loaded in 
 the scanner.  The second has paper loaded on startup.

 Sorry, but I need all config files (also the included ones) and please start 
 with debug level = 7.


 Regards,
 G Kontos




 Greg Kontos
 LIMS Integration Specialist

 Innovative Diagnostic Laboratory
 8751 Park Central Drive, Suite 200
 Richmond, VA 23227
 Phone: (804) 261-3340 ext.1846
 Cell Phone:
 Fax: (804) 515-7291
 mailto:gkon...@myinnovativelab.com

 Visit our website: http://www.myinnovativelab.com

 CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files

Re: [sane-devel] Scanbd fails to start with multiple scanners (and no paper loaded)

[Wilhelm]

Hi Greg,

please post the scanbd.conf and all the included config files (e.g.
fujitsu.conf, ...),


Am 21.05.2015 um 15:59 schrieb Greg Kontos:
 Thank you, Wilhelm.
 
 The attached zip contains log files with debug level 7.  The file 
 syslog_20150521 shows the process exiting.  The file syslog_start_20150521 
 shows the process starting properly with paper loaded into the scanners.
 
 I have also included
 - the *.script files referenced in the scanbd.conf file.
 - scanbd is the config file from /etc/default/scanbd
 - scanbd.service is the systemctl file from /lib/systemd/system/scanbd.service
 
 Let me know if there are any more files or test cases that I can run to help 
 troubleshoot this issue.
 
 Regards,
 G Kontos
 
 
 
 
 Greg Kontos
 LIMS Integration Specialist
 
 Innovative Diagnostic Laboratory
 8751 Park Central Drive, Suite 200
 Richmond, VA 23227
 Phone: (804) 261-3340 ext.1846
 Cell Phone:
 Fax: (804) 515-7291
 mailto:gkon...@myinnovativelab.com
 
 Visit our website: http://www.myinnovativelab.com
 
 CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files or 
 previous e-mail messages attached to it contain confidential and/or 
 privileged information meant for the listed recipient(s) only. You may not 
 distribute or share this correspondence without written authorization from 
 the above author.
 
 If you are not the intended recipient, or a person responsible for delivering 
 it to the intended recipient, you are hereby notified that any disclosure, 
 copying, distribution or use of any of the information contained in or 
 attached to this transmission is STRICTLY PROHIBITED. If you have received 
 this transmission in error, please immediately notify me by reply e-mail and 
 destroy the original transmission and its attachments without saving them in 
 any manner.
 
 -Original Message-
 From: Wilhelm [mailto:wilhelm.me...@fh-kl.de]
 Sent: Wednesday, May 20, 2015 5:24 PM
 To: Greg Kontos; sane-devel@lists.alioth.debian.org
 Subject: Re: [sane-devel] Scanbd fails to start with multiple scanners (and 
 no paper loaded)
 
 Am 20.05.2015 um 21:24 schrieb Greg Kontos:
 Thank you, Wilhelm.  I appreciate you taking the time to look into this.

 I am using version 1.4.0-2 of scanbd.  This problem does not persist with 
 only one scanner.  It seems that the scanner will trigger the page-loaded 
 action after a scan is complete.  So the strange behavior of the scan button 
 happens in other situations.

 In the attached zip file please find the scanbd.conf and log files.  The log 
 file shows two startup sequences.  The first is without paper loaded in the 
 scanner.  The second has paper loaded on startup.
 
 Sorry, but I need all config files (also the included ones) and please start 
 with debug level = 7.
 

 Regards,
 G Kontos




 Greg Kontos
 LIMS Integration Specialist

 Innovative Diagnostic Laboratory
 8751 Park Central Drive, Suite 200
 Richmond, VA 23227
 Phone: (804) 261-3340 ext.1846
 Cell Phone:
 Fax: (804) 515-7291
 mailto:gkon...@myinnovativelab.com

 Visit our website: http://www.myinnovativelab.com

 CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files 
 or previous e-mail messages attached to it contain confidential and/or 
 privileged information meant for the listed recipient(s) only. You may not 
 distribute or share this correspondence without written authorization from 
 the above author.

 If you are not the intended recipient, or a person responsible for 
 delivering it to the intended recipient, you are hereby notified that any 
 disclosure, copying, distribution or use of any of the information contained 
 in or attached to this transmission is STRICTLY PROHIBITED. If you have 
 received this transmission in error, please immediately notify me by reply 
 e-mail and destroy the original transmission and its attachments without 
 saving them in any manner.

 -Original Message-
 From: sane-devel
 [mailto:sane-devel-bounces+gkontos=myinnovativelab@lists.alioth.de
 bian.org] On Behalf Of Wilhelm
 Sent: Wednesday, May 20, 2015 11:55 AM
 To: sane-devel@lists.alioth.debian.org
 Subject: Re: [sane-devel] Scanbd fails to start with multiple scanners
 (and no paper loaded)

 Hi Greg,

 please

 1) post your scabd config files
 2) provide scanbd version information

 I see a page-load event with no script defined - looks strange.

 You said that there wasn't any paper load: so the page-load event get fired 
 without any paper load action? More strange.

 3) Can please give the full log from scanbd startup till crash.

 Does the problem remain with only one scanner?


 Am 20.05.2015 um 16:49 schrieb Greg Kontos:
 Hello,



 I’m running scanbd on a debian machine with version 1.0.25 of the
 sane-backend.  I installed scanbd using apt-get, sane-backend was
 compiled from a git clone.  I’m using two fujitsu fi-7160 scanners in
 my setup.  The problem: If there is no paper loaded in at least one
 scanner, scanbd.service

Re: [sane-devel] Scanbd fails to start with multiple scanners (and no paper loaded)

[Wilhelm]

Hi Greg,

please

1) post your scabd config files
2) provide scanbd version information

I see a page-load event with no script defined - looks strange.

You said that there wasn't any paper load: so the page-load event get
fired without any paper load action? More strange.

3) Can please give the full log from scanbd startup till crash.

Does the problem remain with only one scanner?


Am 20.05.2015 um 16:49 schrieb Greg Kontos:
 Hello,
 
  
 
 I’m running scanbd on a debian machine with version 1.0.25 of the
 sane-backend.  I installed scanbd using apt-get, sane-backend was
 compiled from a git clone.  I’m using two fujitsu fi-7160 scanners in my
 setup.  The problem: If there is no paper loaded in at least one
 scanner, scanbd.service will exit the main process and abort.  This
 failure will at a variety of times depending on the circumstances.  It
 will happen during startup of the machine.  It will also happen after a
 few minutes after a scan process is complete.  This post-scan behavior
 is not 100% replicable. 
 
  
 
 The following is /var/log/syslog after a system restart.  : (I can
 provide a more detailed log if that will be helpful)
 
  
 
 May 20 09:36:40 hp6300pro-23 systemd[1151]: Starting Paths.
 
 May 20 09:36:40 hp6300pro-23 systemd[1151]: Reached target Paths.
 
 May 20 09:36:40 hp6300pro-23 systemd[1151]: Starting Timers.
 
 May 20 09:36:40 hp6300pro-23 systemd[1151]: Reached target Timers.
 
 May 20 09:36:40 hp6300pro-23 systemd[1151]: Starting Sockets.
 
 May 20 09:36:40 hp6300pro-23 systemd[1151]: Reached target Sockets.
 
 May 20 09:36:40 hp6300pro-23 systemd[1151]: Starting Basic System.
 
 May 20 09:36:40 hp6300pro-23 systemd[1151]: Reached target Basic System.
 
 May 20 09:36:40 hp6300pro-23 systemd[1151]: Starting Default.
 
 May 20 09:36:40 hp6300pro-23 systemd[1151]: Reached target Default.
 
 May 20 09:36:40 hp6300pro-23 systemd[1151]: Startup finished in 4ms.
 
 May 20 09:37:06 hp6300pro-23 scanbd: /usr/sbin/scanbd: trigger action
 for page-loaded for device fujitsu:fi-7160:188290 with script (null)
 
 May 20 09:37:07 hp6300pro-23 scanbd: /usr/sbin/scanbd: trigger action
 for page-loaded for device fujitsu:fi-7160:187984 with script (null)
 
 May 20 09:40:13 hp6300pro-23 scanbd[542]: scanbd: sane.c:852: sane_poll:
 Assertion `st-triggered_option  st-num_of_options_with_scripts' failed.
 
 May 20 09:40:13 hp6300pro-23 scanbd[542]: /usr/sbin/scanbd: dbus match
 type='signal',interface='org.freedesktop.Hal.Manager'
 
 May 20 09:40:13 hp6300pro-23 scanbd[542]: /usr/sbin/scanbd: trigger
 action for page-loaded for device fujitsu:fi-7160:188290 with script (null)
 
 May 20 09:40:13 hp6300pro-23 scanbd[542]: /usr/sbin/scanbd: trigger
 action for page-loaded for device fujitsu:fi-7160:187984 with script (null)
 
 May 20 09:40:13 hp6300pro-23 scanbd[542]: /usr/sbin/scanbd: trigger
 action for page-loaded for device fujitsu:fi-7160:188290 with script (null)
 
 May 20 09:40:13 hp6300pro-23 scanbd[542]: /usr/sbin/scanbd: trigger
 action for page-loaded for device fujitsu:fi-7160:188290 with script (null)
 
 May 20 09:40:13 hp6300pro-23 scanbd[542]: /usr/sbin/scanbd: trigger
 action for page-loaded for device fujitsu:fi-7160:188290 with script (null)
 
 May 20 09:40:13 hp6300pro-23 scanbd[542]: /usr/sbin/scanbd: trigger
 action for page-loaded for device fujitsu:fi-7160:188290 with script (null)
 
 May 20 09:40:13 hp6300pro-23 scanbd[542]: /usr/sbin/scanbd: trigger
 action for page-loaded for device fujitsu:fi-7160:187984 with script (null)
 
 May 20 09:40:13 hp6300pro-23 systemd[1]: scanbd.service: main process
 exited, code=killed, status=6/ABRT
 
 May 20 09:40:13 hp6300pro-23 systemd[1]: Unit scanbd.service entered
 failed state.
 
  
 
 It may be worth noting that there was no paper loaded in the scanners
 when this log file was created.  Also, after the service exits, the
 scanners can both be found using scanimage –L.
 
  
 
 Currently I’ve found a work around : If a piece of paper is kept loaded
 in the scanners, the process starts properly after boot and seems to
 stay active.  Should my use case work with scanbd?  Does anyone know of
 a better work around?  Perhaps there is an option or setting that I have
 overlooked?  Thank you for any help with this issue.
 
  
 
 Thanks,
 G Kontos
 
 
 
 Greg Kontos
 LIMS Integration Specialist
 
 Innovative Diagnostic Laboratory
 8751 Park Central Drive, Suite 200
 Richmond, VA 23227
 Phone: (804) 261-3340 ext.1846
 Cell Phone:
 Fax: (804) 515-7291
 gkon...@myinnovativelab.com mailto:gkon...@myinnovativelab.com
 
 Visit our website: www.myinnovativelab.com http://www.myinnovativelab.com
 
 http://
 
 CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents,
 files or previous e-mail messages attached to it contain confidential
 and/or privileged information meant for the listed recipient(s) only.
 You may not distribute or share this correspondence without written
 authorization from the above author.
 
 If you are not the 

Re: [sane-devel] Scanbd fails to start with multiple scanners (and no paper loaded)

[Wilhelm]

Am 20.05.2015 um 21:24 schrieb Greg Kontos:
 Thank you, Wilhelm.  I appreciate you taking the time to look into this.
 
 I am using version 1.4.0-2 of scanbd.  This problem does not persist with 
 only one scanner.  It seems that the scanner will trigger the page-loaded 
 action after a scan is complete.  So the strange behavior of the scan button 
 happens in other situations.
 
 In the attached zip file please find the scanbd.conf and log files.  The log 
 file shows two startup sequences.  The first is without paper loaded in the 
 scanner.  The second has paper loaded on startup.

Sorry, but I need all config files (also the included ones) and please
start with debug level = 7.

 
 Regards,
 G Kontos
 
 
 
 
 Greg Kontos
 LIMS Integration Specialist
 
 Innovative Diagnostic Laboratory
 8751 Park Central Drive, Suite 200
 Richmond, VA 23227
 Phone: (804) 261-3340 ext.1846
 Cell Phone:
 Fax: (804) 515-7291
 mailto:gkon...@myinnovativelab.com
 
 Visit our website: http://www.myinnovativelab.com
 
 CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files or 
 previous e-mail messages attached to it contain confidential and/or 
 privileged information meant for the listed recipient(s) only. You may not 
 distribute or share this correspondence without written authorization from 
 the above author.
 
 If you are not the intended recipient, or a person responsible for delivering 
 it to the intended recipient, you are hereby notified that any disclosure, 
 copying, distribution or use of any of the information contained in or 
 attached to this transmission is STRICTLY PROHIBITED. If you have received 
 this transmission in error, please immediately notify me by reply e-mail and 
 destroy the original transmission and its attachments without saving them in 
 any manner.
 
 -Original Message-
 From: sane-devel 
 [mailto:sane-devel-bounces+gkontos=myinnovativelab@lists.alioth.debian.org]
  On Behalf Of Wilhelm
 Sent: Wednesday, May 20, 2015 11:55 AM
 To: sane-devel@lists.alioth.debian.org
 Subject: Re: [sane-devel] Scanbd fails to start with multiple scanners (and 
 no paper loaded)
 
 Hi Greg,
 
 please
 
 1) post your scabd config files
 2) provide scanbd version information
 
 I see a page-load event with no script defined - looks strange.
 
 You said that there wasn't any paper load: so the page-load event get fired 
 without any paper load action? More strange.
 
 3) Can please give the full log from scanbd startup till crash.
 
 Does the problem remain with only one scanner?
 
 
 Am 20.05.2015 um 16:49 schrieb Greg Kontos:
 Hello,



 I’m running scanbd on a debian machine with version 1.0.25 of the
 sane-backend.  I installed scanbd using apt-get, sane-backend was
 compiled from a git clone.  I’m using two fujitsu fi-7160 scanners in
 my setup.  The problem: If there is no paper loaded in at least one
 scanner, scanbd.service will exit the main process and abort.  This
 failure will at a variety of times depending on the circumstances.  It
 will happen during startup of the machine.  It will also happen after
 a few minutes after a scan process is complete.  This post-scan
 behavior is not 100% replicable.



 The following is /var/log/syslog after a system restart.  : (I can
 provide a more detailed log if that will be helpful)



 May 20 09:36:40 hp6300pro-23 systemd[1151]: Starting Paths.

 May 20 09:36:40 hp6300pro-23 systemd[1151]: Reached target Paths.

 May 20 09:36:40 hp6300pro-23 systemd[1151]: Starting Timers.

 May 20 09:36:40 hp6300pro-23 systemd[1151]: Reached target Timers.

 May 20 09:36:40 hp6300pro-23 systemd[1151]: Starting Sockets.

 May 20 09:36:40 hp6300pro-23 systemd[1151]: Reached target Sockets.

 May 20 09:36:40 hp6300pro-23 systemd[1151]: Starting Basic System.

 May 20 09:36:40 hp6300pro-23 systemd[1151]: Reached target Basic System.

 May 20 09:36:40 hp6300pro-23 systemd[1151]: Starting Default.

 May 20 09:36:40 hp6300pro-23 systemd[1151]: Reached target Default.

 May 20 09:36:40 hp6300pro-23 systemd[1151]: Startup finished in 4ms.

 May 20 09:37:06 hp6300pro-23 scanbd: /usr/sbin/scanbd: trigger action
 for page-loaded for device fujitsu:fi-7160:188290 with script (null)

 May 20 09:37:07 hp6300pro-23 scanbd: /usr/sbin/scanbd: trigger action
 for page-loaded for device fujitsu:fi-7160:187984 with script (null)

 May 20 09:40:13 hp6300pro-23 scanbd[542]: scanbd: sane.c:852: sane_poll:
 Assertion `st-triggered_option  st-num_of_options_with_scripts' failed.

 May 20 09:40:13 hp6300pro-23 scanbd[542]: /usr/sbin/scanbd: dbus match
 type='signal',interface='org.freedesktop.Hal.Manager'

 May 20 09:40:13 hp6300pro-23 scanbd[542]: /usr/sbin/scanbd: trigger
 action for page-loaded for device fujitsu:fi-7160:188290 with script
 (null)

 May 20 09:40:13 hp6300pro-23 scanbd[542]: /usr/sbin/scanbd: trigger
 action for page-loaded for device fujitsu:fi-7160:187984 with script
 (null)

 May 20 09:40:13 hp6300pro-23 scanbd[542]: /usr/sbin/scanbd: trigger

[sane-devel] Scanbd fails to start with multiple scanners (and no paper loaded)

[Greg Kontos]

Hello,

I’m running scanbd on a debian machine with version 1.0.25 of the sane-backend. 
 I installed scanbd using apt-get, sane-backend was compiled from a git clone.  
I’m using two fujitsu fi-7160 scanners in my setup.  The problem: If there is 
no paper loaded in at least one scanner, scanbd.service will exit the main 
process and abort.  This failure will at a variety of times depending on the 
circumstances.  It will happen during startup of the machine.  It will also 
happen after a few minutes after a scan process is complete.  This post-scan 
behavior is not 100% replicable.

The following is /var/log/syslog after a system restart.  : (I can provide a 
more detailed log if that will be helpful)

May 20 09:36:40 hp6300pro-23 systemd[1151]: Starting Paths.
May 20 09:36:40 hp6300pro-23 systemd[1151]: Reached target Paths.
May 20 09:36:40 hp6300pro-23 systemd[1151]: Starting Timers.
May 20 09:36:40 hp6300pro-23 systemd[1151]: Reached target Timers.
May 20 09:36:40 hp6300pro-23 systemd[1151]: Starting Sockets.
May 20 09:36:40 hp6300pro-23 systemd[1151]: Reached target Sockets.
May 20 09:36:40 hp6300pro-23 systemd[1151]: Starting Basic System.
May 20 09:36:40 hp6300pro-23 systemd[1151]: Reached target Basic System.
May 20 09:36:40 hp6300pro-23 systemd[1151]: Starting Default.
May 20 09:36:40 hp6300pro-23 systemd[1151]: Reached target Default.
May 20 09:36:40 hp6300pro-23 systemd[1151]: Startup finished in 4ms.
May 20 09:37:06 hp6300pro-23 scanbd: /usr/sbin/scanbd: trigger action for 
page-loaded for device fujitsu:fi-7160:188290 with script (null)
May 20 09:37:07 hp6300pro-23 scanbd: /usr/sbin/scanbd: trigger action for 
page-loaded for device fujitsu:fi-7160:187984 with script (null)
May 20 09:40:13 hp6300pro-23 scanbd[542]: scanbd: sane.c:852: sane_poll: 
Assertion `st-triggered_option  st-num_of_options_with_scripts' failed.
May 20 09:40:13 hp6300pro-23 scanbd[542]: /usr/sbin/scanbd: dbus match 
type='signal',interface='org.freedesktop.Hal.Manager'
May 20 09:40:13 hp6300pro-23 scanbd[542]: /usr/sbin/scanbd: trigger action for 
page-loaded for device fujitsu:fi-7160:188290 with script (null)
May 20 09:40:13 hp6300pro-23 scanbd[542]: /usr/sbin/scanbd: trigger action for 
page-loaded for device fujitsu:fi-7160:187984 with script (null)
May 20 09:40:13 hp6300pro-23 scanbd[542]: /usr/sbin/scanbd: trigger action for 
page-loaded for device fujitsu:fi-7160:188290 with script (null)
May 20 09:40:13 hp6300pro-23 scanbd[542]: /usr/sbin/scanbd: trigger action for 
page-loaded for device fujitsu:fi-7160:188290 with script (null)
May 20 09:40:13 hp6300pro-23 scanbd[542]: /usr/sbin/scanbd: trigger action for 
page-loaded for device fujitsu:fi-7160:188290 with script (null)
May 20 09:40:13 hp6300pro-23 scanbd[542]: /usr/sbin/scanbd: trigger action for 
page-loaded for device fujitsu:fi-7160:188290 with script (null)
May 20 09:40:13 hp6300pro-23 scanbd[542]: /usr/sbin/scanbd: trigger action for 
page-loaded for device fujitsu:fi-7160:187984 with script (null)
May 20 09:40:13 hp6300pro-23 systemd[1]: scanbd.service: main process exited, 
code=killed, status=6/ABRT
May 20 09:40:13 hp6300pro-23 systemd[1]: Unit scanbd.service entered failed 
state.

It may be worth noting that there was no paper loaded in the scanners when this 
log file was created.  Also, after the service exits, the scanners can both be 
found using scanimage –L.

Currently I’ve found a work around : If a piece of paper is kept loaded in the 
scanners, the process starts properly after boot and seems to stay active.  
Should my use case work with scanbd?  Does anyone know of a better work around? 
 Perhaps there is an option or setting that I have overlooked?  Thank you for 
any help with this issue.

Thanks,
G Kontos


Greg Kontos
LIMS Integration Specialist

Innovative Diagnostic Laboratory
8751 Park Central Drive, Suite 200
Richmond, VA 23227
Phone: (804) 261-3340 ext.1846
Cell Phone:
Fax: (804) 515-7291
gkon...@myinnovativelab.commailto:gkon...@myinnovativelab.com

Visit our website: www.myinnovativelab.comhttp://www.myinnovativelab.com

[cid:image4ae1b1.PNG@323451c5.4da480a6]http://

CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files or 
previous e-mail messages attached to it contain confidential and/or privileged 
information meant for the listed recipient(s) only. You may not distribute or 
share this correspondence without written authorization from the above author.

If you are not the intended recipient, or a person responsible for delivering 
it to the intended recipient, you are hereby notified that any disclosure, 
copying, distribution or use of any of the information contained in or attached 
to this transmission is STRICTLY PROHIBITED. If you have received this 
transmission in error, please immediately notify me by reply e-mail and destroy 
the original transmission and its attachments without saving them in any manner.



-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org

Re: [sane-devel] scanbd and actually scanning over the LAN

[Wilhelm]

Am 04.03.2015 um 14:30 schrieb Rolf Leggewie:
 Hello,
 
 with scanbd sitting on top of the net backend I wonder if and how actual
 scanning over the LAN still works.  Two scenarios.
 
 a) sharing a scanbd scan host SH via the LAN to scan client SC
 b) accessing a saned LAN scanner LS on a scanbd-enabled computer SES
 
 Are both scenarios supported?  This will have implications for my
 packaging as well.
 
 I guess scenario A ought to be possible by adding something like
 192.168.0.0/24 to /etc/sane.d/saned.conf on SH, while scenario B would
 require adding the IP or hostname of LS to /etc/sane.d/net.conf on SES.
 
 So far, so (theoretically) good?  I wonder especially if scenario B
 isn't going to blow up in my face.

Should be ok if you omit localhost in saned / /etc/scanbd/net.conf.

But: local or remote scan-applications must (only) include the scanbd
host in /etc/sane.d/net.conf (either localhost or remote).


-- 
Wilhelm
w.me...@unix.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

[sane-devel] scanbd and actually scanning over the LAN

[Rolf Leggewie]

Hello,

with scanbd sitting on top of the net backend I wonder if and how actual
scanning over the LAN still works.  Two scenarios.

a) sharing a scanbd scan host SH via the LAN to scan client SC
b) accessing a saned LAN scanner LS on a scanbd-enabled computer SES

Are both scenarios supported?  This will have implications for my
packaging as well.

I guess scenario A ought to be possible by adding something like
192.168.0.0/24 to /etc/sane.d/saned.conf on SH, while scenario B would
require adding the IP or hostname of LS to /etc/sane.d/net.conf on SES.

So far, so (theoretically) good?  I wonder especially if scenario B
isn't going to blow up in my face.

Regards

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] scanbd Post Processing

[ylafont]

Honestly, i thought that was comment  out.  I Had tried a few thins to see
what was working or not.   Regardless that was the not the problem.

Haven't quite figure it out. Although it makes no sense the  only thing that
has worked is to place 

cd $CurrentDir before the script is executed.  

I would expect the $Currentdir to be be /usr/local/etc/scanbd, however it is
recorded as /

some funky things go on as well like directories are not changes when a cd
command is issued, which screws most of the script. 

Will have watch the folder for new files for now.





--
View this message in context: 
http://sane.10972.n7.nabble.com/scanbd-Post-Processing-tp19426p19441.html
Sent from the SANE - Dev mailing list archive at Nabble.com.

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

Re: [sane-devel] scanbd Post Processing

[ylafont]

Yes, 

the last line of the script, calls a script to process the scans,  

The complete scan.sh.  is as follows. 

logger -t scanbd: $0 Begin of $SCANBD_ACTION for device $SCANBD_DEVICE

# printout all env-variables
/usr/bin/printenv  /tmp/scanbd.env

CurrentDir=$(pwd)   #Script 
Starting Directory
scandir=/home/pi/PiScans  #Scanning 
Directory
tmpdir=Scan-$RANDOM #Script 
temporary Directory of processing.

mkdir $scandir/$tmpdir
cd $scandir/$tmpdir

if  [ $SCANBD_FUNCTION -eq 2 ]; then
#if [ $SCANBD_ACTION -eq paperload ]  [ $SCANBD_FUNCTION -eq 2 ]; then
logger -t scanbd: $0 * Now Scanning on device 
$SCANBD_DEVICE
***
#scanimage -d net:localhost:fujitsu:fi-4220C2dj:100742 -y 279.4 -x 215.9
--batch --format=tiff --mode Lineart --resolution 300 --source=ADF Duplex
scanimage -d $SCANBD_DEVICE -y 279.4 -x 215.9 --batch --format=tiff 
--mode
Lineart --resolution 300 --source=ADF Duplex
logger -t scanbd: $0 * Scanning ended on device
$SCANBD_DEVICE ***
fi

. ./premove.sh

logger -t scanbd: $0 End   of $SCANBD_ACTION for device $SCANBD_DEVICE
___


I had also address the error - but the second script which is in the same
location as scan.sh does not execute.

Feb 11 02:19:18 PiScanner scanbd: /usr/local/etc/scanbd/scan.sh: Begin of
scan for device fujitsu:fi-4220C2dj:100742
Feb 11 02:19:18 PiScanner scanbd: /usr/local/etc/scanbd/scan.sh:
* Now Scanning on device fujitsu:fi-4220C2dj:100742
***
Feb 11 02:19:19 PiScanner scanbd: /usr/local/sbin/scanbd: Iteration on dbus
call
Feb 11 02:19:20 PiScanner scanbd: /usr/local/sbin/scanbd: Iteration on dbus
call
Feb 11 02:19:21 PiScanner scanbd: /usr/local/sbin/scanbd: Iteration on dbus
call
Feb 11 02:19:22 PiScanner scanbd: /usr/local/sbin/scanbd: Iteration on dbus
call
Feb 11 02:19:23 PiScanner scanbd: /usr/local/sbin/scanbd: Iteration on dbus
call
Feb 11 02:19:24 PiScanner scanbd: /usr/local/sbin/scanbd: Iteration on dbus
call
Feb 11 02:19:25 PiScanner scanbd: /usr/local/sbin/scanbd: Iteration on dbus
call
Feb 11 02:19:26 PiScanner scanbd: /usr/local/sbin/scanbd: Iteration on dbus
call
Feb 11 02:19:27 PiScanner scanbd: /usr/local/sbin/scanbd: Iteration on dbus
call
Feb 11 02:19:27 PiScanner scanbd: /usr/local/etc/scanbd/scan.sh:
* Scanning ended on device fujitsu:fi-4220C2dj:100742
***
Feb 11 02:19:27 PiScanner scanbd: /usr/local/etc/scanbd/scan.sh: This this
End  ***  of scan for device fujitsu:fi-4220C2dj:100742
Feb 11 02:19:27 PiScanner scanbd: /usr/local/sbin/scanbd: child
/usr/local/etc/scanbd/scan.sh exited with status: 0
Feb 11 02:19:27 PiScanner scanbd: /usr/local/sbin/scanbd: append string
fujitsu:fi-4220C2dj:100742 to signal scan_end





--
View this message in context: 
http://sane.10972.n7.nabble.com/scanbd-Post-Processing-tp19426p19430.html
Sent from the SANE - Dev mailing list archive at Nabble.com.

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

Re: [sane-devel] scanbd Post Processing

[Wilhelm]

Am 10.02.2015 um 04:30 schrieb ylafont:
 Forgive me if this  not the correct section  for this.
 
 I wanted to start a bash script to process the completed scans. I created a
 link to Scan.sh from test.script
 
 test.script - scan.sh
 
 A section of scan.sh contains the following when scanning via the ADF
 
 if [ $SCANBD_ACTION -eq paperload ]  [ $SCANBD_FUNCTION -eq 2 ]; then
 
 logger -t scanbd: $0 * Now Scanning on device $SCANBD_DEVICE
 ***
 scanimage -d $SCANBD_DEVICE -y 279.4 -x 215.9 --batch --format=tiff --mode
 Lineart --resolution 300 --source=ADF Duplex
 
 logger -t scanbd: $0 * Scanning ended on device
 $SCANBD_DEVICE ***
 fi
 
 logger -t scanbd: $0 End of $SCANBD_ACTION for device $SCANBD_DEVICE
 Removing blank pages and cleaning all others.
 logger -t scanbd: $0  Starting Page Removal Process **
 
 *. ./premove.sh*   - Post processing script

Is the above line part of the scan-script?

You can only use *one* script for one action.

 
 After the scanner completes the scan the script is terminated and does not
 allow processing to continue.
 Feb 10 00:38:14 PiScanner scanbd: /usr/local/etc/scanbd/scan.sh: 
 Scanning ended on device fujitsu:fi-4220C2dj:100742 **
 Feb 10 00:38:14 PiScanner scanbd: /usr/local/etc/scanbd/scan.sh: End of scan
 for device fujitsu:fi-4220C2dj:100742
 Feb 10 00:38:14 PiScanner scanbd: /usr/local/sbin/scanbd: child
 /usr/local/etc/scanbd/scan.sh exited with status: 1

The scan-script terminates with an error - this might be a problem...

 Feb 10 00:38:15 PiScanner scanbd: /usr/local/sbin/scanbd: append string
 fujitsu:fi-4220C2dj:100742 to signal scan_end
 Feb 10 00:38:15 PiScanner scanbd: /usr/local/sbin/scanbd: now sending signal
 scan_end
 
 
 Is there a method allowing the second script to continue and process the
 pages scanned?
 
 
 
 --
 View this message in context: 
 http://sane.10972.n7.nabble.com/scanbd-Post-Processing-tp19426.html
 Sent from the SANE - Dev mailing list archive at Nabble.com.
 


-- 
Wilhelm
w.me...@unix.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] scanbd Post Processing

[Wilhelm]

Am 11.02.2015 um 03:19 schrieb ylafont:
 Yes, 
 
 the last line of the script, calls a script to process the scans,  

You are source-ing the premove.sh.
What happens if you start it by hand? But the problem then isn't related
to scanbd, seems to be bash related.

 
 The complete scan.sh.  is as follows. 
 
 logger -t scanbd: $0 Begin of $SCANBD_ACTION for device $SCANBD_DEVICE
 
 # printout all env-variables
 /usr/bin/printenv  /tmp/scanbd.env
 
 CurrentDir=$(pwd) #Script 
 Starting Directory
 scandir=/home/pi/PiScans#Scanning 
 Directory
 tmpdir=Scan-$RANDOM   #Script 
 temporary Directory of processing.
 
 mkdir $scandir/$tmpdir
 cd $scandir/$tmpdir
 
 if  [ $SCANBD_FUNCTION -eq 2 ]; then
 #if [ $SCANBD_ACTION -eq paperload ]  [ $SCANBD_FUNCTION -eq 2 ]; then
   logger -t scanbd: $0 * Now Scanning on device 
 $SCANBD_DEVICE
 ***
   #scanimage -d net:localhost:fujitsu:fi-4220C2dj:100742 -y 279.4 -x 215.9
 --batch --format=tiff --mode Lineart --resolution 300 --source=ADF Duplex
   scanimage -d $SCANBD_DEVICE -y 279.4 -x 215.9 --batch --format=tiff 
 --mode
 Lineart --resolution 300 --source=ADF Duplex
   logger -t scanbd: $0 * Scanning ended on device
 $SCANBD_DEVICE ***
 fi
 
 . ./premove.sh
 
 logger -t scanbd: $0 End   of $SCANBD_ACTION for device $SCANBD_DEVICE
 ___
 
 
 I had also address the error - but the second script which is in the same
 location as scan.sh does not execute.
 
 Feb 11 02:19:18 PiScanner scanbd: /usr/local/etc/scanbd/scan.sh: Begin of
 scan for device fujitsu:fi-4220C2dj:100742
 Feb 11 02:19:18 PiScanner scanbd: /usr/local/etc/scanbd/scan.sh:
 * Now Scanning on device fujitsu:fi-4220C2dj:100742
 ***
 Feb 11 02:19:19 PiScanner scanbd: /usr/local/sbin/scanbd: Iteration on dbus
 call
 Feb 11 02:19:20 PiScanner scanbd: /usr/local/sbin/scanbd: Iteration on dbus
 call
 Feb 11 02:19:21 PiScanner scanbd: /usr/local/sbin/scanbd: Iteration on dbus
 call
 Feb 11 02:19:22 PiScanner scanbd: /usr/local/sbin/scanbd: Iteration on dbus
 call
 Feb 11 02:19:23 PiScanner scanbd: /usr/local/sbin/scanbd: Iteration on dbus
 call
 Feb 11 02:19:24 PiScanner scanbd: /usr/local/sbin/scanbd: Iteration on dbus
 call
 Feb 11 02:19:25 PiScanner scanbd: /usr/local/sbin/scanbd: Iteration on dbus
 call
 Feb 11 02:19:26 PiScanner scanbd: /usr/local/sbin/scanbd: Iteration on dbus
 call
 Feb 11 02:19:27 PiScanner scanbd: /usr/local/sbin/scanbd: Iteration on dbus
 call
 Feb 11 02:19:27 PiScanner scanbd: /usr/local/etc/scanbd/scan.sh:
 * Scanning ended on device fujitsu:fi-4220C2dj:100742
 ***
 Feb 11 02:19:27 PiScanner scanbd: /usr/local/etc/scanbd/scan.sh: This this
 End  ***  of scan for device fujitsu:fi-4220C2dj:100742
 Feb 11 02:19:27 PiScanner scanbd: /usr/local/sbin/scanbd: child
 /usr/local/etc/scanbd/scan.sh exited with status: 0
 Feb 11 02:19:27 PiScanner scanbd: /usr/local/sbin/scanbd: append string
 fujitsu:fi-4220C2dj:100742 to signal scan_end
 
 
 
 
 
 --
 View this message in context: 
 http://sane.10972.n7.nabble.com/scanbd-Post-Processing-tp19426p19430.html
 Sent from the SANE - Dev mailing list archive at Nabble.com.
 


-- 
Wilhelm
w.me...@unix.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

[sane-devel] scanbd Post Processing

[ylafont]

Forgive me if this  not the correct section  for this.

I wanted to start a bash script to process the completed scans. I created a
link to Scan.sh from test.script

test.script - scan.sh

A section of scan.sh contains the following when scanning via the ADF

if [ $SCANBD_ACTION -eq paperload ]  [ $SCANBD_FUNCTION -eq 2 ]; then

logger -t scanbd: $0 * Now Scanning on device $SCANBD_DEVICE
***
scanimage -d $SCANBD_DEVICE -y 279.4 -x 215.9 --batch --format=tiff --mode
Lineart --resolution 300 --source=ADF Duplex

logger -t scanbd: $0 * Scanning ended on device
$SCANBD_DEVICE ***
fi

logger -t scanbd: $0 End of $SCANBD_ACTION for device $SCANBD_DEVICE
Removing blank pages and cleaning all others.
logger -t scanbd: $0  Starting Page Removal Process **

*. ./premove.sh*   - Post processing script

After the scanner completes the scan the script is terminated and does not
allow processing to continue.
Feb 10 00:38:14 PiScanner scanbd: /usr/local/etc/scanbd/scan.sh: 
Scanning ended on device fujitsu:fi-4220C2dj:100742 **
Feb 10 00:38:14 PiScanner scanbd: /usr/local/etc/scanbd/scan.sh: End of scan
for device fujitsu:fi-4220C2dj:100742
Feb 10 00:38:14 PiScanner scanbd: /usr/local/sbin/scanbd: child
/usr/local/etc/scanbd/scan.sh exited with status: 1
Feb 10 00:38:15 PiScanner scanbd: /usr/local/sbin/scanbd: append string
fujitsu:fi-4220C2dj:100742 to signal scan_end
Feb 10 00:38:15 PiScanner scanbd: /usr/local/sbin/scanbd: now sending signal
scan_end


Is there a method allowing the second script to continue and process the
pages scanned?



--
View this message in context: 
http://sane.10972.n7.nabble.com/scanbd-Post-Processing-tp19426.html
Sent from the SANE - Dev mailing list archive at Nabble.com.

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

Re: [sane-devel] scanbd: Can't get the scbtn device list

[Alexander Tomisch]

Hi Wilhelm,

Am 29.12.2014 um 06:32 schrieb Wilhelm:

Hi Alex,

Am 28.12.2014 um 21:08 schrieb Alexander Tomisch:

Hello,

I tried to install scanbd on a Arch Linux X64 but it did not recognize
my Scanner - output of scanbd: Can't get the scbtn device list.

It is not my first time with scanbd and on my previous installations it
was already working with my scanner and the scanbuttond epson backend.


do you really need the scanbuttond backend? These backends are included
into scanbd as is, because they aren't actively maintained.



The scanner is also not recognized without the old backends and I did 
not found any information, that sane can read the scanner buttons.



It has been a while since I started with scanbd and this scanner (2011 / 
2012 ?) but I used the scanbuttond backend from the beginning.



I will try to find out, which was the last working version.


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

[sane-devel] scanbd: Can't get the scbtn device list

[Alexander Tomisch]

Hello,

I tried to install scanbd on a Arch Linux X64 but it did not recognize 
my Scanner - output of scanbd: Can't get the scbtn device list.


It is not my first time with scanbd and on my previous installations it 
was already working with my scanner and the scanbuttond epson backend.



I first installed scanbd from AUR (1.4.0) and then i tried the latest 
(1.4.1) from sourceforge - same problem.



Scanning with sane is working, also through the running scanbd-service.


Output of lsusb:

Bus 001 Device 049: ID 04b8:010c Seiko Epson Corp. GT-6700U [Perfection 640]


Output of scanbd, it runs as root for testing:

/usr/bin/scanbd -d7 -f -c /etc/scanbd/scanbd.conf
##

/usr/bin/scanbd: foreground
/usr/bin/scanbd: config-file: /etc/scanbd/scanbd.conf
/usr/bin/scanbd: reading config file /etc/scanbd/scanbd.conf
/usr/bin/scanbd: debug on: level: 7
/usr/bin/scanbd: dropping privs to uid root
/usr/bin/scanbd: dropping privs to gid scanner
/usr/bin/scanbd: group scanner has member:
/usr/bin/scanbd: alex
/usr/bin/scanbd: drop privileges to gid: 96
/usr/bin/scanbd: Running as effective gid 96
/usr/bin/scanbd: drop privileges to uid: 0
/usr/bin/scanbd: Running as effective uid 0
/usr/bin/scanbd: dbus_init
/usr/bin/scanbd: dbus match 
type='signal',interface='org.freedesktop.Hal.Manager'

/usr/bin/scanbd: Loading /usr/lib/scanbd/scanbuttond/backends/meta.so
/usr/bin/scanbd: meta-backend: init
/usr/bin/scanbd: libusbi: initializing...
/usr/bin/scanbd: Loading /usr/lib/scanbd/scanbuttond/backends/epson.so
/usr/bin/scanbd: meta-backend: attaching backend: Epson USB
/usr/bin/scanbd: epson-backend: init
/usr/bin/scanbd: Scanning for local-only devices
/usr/bin/scanbd: Can't get the scbtn device list
/usr/bin/scanbd: device list null
/usr/bin/scanbd: start_scbtn_threads
/usr/bin/scanbd: start the threads (0)
/usr/bin/scanbd: start dbus thread
/usr/bin/scanbd: Not Primary Owner (-1)
/usr/bin/scanbd: Name Error (Connection :1.110 is not allowed to own 
the service de.kmux.scanbd.server due to security policies in the 
configuration file)

/usr/bin/scanbd: udev init
/usr/bin/scanbd: get udev monitor
/usr/bin/scanbd: udev fd is non-blocking, now setting to blocking mode
/usr/bin/scanbd: start udev thread
/usr/bin/scanbd: udev thread started
^C/usr/bin/scanbd: sig_term/int_handler called with signal 2
/usr/bin/scanbd: stop_scbtn_threads
/usr/bin/scanbd: waiting ...
/usr/bin/scanbd: stop dbus thread
/usr/bin/scanbd: stop udev thread
/usr/bin/scanbd: join udev thread
/usr/bin/scanbd: cleanup device handler
/usr/bin/scanbd: close udev monitor
/usr/bin/scanbd: close udev
/usr/bin/scanbd: exiting scanbd

##

Any hints?

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] scanbd: Can't get the scbtn device list

[Wilhelm]

Hi Alex,

Am 28.12.2014 um 21:08 schrieb Alexander Tomisch:
 Hello,
 
 I tried to install scanbd on a Arch Linux X64 but it did not recognize
 my Scanner - output of scanbd: Can't get the scbtn device list.
 
 It is not my first time with scanbd and on my previous installations it
 was already working with my scanner and the scanbuttond epson backend.

do you really need the scanbuttond backend? These backends are included
into scanbd as is, because they aren't actively maintained.

 
 I first installed scanbd from AUR (1.4.0) and then i tried the latest
 (1.4.1) from sourceforge - same problem.
 
 
 Scanning with sane is working, also through the running scanbd-service.

This indicates, that libsane is working correctly!

 
 
 Output of lsusb:
 
 Bus 001 Device 049: ID 04b8:010c Seiko Epson Corp. GT-6700U [Perfection
 640]

Unfortunately I don't have access to this type of scanner ...

 
 
 Output of scanbd, it runs as root for testing:
 
 /usr/bin/scanbd -d7 -f -c /etc/scanbd/scanbd.conf
 ##
 
 /usr/bin/scanbd: foreground
 /usr/bin/scanbd: config-file: /etc/scanbd/scanbd.conf
 /usr/bin/scanbd: reading config file /etc/scanbd/scanbd.conf
 /usr/bin/scanbd: debug on: level: 7
 /usr/bin/scanbd: dropping privs to uid root
 /usr/bin/scanbd: dropping privs to gid scanner
 /usr/bin/scanbd: group scanner has member:
 /usr/bin/scanbd: alex
 /usr/bin/scanbd: drop privileges to gid: 96
 /usr/bin/scanbd: Running as effective gid 96
 /usr/bin/scanbd: drop privileges to uid: 0
 /usr/bin/scanbd: Running as effective uid 0
 /usr/bin/scanbd: dbus_init
 /usr/bin/scanbd: dbus match
 type='signal',interface='org.freedesktop.Hal.Manager'
 /usr/bin/scanbd: Loading /usr/lib/scanbd/scanbuttond/backends/meta.so
 /usr/bin/scanbd: meta-backend: init
 /usr/bin/scanbd: libusbi: initializing...
 /usr/bin/scanbd: Loading /usr/lib/scanbd/scanbuttond/backends/epson.so
 /usr/bin/scanbd: meta-backend: attaching backend: Epson USB
 /usr/bin/scanbd: epson-backend: init
 /usr/bin/scanbd: Scanning for local-only devices
 /usr/bin/scanbd: Can't get the scbtn device list
 /usr/bin/scanbd: device list null
 /usr/bin/scanbd: start_scbtn_threads
 /usr/bin/scanbd: start the threads (0)
 /usr/bin/scanbd: start dbus thread
 /usr/bin/scanbd: Not Primary Owner (-1)
 /usr/bin/scanbd: Name Error (Connection :1.110 is not allowed to own
 the service de.kmux.scanbd.server due to security policies in the
 configuration file)
 /usr/bin/scanbd: udev init
 /usr/bin/scanbd: get udev monitor
 /usr/bin/scanbd: udev fd is non-blocking, now setting to blocking mode
 /usr/bin/scanbd: start udev thread
 /usr/bin/scanbd: udev thread started
 ^C/usr/bin/scanbd: sig_term/int_handler called with signal 2
 /usr/bin/scanbd: stop_scbtn_threads
 /usr/bin/scanbd: waiting ...
 /usr/bin/scanbd: stop dbus thread
 /usr/bin/scanbd: stop udev thread
 /usr/bin/scanbd: join udev thread
 /usr/bin/scanbd: cleanup device handler
 /usr/bin/scanbd: close udev monitor
 /usr/bin/scanbd: close udev
 /usr/bin/scanbd: exiting scanbd
 
 ##
 
 Any hints?
 
 Alex
 


-- 
Wilhelm
w.me...@unix.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

[sane-devel] scanbd with canon

[Franz Fuder]

All,
just updated my system to suse 13.2 wiht 13.1 all was fine.

Compiled the scanbd 1.4.1 all fine with usb_enabled. In the foreground.
The scan is working fine. After the scanadf is finished I got a
segemtation fault from scanbd. It looks like that the usb system has a
problem and the device can not opened again. When I start scanbd after
the segemntatio fault it scans fine but the fault comes again.

I compiled and using the latest sane-backend from today. All programms
that I tested are working fine.

Any help for me in this group? Here is the output of scanbd

Cheers

Franz

scanbd  -f -c /etc/scanbd/scanbd.conf

/usr/sbin/scanbd: polling device canon_dr:libusb:003:004
/usr/sbin/scanbd: get_sane_option_value
/usr/sbin/scanbd: checking option start number 32 (0) for device
canon_dr:libusb:003:004: value: 0
/usr/sbin/scanbd: value trigger: numerical
/usr/sbin/scanbd: trigger action for start for device
canon_dr:libusb:003:004 with script scanadf.script
/usr/sbin/scanbd: get_sane_option_value
/usr/sbin/scanbd: Value of mode as string (len 4, hash 2089152600): Gray
/usr/sbin/scanbd: setting env: SCANBD_FUNCTION_MODE=Gray
/usr/sbin/scanbd: setting env:
PATH=/home/lxuser/bin:/usr/local/bin:/usr/bin:/sbin:/usr/sbin:/bin:/usr/bin/X11:/usr/games:/home/lxuser/software/gwt-linux-1.5.3
/usr/sbin/scanbd: setting env: PWD=/etc/scanbd
/usr/sbin/scanbd: setting env: USER=lxuser
/usr/sbin/scanbd: setting env: HOME=/root
/usr/sbin/scanbd: setting env: canon_dr=canon_dr:libusb:003:004
/usr/sbin/scanbd: setting env: scan=scan
/usr/sbin/scanbd: append string canon_dr:libusb:003:004 to signal scan_begin
/usr/sbin/scanbd: now sending signal scan_begin
/usr/sbin/scanbd: append string SCANBD_FUNCTION_MODE=Gray to signal trigger
/usr/sbin/scanbd: append string
PATH=/home/lxuser/bin:/usr/local/bin:/usr/bin:/sbin:/usr/sbin:/bin:/usr/bin/X11:/usr/games:/home/lxuser/software/gwt-linux-1.5.3
to signal trigger
/usr/sbin/scanbd: append string PWD=/etc/scanbd to signal trigger
/usr/sbin/scanbd: append string USER=lxuser to signal trigger
/usr/sbin/scanbd: append string HOME=/root to signal trigger
/usr/sbin/scanbd: append string canon_dr=canon_dr:libusb:003:004 to
signal trigger
/usr/sbin/scanbd: append string scan=scan to signal trigger
/usr/sbin/scanbd: now sending signal trigger
/usr/sbin/scanbd: now flushing the dbus
/usr/sbin/scanbd: unref the signal
/usr/sbin/scanbd: using relative script path: scanadf.script, expanded
to: /etc/scanbd/scanadf.script
/usr/sbin/scanbd: waiting for child: /etc/scanbd/scanadf.script
/usr/sbin/scanbd: exec for /etc/scanbd/scanadf.script
/usr/sbin/scanbd: Iteration on dbus call
scanadf: rounded value of page-height from 297 to 296.994
scanadf: rounded value of br-x from 215.872 to 215.872
scanadf: rounded value of br-y from 297 to 296.994
scanadf: scanning image of size 5100x7016 pixels at 24 bits/pixel
scanadf: acquiring RGB frame
/usr/sbin/scanbd: Iteration on dbus call
/usr/sbin/scanbd: Iteration on dbus call
/usr/sbin/scanbd: Iteration on dbus call
/usr/sbin/scanbd: Iteration on dbus call
scanadf: min/max graylevel value = 48/254
Scanned document /tmp/scanadf/image-0001.pgm
scanadf: scanning image of size 5100x7016 pixels at 24 bits/pixel
scanadf: acquiring RGB frame
/usr/sbin/scanbd: Iteration on dbus call
scanadf: min/max graylevel value = 5/254
Scanned document /tmp/scanadf/image-0002.pgm
scanadf: scanning image of size 5100x7016 pixels at 24 bits/pixel
scanadf: acquiring RGB frame
scanadf: min/max graylevel value = 255/0
scanadf: sane_read: Document feeder out of documents
Scanned 2 pages
pnmtotiff: computing colormap...
pnmtotiff: Too many colors - proceeding to write a 24-bit RGB file.
pnmtotiff: If you want an 8-bit palette file, try doing a 'pnmquant 256'.
pnmtotiff: computing colormap...
pnmtotiff: Too many colors - proceeding to write a 24-bit RGB file.
pnmtotiff: If you want an 8-bit palette file, try doing a 'pnmquant 256'.
pnmtotiff: computing colormap...
pnmtotiff: End of file encountered when trying to read a row from input
file.
/usr/sbin/scanbd: child /etc/scanbd/scanadf.script exited with status: 0
/usr/sbin/scanbd: Iteration on dbus call
/usr/sbin/scanbd: append string canon_dr:libusb:003:004 to signal scan_end
/usr/sbin/scanbd: now sending signal scan_end
/usr/sbin/scanbd: reopen device canon_dr:libusb:003:004
/usr/sbin/scanbd: Can't open device canon_dr:libusb:003:004, Error
during device I/O
/usr/sbin/scanbd: Iteration on dbus call
/usr/sbin/scanbd: polling thread for canon_dr:libusb:003:004
cancellation point
/usr/sbin/scanbd: polling device canon_dr:libusb:003:004
Speicherzugriffsfehler (segementation fault)


-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.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 occasionally ignores scanner button presses

[Milan Knížek]

Hallo Wilhelm,

Wilhelm píše v Pá 16. 05. 2014 v 14:08 +0200:
 Hi Milan,
 
 Am 16.05.2014 09:38, schrieb Milan Knížek:
  
  I have yet to confirm it by further testing, but it seems that I can
  trigger the stale status of the scanbd by repeatedly pressing the
  scanner button (e.g. the PDF merge button, which does not really scan
  anything) in a quick sequence.
  

Well, it seems I can reproduce it reliably by repeatedly pressing a
button on my CanoScan 9000F before the child (action) process exits. I
do not have access to another scanner to test if this is a common
behaviour or not.
  
  Is there any SIGNAL I could send to scanbd process to refresh itself
  without the need to restart scanbd.service?
 
 Try to send SIGUSR1 to stop all polling and then SIGUSR2 to restart all
 polling.

The signals were caught by the process and it responded as described,
however, it did not resolve the bug.

I will report this behaviour in the Discussion forum of
Sourceforge.net / scanbd so that it does not get lost.

regards,
Milan


-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.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] scanbd occasionally ignores scanner button presses

[Milan Knížek]

Hello devs!

I have setup scanbd to poll CanoScan 9000F button presses (Arch Linux,
x86_64, sane-git from 2013-07-08, scanbd 1.3.1), scanbd.service and
scanbm.socket are run through systemd unit files.

It usually works just fine, but randomly scanbd completely ignores the
button presses - usually, it does not even help to switch the scanner
off/on. The only reliable solution so far is to restart the
scanbd.service.

I increased the debug level to 3 and watched syslog for messages when
scanbd operates normally and when it ignores the presses. I could not
find anything unusual in the messages. Scanbd continues to send lot of
repeated messages (like in normal state), but pressing a button does not
log any messages anymore.

I have yet to confirm it by further testing, but it seems that I can
trigger the stale status of the scanbd by repeatedly pressing the
scanner button (e.g. the PDF merge button, which does not really scan
anything) in a quick sequence.

Is this a known behaviour? How can I debug it further?

Is there any SIGNAL I could send to scanbd process to refresh itself
without the need to restart scanbd.service?

At the moment, I implemented a workaround by killing (SIGKILL) the
scanbd process every time the button is pressed and restarting
scanbd.service (at the end of the action script).

regards,
Milan

-- 
http://milan-knizek.net/
About linux and photography (Czech only)
O linuxu a fotografování




-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.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] scanbd with MX925

[Thomas Escher]

Dear all,

I've read that editing of inetd.conf or xinetd.conf is not need anymore since 
1.3.1.
Is this right
That means ./configure --prefix/usr --sysconfdir=/etc --localstatedir=/var is 
anything to do?

Thank you,

Tom
-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20140507/348ea84c/attachment.html

[sane-devel] scanbd Epson Perfection V37

[alar...@gmail.com]

Trying to do a scan by pressing a button on the scanner.
Button works in the program Image Scan! For Linux. But I can not get 
it to work with scanbd.

root at scaner:/# scanimage -L
device `epkowa:interpreter:001:010' is a Epson Perfection V37 flatbed 
scanner

This command does not expect to press a button on the scanner, but 
begins to continuously execute the script, which is written first in the 
file scanbd.conf.:

root at scaner:/# /usr/local/sbin/scanbd -d -f -c 
/usr/local/etc/scanbd/scanbd.conf
/usr/local/sbin/scanbd: debug on: level: 4
/usr/local/sbin/scanbd: dropping privs to uid root
/usr/local/sbin/scanbd: dropping privs to gid root
/usr/local/sbin/scanbd: drop privileges to gid: 0
/usr/local/sbin/scanbd: Running as effective gid 0
/usr/local/sbin/scanbd: drop privileges to uid: 0
/usr/local/sbin/scanbd: Running as effective uid 0
/usr/local/sbin/scanbd: dbus_init
/usr/local/sbin/scanbd: dbus match 
type='signal',interface='org.freedesktop.Hal.Manager'
/usr/local/sbin/scanbd: sane version 1.0
/usr/local/sbin/scanbd: Scanning for local-only devices
/usr/local/sbin/scanbd: found device: epkowa:interpreter:001:010 Epson 
Perfection V37 flatbed scanner
/usr/local/sbin/scanbd: start_sane_threads
/usr/local/sbin/scanbd: Starting poll thread for epkowa:interpreter:001:010
/usr/local/sbin/scanbd: Thread started for device epkowa:interpreter:001:010
/usr/local/sbin/scanbd: start dbus thread
/usr/local/sbin/scanbd: Not Primary Owner (-1)
/usr/local/sbin/scanbd: Name Error (Connection :1.107 is not allowed 
to own the service de.kmux.scanbd.server due to security policies in 
the configuration file)
/usr/local/sbin/scanbd: udev init
/usr/local/sbin/scanbd: sane_poll
/usr/local/sbin/scanbd: get udev monitor
/usr/local/sbin/scanbd: start udev thread
/usr/local/sbin/scanbd: udev thread started
/usr/local/sbin/scanbd: found 67 options for device 
epkowa:interpreter:001:010
/usr/local/sbin/scanbd: sane_find_matching_options
/usr/local/sbin/scanbd: found 5 actions in section (null)
/usr/local/sbin/scanbd: checking action scan with filter: ^scan.*
/usr/local/sbin/scanbd: found active option[2] mode (type: 3) for device 
epkowa:interpreter:001:010
/usr/local/sbin/scanbd: found active option[3] depth (type: 1) for 
device epkowa:interpreter:001:010
.
.
What is wrong?

[sane-devel] scanbd with HP8250 (avision)

[Wilhelm]

Hi James,

Am 08.11.2013 18:17, schrieb James Klaas:

...

 and enumerates the options repeatedly until I hit a button on the
 scanner, at which point it goes back to only showing the above
 Iteration on dbus call messages. I posted my log at
 http://pastebin.com/XbHawE9c.

looks good as your scanner seems to be recognized via libsane. Now you
have to figure out which button maps to which option: watch the logfile
while you are pressing the buttons. Then you can modify the example
scripts to get useful actions to be done.

-- 
Wilhelm
w.meier at unix.net

[sane-devel] scanbd with HP8250 (avision)

[James Klaas]

I spent some time last night trying to get scanbd running on my Ubuntu
12.03 system. I got 1.3.1 and after figuring out the dependencies, I got it
compiled and installed. I followed a post here
http://thehomeserverhandbook.com/category/hardware/scanner/ and modified
what I thought I needed to for my scanner.

On my system, the scanner owner and group is set to saned and I set the
udev rules to reflect that using 99-saned.rules found in the integration
directory. I preferred to have the daemon running separately, rather than
from xinetd, so I used the startup script.

I made sure that all the following files were set up as directed:

/etc/sane.d/dll.conf
/etc/sane.d/net.conf
/usr/local/etc/scanbd/dll.conf

I copied /etc/sane.d/saned.conf to /usr/local/etc/scanbd/saned.conf. and
commented out the access list in /etc/sane.d/saned.conf.

I can't tell if it's working or not.

If I don't restart the scanner between using saned and getting scanbd
running, I only get these messages in syslog (or on the screen if I run it
in the foreground):

localhost scanbd: /usr/local/sbin/scanbd: Iteration on dbus call

If I do restart my scanner, it will go through a different set of messages:

localhost scanbd: /usr/local/sbin/scanbd: found 34 options for device
avision:libusb:002:003

and enumerates the options repeatedly until I hit a button on the scanner,
at which point it goes back to only showing the above Iteration on dbus
call messages. I posted my log at http://pastebin.com/XbHawE9c.

Can anyone give me any pointers or things to try? I've looked at other
peoples posted logs and only see some similarities to what I get.

James
-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20131108/9bd8a25f/attachment.html

[sane-devel] scanbd daemon does not load firmware

[Wilhelm]

Hi Ilya,

Am 20.09.2013 06:36, schrieb Ilya V. Ivanchenko:
 Wilhelm,
 Here's a patch that implements device insertion/removal hooks. I've
 tested it with scanbuttond backend and it solves the problem of firmware
 not being loaded to the scanner.

thanks again. Just added the patches!

 --
 Ilya
 
 
 *From:* Wilhelm wilhelm.meier at fh-kl.de
 *To:* Ilya V. Ivanchenko iva2k at yahoo.com
 *Cc:* w.meier at unix.net w.meier at unix.net;
 sane-devel at lists.alioth.debian.org sane-devel at 
 lists.alioth.debian.org
 *Sent:* Friday, August 30, 2013 10:29 PM
 *Subject:* Re: scanbd daemon does not load firmware
 
 Am 31.08.2013 02:28, schrieb Ilya V. Ivanchenko:
 Thanks, that clarifies the situation and also explains what you meant by
 the callback. This external hook should be given in configuration file,
 like in /etc/scanbd/scanbd.conf. Do you have a name you'd like for that
 option?
 
 Well, could imagine prepare_script as an option name for the
 scriptname. It's value should be an absolute path name or a relative
 pathname, where the same rules apply as for all scripts (see scriptdir
 option). And I would to pass it at most the same env vars the action
 scripts receive. And additionally an env variable called WHEN (or make
 it configurable) with the values inserted or removed or thelike.
 
 I'm looking forward to your contribution!
 Thanks!
 -- 
 Wilhelm
 w.meier at unix.net mailto:w.meier at unix.net
 
 
 
 


-- 
Wilhelm
w.meier at unix.net

[sane-devel] scanbd daemon does not load firmware

[Ilya V. Ivanchenko]

Wilhelm,
Great, thanks!
---
Ilya

 Here's a patch that implements device insertion/removal hooks. I've
 tested it with scanbuttond backend and it solves the problem of firmware
 not being loaded to the scanner.

thanks again. Just added the patches!
-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130923/3f482085/attachment.html

[sane-devel] scanbd daemon does not load firmware

[Wilhelm]

Hi Ilya,

Am 20.09.2013 06:36, schrieb Ilya V. Ivanchenko:
 Wilhelm,
 Here's a patch that implements device insertion/removal hooks. I've
 tested it with scanbuttond backend and it solves the problem of firmware
 not being loaded to the scanner.

thank you for your patch! Looks very good. I will integrate that in the
next few days, please be a little patient because I have a very tight
time budget this weekend.

Thanks!
Wilhelm

 --
 Ilya
 
 
 *From:* Wilhelm wilhelm.meier at fh-kl.de
 *To:* Ilya V. Ivanchenko iva2k at yahoo.com
 *Cc:* w.meier at unix.net w.meier at unix.net;
 sane-devel at lists.alioth.debian.org sane-devel at 
 lists.alioth.debian.org
 *Sent:* Friday, August 30, 2013 10:29 PM
 *Subject:* Re: scanbd daemon does not load firmware
 
 Am 31.08.2013 02:28, schrieb Ilya V. Ivanchenko:
 Thanks, that clarifies the situation and also explains what you meant by
 the callback. This external hook should be given in configuration file,
 like in /etc/scanbd/scanbd.conf. Do you have a name you'd like for that
 option?
 
 Well, could imagine prepare_script as an option name for the
 scriptname. It's value should be an absolute path name or a relative
 pathname, where the same rules apply as for all scripts (see scriptdir
 option). And I would to pass it at most the same env vars the action
 scripts receive. And additionally an env variable called WHEN (or make
 it configurable) with the values inserted or removed or thelike.
 
 I'm looking forward to your contribution!
 Thanks!
 -- 
 Wilhelm
 w.meier at unix.net mailto:w.meier at unix.net
 
 
 
 


-- 
Wilhelm
w.meier at unix.net

[sane-devel] scanbd with sane backend - howto read buttons?

[m. allan noah]

Button support is entirely dependent on which sane backend is in use.
Not all backends support buttons, even if they are on the scanner.

allan

On Fri, Sep 20, 2013 at 1:35 AM, Ilya V. Ivanchenko iva2k at yahoo.com wrote:
 Is there a way to query button states in command line from sane or scanbd
 with sane backend?

 I want to see that I can read buttons first, then attempt again to configure
 scanbd with sane backend. So far I failed to get any response to buttons via
 sane backend.

 I checked scanimage -h | grep button, and it reports only
 --wait-for-button (which is just to pause the scan until user presses a
 button on the scanner).

 The only hint I've got is scanimage -A | grep button which returns
 --monitor-button[=(yes|no)] [no] [read-only].

 Both manpage and scanimage --help are mum on the topic. Google is of no help
 either.

 --
 Ilya

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



-- 
The truth is an offense, but not a sin

[sane-devel] scanbd with sane backend - howto read buttons?

[Ilya V. Ivanchenko]

That probably means that my scanner's sane backend does not support buttons 
(its epkowa, Epson GT-1500). However scanbuttond supports it (with a patch to 
backends/epson_vphoto.c).

How one would port buttons support from scanbuttond to sane backend? I may have 
enough spare time to roll a patch, but not enough to dig out all inner workings 
of both scanbuttonbd and sane.

--
Ilya



 From: m. allan noah kitno455 at gmail.com
To: Ilya V. Ivanchenko iva2k at yahoo.com 
Cc: sane-devel at lists.alioth.debian.org sane-devel at 
lists.alioth.debian.org 
Sent: Friday, September 20, 2013 4:20 AM
Subject: Re: [sane-devel] scanbd with sane backend - howto read buttons?
 

Button support is entirely dependent on which sane backend is in use.
Not all backends support buttons, even if they are on the scanner.

allan

On Fri, Sep 20, 2013 at 1:35 AM, Ilya V. Ivanchenko iva2k at yahoo.com wrote:
 Is there a way to query button states in command line from sane or scanbd
 with sane backend?

 I want to see that I can read buttons first, then attempt again to configure
 scanbd with sane backend. So far I failed to get any response to buttons via
 sane backend.

 I checked scanimage -h | grep button, and it reports only
 --wait-for-button (which is just to pause the scan until user presses a
 button on the scanner).

 The only hint I've got is scanimage -A | grep button which returns
 --monitor-button[=(yes|no)] [no] [read-only].

 Both manpage and scanimage --help are mum on the topic. Google is of no help
 either.

 --
 Ilya

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



-- 
The truth is an offense, but not a sin
-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130920/26965797/attachment.html

[sane-devel] scanbd daemon does not load firmware

[Ilya V. Ivanchenko]

Wilhelm,
Here's a patch that implements device insertion/removal hooks. I've tested it 
with scanbuttond backend and it solves the problem of firmware not being loaded 
to the scanner.
--
Ilya



 From: Wilhelm wilhelm.meier at fh-kl.de
To: Ilya V. Ivanchenko iva2k at yahoo.com 
Cc: w.meier at unix.net w.meier at unix.net; sane-devel at 
lists.alioth.debian.org sane-devel at lists.alioth.debian.org 
Sent: Friday, August 30, 2013 10:29 PM
Subject: Re: scanbd daemon does not load firmware
 

Am 31.08.2013 02:28, schrieb Ilya V. Ivanchenko:
 Thanks, that clarifies the situation and also explains what you meant by
 the callback. This external hook should be given in configuration file,
 like in /etc/scanbd/scanbd.conf. Do you have a name you'd like for that
 option?

Well, could imagine prepare_script as an option name for the 
scriptname. It's value should be an absolute path name or a relative 
pathname, where the same rules apply as for all scripts (see scriptdir 
option). And I would to pass it at most the same env vars the action 
scripts receive. And additionally an env variable called WHEN (or make 
it configurable) with the values inserted or removed or thelike.

I'm looking forward to your contribution!
Thanks!
-- 
Wilhelm
w.meier at unix.net
-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130919/430151fc/attachment.html
-- next part --
A non-text attachment was scrubbed...
Name: scanbd-hooks-iva2k-20130919.patch
Type: text/x-patch
Size: 10730 bytes
Desc: not available
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130919/430151fc/attachment.bin

[sane-devel] scanbd with sane backend - howto read buttons?

[Ilya V. Ivanchenko]

Is there a way to query button states in command line from sane or scanbd with 
sane backend?

I want to see that I can read buttons first, then attempt again to configure 
scanbd with sane backend. So far I failed to get any response to buttons via 
sane backend.

I checked scanimage -h | grep button, and it reports only --wait-for-button 
(which is just to pause the scan until user presses a button on the scanner).


The only hint I've got is?scanimage -A | grep button which returns 
--monitor-button[=(yes|no)] [no] [read-only].?

Both manpage and scanimage --help are mum on the topic.?Google is of no help 
either.

--
Ilya
-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130919/dd93e146/attachment.html

[sane-devel] scanbd daemon does not load firmware

[Wilhelm]

Am 30.08.2013 19:44, schrieb Ilya V. Ivanchenko:
 Hi Wilhelm,

 Thanks! I checked out the code from svn and found the markers without
 problems.

 It is first time I reviewed scanbd code, so I got few questions, maybe
 you can answer and save me some time.

I hope so ...


 It looks like the backend selection sane vs. scanbuttond is exclusive
 (compiled with #ifdef). What I gathered is in sane branch the calling
 sequence will be sane_init(), sane_get_devices(). I peeked into sanei
 code, and it seems it will call sane_open() from sane_get_devices().
 sane_open() does load firmware for the scanner if it is required (each
 sane backend has its own implementation). So my understanding is that
 scanbd with sane backend will load the firmware and have no problem. Is
 that correct?

yes!


 Now to the scanbuttonbd backend of scanbd. It looks like it won't call
 into sane backends as it has its own backends library. And scanbuttond
 backend has no code that loads firmware. As such, the bug of not loading
 the firmware is only happens with scanbuttond backend. Am I right?

yes!


 Now I have to select an appropriate fix for the firmware issue, and my
 #1 option is to call sane_get_devices(), even when using scanbuttond
 backend which now is exclusive from sane backend. Will that be a
 problem?

The scanbuttons backends exists only for old scanners / for historical 
reasons. So, the preferred way is to use sane-backends.

Because there are scanbuttond backends for scanners with no sane-backend 
I don't want to couple scanbuttond and sane together. Therefore I would 
suggest a generic solution to call an external programm / script in the 
case a device is inserted / removed. This external programm / script can 
then load the firmware by any means - even calling simply scanimage if 
sane is configured correctly.

One can aruge that using scanbd/scanbuttond for a scanner with no 
sane-support is sort of useless in case the buttons should trigger a 
scan-operation. But there might be other scan-applications than sane ...

 If it is, then I don't have an option #2... or better said it
 gets very complicated very quickly.

 --
 Ilya

 
 *From:* Wilhelm wilhelm.meier at fh-kl.de
 *To:* Ilya V. Ivanchenko iva2k at yahoo.com
 *Cc:* w.meier at unix.net w.meier at unix.net;
 sane-devel at lists.alioth.debian.org sane-devel at 
 lists.alioth.debian.org
 *Sent:* Thursday, August 29, 2013 12:33 PM
 *Subject:* Re: scanbd daemon does not load firmware

 Am 29.08.2013 16:03, schrieb Ilya V. Ivanchenko:
 2. When using scanbuttond-backends, fix loading firmware on USB
 insert.
  
   what I could imagine is to fix this problem with a special
   shell-callback, when scanbd detects a device inserion / removal.
  
  Forgot to say: would you like to write a patch for that? I will provide
  you with the neccessary info to do that. Shouldn't be too much work ;-)
  
   Not a problem. I'm a software/systems engineer, so I know what I (will
   be) doing. Only I have short window before I leave for a business trip.

 I just marked the code with four place to insert code to start such a
 callback:

 // TODO: call the device insertion / removal callback

 (if you use qtcreator you'll quickly find them)


 I'm looking forward to your patches ;-)

  
  2. When using scanbuttond-backends, fix loading firmware on
 USB insert.

what I could imagine is to fix this problem with a special
shell-callback, when scanbd detects a device inserion / removal.
   This is in the nutshell how I patched the problem from udev.
  
  yes, but you had to stop / restart the scanbd and that's more a
  workaround than a solution ...
  
   I agree.
  
   --
   Ilya


 --
 Wilhelm
 w.meier at unix.net mailto:w.meier at unix.net




-- 
Wilhelm
w.meier at unix.net

[sane-devel] scanbd daemon does not load firmware

[Ilya V. Ivanchenko]

Thanks, that clarifies the situation and also explains what you meant by the 
callback. This external hook should be given in configuration file, like in 
/etc/scanbd/scanbd.conf. Do you have a name you'd like for that option?

--
Ilya
-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130830/c0715150/attachment.html

[sane-devel] scanbd daemon does not load firmware

[Wilhelm]

Hi Ilya,

is there a special reason using the (old) scanbuttond-backends and not 
sane-backends?

If you plugin / poweron the scanner for the first time, who does the 
firmware get loaded in this case?

Am 29.08.2013 03:42, schrieb Ilya Ivanchenko:
 On Wed, 2013-08-28, Wilhelm wrote:
 Am 28.08.2013 07:11, schrieb Ilya V. Ivanchenko:
 I created a neat setup using xinet + scanbd service + scanbd daemon (for
 buttons) + sane (client) to use Epson GT-1500 (with ADF) as a workhorse
 of a network scanner, with scanner buttons hooked to various jobs.
 Everything is working great, except...

 I encountered a problem after the scanner is powered off and then on
 again. The buttons service (scanbd daemon) stops reading the buttons and
 keeps getting communication error in the syslog.

 that shouldn't happen. Normally, scanbd gets via udev | hal | dbus a
 device-removed event and then abandones the device until it gets plugged
 in again.

 Good to know that scanbd should manage firmware loading, it answers the
 questions I had. Now it seems we better dig to the root of the
 problem...


 So, please show the syslog from beginning of the scanbd log messages and
 in the situation when the device is removed.

 I've pasted syslog snippet with the problem when firmware is not loaded
 (with scanbd debug-level=7) here (device was removed on Aug 28 18:02:28,
 communication error happens on Aug 28 18:03:19):
 http://pastebin.com/BweSr5p2
 (it will expire in 1 month)


 And please: how did you configure / compile, which platform, ...

 Ubuntu 12.04LTS on Intel amd64, 1st installed sane and Epson's iscan:

 sudo apt-get install sane-utils
 sudo dpkg -i iscan-data_1.23.0-1_all.deb
 sudo dpkg -i iscan_2.29.1-5~usb0.1.ltdl7_amd64.deb
 sudo dpkg -i iscan-plugin-gt-1500_2.2.0-1_amd64.deb
 scanimage -L
 # works

 2nd downloaded scanbd (181-trunk)
 Prepared:
 sudo apt-get install build-essential checkinstall
 sudo apt-get install libconfuse-dev libsane-dev libudev-dev
 sudo apt-get install libconfuse-dev libusb-dev libudev-dev libdbus-1-dev
 dbus libsane-dev
 ## Sane option will only work if sane backend supports reading buttons
 from the scanner (use scanimage -A to check):
 # ./configure --prefix= --with-user=saned --with-group=scanner
 ## Use scanbuttond backend (embedded into scanbd):
 ./configure --prefix= --with-user=saned --with-group=scanner
 --enable-scanbuttond

 I patched 2 files:

 - src/scanbuttond/backends/epson_vphoto.c - added VID/PID 04B8/0133 for
 Epson GT-1500:
{ 0x04B8, 0x0133, 5 }   // Epson GT-1500, buttons: 1=scan, 2=copy,
 3=email, 4=pdf, 5=stop
...
{ Epson, GT-1500}

 - src/scanbd/scanbuttond_wrapper.c function scanbtnd_button_name()
 (upped the assert for button count =4 to =5 and renamed buttons per
 Epson line above)

 BTW - it would be nice if device definitions can name their own buttons
 instead of hard-coded values.That first list with VID/PID/count_buttons
 could contain an array of strings for that.

 Then I compiled:
 make
 sudo make install


 The system configuration involved some editing in /etc/, but I think it
 is not the issue here. Anyway let me know if you need any other
 information.

 Regards,

 --
 Ilya




-- 
Wilhelm
w.meier at unix.net

[sane-devel] scanbd daemon does not load firmware

[Ilya V. Ivanchenko]

Hi Wilhelm,

is there a special reason using the (old) scanbuttond-backends and not?

sane-backends?
I first tried sane-backends, and apparently it does not read the buttons for 
Epson GT-1500. I tried various things with sane-backends, but scanimage -A 
gives no button options and it was very unclear how to patch sane-backends or 
even where to start. So I quickly gave up and moved to scanbuttond-backends 
where it was easy to figure out a patch and it worked right away. I'd be glad 
if sane backend worked, but even Epson's iscan does not support buttons 
(seemingly on any of their scanners).

If you plugin / poweron the scanner for the first time, who does the 
firmware get loaded in this case?
Good question. Now retracing my steps backwards, I think I got iscan+sane to 
load the drivers the very first time and I did not notice this problem. When I 
tested things, I always used scanimage -L as a quick test, and it pulled the 
string up to the firmware loading (at which moment scanner clearly does a whizz 
sound moving the head in its POST). It appears to me that scanbd somehow misses 
calling the firmware load on USB insert (before reading buttons), but does it 
on scanimage -L. Perhaps it is due to the use of scanbuttond-backends and not 
sane-backends.

So my current conclusions are that there are two potential issues to fix:
?1. Make sane-backends support buttons that scanbuttond-backends support.
?2. When using scanbuttond-backends, fix loading firmware on USB insert.
Please correct me if I'm wrong here.

-- 
Wilhelm
w.meier at unix.net
-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130829/c1035439/attachment.html

[sane-devel] scanbd daemon does not load firmware

[Wilhelm]

Hi Ilja,

Am 29.08.2013 15:25, schrieb Ilya V. Ivanchenko:
 Hi Wilhelm,

 **is there a special reason using the (old) scanbuttond-backends and not
sane-backends?
 I first tried sane-backends, and apparently it does not read the buttons
 for Epson GT-1500.

did you use the epkowa backend? The sane-support-page says, that this 
backend supports most features of the GT-1500.

 I tried various things with sane-backends, but
 scanimage -A gives no button options and it was very unclear how to
 patch sane-backends or even where to start. So I quickly gave up and
 moved to scanbuttond-backends where it was easy to figure out a patch
 and it worked right away. I'd be glad if sane backend worked, but even
 Epson's iscan does not support buttons (seemingly on any of their scanners).

If you plugin / poweron the scanner for the first time, who does the
firmware get loaded in this case?
 Good question. Now retracing my steps backwards, I think I got
 iscan+sane to load the drivers the very first time and I did not notice
 this problem. When I tested things, I always used scanimage -L as a
 quick test, and it pulled the string up to the firmware loading (at
 which moment scanner clearly does a whizz sound moving the head in its
 POST). It appears to me that scanbd somehow misses calling the firmware
 load on USB insert (before reading buttons), but does it on scanimage
 -L. Perhaps it is due to the use of scanbuttond-backends and not
 sane-backends.

 So my current conclusions are that there are two potential issues to fix:
   1. Make sane-backends support buttons that scanbuttond-backends support.

that would be the best choice, since I have no real plans to support the 
scanbuttond backends.

   2. When using scanbuttond-backends, fix loading firmware on USB insert.

what I could imagine is to fix this problem with a special 
shell-callback, when scanbd detects a device inserion / removal.

 Please correct me if I'm wrong here.

 --
 Wilhelm
 w.meier at unix.net mailto:w.meier at unix.net




-- 
Wilhelm
w.meier at unix.net

[sane-devel] scanbd daemon does not load firmware

[Ilya V. Ivanchenko]

Hi Wilhelm,

 is there a special reason using the (old) scanbuttond-backends and not

sane-backends?
 I first tried sane-backends, and apparently it does not read the buttons
 for Epson GT-1500.

did you use the epkowa backend? The sane-support-page says, that this 
backend supports most features of the GT-1500.
Yes, epkowa is the backend used in the current configuration. I had problems of 
getting buttons to work with sane, but now retracing back it may be due to sane 
configuration needing epson2 (would not work with epkowa for some reason), and 
switching to scanbd needing epkowa (would not work with epson2).

I just tried scanimage -A again and found --monitor-button option there, 
but scanimage -h does not have button options (except --wait-for-button). Can 
you suggest what commands I should use to test the buttons from command line?

 So my current conclusions are that there are two potential issues to fix:
?  1. Make sane-backends support buttons that scanbuttond-backends support.

that would be the best choice, since I have no real plans to support the 
scanbuttond backends.
I guess I could try sane-backends again to see if I can make the buttons work 
with epkowa backend.

?  2. When using scanbuttond-backends, fix loading firmware on USB insert.

what I could imagine is to fix this problem with a special 
shell-callback, when scanbd detects a device inserion / removal.
This is in the nutshell how I patched the problem from udev.

--
Ilya
-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130829/780263cb/attachment.html

[sane-devel] scanbd daemon does not load firmware

[Wilhelm]

Am 29.08.2013 15:33, schrieb Wilhelm:
 Hi Ilja,

 Am 29.08.2013 15:25, schrieb Ilya V. Ivanchenko:
 Hi Wilhelm,

 **is there a special reason using the (old) scanbuttond-backends and not
 sane-backends?
 I first tried sane-backends, and apparently it does not read the buttons
 for Epson GT-1500.

 did you use the epkowa backend? The sane-support-page says, that this
 backend supports most features of the GT-1500.

 I tried various things with sane-backends, but
 scanimage -A gives no button options and it was very unclear how to
 patch sane-backends or even where to start. So I quickly gave up and
 moved to scanbuttond-backends where it was easy to figure out a patch
 and it worked right away. I'd be glad if sane backend worked, but even
 Epson's iscan does not support buttons (seemingly on any of their
 scanners).

 If you plugin / poweron the scanner for the first time, who does the
 firmware get loaded in this case?
 Good question. Now retracing my steps backwards, I think I got
 iscan+sane to load the drivers the very first time and I did not notice
 this problem. When I tested things, I always used scanimage -L as a
 quick test, and it pulled the string up to the firmware loading (at
 which moment scanner clearly does a whizz sound moving the head in its
 POST). It appears to me that scanbd somehow misses calling the firmware
 load on USB insert (before reading buttons), but does it on scanimage
 -L. Perhaps it is due to the use of scanbuttond-backends and not
 sane-backends.

 So my current conclusions are that there are two potential issues to fix:
   1. Make sane-backends support buttons that scanbuttond-backends
 support.

 that would be the best choice, since I have no real plans to support the
 scanbuttond backends.

   2. When using scanbuttond-backends, fix loading firmware on USB insert.

 what I could imagine is to fix this problem with a special
 shell-callback, when scanbd detects a device inserion / removal.

Forgot to say: would you like to write a patch for that? I will provide 
you with the neccessary info to do that. Shouldn't be too much work ;-)


 Please correct me if I'm wrong here.

 --
 Wilhelm
 w.meier at unix.net mailto:w.meier at unix.net






-- 
Wilhelm
w.meier at unix.net

[sane-devel] scanbd daemon does not load firmware

[Wilhelm]

Am 29.08.2013 15:52, schrieb Ilya V. Ivanchenko:
 Hi Wilhelm,

  is there a special reason using the (old) scanbuttond-backends and not
  sane-backends?
   I first tried sane-backends, and apparently it does not read the buttons
   for Epson GT-1500.
  
  did you use the epkowa backend? The sane-support-page says, that this
  backend supports most features of the GT-1500.
 Yes, epkowa is the backend used in the current configuration. I had
 problems of getting buttons to work with sane, but now retracing back it
 may be due to sane configuration needing epson2 (would not work with
 epkowa for some reason), and switching to scanbd needing epkowa (would
 not work with epson2).

 I just tried scanimage -A again and found --monitor-button option
 there, but scanimage -h does not have button options (except
 --wait-for-button). Can you suggest what commands I should use to test
 the buttons from command line?

   So my current conclusions are that there are two potential issues to
 fix:
1. Make sane-backends support buttons that scanbuttond-backends
 support.
  
  that would be the best choice, since I have no real plans to support the
  scanbuttond backends.
 I guess I could try sane-backends again to see if I can make the buttons
 work with epkowa backend.

2. When using scanbuttond-backends, fix loading firmware on USB insert.
  
  what I could imagine is to fix this problem with a special
  shell-callback, when scanbd detects a device inserion / removal.
 This is in the nutshell how I patched the problem from udev.

yes, but you had to stop / restart the scanbd and that's more a 
workaround than a solution ...


 --
 Ilya


-- 
Wilhelm
w.meier at unix.net

[sane-devel] scanbd daemon does not load firmware

[Ilya V. Ivanchenko]

?  2. When using scanbuttond-backends, fix loading firmware on USB insert.


 what I could imagine is to fix this problem with a special
 shell-callback, when scanbd detects a device inserion / removal.

Forgot to say: would you like to write a patch for that? I will provide 
you with the neccessary info to do that. Shouldn't be too much work ;-)


Not a problem. I'm a software/systems engineer, so I know what I (will be) 
doing. Only I have short window before I leave for a business trip.

? ? 2. When using scanbuttond-backends, fix loading firmware on USB insert.
? 
? what I could imagine is to fix this problem with a special
? shell-callback, when scanbd detects a device inserion / removal.
 This is in the nutshell how I patched the problem from udev.

yes, but you had to stop / restart the scanbd and that's more a?
workaround than a solution ...


I agree.

--
Ilya
-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130829/fbb4a285/attachment.html

[sane-devel] scanbd daemon does not load firmware

[Wilhelm]

Am 29.08.2013 16:03, schrieb Ilya V. Ivanchenko:
   2. When using scanbuttond-backends, fix loading firmware on USB insert.

 what I could imagine is to fix this problem with a special
 shell-callback, when scanbd detects a device inserion / removal.

Forgot to say: would you like to write a patch for that? I will provide
you with the neccessary info to do that. Shouldn't be too much work ;-)

 Not a problem. I'm a software/systems engineer, so I know what I (will
 be) doing. Only I have short window before I leave for a business trip.

I just marked the code with four place to insert code to start such a 
callback:

// TODO: call the device insertion / removal callback

(if you use qtcreator you'll quickly find them)


I'm looking forward to your patches ;-)


2. When using scanbuttond-backends, fix loading firmware on USB insert.
  
  what I could imagine is to fix this problem with a special
  shell-callback, when scanbd detects a device inserion / removal.
 This is in the nutshell how I patched the problem from udev.

yes, but you had to stop / restart the scanbd and that's more a
workaround than a solution ...

 I agree.

 --
 Ilya


-- 
Wilhelm
w.meier at unix.net

[sane-devel] scanbd daemon does not load firmware

[Wilhelm]

Hello,

Am 28.08.2013 07:11, schrieb Ilya V. Ivanchenko:
 I created a neat setup using xinet + scanbd service + scanbd daemon (for
 buttons) + sane (client) to use Epson GT-1500 (with ADF) as a workhorse
 of a network scanner, with scanner buttons hooked to various jobs.
 Everything is working great, except...

 I encountered a problem after the scanner is powered off and then on
 again. The buttons service (scanbd daemon) stops reading the buttons and
 keeps getting communication error in the syslog.

that shouldn't happen. Normally, scanbd gets via udev | hal | dbus a 
device-removed event and then abandones the device until it gets plugged 
in again.

So, please show the syslog from beginning of the scanbd log messages and 
in the situation when the device is removed.

And please: how did you configure / compile, which platform, ...

 I tried various things until it occurred to me that Epson GT-1500 uses
 iscan plugin that loads firmware file (/usr/share/iscan/esfw86.bin) and
 the power off-on resets the scanner and thus wipes out the firmware. It
 seems like scanbd daemon does not load the firmware when the scanner is
 powered back on (at least I was not able to find how to configure it to
 do so), and it gets into trouble trying to read the buttons from device
 without its firmware.

This seems to be a consequence of the above failure: the device isn't 
closed correctly and not reopened therefore. So the firmware isn't 
loaded again (should be done on device opening).


 I have few questions to scanbd team:

 1. Can scanbd daemon automatically load firmware file and what should be
 done in the config files to achieve that? sane config files seem to have
 firmware option, but I don't see anything in scanbd documentation.

as stated above: should be done on openeing the device


 2. If scanbd daemon currently cannot load the firmware, are there any
 plans to add this feature?

see above


 3. If not, what is the recommended way to set scanbd up so it will work
 with scanners that require firmware to be loaded?

see above


 I spent few hours and came up with the following rework using udev rule
 that invokes scanimage -L command to pull the command chain that loads
 the firmware. It works fine and I have not seen communication error since.

 A. Create a script that causes firmware to be loaded (I'm open to other
 methods, but scanimage -L is the only I found so far)
 sudo tee /etc/scanbd/scanner.d/on_insert.sh  /dev/null  CATEOF
 #! /bin/bash
 logger=/usr/bin/logger -t scanbd
 $logger Loading firmware for $1
 /usr/sbin/service scanbd stop 21 /dev/null
 /usr/bin/scanimage -L 21 | $logger
 /usr/sbin/service scanbd start 21 /dev/null
 $logger Done loading firmware for $1
 CATEOF
 sudo chmod a+x /etc/scanbd/scanner.d/on_insert.sh

 B. Create udev rule to call the above script.
 sudo tee /etc/udevd/rules.d/98-epson.rules  /dev/null  CATEOF
 # Force firmware load for EPSON GT-1500
 ACTION==add, ENV{DEVTYPE}==usb_device, ATTRS{idVendor}==04b8,
 ATTRS{idProduct}==0133, RUN+=/etc/scanbd/scanner.d/on_insert.sh %p
 CATEOF





-- 
Wilhelm
w.meier at unix.net

[sane-devel] scanbd daemon does not load firmware

[Ilya Ivanchenko]

On Wed, 2013-08-28, Wilhelm wrote:
 Am 28.08.2013 07:11, schrieb Ilya V. Ivanchenko:
  I created a neat setup using xinet + scanbd service + scanbd daemon (for
  buttons) + sane (client) to use Epson GT-1500 (with ADF) as a workhorse
  of a network scanner, with scanner buttons hooked to various jobs.
  Everything is working great, except...
 
  I encountered a problem after the scanner is powered off and then on
  again. The buttons service (scanbd daemon) stops reading the buttons and
  keeps getting communication error in the syslog.
 
 that shouldn't happen. Normally, scanbd gets via udev | hal | dbus a 
 device-removed event and then abandones the device until it gets plugged 
 in again.

Good to know that scanbd should manage firmware loading, it answers the
questions I had. Now it seems we better dig to the root of the
problem...


 So, please show the syslog from beginning of the scanbd log messages and 
 in the situation when the device is removed.

I've pasted syslog snippet with the problem when firmware is not loaded
(with scanbd debug-level=7) here (device was removed on Aug 28 18:02:28,
communication error happens on Aug 28 18:03:19):
http://pastebin.com/BweSr5p2
(it will expire in 1 month)

 
 And please: how did you configure / compile, which platform, ...

Ubuntu 12.04LTS on Intel amd64, 1st installed sane and Epson's iscan:

sudo apt-get install sane-utils
sudo dpkg -i iscan-data_1.23.0-1_all.deb
sudo dpkg -i iscan_2.29.1-5~usb0.1.ltdl7_amd64.deb
sudo dpkg -i iscan-plugin-gt-1500_2.2.0-1_amd64.deb
scanimage -L
# works

2nd downloaded scanbd (181-trunk)
Prepared:
sudo apt-get install build-essential checkinstall
sudo apt-get install libconfuse-dev libsane-dev libudev-dev
sudo apt-get install libconfuse-dev libusb-dev libudev-dev libdbus-1-dev
dbus libsane-dev 
## Sane option will only work if sane backend supports reading buttons
from the scanner (use scanimage -A to check):
# ./configure --prefix= --with-user=saned --with-group=scanner
## Use scanbuttond backend (embedded into scanbd):
./configure --prefix= --with-user=saned --with-group=scanner
--enable-scanbuttond

I patched 2 files:

- src/scanbuttond/backends/epson_vphoto.c - added VID/PID 04B8/0133 for
Epson GT-1500:
  { 0x04B8, 0x0133, 5 }   // Epson GT-1500, buttons: 1=scan, 2=copy,
3=email, 4=pdf, 5=stop
  ...
  { Epson, GT-1500}

- src/scanbd/scanbuttond_wrapper.c function scanbtnd_button_name()
(upped the assert for button count =4 to =5 and renamed buttons per
Epson line above) 

BTW - it would be nice if device definitions can name their own buttons
instead of hard-coded values.That first list with VID/PID/count_buttons
could contain an array of strings for that.

Then I compiled:
make
sudo make install


The system configuration involved some editing in /etc/, but I think it
is not the issue here. Anyway let me know if you need any other
information.

Regards,

--
Ilya

[sane-devel] scanbd daemon does not load firmware

[Ilya V. Ivanchenko]

I created a neat setup using xinet + scanbd service + scanbd daemon (for 
buttons) + sane (client) to use Epson GT-1500 (with ADF) as a workhorse of a 
network scanner, with scanner buttons hooked to various jobs. Everything is 
working great, except...

I encountered a problem after the scanner is powered off and then on again. The 
buttons service (scanbd daemon) stops reading the buttons and keeps getting 
communication error in the syslog.

I tried various things until it occurred to me that Epson GT-1500 uses iscan 
plugin that loads firmware file (/usr/share/iscan/esfw86.bin) and the power 
off-on resets the scanner and thus wipes out the firmware. It seems like scanbd 
daemon does not load the firmware when the scanner is powered back on (at least 
I was not able to find how to configure it to do so), and it gets into trouble 
trying to read the buttons from device without its firmware.?

I have few questions to scanbd team:

1. Can scanbd daemon automatically load firmware file and what should be done 
in the config files to achieve that? sane config files seem to have firmware 
option, but I don't see anything in scanbd documentation.

2. If scanbd daemon currently cannot load the firmware, are there any plans to 
add this feature?

3. If not, what is the recommended way to set scanbd up so it will work with 
scanners that require firmware to be loaded?

I spent few hours and came up with the following rework using udev rule that 
invokes scanimage -L command to pull the command chain that loads the 
firmware. It works fine and I have not seen communication error since.

A. Create a script that causes firmware to be loaded (I'm open to other 
methods, but scanimage -L is the only I found so far)
sudo tee /etc/scanbd/scanner.d/on_insert.sh  /dev/null  CATEOF
#! /bin/bash
logger=/usr/bin/logger -t scanbd
$logger Loading firmware for $1
/usr/sbin/service scanbd stop 21 /dev/null
/usr/bin/scanimage -L 21 | $logger
/usr/sbin/service scanbd start 21 /dev/null
$logger Done loading firmware for $1
CATEOF
sudo chmod a+x /etc/scanbd/scanner.d/on_insert.sh

B. Create udev rule to call the above script.
sudo tee /etc/udevd/rules.d/98-epson.rules  /dev/null  CATEOF
# Force firmware load for EPSON GT-1500
ACTION==add, ENV{DEVTYPE}==usb_device, ATTRS{idVendor}==04b8, 
ATTRS{idProduct}==0133, RUN+=/etc/scanbd/scanner.d/on_insert.sh %p
CATEOF
-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130827/4ebe50df/attachment-0001.html

[sane-devel] scanbd with old udev version

[Wilhelm]

Am 24.08.2013 15:55, schrieb Sander Devrieze:
 2013/8/22 Sander Devrieze s.devrieze at gmail.com
 mailto:s.devrieze at gmail.com

 snip
 I got a bit further this evening:

 1) saned not running + /usr/local/sbin/scanbm  sleep 1 
 SANE_CONFIG_DIR=/usr/local/etc/scanbd/ scanimage -L -- found
 2) saned not running +/usr/local/sbin/scanbm  sleep 1  scanimage
 -L -- not found
 3) saned running + scanimage -L -- not found
 4) saned running + SANE_CONFIG_DIR=/usr/local/etc/scanbd/ scanimage
 -L -- found

 What to try next?

 Please note I also still getting this error as in the beginning:

 libudev: udev_monitor_enable_receiving: bind failed: Operation not
 permitted
 /usr/local/sbin/scanbd: Can't enable udev receiving
 /usr/local/sbin/scanbd: Can't init udev


 Ok, I got everything working as it should. It came out the permissions
 in /usr/local/etc/scanbd/saned.conf had to be fixed.

Can you describe what the problem was? Which permission do you mean? Or 
do you mean the access-list?

 Maybe some note can
 be added to the documentation?

do you feel the paragraph for saned isn't sufficient?


 In attachment you can find my action script which is based on some GPL
 script I found. Same license applies. For sending the emails, I suggest
 installing ssmtp if you do not want to setup your own mailserver.

Thank you. Will put this into the contrib dir.

-- 
Wilhelm
w.meier at unix.net

[sane-devel] scanbd with old udev version

[Wilhelm]

Am 25.08.2013 11:41, schrieb Wilhelm:
 Am 24.08.2013 15:55, schrieb Sander Devrieze:
 2013/8/22 Sander Devrieze s.devrieze at gmail.com
 mailto:s.devrieze at gmail.com

 snip
 I got a bit further this evening:

 1) saned not running + /usr/local/sbin/scanbm  sleep 1 
 SANE_CONFIG_DIR=/usr/local/etc/scanbd/ scanimage -L -- found
 2) saned not running +/usr/local/sbin/scanbm  sleep 1  scanimage
 -L -- not found
 3) saned running + scanimage -L -- not found
 4) saned running + SANE_CONFIG_DIR=/usr/local/etc/scanbd/ scanimage
 -L -- found

 What to try next?

 Please note I also still getting this error as in the beginning:

 libudev: udev_monitor_enable_receiving: bind failed: Operation not
 permitted
 /usr/local/sbin/scanbd: Can't enable udev receiving
 /usr/local/sbin/scanbd: Can't init udev


 Ok, I got everything working as it should. It came out the permissions
 in /usr/local/etc/scanbd/saned.conf had to be fixed.

 Can you describe what the problem was? Which permission do you mean? Or
 do you mean the access-list?

 Maybe some note can
 be added to the documentation?

 do you feel the paragraph for saned isn't sufficient?

ohm just found a typo in the documentation ... it must read saned.conf 
instead of net.conf !



 In attachment you can find my action script which is based on some GPL
 script I found. Same license applies. For sending the emails, I suggest
 installing ssmtp if you do not want to setup your own mailserver.

 Thank you. Will put this into the contrib dir.



-- 
Wilhelm
w.meier at unix.net

[sane-devel] scanbd with old udev version

[Sander Devrieze]

2013/8/25 Wilhelm wilhelm.meier at fh-kl.de

 Am 24.08.2013 15:55, schrieb Sander Devrieze:

 2013/8/22 Sander Devrieze s.devrieze at gmail.com
 snip
 Ok, I got everything working as it should. It came out the permissions
 in /usr/local/etc/scanbd/saned.**conf had to be fixed.


 Can you describe what the problem was? Which permission do you mean? Or do
 you mean the access-list?


Yes, the access list contained no entries.


  Maybe some note can
 be added to the documentation?


 do you feel the paragraph for saned isn't sufficient?


Indeed, the documentation is very good, but it is written for people who
have (much) experience with configuring sane. It will be better if you
write the documentation with people in mind who do not know anything about
sane.
-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130825/22d0cf76/attachment-0001.html

[sane-devel] scanbd with old udev version

[Sander Devrieze]

2013/8/22 Sander Devrieze s.devrieze at gmail.com

 snip
 I got a bit further this evening:

 1) saned not running + /usr/local/sbin/scanbm  sleep 1 
 SANE_CONFIG_DIR=/usr/local/etc/scanbd/ scanimage -L -- found
 2) saned not running +/usr/local/sbin/scanbm  sleep 1  scanimage -L --
 not found
 3) saned running + scanimage -L -- not found
 4) saned running + SANE_CONFIG_DIR=/usr/local/etc/scanbd/ scanimage -L --
 found

 What to try next?

 Please note I also still getting this error as in the beginning:

 libudev: udev_monitor_enable_receiving: bind failed: Operation not
 permitted
 /usr/local/sbin/scanbd: Can't enable udev receiving
 /usr/local/sbin/scanbd: Can't init udev


Ok, I got everything working as it should. It came out the permissions in
/usr/local/etc/scanbd/saned.conf had to be fixed. Maybe some note can be
added to the documentation?

In attachment you can find my action script which is based on some GPL
script I found. Same license applies. For sending the emails, I suggest
installing ssmtp if you do not want to setup your own mailserver.
-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130824/b2b747d1/attachment.html
-- next part --
A non-text attachment was scrubbed...
Name: actions.script
Type: application/octet-stream
Size: 4974 bytes
Desc: not available
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130824/b2b747d1/attachment.obj

[sane-devel] scanbd with old udev version

[Sander Devrieze]

2013/8/21 Wilhelm wilhelm.meier at fh-kl.de

 Am 21.08.2013 16:04, schrieb Sander Devrieze:

 2013/8/21 Wilhelm wilhelm.meier at fh-kl.de mailto:wilhelm.meier at 
 fh-kl.de


snip


 Mmh, looks good.

 So, if scanimage finds the scanner (started with the uid/gid as in
 scanbd.conf), scanbd should find it too, if started as root and the env-var
 SANE_CONFIG_DIR set.


Scanimage does not find the scanner right now. It did only find the scanner
when not using the net backend os sane. In that case, the genesys backend
was immediately chosen. What else can I try?

Line in /etc/passwd
saned:x:104:109::/home/saned:/bin/false

This uid and gid do match with scandb:

/usr/local/sbin/scanbd: foreground
/usr/local/sbin/scanbd: config-file: /usr/local/etc/scanbd/scanbd.conf
/usr/local/sbin/scanbd: reading config file
/usr/local/etc/scanbd/scanbd.conf
/usr/local/sbin/scanbd: debug on: level: 7
/usr/local/sbin/scanbd: dropping privs to uid saned
/usr/local/sbin/scanbd: dropping privs to gid saned
/usr/local/sbin/scanbd: drop privileges to gid: 109
/usr/local/sbin/scanbd: Running as effective gid 109
/usr/local/sbin/scanbd: drop privileges to uid: 104
/usr/local/sbin/scanbd: Running as effective uid 104
/usr/local/sbin/scanbd: dbus_init
/usr/local/sbin/scanbd: dbus match
type='signal',interface='org.freedesktop.Hal.Manager'
/usr/local/sbin/scanbd: sane version 1.0
/usr/local/sbin/scanbd: Scanning for local-only devices
/usr/local/sbin/scanbd: found device: genesys:libusb:001:005 Canon LiDE 110
flatbed scanner
/usr/local/sbin/scanbd: start_sane_threads
/usr/local/sbin/scanbd: Starting poll thread for genesys:libusb:001:005
/usr/local/sbin/scanbd: sane_poll
/usr/local/sbin/scanbd: Thread started for device genesys:libusb:001:005
/usr/local/sbin/scanbd: start dbus thread
/usr/local/sbin/scanbd: timeout: 500 ms
/usr/local/sbin/scanbd: Iteration on dbus call
/usr/local/sbin/scanbd: udev init
/usr/local/sbin/scanbd: get udev monitor
libudev: udev_monitor_enable_receiving: bind failed: Operation not permitted
/usr/local/sbin/scanbd: Can't enable udev receiving
/usr/local/sbin/scanbd: Can't init udev
/usr/local/sbin/scanbd: found 41 options for device genesys:libusb:001:005
/usr/local/sbin/scanbd: sane_find_matching_options
/usr/local/sbin/scanbd: found 5 actions in section (null)
-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130821/6600f819/attachment.html

[sane-devel] scanbd with old udev version

[Wilhelm]

Am 21.08.2013 23:27, schrieb Sander Devrieze:
 2013/8/21 Wilhelm wilhelm.meier at fh-kl.de mailto:wilhelm.meier at 
 fh-kl.de

 Am 21.08.2013 16:04, schrieb Sander Devrieze:

 2013/8/21 Wilhelm wilhelm.meier at fh-kl.de
 mailto:wilhelm.meier at fh-kl.de mailto:wilhelm.meier at fh-kl.de
 mailto:wilhelm.meier at fh-kl.de


 snip

 Mmh, looks good.

 So, if scanimage finds the scanner (started with the uid/gid as in
 scanbd.conf), scanbd should find it too, if started as root and the
 env-var SANE_CONFIG_DIR set.


 Scanimage does not find the scanner right now. It did only find the
 scanner when not using the net backend os sane.

That's ok. For a desktop machine using scanbd and local scanning apps 
(like scanimage), scanbd / scanbm must be running. Please read 0.1) 
solution from the README.txt: scanbm acts as a proxy for saned.

 In that case, the
 genesys backend was immediately chosen. What else can I try?

The below log shows, that scanbd recognizes the scanner and his options. 
So now you have to figure out which buttons correlate to which option 
value changes: just press a button and watch the log. Then you can tweak 
the scripts for the button actions.


 Line in /etc/passwd
 saned:x:104:109::/home/saned:/bin/false

 This uid and gid do match with scandb:

 /usr/local/sbin/scanbd: foreground
 /usr/local/sbin/scanbd: config-file: /usr/local/etc/scanbd/scanbd.conf
 /usr/local/sbin/scanbd: reading config file
 /usr/local/etc/scanbd/scanbd.conf
 /usr/local/sbin/scanbd: debug on: level: 7
 /usr/local/sbin/scanbd: dropping privs to uid saned
 /usr/local/sbin/scanbd: dropping privs to gid saned
 /usr/local/sbin/scanbd: drop privileges to gid: 109
 /usr/local/sbin/scanbd: Running as effective gid 109
 /usr/local/sbin/scanbd: drop privileges to uid: 104
 /usr/local/sbin/scanbd: Running as effective uid 104
 /usr/local/sbin/scanbd: dbus_init
 /usr/local/sbin/scanbd: dbus match
 type='signal',interface='org.freedesktop.Hal.Manager'
 /usr/local/sbin/scanbd: sane version 1.0
 /usr/local/sbin/scanbd: Scanning for local-only devices
 /usr/local/sbin/scanbd: found device: genesys:libusb:001:005 Canon LiDE
 110 flatbed scanner
 /usr/local/sbin/scanbd: start_sane_threads
 /usr/local/sbin/scanbd: Starting poll thread for genesys:libusb:001:005
 /usr/local/sbin/scanbd: sane_poll
 /usr/local/sbin/scanbd: Thread started for device genesys:libusb:001:005
 /usr/local/sbin/scanbd: start dbus thread
 /usr/local/sbin/scanbd: timeout: 500 ms
 /usr/local/sbin/scanbd: Iteration on dbus call
 /usr/local/sbin/scanbd: udev init
 /usr/local/sbin/scanbd: get udev monitor
 libudev: udev_monitor_enable_receiving: bind failed: Operation not permitted
 /usr/local/sbin/scanbd: Can't enable udev receiving
 /usr/local/sbin/scanbd: Can't init udev
 /usr/local/sbin/scanbd: found 41 options for device genesys:libusb:001:005
 /usr/local/sbin/scanbd: sane_find_matching_options
 /usr/local/sbin/scanbd: found 5 actions in section (null)



-- 
Wilhelm
w.meier at unix.net

[sane-devel] scanbd with old udev version

[Sander Devrieze]

2013/8/22 Wilhelm wilhelm.meier at fh-kl.de

 Am 21.08.2013 23:27, schrieb Sander Devrieze:

 2013/8/21 Wilhelm wilhelm.meier at fh-kl.de mailto:wilhelm.meier at 
 fh-kl.de*
 *

 Am 21.08.2013 16:04, schrieb Sander Devrieze:

 2013/8/21 Wilhelm wilhelm.meier at fh-kl.de
 mailto:wilhelm.meier at fh-kl.de** mailto:wilhelm.meier at 
 fh-kl.de

 mailto:wilhelm.meier at fh-kl.de**


 snip

 Mmh, looks good.

 So, if scanimage finds the scanner (started with the uid/gid as in
 scanbd.conf), scanbd should find it too, if started as root and the
 env-var SANE_CONFIG_DIR set.


 Scanimage does not find the scanner right now. It did only find the
 scanner when not using the net backend os sane.


 That's ok. For a desktop machine using scanbd and local scanning apps
 (like scanimage), scanbd / scanbm must be running. Please read 0.1)
 solution from the README.txt: scanbm acts as a proxy for saned.


  In that case, the
 genesys backend was immediately chosen. What else can I try?


 The below log shows, that scanbd recognizes the scanner and his options.
 So now you have to figure out which buttons correlate to which option value
 changes: just press a button and watch the log. Then you can tweak the
 scripts for the button actions.


This is the current status:
1) saned not running + scanbd not running + scanimage -L -- scanner found
2) saned not running + scanbd running + manually running scanbm -- the
logs show scanbd is interrupted for a short moment
3) saned not running + scanbd running + scanimage -L -- scanner *not* found

Why is case #3 not working?
-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130822/42a51c95/attachment-0001.html

[sane-devel] scanbd with old udev version

[Wilhelm]

Am 22.08.2013 08:58, schrieb Sander Devrieze:
 2013/8/22 Wilhelm wilhelm.meier at fh-kl.de mailto:wilhelm.meier at 
 fh-kl.de

 Am 21.08.2013 23:27, schrieb Sander Devrieze:

 2013/8/21 Wilhelm wilhelm.meier at fh-kl.de
 mailto:wilhelm.meier at fh-kl.de mailto:wilhelm.meier at fh-kl.de
 mailto:wilhelm.meier at fh-kl.de__

  Am 21.08.2013 16:04, schrieb Sander Devrieze:

  2013/8/21 Wilhelm wilhelm.meier at fh-kl.de
 mailto:wilhelm.meier at fh-kl.de
  mailto:wilhelm.meier at fh-kl.de
 mailto:wilhelm.meier at fh-kl.de__
 mailto:wilhelm.meier at fh-kl.de mailto:wilhelm.meier at fh-kl.de

  mailto:wilhelm.meier at fh-kl.de
 mailto:wilhelm.meier at fh-kl.de__


 snip

  Mmh, looks good.

  So, if scanimage finds the scanner (started with the
 uid/gid as in
  scanbd.conf), scanbd should find it too, if started as root
 and the
  env-var SANE_CONFIG_DIR set.


 Scanimage does not find the scanner right now. It did only find the
 scanner when not using the net backend os sane.


 That's ok. For a desktop machine using scanbd and local scanning
 apps (like scanimage), scanbd / scanbm must be running. Please read
 0.1) solution from the README.txt: scanbm acts as a proxy for saned.


 In that case, the
 genesys backend was immediately chosen. What else can I try?


 The below log shows, that scanbd recognizes the scanner and his
 options. So now you have to figure out which buttons correlate to
 which option value changes: just press a button and watch the log.
 Then you can tweak the scripts for the button actions.


 This is the current status:
 1) saned not running + scanbd not running + scanimage -L -- scanner found

this is not intended to work: scanimage should use the net backend and 
if saned isn't running it shouldn't work

 2) saned not running + scanbd running + manually running scanbm -- the
 logs show scanbd is interrupted for a short moment

ok

 3) saned not running + scanbd running + scanimage -L -- scanner *not* found

 Why is case #3 not working?

Presumably, scanimage is using the wrong dll.conf.

-- 
Wilhelm
w.meier at unix.net

[sane-devel] scanbd with old udev version

[Sander Devrieze]

2013/8/22 Wilhelm wilhelm.meier at fh-kl.de

 Am 22.08.2013 08:58, schrieb Sander Devrieze:

 2013/8/22 Wilhelm wilhelm.meier at fh-kl.de mailto:wilhelm.meier at 
 fh-kl.de*
 *



 This is the current status:
 1) saned not running + scanbd not running + scanimage -L -- scanner found


 this is not intended to work: scanimage should use the net backend and if
 saned isn't running it shouldn't work


  2) saned not running + scanbd running + manually running scanbm -- the
 logs show scanbd is interrupted for a short moment


 ok


  3) saned not running + scanbd running + scanimage -L -- scanner *not*
 found

 Why is case #3 not working?


 Presumably, scanimage is using the wrong dll.conf.


How can I check this?
-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130822/724fe20d/attachment.html

[sane-devel] scanbd with old udev version

[Sander Devrieze]

2013/8/22 Wilhelm wilhelm.meier at fh-kl.de

 Am 22.08.2013 08:58, schrieb Sander Devrieze:



 snip



 This is the current status:
 1) saned not running + scanbd not running + scanimage -L -- scanner found


 this is not intended to work: scanimage should use the net backend and if
 saned isn't running it shouldn't work


  2) saned not running + scanbd running + manually running scanbm -- the
 logs show scanbd is interrupted for a short moment


 ok


  3) saned not running + scanbd running + scanimage -L -- scanner *not*
 found

 Why is case #3 not working?


 Presumably, scanimage is using the wrong dll.conf.


I got a bit further this evening:

1) saned not running + /usr/local/sbin/scanbm  sleep 1 
SANE_CONFIG_DIR=/usr/local/etc/scanbd/ scanimage -L -- found
2) saned not running +/usr/local/sbin/scanbm  sleep 1  scanimage -L --
not found
3) saned running + scanimage -L -- not found
4) saned running + SANE_CONFIG_DIR=/usr/local/etc/scanbd/ scanimage -L --
found

What to try next?

Please note I also still getting this error as in the beginning:

libudev: udev_monitor_enable_receiving: bind failed: Operation not permitted
/usr/local/sbin/scanbd: Can't enable udev receiving
/usr/local/sbin/scanbd: Can't init udev
-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130822/bc845bd0/attachment.html

[sane-devel] scanbd with old udev version

[Sander Devrieze]

Hello,

I am trying to convert a WD MyBook into a scanner server. Sane detects the
scanner and I was able to scan, but I cannot get scanbd to work.

May this be related to the fact that I am using a *very* old udev version
(0.125-7+lenny3) which cannot be upgraded? Check the debug output below.
How can I get scanbd running on my system?

Thanks for helping me out!

/usr/local/sbin/scanbd: foreground
/usr/local/sbin/scanbd: config-file: /usr/local/etc/scanbd/scanbd.conf
/usr/local/sbin/scanbd: reading config file
/usr/local/etc/scanbd/scanbd.conf
/usr/local/sbin/scanbd: debug on: level: 7
/usr/local/sbin/scanbd: dropping privs to uid saned
/usr/local/sbin/scanbd: dropping privs to gid saned
/usr/local/sbin/scanbd: drop privileges to gid: 109
/usr/local/sbin/scanbd: Running as effective gid 109
/usr/local/sbin/scanbd: drop privileges to uid: 104
/usr/local/sbin/scanbd: Running as effective uid 104
/usr/local/sbin/scanbd: dbus_init
/usr/local/sbin/scanbd: dbus match
type='signal',interface='org.freedesktop.Hal.Manager'
/usr/local/sbin/scanbd: sane version 1.0
/usr/local/sbin/scanbd: Scanning for local-only devices
/usr/local/sbin/scanbd: start_sane_threads
/usr/local/sbin/scanbd: start dbus thread
/usr/local/sbin/scanbd: timeout: 500 ms
/usr/local/sbin/scanbd: Iteration on dbus call
/usr/local/sbin/scanbd: udev init
/usr/local/sbin/scanbd: get udev monitor
libudev: udev_monitor_enable_receiving: bind failed: Operation not permitted
/usr/local/sbin/scanbd: Can't enable udev receiving
/usr/local/sbin/scanbd: Can't init udev
/usr/local/sbin/scanbd: Iteration on dbus call
/usr/local/sbin/scanbd: Iteration on dbus call
/usr/local/sbin/scanbd: Iteration on dbus call

-- 
Kind Regards,
Sander Devrieze
-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130821/819f6218/attachment-0001.html

[sane-devel] scanbd with old udev version

[Wilhelm]

Hi Sander,

Am 21.08.2013 00:40, schrieb Sander Devrieze:
 Hello,

 I am trying to convert a WD MyBook into a scanner server. Sane detects
 the scanner and I was able to scan, but I cannot get scanbd to work.

Which options did you use for configure?


 May this be related to the fact that I am using a *very* old udev
 version (0.125-7+lenny3) which cannot be upgraded?

On Lenny you should try usind hal instead of udev. But this is only 
resonsible for detecting removable devices. As a fallback scanbd can be 
signaled (using some udev-rule, e.g.), please check the docu.

 Check the debug
 output below. How can I get scanbd running on my system?

First of all scanbd doesn't detect any scanner. There may be various 
reasons. But most likely scanbd uses a wrong dll.conf.

Did you
export SANE_CONFIG_DIR=/usr/local/etc/scanbd ?

please show your configs:

/etc/sane/dll.conf
/usr/local/sbin/scanbd/dll.conf
/usr/local/etc/scanbd/scanbd.conf

and show the env-vars for the user starting the scanbd (root).



 Thanks for helping me out!

 /usr/local/sbin/scanbd: foreground
 /usr/local/sbin/scanbd: config-file: /usr/local/etc/scanbd/scanbd.conf
 /usr/local/sbin/scanbd: reading config file
 /usr/local/etc/scanbd/scanbd.conf
 /usr/local/sbin/scanbd: debug on: level: 7
 /usr/local/sbin/scanbd: dropping privs to uid saned
 /usr/local/sbin/scanbd: dropping privs to gid saned
 /usr/local/sbin/scanbd: drop privileges to gid: 109
 /usr/local/sbin/scanbd: Running as effective gid 109
 /usr/local/sbin/scanbd: drop privileges to uid: 104
 /usr/local/sbin/scanbd: Running as effective uid 104
 /usr/local/sbin/scanbd: dbus_init
 /usr/local/sbin/scanbd: dbus match
 type='signal',interface='org.freedesktop.Hal.Manager'
 /usr/local/sbin/scanbd: sane version 1.0
 /usr/local/sbin/scanbd: Scanning for local-only devices
 /usr/local/sbin/scanbd: start_sane_threads
 /usr/local/sbin/scanbd: start dbus thread
 /usr/local/sbin/scanbd: timeout: 500 ms
 /usr/local/sbin/scanbd: Iteration on dbus call
 /usr/local/sbin/scanbd: udev init
 /usr/local/sbin/scanbd: get udev monitor
 libudev: udev_monitor_enable_receiving: bind failed: Operation not permitted
 /usr/local/sbin/scanbd: Can't enable udev receiving
 /usr/local/sbin/scanbd: Can't init udev
 /usr/local/sbin/scanbd: Iteration on dbus call
 /usr/local/sbin/scanbd: Iteration on dbus call
 /usr/local/sbin/scanbd: Iteration on dbus call

 --
 Kind Regards,
 Sander Devrieze




-- 
Wilhelm
w.meier at unix.net

[sane-devel] scanbd with old udev version

[Sander Devrieze]

2013/8/21 Wilhelm wilhelm.meier at fh-kl.de

 Hi Sander,

 Am 21.08.2013 00:40, schrieb Sander Devrieze:

  Hello,

 I am trying to convert a WD MyBook into a scanner server. Sane detects
 the scanner and I was able to scan, but I cannot get scanbd to work.


 Which options did you use for configure?


None, I just did a plain ./configure.




 May this be related to the fact that I am using a *very* old udev
 version (0.125-7+lenny3) which cannot be upgraded?


 On Lenny you should try usind hal instead of udev. But this is only
 resonsible for detecting removable devices. As a fallback scanbd can be
 signaled (using some udev-rule, e.g.), please check the docu.


I am running Debian Squeeze. Only the udev package is from Lenny. This is
needed because otherwise the special MyBook Linux kernel will not boot.


  Check the debug
 output below. How can I get scanbd running on my system?


 First of all scanbd doesn't detect any scanner. There may be various
 reasons. But most likely scanbd uses a wrong dll.conf.

 Did you
 export SANE_CONFIG_DIR=/usr/local/etc/scanbd ?


Yes, and I also run scanbd like this to be sure:
/usr/local/sbin/scanbd -d7 -f -c /usr/local/etc/scanbd/scanbd.conf

When running scanbm, one of the lines reads like this:

scanbm: Setting environment: SANE_CONFIG_DIR=/usr/local/etc/scanbd/sane.d


please show your configs:

 /etc/sane/dll.conf


# /etc/sane.d/dll.conf - Configuration file for the SANE dynamic backend
loader
#
# Backends can also be enabled by configuration snippets under
# /etc/sane.d/dll.d directory -- packages providing backends should drop
# a config file similar to dll.conf in this directory, named after the
package.
#

# The next line enables the network backend; comment it out if you don't
need
# to use a remote SANE scanner over the network - see sane-net(5) and
saned(8)
net
#abaton
#agfafocus
#apple
snip all lines commented out below this



 /usr/local/sbin/scanbd/dll.**conf


Ok, that seems to help. Maybe the readme file should be more clear that you
need to copy the config files and not the directory sane.d in here.
scanbd seems to work. However, sane does not recognize the scanner:

scanimage: no SANE devices found

Any idea what can be wrong?


 /usr/local/etc/scanbd/scanbd.**conf


# global settings
global {
# turn on debugging

# log to console
debug   = true

# debug logging
# 1=error, 2=warn, 3=info, 4-7=debug
debug-level = 7

# drop priviliges to this user
#=
# Linux:
# user= saned # root
# *BSD
# user= root
user= saned

# Group to be used
#=
# Linux (most distributions use the lp group to access scanners)
# group   = lp
# ArchLinux (ArchLinux uses the scanner group)
# group = scanner
#
# *BSD (no group lp here, use daemon instead)
# group   = daemon # root
#
group   = saned
# the saned executable for manager-mode
saned   = /usr/sbin/saned
saned_opt  = {} # string-list
saned_env  = { SANE_CONFIG_DIR=/usr/local/etc/scanbd } # list of
environment vars for saned

# Scriptdir specifies where scanbs normally looks for scripts.
# The scriptdir option can be defined as:
#   - a path relative to the configuations (path/etc/scanbd)
directory
#   - an abosolute path
# Examples:
# scriptdir = scripts
# sets scriptdir to path/etc/scripts.
# scriptdir = /some/path
# sets scriptdir to the specified absolute path
# Default scriptdir is path/etc/scanbd, this is normally
appropriate
# scriptdir =

# scanbuttond_backends_dir sets the path where scanbd looks for the
scanbuttond backends
# It can be defined as relative path, starting from the scanbd
config directory or
# as an absolute path
# Default is libdir/scanbd/scanbutond/backends
# Example
# scanbuttond_backends_dir =
/usr/local/lib/scanbd/scanbuttond/backends

# poll timeout in [ms]
# (for polling the devices)
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 definitions
# values of the options are simply passed via env-vars

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
}

[sane-devel] scanbd with old udev version

[Wilhelm]

Am 21.08.2013 07:56, schrieb Sander Devrieze:
 2013/8/21 Wilhelm wilhelm.meier at fh-kl.de mailto:wilhelm.meier at 
 fh-kl.de

 Hi Sander,

 Am 21.08.2013 00:40, schrieb Sander Devrieze:

 Hello,

 I am trying to convert a WD MyBook into a scanner server. Sane
 detects
 the scanner and I was able to scan, but I cannot get scanbd to work.


 Which options did you use for configure?


 None, I just did a plain ./configure.



 May this be related to the fact that I am using a *very* old udev
 version (0.125-7+lenny3) which cannot be upgraded?


 On Lenny you should try usind hal instead of udev. But this is only
 resonsible for detecting removable devices. As a fallback scanbd can
 be signaled (using some udev-rule, e.g.), please check the docu.


 I am running Debian Squeeze. Only the udev package is from Lenny. This
 is needed because otherwise the special MyBook Linux kernel will not boot.


 Check the debug
 output below. How can I get scanbd running on my system?


 First of all scanbd doesn't detect any scanner. There may be various
 reasons. But most likely scanbd uses a wrong dll.conf.

 Did you
 export SANE_CONFIG_DIR=/usr/local/etc/scanbd ?


 Yes, and I also run scanbd like this to be sure:
 /usr/local/sbin/scanbd -d7 -f -c /usr/local/etc/scanbd/scanbd.conf

 When running scanbm, one of the lines reads like this:

 scanbm: Setting environment: SANE_CONFIG_DIR=/usr/local/etc/scanbd/sane.d


 please show your configs:

 /etc/sane/dll.conf


 # /etc/sane.d/dll.conf - Configuration file for the SANE dynamic backend
 loader
 #
 # Backends can also be enabled by configuration snippets under
 # /etc/sane.d/dll.d directory -- packages providing backends should drop
 # a config file similar to dll.conf in this directory, named after the
 package.
 #

 # The next line enables the network backend; comment it out if you don't
 need
 # to use a remote SANE scanner over the network - see sane-net(5) and
 saned(8)
 net
 #abaton
 #agfafocus
 #apple
 snip all lines commented out below this

 /usr/local/sbin/scanbd/dll.__conf


what is the contents of this file?




 Ok, that seems to help. Maybe the readme file should be more clear that
 you need to copy the config files and not the directory sane.d in
 here. scanbd seems to work. However, sane does not recognize the scanner:

 scanimage: no SANE devices found

 Any idea what can be wrong?

 /usr/local/etc/scanbd/scanbd.__conf


 # global settings
 global {
  # turn on debugging

  # log to console
  debug   = true

  # debug logging
  # 1=error, 2=warn, 3=info, 4-7=debug
  debug-level = 7

  # drop priviliges to this user
  #=
  # Linux:
  # user= saned # root
  # *BSD
  # user= root
  user= saned

  # Group to be used
  #=
  # Linux (most distributions use the lp group to access scanners)
  # group   = lp
  # ArchLinux (ArchLinux uses the scanner group)
  # group = scanner
  #
  # *BSD (no group lp here, use daemon instead)
  # group   = daemon # root
  #
  group   = saned
  # the saned executable for manager-mode
  saned   = /usr/sbin/saned
  saned_opt  = {} # string-list
  saned_env  = { SANE_CONFIG_DIR=/usr/local/etc/scanbd } # list
 of environment vars for saned

  # Scriptdir specifies where scanbs normally looks for scripts.
  # The scriptdir option can be defined as:
  #   - a path relative to the configuations (path/etc/scanbd)
 directory
  #   - an abosolute path
  # Examples:
  # scriptdir = scripts
  # sets scriptdir to path/etc/scripts.
  # scriptdir = /some/path
  # sets scriptdir to the specified absolute path
  # Default scriptdir is path/etc/scanbd, this is normally
 appropriate
  # scriptdir =

  # scanbuttond_backends_dir sets the path where scanbd looks for
 the scanbuttond backends
  # It can be defined as relative path, starting from the scanbd
 config directory or
  # as an absolute path
  # Default is libdir/scanbd/scanbutond/backends
  # Example
  # scanbuttond_backends_dir =
 /usr/local/lib/scanbd/scanbuttond/backends

  # poll timeout in [ms]
  # (for polling the devices)
  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 definitions
  # values of the options are