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
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
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
Hi all,
Debian's "hardware wanted" web page says that the SANE maintainers are
looking for hardware donations of scanners related to bugs filed by
Debian users about support for their scanners in SANE. Is this hardware
request still useful or should the web team remove it from the website?
https:
Dear SANE developers,
I have got a multi-function color laser printer and scanner KONICA - MINOLTA
magicolor 1680MF. There is a couple of owners of this one on the Internet
looking for scanner driver (printing is easy possible) without success.
I found a magicolor backend
http://www.sane-proj
> I did not verify if it actually works but I think for you
>
>
> xsane pixma:04A92775_1144T3603236
>
> should (hopefully) work.
>
>
> Kind Regards
> Johannes Meixner
Yes. This did indeed work, once I resolved the LD paths problem. Doing
this automatically selects my scanner so I don't have to sel
Thanks so much for the information. You are exactly right. Fedora20_x86
installed sane libs from the repos in /usr/lib64. When I compiled from
git, sane backends libs were installed in /usr/local/lib/.
The path to the new scanimage binary was already first in the path:
/usr/local/bin. So, the fix
Hello,
On Oct 21 10:25 tx wrote (excerpt):
I don't know of anyway to specify the device on the command line
when using xsane
My xsane man page reads:
---
SYNOPSIS
xsane ... [devicename]
DESCRIPTION
...
To access an ava
Sounds like you have two copies of sane-backends (and hence,
scanimage) installed. If you call the replacement copy of scanimage,
it will default to using the replacement libs. You will need to setup
your ld paths to load the replacement first. I continue to be
surprised that distro's do this- put
Thanks for the link. It contains some good info. Actually, I've been able
to run scanimage as a regular user after adding the user to the "lp"
group. I do have to specify the device as a command line argument.
My current problem is that I can't use SANE frontend GUIs. Xsane and its
variants are no
Hello,
On Oct 20 21:39 tx wrote (excerpt):
I am now able to scan as root
...
I guess my issue now is one of permissions.
I did not read all the details in this mail thread but
perhaps the section about "scanner access permissions" in
http://en.opensuse.org/SDB:Configuring_Scanners
might pro
11 matches
Mail list logo
