Re: [sane-devel] Saned and root privileges ????

On 03/10/2018 12:23 PM, ToddAndMargo wrote: On 03/10/2018 09:22 AM, Andrew Goodbody wrote: On 10/03/18 11:17, ToddAndMargo wrote: On 03/10/2018 03:06 AM, Andrew Goodbody wrote: On 10/03/18 04:59, ToddAndMargo wrote: On 03/09/2018 12:53 PM, ToddAndMargo wrote: Hi All, Okay, now this is "sc

Re: [sane-devel] Saned and root privileges ????

one more: $ grep lp /etc/group lp:x:7:saned -- 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] Saned and root privileges ????

On 03/10/2018 09:22 AM, Andrew Goodbody wrote: On 10/03/18 11:17, ToddAndMargo wrote: On 03/10/2018 03:06 AM, Andrew Goodbody wrote: On 10/03/18 04:59, ToddAndMargo wrote: On 03/09/2018 12:53 PM, ToddAndMargo wrote: Hi All, Okay, now this is "scary". Both xsane and Simple Scan work locall

Re: [sane-devel] Saned and root privileges ????

On 10/03/18 11:17, ToddAndMargo wrote: On 03/10/2018 03:06 AM, Andrew Goodbody wrote: On 10/03/18 04:59, ToddAndMargo wrote: On 03/09/2018 12:53 PM, ToddAndMargo wrote: Hi All, Okay, now this is "scary". Both xsane and Simple Scan work locally. I can not get saned to work, UNLESS, I edit

Re: [sane-devel] Saned and root privileges ????

On 03/09/2018 12:53 PM, ToddAndMargo wrote: Hi All, Okay, now this is "scary". Both xsane and Simple Scan work locally. I can not get saned to work, UNLESS, I edit /etc/group and add the following to root root:x:0:saned Without it, I get $ xsane net:localhost:epkowa:interpreter:001:007 Acce

[sane-devel] Saned and root privileges ????

Hi All, Okay, now this is "scary". Both xsane and Simple Scan work locally. I can not get saned to work, UNLESS, I edit /etc/group and add the following to root root:x:0:saned Without it, I get $ xsane net:localhost:epkowa:interpreter:001:007 Access to resource has been denied Now what am I

[sane-devel] Saned denies access

Hi, I followed the instructions in this tutorial https://help.ubuntu.com/community/Sa...ane.d+tutorial to set up a network scanner. Everything should be set as needed. However, when I open xsane on a

Re: [sane-devel] saned@service environment question

On Wed, 2017-12-06 at 20:27 +0900, Olaf Meeuwissen wrote: > Hi, > > Apologies for the belated reply. > > ToddAndMargo writes: > > > On 11/25/2017 01:09 AM, Olaf Meeuwissen wrote: > > > Hi ToddAndMargo, > > > > > > ToddAndMargo writes: > > > > > > > Dear list, > > > > > > > > In the man page,

Re: [sane-devel] saned@service environment question

Hi, Apologies for the belated reply. ToddAndMargo writes: > On 11/25/2017 01:09 AM, Olaf Meeuwissen wrote: >> Hi ToddAndMargo, >> >> ToddAndMargo writes: >> >>> Dear list, >>> >>> In the man page, the script for saned@.service shows: >> >> # OK, you are reading the documentation, just rather sel

Re: [sane-devel] saned@service environment question

On 11/25/2017 01:09 AM, Olaf Meeuwissen wrote: Hi ToddAndMargo, ToddAndMargo writes: Dear list, In the man page, the script for saned@.service shows: # OK, you are reading the documentation, just rather selectively ;-) Environment=SANE_CONFIG_DIR=/etc/sane.d # If you need to debug your co

Re: [sane-devel] saned@service environment question

Hi ToddAndMargo, ToddAndMargo writes: > Dear list, > > In the man page, the script for saned@.service shows: # OK, you are reading the documentation, just rather selectively ;-) > Environment=SANE_CONFIG_DIR=/etc/sane.d > # If you need to debug your configuration uncomment the next line and > #

[sane-devel] saned@service environment question

Dear list, In the man page, the script for saned@.service shows: Environment=SANE_CONFIG_DIR=/etc/sane.d # If you need to debug your configuration uncomment the next line and # change it as appropriate to set the desired debug options # Environment=SANE_DEBUG_DLL=255 SANE_DEBUG_BJNP=5 https://b

Re: [sane-devel] Saned systemd issues

On 11/18/2017 02:48 AM, ToddAndMargo wrote: Hi All, Scientific Linux 7.4 (RHEL Clone based on CentOS) # rpm -qa sane-backends sane-backends-1.0.24-9.el7.x86_64 I can start /usr/sbin/saned from the command line: /usr/sbin/saned -a saned -d128; echo $?; ps ax | grep -i [s]aned 0 29857 ?   

Re: [sane-devel] saned not running without -d

AFAIK, no. Loglevel is only define using -s or -d. Both enable debug mode which exits after first connection. The next sane release will change -d behavior, and "quit after first connection" will only be enabled if explicitly set (-o|--once). You could temporarily build from unstable source (until

[sane-devel] saned not running without -d

root@raspberrypi:~:x86$ saned -d256 [saned] main: starting debug mode (level 256) [saned] read_config: searching for config file [saned] read_config: done reading config [saned] saned (AF-indep+IPv6) from sane-backends 1.0.24 starting up [saned] do_bindings: trying to get port for service "sane-por

Re: [sane-devel] Saned systemd issues

On 11/18/2017 02:48 AM, ToddAndMargo wrote: Note that I can use the name saned\@.service name due to a very long standing bug: that should have been "can not" :'( -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-deve

[sane-devel] Saned systemd issues

Hi All, Scientific Linux 7.4 (RHEL Clone based on CentOS) # rpm -qa sane-backends sane-backends-1.0.24-9.el7.x86_64 I can start /usr/sbin/saned from the command line: /usr/sbin/saned -a saned -d128; echo $?; ps ax | grep -i [s]aned 0 29857 ?Ss 0:00 /usr/sbin/saned -a saned -d128

Re: [sane-devel] Saned Tutorial is not correct -

Hi Louis, Louis Lagendijk writes: > On Thu, 2017-11-09 at 20:53 +0900, Olaf Meeuwissen wrote: >> Hi Alvaro, >> >> Simon Matter writes: >> (that you wrote) >> > > The mistake is also in the man pages: >> > > >> > > using Ubuntu 16.04: man saned >> > > >> > > excerpt start: >> > > >> > > SYSTEMD C

Re: [sane-devel] Saned Tutorial is not correct -

On Thu, 2017-11-09 at 20:53 +0900, Olaf Meeuwissen wrote: > Hi Alvaro, > > Simon Matter writes: > (that you wrote) > > > The mistake is also in the man pages: > > > > > > using Ubuntu 16.04: man saned > > > > > > excerpt start: > > > > > > SYSTEMD CONFIGURATION > > >for systemd we need

Re: [sane-devel] Saned Tutorial is not correct -

Hi Alvaro, Simon Matter writes: (that you wrote) >> The mistake is also in the man pages: >> >> using Ubuntu 16.04: man saned >> >> excerpt start: >> >> SYSTEMD CONFIGURATION >>for systemd we need to add 2 configuation files in >> /etc/systemd/system. <--

Re: [sane-devel] Saned Tutorial is not correct -

> The mistake is also in the man pages: > > using Ubuntu 16.04: man saned > > excerpt start: > > SYSTEMD CONFIGURATION >for systemd we need to add 2 configuation files in > /etc/systemd/system. < This should > be > /etc/systemd I'm not sure but at lea

Re: [sane-devel] Saned Tutorial is not correct -

The mistake is also in the man pages: using Ubuntu 16.04: man saned excerpt start: SYSTEMD CONFIGURATION for systemd we need to add 2 configuation files in /etc/systemd/system. < This should be /etc/systemd The first file we need to add here

Re: [sane-devel] Saned Tutorial is not correct -

Just to be sure we are clear: the tutorial mentioned in this thread is on the Ubuntu Wiki and it is written by the community. You could create an account on the Ubuntu Wiki and propose them a change to this wiki to improve its content. It will be really help for others indeed. Thanks for checki

Re: [sane-devel] Saned Tutorial is not correct -

We are not the authors of the tutorial with the error. allan On Mon, Nov 6, 2017 at 10:29 PM, Alvaro Gil wrote: > Hi, the saned tutorial is not correct on this page: > https://help.ubuntu.com/community/SaneDaemonTutorial > > Lots of people are having this issue: > https://bugs.launchpad.net/ubun

[sane-devel] Saned Tutorial is not correct -

Hi, the saned tutorial is not correct on this page: https://help.ubuntu.com/community/SaneDaemonTutorial Lots of people are having this issue: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1577137 I posted the fix to post #32 --- The problem is the documentation is

Re: [sane-devel] saned does not find hpaio scanner [Fwd: madd...@debian.org]

Hello, the following message¹ is now 6 months without a response, and the problem is unsolved. ¹) https://lists.alioth.debian.org/pipermail/sane-devel/2016-March/034413.html What does it mean? Is sane dead? - Forwarded message from martin f krafft - Date: Sun, 13 Mar 2016 12:36:02 +01

[sane-devel] saned bind failed. adress already in use

Hello List, I've a problem that saned, which worked good on ver 1.0.24?, after the latest updates failed to bind on the IP-Adresses given and used succesfully before. My system (server): Ubuntu 14.04 LTS IP: 192.168.2.10 SANE(d): 1.0.25/26-git Connected Scanner: Canon Maxify MB2050 Attached the

Re: [sane-devel] saned does not find hpaio scanner

I traced the problem to https://sourceforge.net/p/hplip/mailman/hplip-devel/thread/46a1257e.5060...@cab.cnea.gov.ar/ tl;dr: hplip changed and now the hpaio backend no longer ignores the local_only flag. In the past, saned/hpaio was able to access network printers, even though saned asked it to

[sane-devel] saned does not find hpaio scanner

Hey, We have a scanner available through a network and since we wanted to avoid having to install the hplip drivers on all workstations, we thought we'd employ saned to make the scanner available on the network. This worked fine until we upgraded to Debian jessie / sane 1.0.24 (from 1.0.22). Now

Re: [sane-devel] saned option handling changes (was Re: [PATCH v4 1/5] saned: parse standalone args in main())

Matteo Croce writes: > Hi Olaf, > > great, but I think that commit 45e66aee is wrong because it's > shadowing the global variable 'bind_addr'. My bad. > Also there is no need to initialize it to NULL because static > variables are always set to 0. I write a lot of C++. There static variables

[sane-devel] saned option handling changes (was Re: [PATCH v4 1/5] saned: parse standalone args in main())

Hi Matteo, Matteo Croce writes: I was about to ping you about this ;-) I've pushed all your changes (plus a few nitpick changes) to Alioth's master. The only thing that is still missing now is an updated manual page. If you could take care of that, it'll be appreciated. > [...snip...] Hope t

Re: [sane-devel] [saned] do_bindings: [0] bind failed: Address already in use

Hi Allan And thanks for this. Makes sense and feel daft for not having thought of it. Tho", not certain saned was called or running by xinetd. Will check it tomorrow if kids allow. Thanks for advice Andy Sent from my iPhone > On 21 Oct 2014, at 20:35, m. allan noah wrote: > > if you ha

Re: [sane-devel] [saned] do_bindings: [0] bind failed: Address already in use

if you have configured inetd to listen on the sane port, you cannot then also start saned in debug mode, where it also tries to listen on that port. Either stop inetd during your testing, or don't start saned directly (inetd will do it for you) allan On Tue, Oct 21, 2014 at 3:21 PM, Andy Ody wro

[sane-devel] [saned] do_bindings: [0] bind failed: Address already in use

Hi ALL, Apologies for being a noob, but sort of struggling now. I'm trying to setup an old BT Homehub 2 router as a scanner server, and have ref lashed it with OpenWRT. I've installed Sane frontends and backends, and libs. >From the command line, the scanner shows up (an HP5590), and I can scan

[sane-devel] saned auf Alix

"Nils W." writes: > I Download the following driver on the Kodak Page > http://download.kodak.com/docimaging/drivers/LinuxSoftware_i1100_v2.2.tar.gz > and i opend this file and start the setup. this is actually for ubuntu > but the setup convert all files automaticly for debian. Since SANE doesn

[sane-devel] saned auf Alix

On Thu, Jan 23, 2014 at 10:04 PM, Mark Buda wrote: > "Nils W." writes: > I have a Kodak i1120 scanner and would like to scan with it on an Alix > PC with Debian. Debian is installed on the Alix and the scanner is also > installed and is found by "scanimage -L". I would like, though, to scan > fro

[sane-devel] saned auf Alix

I Download the following driver on the Kodak Page http://download.kodak.com/docimaging/drivers/LinuxSoftware_i1100_v2.2.tar.gz and i opend this file and start the setup. this is actually for ubuntu but the setup convert all files automaticly for debian. after the driver installation i installed th

[sane-devel] saned auf Alix

Hallo Ich habe einen Kodak i1120 Scanner und w?rde gerne mit diesem an einem Alix PC mit Debian scannen. Auf dem Alix das Debian ist installiert und der Scanner ist auch installiert und wird bei "scanimage -L" gefunden Ich w?rde aber gerne ohne X Server nur auf Kosolen ebene Scannen. Software daf?r

[sane-devel] saned auf Alix

"Nils W." writes: English translation follows (Englische Uebersetzung folgt). > Hallo > Ich habe einen Kodak i1120 Scanner und w?rde gerne mit diesem an einem Alix > PC mit Debian scannen. > Auf dem Alix das Debian ist installiert und der Scanner ist auch installiert > und wird bei "scanimage

[sane-devel] saned on headless Centos 6 server

On Tue, 2013-09-03 at 13:47 +1200, Jon Chamberlain wrote: > Hi, > > I have configured an HP 1050 all-in-one on my Centos 6 server using > the manual instructions on the HPLIP site. > > So far I am able to print and scan locally, but have been unsuccessful > in getting it to be seen across the net

[sane-devel] saned on headless Centos 6 server

Hi, I have configured an HP 1050 all-in-one on my Centos 6 server using the manual instructions on the HPLIP site. So far I am able to print and scan locally, but have been unsuccessful in getting it to be seen across the network. net.conf, saned.conf and hp,conf have been setup and I have config

[sane-devel] saned problem on ubuntu: undefined symbol: sanei_w_init

On 03/08/2013 09:26, Jaakko Saarela wrote: > Hi, > > Thanks for your quick reply: > > 1. I downloaded sane-backends-4029979.tar.gz from git - configure, > make and make install > because previous one did not work then I tried: > 2. apt-get install sane > > But is it still using compiled version? W

[sane-devel] saned problem on ubuntu: undefined symbol: sanei_w_init

Does anyone know what has gone wrong in my sane installation. Distributor ID:Ubuntu Description:Ubuntu 12.04.2 LTS Release:12.04 Codename:precise scanimage -V scanimage (sane-backends) 1.0.24git; backend version 1.0.22 scanimage -L device `pixma:04A9173A_B3B91B' is a CANON Canon

[sane-devel] saned problem on ubuntu: undefined symbol: sanei_w_init

On 03/08/2013 08:50, Jaakko Saarela wrote: > Does anyone know what has gone wrong in my sane installation. > > Distributor ID:Ubuntu > Description:Ubuntu 12.04.2 LTS > Release:12.04 > Codename:precise > > scanimage -V > scanimage (sane-backends) 1.0.24git; backend version 1.0.22 > >

[sane-devel] saned

On (08:28 22/08/12), David Woodfall put forth the proposition: >On (21:51 21/08/12), m. allan noah put forth the >proposition: >>What foreign address is it listening for? Should be 0.0.0.0:* > >Yes it is. > >>allan >> >>On Tue, Aug 21, 2012 at 9:37 PM, David Woodfall >>wrote: >>>On (20:09 21/

[sane-devel] saned

On (21:51 21/08/12), m. allan noah put forth the proposition: >What foreign address is it listening for? Should be 0.0.0.0:* Yes it is. >allan > >On Tue, Aug 21, 2012 at 9:37 PM, David Woodfall wrote: >> On (20:09 21/08/12), m. allan noah put forth the >> proposition: >> >>> check that sane-p

[sane-devel] saned

On (20:09 21/08/12), m. allan noah put forth the proposition: >check that sane-port 6566 is listed in /etc/services, then run netstat >-an | grep 6566 to be sure that you are listening on that port. > >allan Ok that's got me a step closer. It now shows on the server as a network scanner, but not

[sane-devel] saned

On 21/08/12 20:49, Stef wrote: > On 21/08/2012 14:27, David Woodfall wrote: >> On 21/08/12 05:57, Stef wrote: >>> On 20/08/2012 23:47, David Woodfall wrote: I'm having a problem with saned via inetd. This is what used to work: /etc/inetd.conf: sane-port stream tcp nowait sa

[sane-devel] saned

What foreign address is it listening for? Should be 0.0.0.0:* allan On Tue, Aug 21, 2012 at 9:37 PM, David Woodfall wrote: > On (20:09 21/08/12), m. allan noah put forth the > proposition: > >> check that sane-port 6566 is listed in /etc/services, then run netstat >> -an | grep 6566 to be sure

[sane-devel] saned

On 21/08/2012 14:27, David Woodfall wrote: > On 21/08/12 05:57, Stef wrote: >> On 20/08/2012 23:47, David Woodfall wrote: >>> I'm having a problem with saned via inetd. This is what used to work: >>> >>> /etc/inetd.conf: >>> >>> sane-port stream tcp nowait saned.saned /usr/sbin/saned saned >>> sane

[sane-devel] saned

check that sane-port 6566 is listed in /etc/services, then run netstat -an | grep 6566 to be sure that you are listening on that port. allan On Tue, Aug 21, 2012 at 8:05 PM, David Woodfall wrote: > On 21/08/12 20:49, Stef wrote: >> >> On 21/08/2012 14:27, David Woodfall wrote: >>> >>> On 21/08/1

[sane-devel] saned

On 21/08/12 05:57, Stef wrote: > On 20/08/2012 23:47, David Woodfall wrote: >> I'm having a problem with saned via inetd. This is what used to work: >> >> /etc/inetd.conf: >> >> sane-port stream tcp nowait saned.saned /usr/sbin/saned saned >> sane stream tcp nowait saned.saned /usr/sbin/tcpd /usr/s

[sane-devel] saned

On 20/08/2012 23:47, David Woodfall wrote: > I'm having a problem with saned via inetd. This is what used to work: > > /etc/inetd.conf: > > sane-port stream tcp nowait saned.saned /usr/sbin/saned saned > sane stream tcp nowait saned.saned /usr/sbin/tcpd /usr/sbin/saned > > On the new server this no

[sane-devel] saned

I'm having a problem with saned via inetd. This is what used to work: /etc/inetd.conf: sane-port stream tcp nowait saned.saned /usr/sbin/saned saned sane stream tcp nowait saned.saned /usr/sbin/tcpd /usr/sbin/saned On the new server this no longer works. I thought it could be a permissions prob

[sane-devel] saned issue on Debian stable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Greetings, I'll cut to the chase. when run with debug, i get the following; [saned] main: starting debug mode (level 8) [saned] read_config: searching for config file [saned] read_config: done reading config [saned] saned (AF-indep+IPv6) from sane-b

[sane-devel] Saned not working any more in Lucid

Hello, On Nov 18 17:40 Lutz Andersohn wrote (shortened): > The syslog file on startup says that > "Bind failed (address already in use (errno = 98). service = saned" > followed by "Service saned failed to start and is deactivated." Another process is already using the same port which should be u

[sane-devel] Saned not working any more in Lucid

I was running saned just fine under Ubuntu Jaunty 64 bit and was able to scan across the network on an Epson Perfection 2580 scanner. After I upgraded to Lucid 64 bit the saned daemon fails to start. I have tried openusb-inetd and xinetd. The syslog file on startup says that "Bind failed (address a

[sane-devel] saned and xinetd

Hi, This does work when saned -d is started as user saned. So I guess the trouble must be somewhere else. Thanks anyway, Fred. m. allan noah wrote: > Two different users. Try to su to the saned user, and run the daemon > in debug mode there. If it does not work, then saned user does not > have

[sane-devel] saned and xinetd

Hi all, I'm trying to set up a shared scanner using saned to use it through my private network. While it works like a charm when started in debug mode (-d), I can't find my scanner (an HP PSC 1510) when stated through (x)inetd Here's my setup: The server (called server) has the scanner The clie

[sane-devel] saned and xinetd

ok, the user works, so the environment must be different. Is the scanner device owned by a group other than saned (maybe 'scanner')? If so, you might need to enable the 'groups' option in your xinetd config? Otherwise, you only get the default group... allan On Sun, Feb 8, 2009 at 9:53 AM, Fred.

[sane-devel] saned and xinetd

Two different users. Try to su to the saned user, and run the daemon in debug mode there. If it does not work, then saned user does not have perms to access the device. allan On Sun, Feb 8, 2009 at 9:25 AM, Fred. Oger wrote: > > Hi all, > > I'm trying to set up a shared scanner using saned to us

[sane-devel] Saned does not compile under Opensolaris

I am testing Sane under Opensolaris to see if the network extensions for the pixma backend work under Opensolaris. During the compilation I noticed that saned does not compile as OpenSolaris does not have getgrouplist(). There is a getgrouplist.c in openssh. Can we add that, or should we only in

[sane-devel] saned, Network Scanner, Automatic Document Feeder

Good news then, I've included this fix for next pixma CVS commit. BTW, my answers to your questions in the text below, I copy also the Sane-dev mailing list too, as those points regarding ADF are interesting: Le samedi 04 octobre 2008 ? 00:55 +0200, Pascal Seiler a ?crit : > Hey Nicolas, your gr

[sane-devel] saned, Network Scanner, Automatic Document Feeder

Ok, thank you very much. I'll be waiting for it. Pascal Nicolas wrote: > Have some presumptions on where this could come from, as ADF code in the > pixma backend isn't very "clear". > But before any change, I'd like to submit a newer version of the > backend, that should enhance ADF scanning (te

[sane-devel] saned, Network Scanner, Automatic Document Feeder

Have some presumptions on where this could come from, as ADF code in the pixma backend isn't very "clear". But before any change, I'd like to submit a newer version of the backend, that should enhance ADF scanning (tested on MX850 currently). I'll keep you posted when commit to CVS, as I've some o

[sane-devel] saned, Network Scanner, Automatic Document Feeder

BTW, this is how the log looks like when I to the same with source=flatbed. Maybe that helps. Pascal Nicolas wrote: > Yes, this is exactly what is needed, but looks like there's only a > single page scan here. > > Could you produce a same trace (but select a _small_ scan area for > smaller log

[sane-devel] saned, Network Scanner, Automatic Document Feeder

Hi Nicolas, I'm sure that this was a 2 page scan. However, I created a new log file as you proposed. It's much smaller and I left all the information in the log. This is the command I used: scanimage --mode=Color --source='Automatic Document Feeder' -y 5 -l 0 --resolution=300 -x 5 -t 0 --batch

[sane-devel] saned, Network Scanner, Automatic Document Feeder

Yes, this is exactly what is needed, but looks like there's only a single page scan here. Could you produce a same trace (but select a _small_ scan area for smaller log size) of a 2 page ADF scan with the issue you get. Note that I'll commit very soon some changes that have been tweaked with a MX

[sane-devel] saned, Network Scanner, Automatic Document Feeder

Strange. I did exactly the same as you did, and I get those lines from the backend (When I start Xsane from a client), which are inserted in the log you sent: [saned] process_request: waiting for request [saned] process_request: got request 1 [sanei_debug] Setting debug level of pixma to 10. [pix

[sane-devel] saned, Network Scanner, Automatic Document Feeder

Nicolas wrote: > - under the root account: > # export SANE_DEBUG_PIXMA=10 > - restart the saned daemon (or through inetd, or xinetd) Won't work if running through *inetd. If you can scan without issue running saned in debug mode, that indicates the pixma backend is doing something nasty, like w

[sane-devel] saned, Network Scanner, Automatic Document Feeder

Strange. I did exactly the same as you did, and I get those lines from the backend (When I start Xsane from a client), which are inserted in the log you sent: [saned] process_request: waiting for request [saned] process_request: got request 1 [sanei_debug] Setting debug level of pixma to 10. [pix

[sane-devel] saned, Network Scanner, Automatic Document Feeder

So you get this issue when pixma backend is called from saned, but not when called directly from scanimage. Could you get some logs from the backend. To get traces using saned, proceed like this (this is how I do): - stop the saned daemon (or inetd, xinetd if called by those) - under the root acc

[sane-devel] saned, Network Scanner, Automatic Document Feeder

Nicolas First of all, thanks for your quick answer. Unfortunately SANE_DEBUG_PIXMA gave absolutely no about at all. I then started scaned from the console with option -d128. This is the output I got: kangaroo:~# saned -d128 [saned] main: starting debug mode (level 128) [saned] saned (AF-indep+

[sane-devel] saned, Network Scanner, Automatic Document Feeder

So you get this issue when pixma backend is called from saned, but not when called directly from scanimage. Could you get some logs from the backend. To get traces using saned, proceed like this (this is how I do): - stop the saned daemon (or inetd, xinetd if called by those) - under the root a

[sane-devel] saned, Network Scanner, Automatic Document Feeder

I have configured a Canon PIXMA MX 310 (Printer/Scanner/FAX) on a Debian Etch server. SANE version is 1.1.0-cvs from 2008-09-30. When I try to scan multiple pages using the Automatic Document Feeder the jobs fails after the first page with the following error: scanimage: sane_start: Invalid ar

[sane-devel] saned -d6 OK saned fails [GishPuppy]

"m. allan noah" wrote: Hi, > see all those 'Address already in use' statements? something is > already listening on the port, perhaps inetd? Nah, it's the dual-stack effect, trying to bind on IPv4 after having bound successfully on an IPv6 interface with v4compat enabled. Perfectly fine, IOW.

[sane-devel] saned -d6 OK saned fails [GishPuppy]

On 18 Mar 2008 at 10:27, m. allan noah wrote: I have checked everything listed below and all looks fine. Inetutils-inetd is shown (Via ps -Af) running as ROOT What is puzzling me is the output of manually running saned with different values after the d flag, d5 and above and it works, less tha

[sane-devel] saned -d6 OK saned fails [GishPuppy]

see all those 'Address already in use' statements? something is already listening on the port, perhaps inetd? allan On Wed, Mar 19, 2008 at 10:53 AM, Geoff Lane wrote: > On 18 Mar 2008 at 10:27, m. allan noah wrote: > > I have checked everything listed below and all looks fine. > > Inetutils-i

[sane-devel] saned -d6 OK saned fails

On 16 Mar 2008 at 17:30, m. allan noah wrote: This USER and GROUPS setup is losing me a wee bit. I have followed the instructions as in the MAN pages, my inetd file showes the following line; stream tcp nowait saned.saned /usr/sbin/saned saned My scanner works fine on my host Linux computer an

[sane-devel] saned -d6 OK saned fails

On Tue, Mar 18, 2008 at 9:45 AM, Geoff Lane wrote: > On 16 Mar 2008 at 17:30, m. allan noah wrote: > > This USER and GROUPS setup is losing me a wee bit. > > I have followed the instructions as in the MAN pages, my inetd file showes > the following line; > > stream tcp nowait saned.saned /usr/

[sane-devel] saned -d6 OK saned fails

the -d flag causes saned to listen on port 6566 as the user that started it. otherwise, saned thinks it is being called from inetd, and so expects to get handed an already connected socket. the real question here is why does inetd not listen on 6566 for you. this is almost certainly an inetd confi

[sane-devel] saned -d6 OK saned fails

Using a network port scanner and a remote graphical scanner I cannot get either to show or connect to port 6566. If I then issue the command saned I again get no acknowledgement of port 6566 but if I issue saned -d6 my graphical scanner connects from a remote computer and my network port sc

[sane-devel] saned -d6 OK saned fails

Using a network port scanner and a remote graphical scanner I cannot get either to show or connect to port 6566. If I then issue the command saned I again get no acknowledgement of port 6566 but if I issue saned -d6 my graphical scanner connects from a remote computer and my network port sca

[sane-devel] Saned not launching at Boot

On 1 Mar 2008 at 19:47, m. allan noah wrote: I naievely thought that as I had saned.conf that saned was installed, it wasn't. I downloaded and installed it but still problems. If in saned.conf I alter the entry sane-port stream tcp nowait saned.saned /usr/sbin/saned saned and delete the .saned

[sane-devel] Saned not launching at Boot

i assume that you mean you needed to install inetd, not saned? anyway- check for group saned, and make sure it is the saned user's default group. beyond that, i dunno. allan On 3/3/08, Geoff Lane wrote: > On 1 Mar 2008 at 19:47, m. allan noah wrote: > > > I naievely thought that as I had saned

[sane-devel] Saned not launching at Boot

On 1 Mar 2008 at 19:47, m. allan noah wrote: This is my entry; ## netbios-ssn stream tcp nowait root/usr/sbin/tcpd /usr/sbin/smbd sane-port stream tcp nowait saned.saned /usr/sbin/saned saned > are you sure the xinetd or inetd (which ever your distro uses, i'm not > sure) is set

[sane-devel] Saned not launching at Boot

I have an Ubuntu (V7.10) Linux system loaded with a Hewlett Packard C5280 MFP connected, other XP laptops can access the printer fine. The scanner functions work fine on my Linux machine. I am having a few problems with saned, I have followed the advice in the MAN pages for setting up for netwo

[sane-devel] Saned not launching at Boot

are you sure the xinetd or inetd (which ever your distro uses, i'm not sure) is set to start at boot up? allan On 3/1/08, Geoff Lane wrote: > I have an Ubuntu (V7.10) Linux system loaded with a Hewlett Packard > C5280 MFP connected, other XP laptops can access the printer fine. The > scanner f

[sane-devel] saned/xinetd

what user did you use with saned -d? and this post comes to mind- http://lists.alioth.debian.org/pipermail/sane-devel/2002-September/004235.html allan 2008/2/27 Gregg Garza : > Sorry if this is not the right place to send this kind of problem. > > I have a small network of computers at home. I

[sane-devel] saned/xinetd

Sorry if this is not the right place to send this kind of problem. I have a small network of computers at home. I just got an Epson V200 scanner and have been mostly successful in getting it running with "iscan" and "xsane" frontends (using the avasys proprietary driver and plugin). I can run

[sane-devel] saned: Permission problem on Fedora 8, Deskjet_F300_series all-in-one

On 1/2/08, Nick Urbanik wrote: > Dear Folks, > > I am having problems setting up saned on Fedora 8: > $ grep sane /var/log/rpmpkgs > libsane-hpaio-2.7.7-6.fc8.i386.rpm > sane-backends-1.0.18-17.fc8.i386.rpm > sane-backends-devel-1.0.18-17.fc8.i386.rpm > sane-backends-libs-1.0.18-17.fc8.i386.rpm >

[sane-devel] saned: Permission problem on Fedora 8, Deskjet_F300_series all-in-one

Dear Folks, I am having problems setting up saned on Fedora 8: $ grep sane /var/log/rpmpkgs libsane-hpaio-2.7.7-6.fc8.i386.rpm sane-backends-1.0.18-17.fc8.i386.rpm sane-backends-devel-1.0.18-17.fc8.i386.rpm sane-backends-libs-1.0.18-17.fc8.i386.rpm sane-frontends-1.0.14-3.fc7.i386.rpm xsane-0.994-

[sane-devel] saned with network-backend hangs

Bjoern Franke schrieb: > Hello, > > I'm using sane 1.0.14 on a debian-etch server. saned is started by inetd > and is used with SaneTwain via network. It works fine, but after some > time the scanner (EPSON Stylus DX 4050) is not accessible any more. It > only works again after restarting the

[sane-devel] saned with network-backend hangs

Hello, I'm using sane 1.0.14 on a debian-etch server. saned is started by inetd and is used with SaneTwain via network. It works fine, but after some time the scanner (EPSON Stylus DX 4050) is not accessible any more. It only works again after restarting the server. Any ideas? TIA bjo -- I

[sane-devel] saned does not work with 2.6.23-rc9

On 03.10.2007 17:26, Joerg Platte wrote: > Am Mittwoch, 3. Oktober 2007 schrieb abel deuring: > >>> # sane-find-scanner will now attempt to detect your scanner. If the >>> # result is different from what you expected, first make sure your >>> # scanner is powered up and properly connected to

[sane-devel] saned does not work with 2.6.23-rc9

Am Mittwoch, 3. Oktober 2007 schrieb abel deuring: > > # sane-find-scanner will now attempt to detect your scanner. If the > > # result is different from what you expected, first make sure your > > # scanner is powered up and properly connected to your computer. > > > > [sanei_debug] Setting

[sane-devel] saned does not work with 2.6.23-rc9

On 03.10.2007 14:46, Joerg Platte wrote: > Am Mittwoch, 3. Oktober 2007 schrieb abel deuring: > Hi, > >> It is very weird that the SG_GET_SCSI_ID ioctl does not work: Could you >> check, if /dev/scanner -- should be a symlink -- indeed points to a >> device file of some SCSI device (ideally, to th

[sane-devel] saned does not work with 2.6.23-rc9

Am Mittwoch, 3. Oktober 2007 schrieb abel deuring: Hi, > It is very weird that the SG_GET_SCSI_ID ioctl does not work: Could you > check, if /dev/scanner -- should be a symlink -- indeed points to a > device file of some SCSI device (ideally, to the scanner's device file)? I wrote this udev rule

[sane-devel] saned does not work with 2.6.23-rc9

On 03.10.2007 10:27, Joerg Platte wrote: > Hi, > > today I updated the kernel on my Debian stable box to vanilla 2.6.23-rc9 and > now, saned (version 1.0.14-2) is unable to find my scanner. Here is the > strace output of sane-find-scanner: > > open("/proc/scsi/scsi", O_RDONLY) = 3 > fstat

[sane-devel] saned does not work with 2.6.23-rc9

Am Mittwoch, 3. Oktober 2007 schrieb Joerg Platte: Hi, this is the output of the same command invoked on 2.6.22.6 and with this kernel the scanner is found. open("/proc/scsi/scsi", O_RDONLY) = 3 fstat64(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE,

  1   2   3   >