[sane-devel] Error message with scanimage -L
Hi. I'm trying to use SANE to make my scanner work, but I'm getting this errors: cluca linux # scanimage -L No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). cluca linux # scanimage -L scanimage: hp-option.c:3710: hp_optset_fix_geometry_options: Assertion `tl_x && tl_y && br_x && br_y' failed. Aborted Some months ago, I was successfull in setting up sane, but now I'm finding difficulties. The scanner is a HP PSC1317. scanimage version is: cluca linux # scanimage --version scanimage (sane-backends) 1.0.15; backend version 1.0.15 I saw that someone else is having the same error, and found to see the output of this command; I can't understand anything but it seems not good the second one: cluca linux # sane-find-scanner -q found USB scanner (vendor=0x03f0 [hp], product=0x3f11 [psc 1310 series ]) at libusb:002:002 cluca linux # ls -l /proc/bus/ubs/002/002 ls: /proc/bus/ubs/002/002: No such file or directory Thank you for any help. Luca
[sane-devel] Error message with scanimage -L
On Tuesday 23 August 2005 16:47, Bertrik Sikken wrote: > This is weird. > You should get the same response when running the scanimage -L command > twice. Perhaps the first time, hotplug had not updated the USB > permissions yet. What kernel are you running? My kernel is 2.6.12-r6. I tried with some previous kernel as well but same results. Anyway, I continue to have these two output with calls to the scanimage -L, look: --- cluca linux # scanimage -L scanimage: hp-option.c:3710: hp_optset_fix_geometry_options: Assertion `tl_x && tl_y && br_x && br_y' failed. Aborted cluca linux # scanimage -L No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). cluca linux # scanimage -L scanimage: hp-option.c:3710: hp_optset_fix_geometry_options: Assertion `tl_x && tl_y && br_x && br_y' failed. Aborted cluca linux # scanimage -L No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). cluca linux # scanimage -L No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). cluca linux # scanimage -L scanimage: hp-option.c:3710: hp_optset_fix_geometry_options: Assertion `tl_x && tl_y && br_x && br_y' failed. Aborted cluca linux # scanimage -L No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). -- :-) It continue to change. > > Some months ago, I was successfull in setting up sane, but now I'm > > finding difficulties. The scanner is a HP PSC1317. scanimage version is: > > > > cluca linux # scanimage --version > > scanimage (sane-backends) 1.0.15; backend version 1.0.15 > > > > I saw that someone else is having the same error, and found to see the > > output of this command; I can't understand anything but it seems not good > > the second one: > > > > cluca linux # sane-find-scanner -q > > found USB scanner (vendor=0x03f0 [hp], product=0x3f11 [psc 1310 series ]) > > at libusb:002:002 > > cluca linux # ls -l /proc/bus/ubs/002/002 > > ls: /proc/bus/ubs/002/002: No such file or directory > > try /proc/bus/usb not /proc/bus/ubs Ok :-), sorry, this is what I get: cluca linux # sane-find-scanner -q found USB scanner (vendor=0x03f0 [hp], product=0x3f11 [psc 1310 series ]) at libusb:002:003 cluca linux # ls -l /proc/bus/usb/002/003 -rw-rw 1 root scanner 147 Aug 24 12:01 /proc/bus/usb/002/003 Is there something else I can try to make it work? Thanks. Luca
[sane-devel] Sonix SN9C101 and SN9C102 USB camera controllers - specifications
I have been told by the TWAIN people that this is the best place where to ask for the detailed specifications of the above chips. Any help would be much appreciated. Sonix does not respond to my emails and google does not help (there's a 12-page long datasheets, but it is not detailed enough to write a driver) Thanks, please answer to l.r...@tiscalinet.it
[sane-devel] Sonix SN9C101 and SN9C102 USB camera controllers - specifications
On Sat, 12 Jun 2004 01:31:59 + gerard klaver wrote: > On Fri, 2004-06-11 at 05:20, Luca wrote: > > I have been told by the TWAIN people that this is the best place > > where to ask for the detailed specifications of the above chips. > > Any help would be much appreciated. Sonix does not respond to my emails > > and google does not help (there's a 12-page long datasheets, but it is > > not detailed enough to write a driver) > > > > Thanks, please answer to l.r...@tiscalinet.it > > Depends what sort of driver you want to write, kernel module or SANE > backend. > > See also these links: > http://www.mnementh.co.uk/sonix/ > > and > http://sonix.sourceforge.net/ That's the unuseful thing I was talking about
[sane-devel] Problem with TRUST FLASTSCAN 19200 usb
Hi guys! I have installed sane for my scanner, using this # Trust Flat Scan USB 19200: override "artec-ultima-2000" vendor "Trust" model "Flat Scan USB 19200" firmware "gt680xfw.usb" firmware "/usr/share/sane/gt68xx/gt680xfw.usb" it the configuration file. Xsane start well, and the process of preview too, but the output is an image with some black and white bend. Any help? THX -- Utente Linux 373965 ICQ 54327636 Scopri le mie canzoni preferite su http://www.audioscrobbler.com/user/Doktoreas/
[sane-devel] Need help for buying a scanner..
Hi guys! Need to buy a scanner, 'couse my Trust has gone... I need full linux support and a price not more then 100 $. Thx Luca -- Utente Linux 373965 ICQ 54327636 Scopri le mie canzoni preferite su http://www.audioscrobbler.com/user/Doktoreas/
[sane-devel] Epson Perfection V700
I am using succesfully the Epson scanner in a medical environment so mainly using the transaprency adapter to store skull x-ray. Up to one year ago I was using the Epson 1680 Pro scanner with wonderful results. Due to the fact that this model is no more available I start using initially the 4990 Photo and actually the Perfection V700. The problem that I have is that with the transparency adapter selected the area available for the scanning process is limited respect to the flatbed selection: about 6 cm. are lost half on the right and half on the left side, giving available only the central part of the scanner. With the Epson 1680 Pro the whole are was available for the flatbed as well as for the transaprency adapter. Has anyone some solution to this problem or is it just a slip in the Epson frontend that could be solved? I appreciate any suggestion \\ - - // ( @ @ ) --oOOo--(_)--oOOo Clemente Luca Via Tavella di S. Andrea, 2/f I-33087 Pasiano di Pordenone (PN) - Italia Tel +39-0434-625373 - Fax +39-0434-610427 e-mail: luca.c...@zerobase.it ---O-- ( ) O ) / ( ) (_/ \ ( \_) -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20070314/a5d4aea8/attachment.htm From kitno...@gmail.com Wed Mar 14 14:32:35 2007 From: kitno...@gmail.com (m. allan noah) Date: Wed Mar 14 13:59:36 2007 Subject: [sane-devel] sending scanned to a remote SANE server In-Reply-To: <67658ecb.54bf101d.8199...@mail.e-integration.net> References: <67658ecb.54bf101d.8199...@mail.e-integration.net> Message-ID: <97246d0e0703140632m2b624355vabe96125fbb89...@mail.gmail.com> sorry tom- you'll get this twice. let me get this right- you want to connect the scanner to a local machine, and run your scanning program on that machine, but you want the output image file to be accessible on a second machine? you need the first machine to write the images onto a shared filesystem like nfs or smb, and have the second machine mount that fs. allan On 3/14/07, Tom Miller wrote: > How can I scanner an image through a local scanner that > attached to my desktop. and able to direct the scanimage > in the local desktop (running linux SANE) to send the > scanned image to a remote server that running Linux (SANE)? > > > Thanks inadvance, > > Tom > > > > > Original message > >Date: Sat, 10 Mar 2007 13:35:01 +0100 > >From: cgi-mai...@kundenserver.de > >Subject: [sane-devel] Formulardaten > >To: sane-devel@lists.alioth.debian.org > > > > > > > >=== > >== Neuer Eintrag > >=== > > > > > >--- > >-- Formular: 'adddev' > >--- > > > >1. Your email address: > > 'lkorts+s...@gmail.com' > >2. Manufacturer (e.g. "Mustek"): > > 'Canon' > >3. Model name (e.g. ScanExpress 1200UB): > > 'LiDe 600f' > >4. Bus type: > > 'USB' > >5. Vendor id (e.g. 0x001): > > '0x04a9' > >6. Product id (e.g. 0x0002): > > '0x2224' > >7. Chipset (e.g. lm9831): > > '' > >8. Comments (e.g. similar to Mustek 1234): > > 'Unit bought from Japan, Akihabara on March 10th, 2007 > > > >Using debian testing/unstable > >sane-find-scanner finds it but scanimage -L doesn't > > > >' > >9. Data (e.g. sane-find-scanner -v -v): > > ' CanoScan)> > >bLength 18 > >bDescriptorType 1 > >bcdUSB2.00 > >bDeviceClass 255 > >bDeviceSubClass 255 > >bDeviceProtocol 255 > >bMaxPacketSize0 64 > >idVendor 0x04A9 > >idProduct 0x2224 > >bcdDevice 0.00 > >iManufacturer 1 (Canon) > >iProduct 2 (CanoScan) > >iSerialNumber 0 () > >bNumConfigurations1 > > > > bLength 9 > > bDescriptorType 2 > > wTotalLength 32 > > bNumInterfaces 1 > > bConfigurationValue 1 > > iConfiguration 0 () > > bmAttributes 160 (Remote Wakeup) > > MaxPower 500 mA > > > > > > bLength9 > > bDescriptorType4 > > bInterfaceNumber 0 > > bAlternateSetting 0 > > bNumEndpoints 2 > > bInterfaceC
[sane-devel] Compiling problem 1.0.9pre1
Hi all, I'm trying to compiling sane backends 1.0.9pre1. I get the following error: abaton.c: In function `sane_abaton_exit': abaton.c:901: warning: cast discards qualifiers from pointer target type abaton.c:902: warning: cast discards qualifiers from pointer target type rm -f abaton-s.c ln ./stubs.c abaton-s.c ln: creating hard link `abaton-s.c' to `./stubs.c': Operation not permitted make[1]: *** [abaton-s.c] Error 1 I have Mandrake 8.1 with gcc 3.0.1. Can anyone help me ? Thanks in advance Luca
[sane-devel] HP5370c and sane
I'm trying to make the HP5370c work under my Mandrake Linux 8.1 distribution (kernel 2.4.18). I'm using Xsane 0.86 with Avision backend under sane 1.0.9pre1 (30 Aug. Version). My scanner is recognized as generic HP5370c. When I try to get the preview, the scanner moves just a bit but it doesn't scan the image inside, and the preview I can see is just random noise. It was the same under sane 1.0.8. I've tried different scan resolution. I can correctly use any other USB peripheral. Does anyone can help me ?? Thank you! luca
[sane-devel] Preserve-preview in xsane
Messaggio in formato MIME composto da più parti. --=_NextPart_000_00B1_01C40115.0D3CB5C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, I am using sane from many years with the xscanimage interface for = which I have found really useful the option "preserve-preview" available = to preserver the previous preview. We are now switching to the xsane interface, but I have not found in the = Preferences and neither in the configuration file any chance to have the = same function. Is anybody able to help me and give me some answer on this matter. Thank you in advance Dr. Clemente Luca - T.I.M. Srl Via D. Alighieri, 5/a I-33080 Puja di Prata (PN) - Italia Tel +39-0434-621900 Fax +39-0434-610427 HTTP: www.zerobase.it e-mail: luca.c...@zerobase.it --=_NextPart_000_00B1_01C40115.0D3CB5C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, I am using sane from = many years=20 with the xscanimage interface for which I have found really useful the = option=20 "preserve-preview" available to preserver the previous = preview. We are now switching to the xsane = interface, but I=20 have not found in the Preferences and neither in the configuration file = any=20 chance to have the same function. Is anybody able to help me and give me = some answer=20 on this matter. Thank you in advance Dr. Clemente Luca - T.I.M. SrlVia = D. Alighieri,=20 5/a I-33080 Puja di Prata (PN) - ItaliaTel +39-0434-621900Fax=20 +39-0434-610427HTTP: http://www.zerobase.it";>www.zerobase.ite-mail: mailto:luca.c...@zerobase.it";>luca.c...@zerobase.it --=_NextPart_000_00B1_01C40115.0D3CB5C0--
[sane-devel] CUPS dependency
Hello, I'm trying to pack sane for OpenWRT. As routers normally have low FS space, it is important to keep program sizes and dependencies to a minimum. While compiling sane-backends, I tried to look for usages of CUPS in every source file and I did not find. Without cups-devel, I get the same backends compiled. When compiled with cups, every sane .so gets linked to it. Is cups dependency still necessary? Also, I did not find a way to tell configure to ignore cups (except by patching it). Is there a better way? Regards, -- 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] CUPS dependency
Thanks Olaf and Simon, I'll cherry-pick it. It is no different from what I've already done but it is better to refer upstream. Regards, Em qui, 20 de ago de 2015 às 20:57, Olaf Meeuwissen < olaf.meeuwis...@avasys.jp> escreveu: > > Luiz Angelo Daros de Luca writes: > > > Hello, > > > > I'm trying to pack sane for OpenWRT. As routers normally have low FS > space, > > it is important to keep program sizes and dependencies to a minimum. > > > > While compiling sane-backends, I tried to look for usages of CUPS in > every > > source file and I did not find. Without cups-devel, I get the same > backends > > compiled. When compiled with cups, every sane .so gets linked to it. > > > > Is cups dependency still necessary? > > It has been commented out in commit efb04936 (on 2013-10-15). > > > Also, I did not find a way to tell configure to ignore cups (except by > > patching it). Is there a better way? > > Cherry pick that commit? > > Use the latest source from the git repository? Not ideal if your > package for OpenWRT needs any kind of long term support though. > You may want to wait for the next release. There is talk[1] of doing > one mid September. > > [1] > http://lists.alioth.debian.org/pipermail/sane-devel/2015-August/033641.html > > Hope this helps, > -- > Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- EPSON AVASYS CORPORATION > FSF Associate Member #1962 Help support software freedom > http://www.fsf.org/jf?referrer=1962 > -- 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] pthread_detach after pthread_join generates segfault
Hello, I was getting a segfault for sane-backends when using device sane-test. This happened when I compiled sane with uclibc or musl (on openwrt). I debugged the problem and traced it to sanei_thread_waitpid (at sanei/sanei_thread.c). It seems that calling pthread_detach after someone already did a pthread_join causes a segfault. I'm no pthread expert but I guess that after a pthread_join, the thread becomes "detached" and "terminated". And, according to man page PTHREAD_DETACH(3): "Attempting to detach an already detached thread results in unspecified behavior." I simply removed these detach lines in order to solve my problem. What would be the correct fix? Is there any case when join fails and detach is still valid? I checked error codes and only EDEADLK(when the thread is already waiting for the caller) and EINVAL (when three is another thread is already waiting for it) are possible situations when detach might do something. Are they possible in sane thread usage? If so, I guess detach might only be called when one of the possible fails of join happens. Regards, Luiz Angelo Daros de Luca -- 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] musl compatibility
Hello, While porting SANE to OpenWRT, I needed to patch SANE in order to compile it using musl (default libc in OpenWRT trunk). The problem is that u_char and u_long was not defined. glibc seems to be fine without it. The fix is quite simple: I added '#include ' to these files: /include/sane/sanei_udp.h /backend/kvs20xx_cmd.h /backend/kvs40xx.h /backend/hp5400.c /backend/hp5590.c I have the patch (attached) for it but it is based on 1.0.24. Is this the best solution? Also, I would be interesting to have a fix upstream. Regards, --- a/include/sane/sanei_udp.h +++ b/include/sane/sanei_udp.h @@ -27,6 +27,7 @@ #include #include #endif +#include extern SANE_Status sanei_udp_open(const char *host, int port, int *fdp); extern SANE_Status sanei_udp_open_broadcast(int *fdp); --- a/backend/kvs20xx_cmd.h +++ b/backend/kvs20xx_cmd.h @@ -9,6 +9,8 @@ Panasonic KV-S20xx USB-SCSI scanners. */ +#include + #define COMMAND_BLOCK 1 #define DATA_BLOCK 2 #define RESPONSE_BLOCK 3 --- a/backend/kvs40xx.h +++ b/backend/kvs40xx.h @@ -10,6 +10,7 @@ #include "../include/sane/config.h" #include +#include #undef BACKEND_NAME #define BACKEND_NAME kvs40xx --- a/backend/hp5400.c +++ b/backend/hp5400.c @@ -67,6 +67,7 @@ #include /* malloc, free */ #include /* memcpy */ #include +#include #define HP5400_CONFIG_FILE "hp5400.conf" --- a/backend/hp5590.c +++ b/backend/hp5590.c @@ -48,6 +48,7 @@ #include #include #include +#include #include "../include/sane/sane.h" #define BACKEND_NAME hp5590 -- 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] ioperm or portaccess for qcam
Hello,
While trying to solve a problem with missing inb/outb for mips, I saw this
check in configure:
qcam)
if test "${ac_cv_func_ioperm}" = "no" \
&& test "${ac_cv_func__portaccess}" = "no"; then
echo "*** $be backend requires ioperm and portaccess functions -
$DISABLE_MSG"
backend_supported="no"
fi
;;
http://anonscm.debian.org/cgit/sane/sane-backends.git/tree/acinclude.m4#n631
Either the message is wrong or the logic. I guess the message should
be "...requires
ioperm or portaccess"
Regards,
--
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] inb outb missing on mips
Hello, I'm trying to get rid of this patch: http://git.openwrt.org/?p=packages.git;a=blob_plain;f=utils/sane-backends/patches/020-non-i386-qcam.patch;hb=HEAD That helps sane-backend cross-compile for MIPS processor. But this seems to be a hacky solution. The problem seems that configure check for ioperm passes for MIPS with libc-musl (I didn't test with other libc), while inb and outb are still missing for this arch. As sane-backend uses HAVE_IOPERM in order to use or not in/outb, it compiles requiring inb/outb. This results in a linker error. Who is not playing nice here? musl providing ioperm where it shouldn't? configure failing to check correcly for ioperm? sane not checking for inb? Regards, -- 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] inb outb missing on mips
Hello, I checked with other libc and got some more info about the problem. Normally, sane-backends deal with ioperm/inb/outb like this: a) sane-backends tries to use sys/io.h in order to provide inb/outb. If missing, it implements them locally but only for i386 (old glibc?) b) if ioperm is missing for any arch but i386. IO_SUPPORT_MISSING is defined c) if either ioperm is missing or IO_SUPPORT_MISSING is defined, inb/outb will not be used. c.1) the exception is backend/qcam.c, which tries to use inb/outb anyway but it will not be compiled if ioperm is missing. Now how libc implementations deal with iopem/inb/oub: When uclibc is used: * it provide sys/io.h for only i386/x32/x86_64 archs and it includes inb/outb * it does not provide sys/io.h for non i386 arch When musl is used: * it provides sys/io.h for any arch that has ioperm syscall (which includes mips, i386/x32/x86_64, powerpc, microblaze) * it does not provide inb/outb for any arch expect i386/x32/x86_64 (using bits/io.h included in sys/io.h) What happens on sane-backend: 1) for i386/x32/x86_64 arch, any libc provides sys/io.h with ioperm and inb/oub. Sane-backends compiles. 2) for any arch that does not implement ioperm syscall, ioperm is missing. Sane-backends compiles. 3) for other non-i386/x32/x86_64-arch that provides ioperm syscall: 3.1) uclibc does not provide sys.io.h. Sane-backends compiles, except for qcam. 3.2) musl provide sys.io.h but inb/outb is missing. Sane-backends fails with multiple undefined symbols (inb/outb). Some files affected are: sanei/sanei_pio.c sanei/sanei_ab306.c sanei/sanei_pa4s2.c sanei/sanei_pp.c backend/umax_pp_low.c backend/qcam.c What is the best solution here? Should all checks for ioperm be replaced by (or added with) checks for inb/outb (including disabling qcam in configure)? It'll not break cases 1), 2) and it will fix 3.1 and 3.2. Regards, Em qua, 9 de set de 2015 às 19:04, Luiz Angelo Daros de Luca < luizl...@gmail.com> escreveu: > Hello, > > I'm trying to get rid of this patch: > > http://git.openwrt.org/?p=packages.git;a=blob_plain;f=utils/sane-backends/patches/020-non-i386-qcam.patch;hb=HEAD > > That helps sane-backend cross-compile for MIPS processor. But this seems > to be a hacky solution. > > The problem seems that configure check for ioperm passes for MIPS with > libc-musl (I didn't test with other libc), while inb and outb are still > missing for this arch. As sane-backend uses HAVE_IOPERM in order to use or > not in/outb, it compiles requiring inb/outb. This results in a linker error. > > Who is not playing nice here? musl providing ioperm where it shouldn't? > configure failing to check correcly for ioperm? sane not checking for inb? > > Regards, > -- 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] inb outb missing on mips
I added some autoconf magic in order to detect missing inb,outb functions. It might not be the best solution as I'm no autoconf expert but it solves my problems. https://raw.githubusercontent.com/luizluca/openwrt-packages/e11fbf71f7f437c64d18929e7895dbaafa8c3293/utils/sane-backends/patches/020-inb_outb.patch Regards, Em qui, 10 de set de 2015 às 01:14, Luiz Angelo Daros de Luca < luizl...@gmail.com> escreveu: > Hello, > > I checked with other libc and got some more info about the problem. > > Normally, sane-backends deal with ioperm/inb/outb like this: > a) sane-backends tries to use sys/io.h in order to provide inb/outb. If > missing, it implements them locally but only for i386 (old glibc?) > b) if ioperm is missing for any arch but i386. IO_SUPPORT_MISSING is > defined > c) if either ioperm is missing or IO_SUPPORT_MISSING is defined, inb/outb > will not be used. > c.1) the exception is backend/qcam.c, which tries to use inb/outb anyway > but it will not be compiled if ioperm is missing. > > Now how libc implementations deal with iopem/inb/oub: > > When uclibc is used: > * it provide sys/io.h for only i386/x32/x86_64 archs and it includes > inb/outb > * it does not provide sys/io.h for non i386 arch > When musl is used: > * it provides sys/io.h for any arch that has ioperm syscall (which > includes mips, i386/x32/x86_64, powerpc, microblaze) > * it does not provide inb/outb for any arch expect i386/x32/x86_64 (using > bits/io.h included in sys/io.h) > > What happens on sane-backend: > 1) for i386/x32/x86_64 arch, any libc provides sys/io.h with ioperm and > inb/oub. Sane-backends compiles. > 2) for any arch that does not implement ioperm syscall, ioperm is > missing. Sane-backends compiles. > 3) for other non-i386/x32/x86_64-arch that provides ioperm syscall: > 3.1) uclibc does not provide sys.io.h. Sane-backends compiles, except for > qcam. > 3.2) musl provide sys.io.h but inb/outb is missing. Sane-backends fails > with multiple undefined symbols (inb/outb). > > Some files affected are: > sanei/sanei_pio.c > sanei/sanei_ab306.c > sanei/sanei_pa4s2.c > sanei/sanei_pp.c > backend/umax_pp_low.c > backend/qcam.c > > What is the best solution here? Should all checks for ioperm be replaced > by (or added with) checks for inb/outb (including disabling qcam in > configure)? > It'll not break cases 1), 2) and it will fix 3.1 and 3.2. > > Regards, > > > > > Em qua, 9 de set de 2015 às 19:04, Luiz Angelo Daros de Luca < > luizl...@gmail.com> escreveu: > >> Hello, >> >> I'm trying to get rid of this patch: >> >> http://git.openwrt.org/?p=packages.git;a=blob_plain;f=utils/sane-backends/patches/020-non-i386-qcam.patch;hb=HEAD >> >> That helps sane-backend cross-compile for MIPS processor. But this seems >> to be a hacky solution. >> >> The problem seems that configure check for ioperm passes for MIPS with >> libc-musl (I didn't test with other libc), while inb and outb are still >> missing for this arch. As sane-backend uses HAVE_IOPERM in order to use or >> not in/outb, it compiles requiring inb/outb. This results in a linker error. >> >> Who is not playing nice here? musl providing ioperm where it shouldn't? >> configure failing to check correcly for ioperm? sane not checking for inb? >> >> Regards, >> > -- 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] Schedule for release of sane-backends 1.0.25
Thanks for the mention Olaf, Adding more to the subject, there are more patches (including some not mine) which would be interesting to be upstreamed: https://github.com/luizluca/openwrt-packages/tree/sane/utils/sane-backends/patches I'll try to explain their motivations: * 002-remove-uneeded.patch: as configure does not offer an option to disable docs and tests, this was done with a patch. I would be interesting to have --disable-docs and --disable-testsuites * 010-dont-add-host-include-path.patch: search for header using absolute path is problematic by itself. For cross-compiling, this is prohibit as headers are not from the host machine. * 020-inb_outb.patch: this is already commented in previous message to maillist * 030-musl.patch: the u_char/u_long fix. Maybe some autoconf check could deal with this. * 040-remove-cups-deps.patch: this I got from sane-devel, so it is already merged. * 050-remove_linked_libs_for_unused_preload.patch: Currently, libsane link is somehow bruteforce. It links any library a backend might need. As already commented inside the Makefile, the correct behavior would be to link only libraries for those backends built-in libsane. As I'm not using built-in backends, I simply removed them. This would need some autoconf magic for a proper fix. * 060-dont_detatch_after_join.patch: another one I sent the list. This was discussed in list but not fix merged. * 070-sane-backends-1.0.24-format-security.patch: this is from fedora. I got a gcc error because the usage of -Werror=format-security. Current sane git code is different from 1.0.24 and I did not checked calmly if it still needed. And there are more patches at fedora that might be interesting too: http://pkgs.fedoraproject.org/cgit/sane-backends.git/plain/ Regards, Em sex, 11 de set de 2015 às 11:15, Olaf Meeuwissen < paddy-h...@member.fsf.org> escreveu: > m. allan noah writes: > > > It has been 2 years since our last release, so here we go again: > > > > Timetable: > > Sept 19, 2015: Feature freeze (only bugs, translation and doc updates) > > Sept 26, 2015: Code freeze (only horrible bugs, translation and doc > updates) > > Oct 03, 2015: Release > > > > Note, it is highly likely that there are patches from end users which > > we failed to apply. If you know of such a case, please speak up, so we > > can start a dialog about including them in the release. Olaf has been > > doing some of this work, but he could use some help from backend > > authors as well as end users. > > After following and occasionally responding to the list @the-office for > well over a decade, I have finally decided to volunteer some of my free > time to the SANE project. In an attempt to avoid confusion, I will be > using my member.fsf.org mail account for my volunteer effort related > mails. > > The main reason that I decided to volunteer was that I think that the > SANE project could use a janitor, somebody who looks after all of the > stuff that is not really backend specific. This kind of work I can't > do @the-office where I am forced to wear a "corporate hat", so in the > end I concluded that doing this in my "free" time was the only way to > get any SANE Project Janitor work done. I'll be wearing a "community > hat" in my free time ;-) > > There you have it, I'll be your self-appointed SANE Project Janitor for > as long as it'll last. > > I have a couple of things on my mental todo list but for now let's focus > on getting sane-backends-1.0.25 out by 2015-10-03. > > I have trudged through the mailing list archive all the way back to > 2015-01-01 looking for patches that have not been applied. Most of > these have been committed recently. Some of those were confirmed as not > really meant for master. There are still a few things that I mean to > get to that were posted after Allan sent the first notice for a new > release. Also, Luiz and Matteo (the OpenWRT folks?) recently have been > "inundating" the list with patches that I will have a look at. > > I am not comfortable (yet) committing directly to the git repository on > Alioth. For the time being, I will prep proposed upgrade (pu) branches > on my clone of master at GitLab[1] and ask the more seasoned developers > to pull specific branches. Those pu branches will be based on patches > that are sent to or mentioned on the list or some of my own work. > > [1] https://gitlab.com/sane-project/backends/branches > > > During the period leading up to the release, it would be helpful if we > > could get some builds on various platforms, and tests done with > > various scanners. The sooner we discover problems, the better. > > With respect to the build, I would like to see any changes to the build > system in as soon as possible. That is, any changes to configure.in, > acinclude.m4 and any of the Makefile.am files should go in real soon. > These kind of changes are most likely to lead to hiccups when building > on less common systems. Backend specific changes are much less likely > to be
[sane-devel] Portbility problems with sane 1.0.25
Hello,
Thanks for the new release! It merged most of the patches I kept in order
to compile for OpenWRT. However, I still faced some new and old problems:
a) backend/pieusb_buffer.c (most of the problems)
a.1) it uses mkostemp without checking its presence. uclibc might not
provide it. If mkstemp is enough, it might be better as it is POSIX and not
a glibc extension. I simply replaced it with mkstemp, which might not be
correct.
https://raw.githubusercontent.com/luizluca/openwrt-packages/hplip/utils/sane-backends/patches/031-fix_uclibc.patch
a.2) le16toh is always redefined, which gives me a "redefined warning". The
problem is that the replacement implementation uses __bswap_16, which is
not present in musl. As le16toh might be already fine, check for it before
reimplementing it:
https://raw.githubusercontent.com/luizluca/openwrt-packages/hplip/utils/sane-backends/patches/020-fix_pieusb.patch
a.3) if mmap is not found, it generates a compile error ("#error mmap(2)
not available, aborting"). The problem is that mmap is checked with
AC_FUNC_MMAP and it depends on a runtime check (ac_fn_c_try_run). As I'm
crosscompiling, no runtime check will ever work because all generated
binaries cannot run in my host system. If "AC_CHECK_FUNCS(mmap)" is not
good enough as a replacement, configure would need to check for other hints
(SO, arch) and heuristically define if mmap is avaiable. Anyway, if ever
mmap check fails, the expected result would be to disable pieusb backend
and never generate a compiler error.
I have no patch for this as I cheated the test defining
ac_cv_func_mmap_fixed_mapped=yes
b) missing includes for sys/types.h (uchar and ulong)
This is an old problem still not fixed. The list of files that need to
include sys/types.h added the new backend epsonds
- include/sane/sanei_udp.h
- backend/kvs20xx_cmd.h
- backend/kvs40xx.h
- backend/hp5400.c
- backend/hp5590.c
- backend/epsonds-io.c (new)
Even these files including sane/config.h, sane/config.h only includes
sys/types.h when replacing some missing functions (inet_ntop, strndup).
Each problematic file might need something like:
#if defined(HAVE_SYS_TYPES_H)
# include
#endif
which is already used in some files (backend/umax_pp_low.c
backend/umax_pp.c backend/genesys_low.h backend/mustek_pp.c
backend/mustek_pp.h backend/pixma_bjnp.c)
or it could be added to sane/config.h (bruteforce solution).
I do have a patch but before upstreaming it, we need to define where to put
the include.
Regards,
--
Luiz Angelo Daros de Luca
--
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] [PATCH] Port to OS X
Olaf and Yurii, The sys/type.h problem is the same I face while compiling with musl instead of glibc. There are just some files that miss it. I have a patch for them but it still misses the ifdef around it. Check the other patches that might easy your port. https://github.com/openwrt/packages/blob/master/utils/sane-backends/patches/ Regards, Em sáb, 17 de out de 2015 01:36, Olaf Meeuwissen escreveu: > Hi Yurii, > > Sorry for the late follow-up. > > Yurii Kolesnykov writes: > > > Hi Olaf, thanks for your feedback. > > Sorry, I forgot to include this comment in previous email. > > > >> > /* > >> > * SANE types and defines > >> > */ > >> > diff --git a/include/sane/sanei_backend.h > b/include/sane/sanei_backend.h > >> > index 1b5afe2..982dedc 100644 > >> > --- a/include/sane/sanei_backend.h > >> > +++ b/include/sane/sanei_backend.h > >> > @@ -96,7 +96,9 @@ > >> > # undef SIG_SETMASK > >> > # endif > >> > > >> > +# ifndef __APPLE__ > >> > # define sigset_t int > >> > +# endif > >> > >> Can you explain what this is trying to fix? The sigset_t macro is > >> undefined a bit above this. If sigset_t is still visible to the > >> compiler, it wasn't a macro and the defines below will quite likely > >> break things. > > > > I had this error: > > > > In file included from epsonds-jpeg.c:18: > > In file included from ./epsonds.h:43: > > In file included from ../include/sane/sanei_usb.h:69: > > In file included from /usr/include/stdlib.h:65: > > In file included from /usr/include/sys/wait.h:109: > > In file included from /usr/include/sys/signal.h:154: > > /usr/include/sys/_types/_sigset_t.h:30:28: error: cannot combine with > previous 'type-name' declaration specifier > > typedef __darwin_sigset_tsigset_t; > > ^ > > ../include/sane/sanei_backend.h:99:33: note: expanded from macro > 'sigset_t' > > # define sigset_tint > > ^ > > 1 error generated. > > Ok, so sigset_t wasn't a define. > > I've dug up some[1] info[2] on __darwin_sigset_t and it seems to just be > a typedef for a 32 bit unsigned integer. In that case, the other signal > related defines in sanei_backend.h won't break. > > [1] http://fxr.watson.org/fxr/ident?v=xnu-792;i=__darwin_sigset_t > [2] > https://www.opensource.apple.com/source/xnu/xnu-792.6.56/bsd/sys/_types.h > > However, I don't think that your fix is the right way to go about fixing > this. It is really something that configure should check for. > > Feel free to keep using this patch yourself but I will not commit it to > Alioth's master. > > Hope this helps, > -- > Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 > Support Free Software Support the Free Software Foundation > https://my.fsf.org/donatehttps://my.fsf.org/join > GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 > > -- > 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 > -- Luiz Angelo Daros de Luca -- 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] Is it time of a new release?
Hi, We already have more than 500 commits since 1.0.25. As a downstream maintainer (openwrt/lede), I get lost between those tons of patches and how to select them to be backported. Shouldn't sane-backend release a new version? Also, It would be really nice if SANE could keep a stable branch. It would be, at least, a place to target cherry-picks. Maybe it could change its version number to something like other projects do as: x.y.0 - feature release x.y x.y.n - fix release n It would be better if x.y is year/month. At least there is no discussion on whether the new release is big enough to tic the first number. Regards, -- Luiz Angelo Daros de Luca luizl...@gmail.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
Re: [sane-devel] [PATCH 3/3] saned: reorganize flags, remove run_mode SANED_RUN_DEBUG
The two first patches are trivial bugfixes. However, this one proposes a new organization on saned options, as shown at: https://alioth.debian.org/tracker/index.php?func=detail&aid=315747&group_id=30186&atid=410366 All flags now do one thing and normally have an opposite flag that can deactivate it. The flag -a was kept compatible but, flags -d and -s now have a different behavior. -d only sets the debug level and -s only forces syslog. I guess this breakage does little harm as those flags are only used for dev (as they quits saned after first client). If not, I can introduce new flags for those actions and revert -d/-s previous behavior. -- Luiz Angelo Daros de Luca luizl...@gmail.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
Re: [sane-devel] [PATCH 3/3] saned: reorganize flags, remove run_mode SANED_RUN_DEBUG
t. The current default behavior is enough for systemd. > > # FWIW, I switched to Devuan in December 2016 after using Debian for > # about 19 years to regain init freedom ;-) Alternative init system > # approaches are welcome! > Procd? I'd think you know ;-) > > > If not, I can introduce new flags for those actions and revert -d/-s > > previous behavior. > > I don't think there is any need to keep these options backwardly > compatible but it might be in order for saned to warn people that these > options have changed since 1.0.27, show the new invocation for the old > behaviour and a pointer to the manual page for details on the changed > options. > Something for the Release Notes as Changelog is built from git log. Is there any place to save relevant changes for the next release? > > Something similar could be done for -a, warning users that this option > is deprecated and will be removed in the future (without any explicit > mention of when exactly). > I still think that it is not worth it. It's a problem when you does not have an option for changing only a specific behavior. However, a "combo option" that aggregates a bundle of options normally used together is good (just like rsync -a). My suggestion is to just keep it. > > You mention something about creating a PID file for the -u option. That > made me think a -p option to specify where you want that file might be a > nice addition. The current location, /var/run/saned.pid, is hard-coded. > It's not a bad location but one may want to change it. > I'll take a look. Normally PID file location is something for a configuration file. Sometimes init would like to take care of the PID file life cycle. Besides being hard-coded, if a previous PID file exists, saned should do some checks, and abort on failure. Today, if someone manage to run two instances of a stand-alone saned, the last one would simply overwrite its own PID inside the PID file. Also it should replace PID file instead of simply rewriting it. At least it would avoid different code paths (and permission requirements) whether a file at PID file exists or not. > > Oh, about the code changes, there are a few places in the manual page > I'd change to improve the English but I can do that for you. There is > one mistake though, you document a -B option (as if it were -D). > Yeah, english skill aren't really my "expertise". :-) I do know my limitations. Feel free to point me or correct them directly. > > I'd drop the SANED_EXEC_* defines you add because they're not used and > apart from a minor English nitpick in the option descriptions, the > saned.c changes look fine. > Sure. I overlooked that. Thanks. > > Hope this helps, > It do really helps. Thanks a lot for the review. > -- > Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 > GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 > Support Free Softwarehttps://my.fsf.org/donate > Join the Free Software Foundation https://my.fsf.org/join > -- Luiz Angelo Daros de Luca luizl...@gmail.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
Re: [sane-devel] [PATCH 3/3] saned: reorganize flags, remove run_mode SANED_RUN_DEBUG
Hi Olaf, Apologies for the late follow-up. Shame on me for pinging you on the > bug report for no follow-up for a long time and then ignoring it when > you promptly send some. :-( > > No apologies needed. We know how it works. I was just waiting for your reply. My changes were already at github (and just rebased): https://github.com/luizluca/sane-backends/tree/reorganize-saned-args > >> If there is no clear use case, perhaps saned should not provide them. > >> In that case, I'd remove: > >> - -D and make running in the background the default because saned is > >>normally meant to run as a daemon > > > > I beg to disagree. It's not true for (x)inet, systemd nor procd. They do > > expect process in foreground. Only running saned standalone might need it > > to go background. Also, I think that changing the default behavior is > even > > more traumatic than changing any behavior of options. > > Rethinking this, I guess you're right. It's not much effort to manually > background a daemon, simply add an `&` at the end of the command-line. > An `&` is not enough as there are some extra logic when going backgroud. `-D` do just that. > Something for the Release Notes as Changelog is built from git log. Is > > there any place to save relevant changes for the next release? > > Eh, I guess the NEWS file would be as good a place as any. Something > like > > New with the development version, not yet released: > > @Allan> Does that look okay? > > I'll just wait for the "NEWS" answered you asked @Allan in order to update only that and send patches to ML. >> You mention something about creating a PID file for the -u option. That > >> made me think a -p option to specify where you want that file might be a > >> nice addition. The current location, /var/run/saned.pid, is hard-coded. > >> It's not a bad location but one may want to change it. > > > > I'll take a look. Normally PID file location is something for a > > configuration file. > > Sometimes init would like to take care of the PID file life cycle. > Besides > > being hard-coded, if a previous PID file exists, saned should do some > > checks, and abort on failure. Today, if someone manage to run two > instances > > of a stand-alone saned, the last one would simply overwrite its own PID > > inside the PID file. Also it should replace PID file instead of simply > > rewriting it. At least it would avoid different code paths (and > permission > > requirements) whether a file at PID file exists or not. > > Looks like any user with write access to the directory holding the PID > file can clobber it because > > pidfile = fopen (SANED_PID_FILE, "w"); > > doesn't pass O_EXCL to the underlying open(). > > On my devuan box, /var/run is a symlink to /run which has 755 perms and > is owned by root. Digging further, /run is actually a mount point for a > tmpfs. But anyway, not all systems are created equally. > I'll leave PID_FILE as is for now. > >> Oh, about the code changes, there are a few places in the manual page > >> I'd change to improve the English but I can do that for you. There is > >> one mistake though, you document a -B option (as if it were -D). > > > > Yeah, english skill aren't really my "expertise". :-) I do know my > > limitations. Feel free to point me or correct them directly. > > I'll correct them directly (if there are any ;-). It's less overhead > for both of us. > OK for me. > PS: I'll be travelling a bit in the next two weeks so will probably be > late again in following up. > Nobody is at a hurry. Regards, > -- > Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 > GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 > Support Free Softwarehttps://my.fsf.org/donate > Join the Free Software Foundation https://my.fsf.org/join > -- Luiz Angelo Daros de Luca luizl...@gmail.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
Re: [sane-devel] how do you use "saned -d and -s?
-d handles only one connection, and then exits. Maybe PDF studio needs to connect twice. If this is your case, you simply cannot use -d/-s. -s is just the same but redirects output to syslog. The next release will change this behavior to something similar to what -d generally mean in other commands (without quitting after the first connection). Regards, Em sáb, 18 de nov de 2017 08:24, ToddAndMargo escreveu: > Dear list, > > Scientific Linux 7.4 (RHEL Clone based on CentOS) > > # rpm -qa sane-backends > sane-backends-1.0.24-9.el7.x86_64 > > # ps ax | grep [s]aned > 29857 ?Ss 0:00 /usr/sbin/saned -a saned -d128 > > > How do I use > /usr/sbin/saned -a saned -d128 > or -s > to see why a scanner command is crashing? > > Simple Scan works. > > PDF Studio requires saned be running and does find the scanner, > gives me the following error: > > com.qoppa.uk.b.b.e.m: Invalid operation > at com.qoppa.uk.b.b.e.k.b(Unknown Source) > at com.qoppa.uk.b.b.b.o.fc(Unknown Source) > at com.qoppa.uk.b.b.b.o.wb(Unknown Source) > at com.qoppa.pdfStudio.k.p.d(Unknown Source) > at com.qoppa.pdfStudio.k.p.e(Unknown Source) > at com.qoppa.pdfStudio.k.p.s(Unknown Source) > at com.qoppa.pdfStudio.l.vd.dae(Unknown Source) > at com.qoppa.pdfStudio.l.vd.fzd(Unknown Source) > at com.qoppa.pdfStudio.l.vd$14.run(Unknown Source) > at java.lang.Thread.run(Thread.java:748) > > > Many thanks, > -T > > > -- > 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 > -- Luiz Angelo Daros de Luca luizl...@gmail.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
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 next release happens), if you could deal with some instability. Regards, Em seg, 20 de nov de 2017 17:49, Jeff Sadowski escreveu: > 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-port" > (getaddrinfo) > [saned] do_bindings: [1] socket () using IPv6 > [saned] do_bindings: [1] setsockopt () > [saned] do_bindings: [1] bind () to port 6566 > [saned] do_bindings: [1] listen () > [saned] do_bindings: [0] socket () using IPv4 > [saned] do_bindings: [0] setsockopt () > [saned] do_bindings: [0] bind () to port 6566 > [saned] do_bindings: [0] bind failed: Address already in use > [saned] run_standalone: spawning Avahi process > [saned] run_standalone: waiting for control connection > [saned] saned_avahi_callback: AVAHI_CLIENT_S_RUNNING > [saned] saned_create_avahi_services: adding service 'saned' > [saned] saned_avahi_group_callback: service 'saned' successfully > established > > I had disabled ipv6 because it interfered with my wireless. > I currently run it in a script that continually restarts it with -d2 > is there a better way? > > -- > 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 > -- Luiz Angelo Daros de Luca luizl...@gmail.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
Re: [sane-devel] Everyone!
Add a single + in a line. Em sex, 24 de nov de 2017 09:47, ToddAndMargo escreveu: > On 11/24/2017 03:44 AM, ToddAndMargo wrote: > > Hi All, > > > > What to I do to saned.conf to tell it I want EVERYONE to > > be able to access it? > > > > Many thanks, > > -T > > > > > > > Both network users and all users in general > > > -- > 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 > -- Luiz Angelo Daros de Luca luizl...@gmail.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
Re: [sane-devel] Everyone!
Yes Em sáb, 25 de nov de 2017 07:24, ToddAndMargo escreveu: > On 11/25/2017 01:02 AM, Olaf Meeuwissen wrote: > > A > > line containing the single character ``+'' is interpreted to > > match any hostname > > > My firewall blocks everything from the Internet. > > "A line containing the single character ``+'' is > interpreted to match any hostname" > > Not sure what that means. Any IP or any host name? > Jut use a "+" on a blank line? > > > > -- > ~~ > Computers are like air conditioners. > They malfunction when you open windows > ~~ > > > -- > 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 > -- Luiz Angelo Daros de Luca luizl...@gmail.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
Re: [sane-devel] [janitorial] Relocating the SANE Project
I also prefer GitHub. Anyway, someone will create a SANE mirror project there and other will fork from it instead of main git repo. It's not a marriage, just conviene. I would like to keep ML but issue and PR can replace most of ML use for dev and users help. However, a sane-releases@ is still interesting for package maintainers. I dunno a github feature for watching new releases. Regards, Em ter, 9 de jan de 2018 14:15, Markus Heiser escreveu: > > > Am 08.01.2018 um 22:40 schrieb Jeff : > > > > On 08/01/18 08:46, Olaf Meeuwissen wrote: > >> What are your preferences? Feel free to mention other options. > > > > There is also Sourceforge. > > IMO sourceforge is a step backward, not really your preference, or? > > -- Markus -- > > -- > 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 > -- Luiz Angelo Daros de Luca luizl...@gmail.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
