[sane-devel] Help debugging avision backend

[James Klaas]

I am running Debian 8 (Jessie) and when I attempt to use "ADF Duplex" on my
HP8250 I get a segmentation fault.

I was running sane-utils 1.0.24-8+deb8u1 and had read on the list of the
many improvements in 1.0.25, so I got the source package for Debian Stretch
which is 1.0.25-2 and built and installed the debs. I've since built and am
running 1.0.27.

I've captured an strace as follows:

strace scanimage --source "ADF Duplex" -b > strace.out 2>&1

I also have some debugging output from when I was testing it in 1.0.25 from
the backend.

It creates an out1.pnm and an "avision-rear-9Izcwz" file that appears to
have image data in it, but isn't an image file.

I've created a bug report in the sane project on alioth, but it hasn't seen
any traffic since I created it over a year ago.

This seems like it could be a simple fix (off by one error sort of thing),
but I don't have any idea how to debug it. I would be happy to do some of
the work needed to debug it but I would need some help.
-- 
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] Problems Connecting to scanner over network

[James Klaas]

I don't see the net backend in your scanimage output. Here's mine:

scanimage -L
device `avision:libusb:003:047' is a Hewlett-Packard ScanJet 8200 flatbed
scanner
device `net:localhost:avision:libusb:003:047' is a Hewlett-Packard ScanJet
8200 flatbed scanner

Make sure you have the networking set up correctly in saned.conf which
should just be an access list.

I have the following (names changed to protect the innocent):

127.0.0.1
localhost
192.168.1.0/24
localdomain.home.

[2002:7f00:1::]
[2002:c0a8:400::]/24

You will want to have your local IP space and maybe your local domain name.

As is mentioned elsewhere, be very conscious of your sane network access
from the internet. If you have real routed IPs for your local network be
sure to ACL them off from the rest of the world in addition to using this
list.

James

On Sat, Jul 8, 2017 at 11:31 AM, Anunay Jain  wrote:

> I  cannot access my scanner (which is detected locally but not) over
> network
> The ports are open and sane-ports is listening.
> I have already done all the configs needed. and consulted them with
> several tutorials online.
> My sane client (which is on Windows ) i.e. SwingSane connects to ip but
> does not detect my scanner,
> While locally the scanner detect as a device.(and works)
>
> scanimage -L
>
>> `hpaio:/usb/HP_LaserJet_M1005?serial=KJ314YS' is a Hewlett-Packard
>> HP_LaserJet_M1005 all-in-one device
>> `hpljm1005:libusb:001:006' is a Hewlett-Packard LaserJet M1005
>> multi-function peripheral
>
>
> I have also tried multiple clients but all give same problems.
>
> Host SANE version: scanimage (sane-backends) 1.0.24; backend version 1.0.24
> Host OS: Raspbian OS 4.4.50 (Debian 8.0)
> Client: Windows 10, SwingSane
>
> --
> sane-devel mailing list: sane-devel@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>  to sane-devel-requ...@lists.alioth.debian.org
>
-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

[sane-devel] scanadf on HP 8250 for "ADF Duplex" causes segfault

[James Klaas]

I am running Debian 8 (Jessie) and when I attempt to use the Duplex on my
HP8250 I get a segmentation fault.

I was running sane-utils 1.0.24-8+deb8u1 and had read on the list of the
many improvements in 1.0.25, so I got the source package for Debian Stretch
which is 1.0.25-2 and built and installed the debs.

If I run 'scanadf --source="ADF Duplex"', the scanner pulls in the first
page, scans it the top, flips the page over, appears to scan it. then dies
with the message:

Scanned document image-0001
Segmentation fault (core dumped)

If I run scanadf on the machine the scanner is attached to, there's a dmesg:

[517673.237090] scanadf[26462]: segfault at 0 ip 7f610e255480 sp
7f610391ac10 error 4 in libc-2.19.so[7f610e1eb000+1a2000]

If I run scanadf remotely, I get the following in dmesg:

[518945.47] saned[2623]: segfault at 0 ip 7f937d6c8480 sp
7f9376fe6bd0 error 4 in libc-2.19.so[7f937d65e000+1a2000]

I captured an strace of running scanadf if that will be of help.

Running the ADF for just one side (scanadf --source="ADF Front") seems to
work pretty flawlessly.

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

[sane-devel] Sane stopped working with my HP Scanjet 8200

[James Klaas]

I was interested in trying gscan2pdf, so I installed it on one of my
computers at home to access my networked Scanjet 8200 sitting on my main
server. I was interested in trying to use the ADF. I've had hit or miss
(mostly miss) success with the ADF, but it's been long enough since I tried
it that I thought there would be some improvement.

Of course, I forgot that I left a document on the bed, but it shouldn't
have interfered with the ADF. In any case, the ADF "jammed" and saned
became wedged on the server. That's usually bad news since it sometimes
requires me to restart the whole server since often the USB stuff seems to
get wedged as well and merely unplugging and replugging the scanner in
doesn't always help.

Well, after fussing with it for a while, including uninstalling sane,
reinstalling sane (and sane-utils) learning how to get systemd working with
sane (since it's Debian 8), then going through and making sure the udev
pieces were in place, I seem to have lost all functionality.

Further troubleshooting. Running saned as root after turning off the
systemd running of it "systemctl stop saned.socket" followed by "systemctl
disable saned.socket", then running saned in debug mode.

# saned -d
[saned] main: starting debug mode (level 2)
[saned] saned (AF-indep+IPv6) from sane-backends 1.0.24 starting up
[saned] do_bindings: [0] bind failed: Address already in use
[saned] check_host: access by remote host: :::192.168.4.243
[saned] init: access granted to jklaas@:::192.168.4.243
[saned] process_request: bad status 22
[saned] bailing out, waiting for children...
[saned] bail_out: all children exited

Using gscan2pdf on a remote machine gives me the above.

sane-find-scanner sees the scanner when run either as root or as a user. If
I run "scanimage -L" while running saned in debug mode, it segfaults. If I
run "scanimage -L" when saned is run from systemd it doesn't segfault.
Looking at syslog it seems to start saned three times though.

I feel like I'm flailing here, so any direction would be helpful in further
troubleshooting this.

I also feel like I fight this battle almost every time I try to scan
something. It's pretty frustrating.

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