date:20171105

Re: [sane-devel] SANE automation setup?

2017-11-05 Thread Adam Lloyd

I am going to include the syslog and debug log from scanbd

here is the debug log
pi@raspberrypi:/etc/scanbd $ sudo pico scanbd.conf
pi@raspberrypi:/etc/scanbd $ export SANE_CONFIG_DIR=/etc/scanbd
pi@raspberrypi:/etc/scanbd $ scanbd
scanbd: debug on: level: 3
pi@raspberrypi:/etc/scanbd $ scanbd -f
scanbd: debug on: level: 3
scanbd: dropping privs to uid saned
scanbd: dropping privs to gid scanner
scanbd: group scanner has member:
scanbd: saned
scanbd: Can't set the effective gid to 116
scanbd: Can't set the effective uid to 111
scanbd: dbus match type='signal',interface='org.freedesktop.Hal.Manager'
scanbd: sane version 1.0
scanbd: Scanning for local-only devices
scanbd: Not Primary Owner (-1)
scanbd: Name Error (Connection ":1.18" is not allowed to own the service
"de.kmux.scanbd.server" due to security policies in the configuration file)
scanbd: udev fd is non-blocking, now setting to blocking mode
scanbd: found 32 options for device rts8891:libusb:001:004
scanbd: found 5 actions in section (null)
scanbd: option[1] standard for device rts8891:libusb:001:004 not of type
BOOL|INT|FIXED|STRING|BUTTON. Skipping
scanbd: found active option[2] mode (type: 3) for device
rts8891:libusb:001:004
scanbd: found active option[3] preview (type: 0) for device
rts8891:libusb:001:004
scanbd: found active option[4] resolution (type: 1) for device
rts8891:libusb:001:004
scanbd: option[5] geometry for device rts8891:libusb:001:004 not of type
BOOL|INT|FIXED|STRING|BUTTON. Skipping
scanbd: found active option[6] tl-x (type: 2) for device
rts8891:libusb:001:004
scanbd: found active option[7] tl-y (type: 2) for device
rts8891:libusb:001:004
scanbd: found active option[8] br-x (type: 2) for device
rts8891:libusb:001:004
scanbd: found active option[9] br-y (type: 2) for device
rts8891:libusb:001:004
scanbd: option[10] enhancement for device rts8891:libusb:001:004 not of
type BOOL|INT|FIXED|STRING|BUTTON. Skipping
scanbd: found active option[12] custom-gamma (type: 0) for device
rts8891:libusb:001:004
scanbd: found active option[18] lamp-on (type: 4) for device
rts8891:libusb:001:004
scanbd: found active option[19] lamp-off (type: 4) for device
rts8891:libusb:001:004
scanbd: option[20] sensors for device rts8891:libusb:001:004 not of type
BOOL|INT|FIXED|STRING|BUTTON. Skipping
scanbd: found active option[21] button-plus (type: 0) for device
rts8891:libusb:001:004
scanbd: found active option[22] button-minus (type: 0) for device
rts8891:libusb:001:004
scanbd: found active option[23] button-copy (type: 0) for device
rts8891:libusb:001:004
scanbd: found active option[24] button-mail (type: 0) for device
rts8891:libusb:001:004
scanbd: found active option[25] button-image-copy (type: 0) for device
rts8891:libusb:001:004
scanbd: found active option[26] button-www (type: 0) for device
rts8891:libusb:001:004
scanbd: found active option[27] button-scan (type: 0) for device
rts8891:libusb:001:004
scanbd: found active option[28] button-power (type: 0) for device
rts8891:libusb:001:004
scanbd: found active option[29] button-cancel (type: 0) for device
rts8891:libusb:001:004
scanbd: found active option[30] button-options (type: 0) for device
rts8891:libusb:001:004
scanbd: found active option[31] button-toggle-mode (type: 0) for device
rts8891:libusb:001:004
scanbd: option[1] standard for device rts8891:libusb:001:004 not of type
BOOL|INT|FIXED|STRING|BUTTON. Skipping
scanbd: found active option[2] mode (type: 3) for device
rts8891:libusb:001:004
scanbd: found active option[3] preview (type: 0) for device
rts8891:libusb:001:004
scanbd: found active option[4] resolution (type: 1) for device
rts8891:libusb:001:004
scanbd: option[5] geometry for device rts8891:libusb:001:004 not of type
BOOL|INT|FIXED|STRING|BUTTON. Skipping
scanbd: found active option[6] tl-x (type: 2) for device
rts8891:libusb:001:004
scanbd: found active option[7] tl-y (type: 2) for device
rts8891:libusb:001:004
scanbd: found active option[8] br-x (type: 2) for device
rts8891:libusb:001:004
scanbd: found active option[9] br-y (type: 2) for device
rts8891:libusb:001:004
scanbd: option[10] enhancement for device rts8891:libusb:001:004 not of
type BOOL|INT|FIXED|STRING|BUTTON. Skipping
scanbd: found active option[12] custom-gamma (type: 0) for device
rts8891:libusb:001:004
scanbd: found active option[18] lamp-on (type: 4) for device
rts8891:libusb:001:004
scanbd: found active option[19] lamp-off (type: 4) for device
rts8891:libusb:001:004
scanbd: option[20] sensors for device rts8891:libusb:001:004 not of type
BOOL|INT|FIXED|STRING|BUTTON. Skipping
scanbd: found active option[21] button-plus (type: 0) for device
rts8891:libusb:001:004
scanbd: found active option[22] button-minus (type: 0) for device
rts8891:libusb:001:004
scanbd: found active option[23] button-copy (type: 0) for device
rts8891:libusb:001:004
scanbd: found active option[24] button-mail (type: 0) for device
rts8891:libusb:001:004
scanbd: found active option[25] button-image-copy (type: 0) for device

[sane-devel] SANE needs a GUI like CUPS's 'system-config-printer' to manually add a network scanner.

2017-11-05 Thread Hans Deragon

Greetings,

I understand that saned is a daemon / API running in the backend, but I
believe that like CUPS's 'system-config-printer', it should come with a
frontend to manage scanners.

I have a network (wifi) scanner setup properly.  One of my Linux machine
(a desktop computer) connects to it without any issue.  I have setup
that machine with hplip.  However, another Linux laptop cannot find it
on the network.  I know its IP and I can ping it, figure out the ports
that are open, but there is no GUI to add a scanner.

In fact, I cannot even figure out how to add this scanner via the
terminal.  Searching for any reference to it under /etc on the desktop
machine for which it works returns nothing.  I have no clue where the
scanner is configured on that machine so I can copy the configuration on
the laptop.

The scanner is part of my MFC "HP Officejet Pro 6978 All-in-one".  hplip
requires me to set it up (again!) with a USB cable.  But this device is
already setup and I should not have to plug as USB cable to it and
reconfigure it.  I should just be able to find it on the network and go
on with it, or at least, add it manually via a GUI.

Has this issue already been discussed?  BTW, I am new to this mailing
list and I have no history regarding the SANE project; I am just a
simple user.

Best regards,
Hans Deragon



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

Re: [sane-devel] SANE automation setup?

2017-11-05 Thread Wilhelm Meier

Please provide the log of scanbd from the beginning on - until the point
where it starts repeating the same messages.

Am 05.11.2017 um 13:07 schrieb Adam Lloyd:
> Here are some of the log files below:
> 
> pi@raspberrypi:~ $ tail -f /var/log/messages
> Nov  3 10:39:44 raspberrypi kernel: [   12.884962] Bluetooth: RFCOMM
> socket layer initialized
> Nov  3 10:39:44 raspberrypi kernel: [   12.884981] Bluetooth: RFCOMM ver
> 1.11
> Nov  3 10:39:45 raspberrypi lightdm[552]: Error getting user list from
> org.freedesktop.Accounts:
> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.freedesktop.Accounts was not provided by any .service files
> Nov  3 10:39:48 raspberrypi kernel: [   17.721642] fuse init (API
> version 7.26)
> Nov  3 10:39:53 raspberrypi kernel: [   21.889090] EXT4-fs (mmcblk0p5):
> mounted filesystem with ordered data mode. Opts: (null)
> Nov  5 11:59:29 raspberrypi kernel: [  176.512360] warning: process
> `scanbd' used the deprecated sysctl system call with 
> Nov  5 11:59:29 raspberrypi kernel: [  176.512370] 8.
> Nov  5 11:59:29 raspberrypi kernel: [  176.512373] 1.
> Nov  5 11:59:29 raspberrypi kernel: [  176.512375] 2.
> Nov  5 11:59:29 raspberrypi kernel: [  176.512376] 
> 
> 
> pi@raspberrypi:~ $ tail -f /var/log/syslog
> Nov  5 11:59:34 raspberrypi scanbd: scanbd: option[10] enhancement for
> device rts8891:libusb:001:004 not of type BOOL|INT|FIXED|STRING|BUTTON.
> Skipping
> Nov  5 11:59:34 raspberrypi scanbd: scanbd: option[20] sensors for
> device rts8891:libusb:001:004 not of type BOOL|INT|FIXED|STRING|BUTTON.
> Skipping
> Nov  5 11:59:34 raspberrypi scanbd: scanbd: option[1] standard for
> device rts8891:libusb:001:004 not of type BOOL|INT|FIXED|STRING|BUTTON.
> Skipping
> Nov  5 11:59:34 raspberrypi scanbd: scanbd: option[5] geometry for
> device rts8891:libusb:001:004 not of type BOOL|INT|FIXED|STRING|BUTTON.
> Skipping
> Nov  5 11:59:34 raspberrypi scanbd: scanbd: option[10] enhancement for
> device rts8891:libusb:001:004 not of type BOOL|INT|FIXED|STRING|BUTTON.
> Skipping
> Nov  5 11:59:34 raspberrypi scanbd: scanbd: option[20] sensors for
> device rts8891:libusb:001:004 not of type BOOL|INT|FIXED|STRING|BUTTON.
> Skipping
> Nov  5 11:59:34 raspberrypi scanbd: scanbd: option[1] standard for
> device rts8891:libusb:001:004 not of type BOOL|INT|FIXED|STRING|BUTTON.
> Skipping
> Nov  5 11:59:34 raspberrypi scanbd: scanbd: option[5] geometry for
> device rts8891:libusb:001:004 not of type BOOL|INT|FIXED|STRING|BUTTON.
> Skipping
> Nov  5 11:59:34 raspberrypi scanbd: scanbd: option[10] enhancement for
> device rts8891:libusb:001:004 not of type BOOL|INT|FIXED|STRING|BUTTON.
> Skipping
> Nov  5 11:59:34 raspberrypi scanbd: scanbd: option[20] sensors for
> device rts8891:libusb:001:004 not of type BOOL|INT|FIXED|STRING|BUTTON.
> Skipping
> 
> pi@raspberrypi:~ $ lsusb
> Bus 001 Device 006: ID 045e:074f Microsoft Corp. 
> Bus 001 Device 005: ID 0603:00f2 Novatek Microelectronics Corp. Keyboard
> (Labtec Ultra Flat Keyboard)
> Bus 001 Device 004: ID 03f0:0805 Hewlett-Packard HP4470C
> Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
> SMSC9512/9514 Fast Ethernet Adapter
> Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> 
> would the dmesg logs provide additional info?
> 
> 
> 
> 
> 
> 
> On Fri, Nov 3, 2017 at 6:21 AM, Wilhelm Meier
>  > wrote:
> 
> Please post the full log, so that one can see the names of all options.
> If the scanner supports a button (option) we will see the name of the
> option in the log. Then one can adapt the config file to match the
> option name and call a scan-script.
> 
> Am 02.11.2017 um 21:49 schrieb Adam Lloyd:
> > Sorry about that. 
> >
> > pi@raspberrypi:~ $ export SANE_CONFIG_DIR=/etc/scanbd
> > pi@raspberrypi:~ $ scanbd -f
> > scanbd: Can't set the effective gid to 116
> > scanbd: Can't set the effective uid to 111
> > scanbd: dbus match
> type='signal',interface='org.freedesktop.Hal.Manager'
> > scanbd: Not Primary Owner (-1)
> > scanbd: Name Error (Connection ":1.18" is not allowed to own the
> service
> > "de.kmux.scanbd.server" due to security policies in the
> configuration file)
> > scanbd: option[1] standard for device rts8891:libusb:001:006 not
> of type
> > BOOL|INT|FIXED|STRING|BUTTON. Skipping
> > scanbd: option[5] geometry for device rts8891:libusb:001:006 not
> of type
> > BOOL|INT|FIXED|STRING|BUTTON. Skipping
> > scanbd: option[10] enhancement for device rts8891:libusb:001:006
> not of
> > type BOOL|INT|FIXED|STRING|BUTTON. Skipping
> > scanbd: option[20] sensors for device rts8891:libusb:001:006 not
> of type
> > BOOL|INT|FIXED|STRING|BUTTON. Skipping
> > scanbd: option[1] standard for device rts8891:libusb:001:006 not

Re: [sane-devel] SANE automation setup?

2017-11-05 Thread Adam Lloyd

Here are some of the log files below:

pi@raspberrypi:~ $ tail -f /var/log/messages
Nov  3 10:39:44 raspberrypi kernel: [   12.884962] Bluetooth: RFCOMM socket
layer initialized
Nov  3 10:39:44 raspberrypi kernel: [   12.884981] Bluetooth: RFCOMM ver
1.11
Nov  3 10:39:45 raspberrypi lightdm[552]: Error getting user list from
org.freedesktop.Accounts:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.Accounts was not provided by any .service files
Nov  3 10:39:48 raspberrypi kernel: [   17.721642] fuse init (API version
7.26)
Nov  3 10:39:53 raspberrypi kernel: [   21.889090] EXT4-fs (mmcblk0p5):
mounted filesystem with ordered data mode. Opts: (null)
Nov  5 11:59:29 raspberrypi kernel: [  176.512360] warning: process
`scanbd' used the deprecated sysctl system call with
Nov  5 11:59:29 raspberrypi kernel: [  176.512370] 8.
Nov  5 11:59:29 raspberrypi kernel: [  176.512373] 1.
Nov  5 11:59:29 raspberrypi kernel: [  176.512375] 2.
Nov  5 11:59:29 raspberrypi kernel: [  176.512376]

pi@raspberrypi:~ $ tail -f /var/log/syslog
Nov  5 11:59:34 raspberrypi scanbd: scanbd: option[10] enhancement for
device rts8891:libusb:001:004 not of type BOOL|INT|FIXED|STRING|BUTTON.
Skipping
Nov  5 11:59:34 raspberrypi scanbd: scanbd: option[20] sensors for device
rts8891:libusb:001:004 not of type BOOL|INT|FIXED|STRING|BUTTON. Skipping
Nov  5 11:59:34 raspberrypi scanbd: scanbd: option[1] standard for device
rts8891:libusb:001:004 not of type BOOL|INT|FIXED|STRING|BUTTON. Skipping
Nov  5 11:59:34 raspberrypi scanbd: scanbd: option[5] geometry for device
rts8891:libusb:001:004 not of type BOOL|INT|FIXED|STRING|BUTTON. Skipping
Nov  5 11:59:34 raspberrypi scanbd: scanbd: option[10] enhancement for
device rts8891:libusb:001:004 not of type BOOL|INT|FIXED|STRING|BUTTON.
Skipping
Nov  5 11:59:34 raspberrypi scanbd: scanbd: option[20] sensors for device
rts8891:libusb:001:004 not of type BOOL|INT|FIXED|STRING|BUTTON. Skipping
Nov  5 11:59:34 raspberrypi scanbd: scanbd: option[1] standard for device
rts8891:libusb:001:004 not of type BOOL|INT|FIXED|STRING|BUTTON. Skipping
Nov  5 11:59:34 raspberrypi scanbd: scanbd: option[5] geometry for device
rts8891:libusb:001:004 not of type BOOL|INT|FIXED|STRING|BUTTON. Skipping
Nov  5 11:59:34 raspberrypi scanbd: scanbd: option[10] enhancement for
device rts8891:libusb:001:004 not of type BOOL|INT|FIXED|STRING|BUTTON.
Skipping
Nov  5 11:59:34 raspberrypi scanbd: scanbd: option[20] sensors for device
rts8891:libusb:001:004 not of type BOOL|INT|FIXED|STRING|BUTTON. Skipping

pi@raspberrypi:~ $ lsusb
Bus 001 Device 006: ID 045e:074f Microsoft Corp.
Bus 001 Device 005: ID 0603:00f2 Novatek Microelectronics Corp. Keyboard
(Labtec Ultra Flat Keyboard)
Bus 001 Device 004: ID 03f0:0805 Hewlett-Packard HP4470C
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514
Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

would the dmesg logs provide additional info?

On Fri, Nov 3, 2017 at 6:21 AM, Wilhelm Meier <
wilhelm.wm.me...@googlemail.com> wrote:

> Please post the full log, so that one can see the names of all options.
> If the scanner supports a button (option) we will see the name of the
> option in the log. Then one can adapt the config file to match the
> option name and call a scan-script.
>
> Am 02.11.2017 um 21:49 schrieb Adam Lloyd:
> > Sorry about that.
> >
> > pi@raspberrypi:~ $ export SANE_CONFIG_DIR=/etc/scanbd
> > pi@raspberrypi:~ $ scanbd -f
> > scanbd: Can't set the effective gid to 116
> > scanbd: Can't set the effective uid to 111
> > scanbd: dbus match type='signal',interface='org.freedesktop.Hal.Manager'
> > scanbd: Not Primary Owner (-1)
> > scanbd: Name Error (Connection ":1.18" is not allowed to own the service
> > "de.kmux.scanbd.server" due to security policies in the configuration
> file)
> > scanbd: option[1] standard for device rts8891:libusb:001:006 not of type
> > BOOL|INT|FIXED|STRING|BUTTON. Skipping
> > scanbd: option[5] geometry for device rts8891:libusb:001:006 not of type
> > BOOL|INT|FIXED|STRING|BUTTON. Skipping
> > scanbd: option[10] enhancement for device rts8891:libusb:001:006 not of
> > type BOOL|INT|FIXED|STRING|BUTTON. Skipping
> > scanbd: option[20] sensors for device rts8891:libusb:001:006 not of type
> > BOOL|INT|FIXED|STRING|BUTTON. Skipping
> > scanbd: option[1] standard for device rts8891:libusb:001:006 not of type
> > BOOL|INT|FIXED|STRING|BUTTON. Skipping
> > scanbd: option[5] geometry for device rts8891:libusb:001:006 not of type
> > BOOL|INT|FIXED|STRING|BUTTON. Skipping
> > scanbd: option[10] enhancement for device rts8891:libusb:001:006 not of
> > type BOOL|INT|FIXED|STRING|BUTTON. Skipping
> > scanbd: option[20] sensors for device rts8891:libusb:001:006 not of type
> > BOOL|INT|FIXED|STRING|BUTTON. Skipping
> > scanbd: option[1] standard for device rts8891:libusb:001:006 not of type
>

Re: [sane-devel] SANE automation setup?

[sane-devel] SANE needs a GUI like CUPS's 'system-config-printer' to manually add a network scanner.

Re: [sane-devel] SANE automation setup?

Re: [sane-devel] SANE automation setup?

4 matches

Site Navigation

Mail list logo

Footer information