Re: [sane-devel] Crash in RHEL-7
On 2015-03-29, 23:33 GMT, m. allan noah wrote: Could you try upgrading to sane-backends development version from our git repository? Well, I hoped to get help to find actual fix for the problem. Matěj -- http://www.ceplovi.cz/matej/, Jabber: mceplatceplovi.cz GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC And religious texts are a bit like software standards, the interpretation is always the tricky and complicated bit. -- Alan Cox -- 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] Alternatives to hpaio for networked hp multifunction printers
Morning all, I'm trying to find an alternative to using the hpaio backend for our network printers (specifically M570DN), the current releases seem to rely on automatic detection and to do so seem to need to have the printer element installed via hp-setup to work which we've found to be less reliable than using standard IP printing, id like to configure hpaio manually however it doesn't seem to support this at all for network scanners (id be happy to be proven wrong on this!). So, has anyone come across and alternative to using hpaio for this ? Or even better, a way to manually configure the hpaio backend (it seems to ignore everything I’ve tried) Apologies if this has already been answered, I have had a search but I’ve not managed to find anything to answer my question. -- -- Mike Woods -- Motion Picture Solutions Ltd The Warehouse, 7a North End Rd, London, W14 8ST Main Office: +44 (0) 207 371 2396 (ext. 295), Desk: +44 (0) 20 3026 0529 -- 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] Raspbian Jessie - scanbd scripting issue
Am 30.03.2015 um 12:17 schrieb RainerF:
I tried to configure scanbd for an EPSON Perfection 1670 on a Raspbian
Jessie system. First I installed scanbd form the Raspbian package
repository, but this version seems to be compiled for sane backends
support only, which don't recognise button pressed events on my scanner.
Then I compiled scanbd from source
http://downloads.sourceforge.net/project/scanbd/releases/scanbd-1.4.2.tgz
with the old scanbutton backends support. That's working, but there are
two issues:
1) only two buttons invoke script execution
The scanner has four buttons, but currently scripts are only executed
for button 2 (copy) and button 3 (email).
Please try to hold down the button a little bit longer ...
I would like to use at least
the scan button (= button 4) as well. Within the syslog I can see that
also for button 1 and button 4 there is a reaction, just no script will
be executed. In scanbd.conf I noticed two kind of checks for button
pressed event handling, one, where a string change is evaluated, the
other, where an integer value changes.
The scanbuttond backend can only check for presses, not for specific
values. So, you shouldn't have to define a trigger-value-change.
Might this be misconfigured?
How can I check, which string has been send from the scanbuttond backend?
It must be in the logs (like the other button presses you receive ...).
Remark: the button numbering seems to be in reverse order, for button 3
is labeled with a printer icon, button 2 with a letter icon.
The backend places names on the button mumers: you can change it if you
want to since you are compiling from source:
const char* scanbtnd_button_name(const backend_t* backend, unsigned int
button) {
slog(SLOG_INFO, scanbtnd_button_name (%d), button);
assert(backend);
const char* backend_name = backend-scanbtnd_get_backend_name();
assert(backend_name);
slog(SLOG_INFO, scanbtnd_button_name, backend: %s, backend_name);
if (strcmp(snapscan, backend_name)) {
assert(button = 5);
switch(button) {
case 0:
return NULL;
break;
case 1:
return scan; // web;
break;
case 2:
return copy; // email;
break;
case 3:
return email; // copy;
break;
case 4:
return pdf; // send;
break;
case 5:
return stop;
break;
default:
return NULL;
break;
}
}
return NULL;
}
But I would suggest to adapt the snapscan.conf.
2) scanimage reports 'no scan device'
When I execute
scanimage -L or
sudo scanimage -L or
SANE_CONFIG_DIR=/usr/local/etc/scanbd/sane.d scanimage -L
Please read the ReadMe.txt: for the frontends don't use SANE_CONFIG_DIR,
thats only for saned.
Just use xsane or scanimage as usual, *but* adapt your
/etc/sane.d/dll.conf to include only the net-backend. And that must
point to the machine with scanbd/saned (e.g. localhost).
HTH,
Wilhelm
I always get the information that no scan device was found. I would have
expected something like
device `net:localhost:snapscan:libusb:001:004' is a EPSON …
which was the output, when scanbd was installed from the Raspbian
package repository. I thought, scanimage would request a scan via sane
port 6566, observed by scanbm, which would then forward the request to
the 'real' saned.
Am I wrong with this assumption?
I attached my configuration and a part of the syslog file.
Thanks in advance for any kind of assistance, which might help to solve
the above mentined issues.
Cheers, Rainer.
---
configuration files
/usr/local/etc/scanbd/scanbd.conf (only changes from default):
saned_env = { ”SANE_CONFIG_DIR=/usr/local/etc/scanbd/sane.d” }
scriptdir = /usr/local/etc/scanbd
device_insert_script = ”insert.script”
#include(scanner.d/avision.conf)
#include(scanner.d/fujitsu.conf)
#include(scanner.d/hp.conf)
#include(scanner.d/pixma.conf)
include(scanner.d/snapscan.conf)
#include(scanner.d/canon.conf)
sudo cp scanbd_dbus.conf /etc/dbus-1/system.d/
this file is copied as is from the integration folder
sudo nano /lib/systemd/system/scanbd.service (only changes from
default):
[Service]
ExecStart=/usr/local/sbin/scanbd –f –c /usr/local/etc/scanbd/scanbd.conf
Environment=SANE_CONFIG_DIR=/usr/local/etc/scanbd/sane.d
syslog (excerpt):
...
Mar 29 16:33:50 PING scanbd: /usr/local/sbin/scanbd: Iteration on dbus call
Mar 29 16:33:51 PING scanbd: /usr/local/sbin/scanbd: polling thread for
Perfection 1670 cancellation point
Mar 29 16:33:51 PING scanbd: /usr/local/sbin/scanbd: polling device
Perfection 1670
[sane-devel] Raspbian Jessie - scanbd scripting issue
I tried to configure scanbd for an EPSON Perfection 1670 on a Raspbian Jessie system. First I installed scanbd form the Raspbian package repository, but this version seems to be compiled for sane backends support only, which don't recognise button pressed events on my scanner. Then I compiled scanbd from source http://downloads.sourceforge.net/project/scanbd/releases/scanbd-1.4.2.tgz with the old scanbutton backends support. That's working, but there are two issues: 1) only two buttons invoke script execution The scanner has four buttons, but currently scripts are only executed for button 2 (copy) and button 3(email). I would like to use at least the scan button (= button 4) as well. Within the syslog I can seethat also for button 1 and button 4 there is a reaction, just no script will be executed. In scanbd.confI noticed two kind of checks for button pressed event handling, one, where a string change is evaluated, the other, where an integer value changes. Might this be misconfigured? How can I check, which string has been send from the scanbuttond backend? Remark: the button numbering seems to be in reverse order, for button 3 is labeled with a printer icon, button 2 with a letter icon. 2) scanimage reports 'no scan device' When I executeI always get the information that no scan device was found. I would have expected something likewhich was the output, when scanbd was installed from the Raspbian package repository. I thought, scanimage would request a scan via sane port 6566, observed by scanbm, which would then forward the request to the 'real' saned. Am I wrong with this assumption? I attached my configuration and a part of the syslog file. Thanks in advance for any kind of assistance,which might help to solve the above mentined issues. Cheers, Rainer. --- configuration files /usr/local/etc/scanbd/scanbd.conf (only changes from default): sudo cp scanbd_dbus.conf /etc/dbus-1/system.d/ this file is copied as is from the integration folder sudo nano /lib/systemd/system/scanbd.service (only changes from default): syslog (excerpt): -- View this message in context: http://sane.10972.n7.nabble.com/Raspbian-Jessie-scanbd-scripting-issue-tp19611.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
[sane-devel] Canon LiDE 120 git commit 128c8931b3
Hi, I noticed the commit for supporting this scanner appear a couple of weeks ago, and I recompiled and tested it today. Unfortunately it doesn't work. It's detected correctly. (the following is all using xsane, just using preview button) At 75dpi default, preview button does nothing - generic error message 300dpi, the scanner flashes for a while but doesn't move, then generic error message. 300dpi again (just in case it was warming up the first time) and it moves! and keeps moving, and keeps moving, until it gets to the end and is still moving (making a horrible noise) I pulled the USB, reconnected to a Windows PC and luckily it still works OK. The driver needs some adjustment though for sure! Thanks, Steven. -- 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] UsbSnoop for Canon DR-C225
Your log has the packets from two different devices in it, or something else strange is going on. What OS was this captured on? allan On Mon, Mar 30, 2015 at 9:15 PM, m. allan noah kitno...@gmail.com wrote: have you tried to use a recent sane-backends git snapshot? I would be interested to see a debugging log of sane trying to make a scan. allan On Mon, Mar 30, 2015 at 9:08 PM, Nicolas Marchildon nico...@marchildon.net wrote: Scanning a blank page at 150 dpi, 24 bit, simplex, using Canon's CaptureOnTouch and Usb Sniffer from http://www.pcausa.com/Utilities/UsbSnoop/ 58 MB log https://drive.google.com/file/d/0B1s3C34oDHi5ZzFqd3E4Nk5uekE/view -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org -- well, I stand up next to a mountain- and I chop it down with the edge of my hand -- well, I stand up next to a mountain- and I chop it down with the edge of my hand -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] UsbSnoop for Canon DR-C225
have you tried to use a recent sane-backends git snapshot? I would be interested to see a debugging log of sane trying to make a scan. allan On Mon, Mar 30, 2015 at 9:08 PM, Nicolas Marchildon nico...@marchildon.net wrote: Scanning a blank page at 150 dpi, 24 bit, simplex, using Canon's CaptureOnTouch and Usb Sniffer from http://www.pcausa.com/Utilities/UsbSnoop/ 58 MB log https://drive.google.com/file/d/0B1s3C34oDHi5ZzFqd3E4Nk5uekE/view -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org -- well, I stand up next to a mountain- and I chop it down with the edge of my hand -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
