Quoting Dave Stevens :
> Is this the right list for help with scanner problems?
--snip--
> have installed xsane. When I run it I get a very brief flash of a text box in
> the middle of my screen which then vanishes, leaving this text in
> the terminal
> window. I haven't any idea where to proc
Scanner is on a USB connection.
USB ID: 0x04a9/0x2214
Status: Unsupported
Comment: GL841 based, to be added to genesys backend
sane page says my Canoscan lide 80 is not supported
http://www.sane-project.org/unsupported/canon-lide-80.html
On that same page, however, it says that "this scanner ma
On Thu, 20 Mar 2008 17:56:35 -0400
"m. allan noah" wrote:
> we dont need to contact them to know that. if they cannot handle the
> default device name, they will return an error message to the hal
> callout, which will not show the device. hence, those users will have
> to run a standard program
Alessandro Zummo wrote:
> so we should maybe first list the proprietary backends and
> then try to find a contact point for each one of them.
>
> so we can at least check that we are not breaking anything.
Unfortunately there are some backends that aren't maintained past the
commercial life
Hello,
> Guillaume Gastebois schrieb:
>> Hello,
>>
>> Pierre Willenbrock a ?crit :
>>> Guillaume Gastebois schrieb:
>>> > Hello,
>>> >
>>> > You can find attached a patch which works like my original code (with
>>> > different contrast and calibration between 2 scans...).
>>> >
>>> > I remo
"Geoff Lane" wrote:
I know this stuff is pretty non-obvious when you don't know how the
underlying API and system work, so I'm going to explain a bit of it,
hopefully this can help as a reference or something.
> geoff at challenger:~$ saned -d1
> [saned] main: [1] bind failed: Address alread
On Thu, 20 Mar 2008 22:21:30 +0100
Julien BLACHE wrote:
>
> > what we are talking about will not break those backends, they just
> > wont work immediately with HAL, just like all the weird PP scanners.
>
> ... this point. If the people proposing the HAL integration and stuff
> today claim to ca
"m. allan noah" wrote:
Hi,
> in one mail you say that we cannot use this solution because of
> external backends, in this mail, you call them proprietary shit.
Two unrelated things. Proprietary backends are crap, all of them with
no exception.
But fact is, quite a lot of desktop users have no
A non-text attachment was scrubbed...
Name: 03_snapscan_usb_ftok_fix.dpatch
Type: text/x-patch
Size: 4953 bytes
Desc: snapscan ftok() patch respin
Url :
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080320/2a0d1437/attachment.bin
Guillaume Gastebois schrieb:
> Hello,
>
> Pierre Willenbrock a ?crit :
>> Guillaume Gastebois schrieb:
>> > Hello,
>> >
>> > You can find attached a patch which works like my original code (with
>> > different contrast and calibration between 2 scans...).
>> >
>> > I removed controversed com
Alessandro Zummo wrote:
Hi,
> btw, do we have a list of proprietary backends and frontends?
Frontends, we don't care, and backends, no, not really. Every other
day we run into some new proprietary shit. Sometimes we find that a
manufacturer developed a GPL backend, months ago.
Fact is, manufa
"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.
On Thu, 20 Mar 2008 20:21:39 +0100
Julien BLACHE wrote:
>
> Why? Simply because it's what common sense dictates, and because when
> it comes to proprietary backends, you'll find a lot of desktop users
> have no other choice than running the Samsung driver or the Brother
> driver, to only name th
?tienne Bersac wrote:
Hi,
> Right. Considering that HAL currently support usb, scsi and ieee1394, it
> makes sens to have a common scanner naming policy :
>
> * USB = ":libusb::"
> * SCSI = ":"
> * IEEE1394 = ":?"
Sorry to tell you, but a quick reality check reveals that this
abel deuring wrote:
Hi,
> That is one step too far -- we should get an agreement about the basic
> stuff first ;) But the HAL callout could also mess with dll.conf and
I hope you're not suggesting modifying a config file, because that's a
big no-no. It's not really clear what you mean with that
Hello,
Pierre Willenbrock a ?crit :
> Guillaume Gastebois schrieb:
> > Hello,
> >
> > You can find attached a patch which works like my original code (with
> > different contrast and calibration between 2 scans...).
> >
> > I removed controversed comments (sorry).
>
> Thanks for the patch.
Hello,
Pierre Willenbrock a ?crit :
> Guillaume Gastebois schrieb:
> > Hello,
> >
> > You can find attached a patch which works like my original code (with
> > different contrast and calibration between 2 scans...).
> >
> > I removed controversed comments (sorry).
>
> Thanks for the patch.
OT WORK whereas openbsd-inetd
WORKED FINE.
Geoff Lane
-- Welwyn Hatfield Computer Club
-- www.whcc.co.uk
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080320/906d76bc/attachment-0001.htm
On 3/20/08, Alessandro Zummo wrote:
> On Thu, 20 Mar 2008 22:21:30 +0100
>
> Julien BLACHE wrote:
>
> >
>
> > > what we are talking about will not break those backends, they just
> > > wont work immediately with HAL, just like all the weird PP scanners.
> >
> > ... this point. If the people p
in one mail you say that we cannot use this solution because of
external backends, in this mail, you call them proprietary shit.
what we are talking about will not break those backends, they just
wont work immediately with HAL, just like all the weird PP scanners.
allan
On 3/20/08, Julien BLACHE
Is this the right list for help with scanner problems?
I have been given an Agfa SnapScan scanner, claimed to be in working order with
Windows XP. I've connected it to my usb hub and so to my Fedora F7 x86_64 box. I
have installed xsane. When I run it I get a very brief flash of a text box in
the
===
== Neuer Eintrag
===
---
-- Formular: 'adddev'
---
1. Your email address:
'ofspibdx'
2. Manufacturer (e.g. "Mustek"):
if you corrected the /usr/local/lib line to not have sane in it, then
ran ldconfig, i dont know. reconfigure/make/install over top of your
system copy.
allan
On 3/20/08, Martin wrote:
>
> Hi Allan, here the output from this, SANE_DEBUG_DLL=4 xsane 2>dll.log
> I looked at it quickly and it is n
1200 scanner working using,
>> >> >>
>> >> >> As a normal user I can scan it:
>> >> >> $ /usr/local/bin/scanimage
>> >> --device-name=gt68xx:/dev/usb/scanner0 --mode
>> >> >> Color --resolution 600 > aaa.pnm
>>
SANE_DEBUG_DLL=4 xsane 2>dll.log
dll.log should show which libraries it is loading.
allan
On 3/20/08, Martin wrote:
>
> I tried $ ldconfig
> but still getting "invalid argument" error.
>
> Thanks for taking the time to help resolve this for me.
> I'm open to more ideas, thanks.
> Martin
>
; >> --device-name=gt68xx:/dev/usb/scanner0 --mode
>> >> >> Color --resolution 600 > aaa.pnm
>> >> >>
>> >> >> I can open up the file in Gimp and save it as aaa.jpg file format:
>> >> >> $ gimp aaa.pnm
>> >> >>
>> >> >> But...
>> >> >> when trying to execute the xsane command,
>> >> >>
>> >> >> $ xsane gt68xx:/dev/usb/scanner0
>> >> >> or
>> >> >> $ xsane
>> >> >>
>> >> >> I get error message, >> Failed to open device
>> gt68xx:/dev/usb/scanner0:
>> >> >> Invalid argument.
>> >> >>
>> >> >> Any ideas would be greatly appreciated, thanks.
>> >> >>
>> >>
>>
>>
>
>
>
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080320/4c26f6d8/attachment.htm
you are going to be around to fix it, so why wait? :)
allan
On 3/19/08, stef wrote:
> Le Friday 14 March 2008 15:01:06 stef, vous avez ?crit :
>
> > Hello,
> >
> > I have finished a new backend for rts8891 based scanner such as HP
> 4470c
> > and Umax Astra 4400.
> > It fe
try /usr/local/lib instead. and you might have to run ldconfig afterwards
allan
On 3/20/08, Martin wrote:
> I changed the file /etc/ld.so.conf , to look at "/usr/local/lib/sane"
> /usr/kerberos/lib
> /usr/X11R6/lib
> /usr/local/lib/sane
> /usr/lib/qt-3.1/lib
>
> but the command $ xsane gt6
I changed the file /etc/ld.so.conf , to look at "/usr/local/lib/sane"
/usr/kerberos/lib
/usr/X11R6/lib
/usr/local/lib/sane
/usr/lib/qt-3.1/lib
but the command $ xsane gt68xx:/dev/usb/scanner0
still errors out with >> "Failed to open device
gt68xx:/dev/usb/scanner0: Invalid argument."
m. allan
29 matches
Mail list logo
