[sane-devel] scanimage picking wrong/invalid device

2016-09-22 Thread Vince Radice
Hello, I am having a problem trying to get my scanner to work. I am running Fedora FC24 64 bit with the latest updates. When I tried to scan an image recently using xsane I got a message that there was an invalid argument. I have spent the last 4 days searching for an answer but I

[sane-devel] Degrading images: Plustek OpticPro UT16

2016-09-22 Thread rhn
Hello, the scanner I am using has a peculiar problem, where scanning consecutive images causes the image quality to degrade: the left part becomes yellow in vertical streaks that increase in numbers; the right part becomes red. To get a completely yellow-red image, about 10 scans are

[sane-devel] Xsane: compilation problems

2016-09-22 Thread rhn
Hello, I downloaded the newest tarball of xsane, and I have to report that it doesn't compile on Fedora 23. It turns out that some libpng structures are not used correctly. I fixed the problems and uploaded the fix to a git repository at https://github.com/rhn/xsane The fix itself is the

Re: [sane-devel] CanoScan Lide 220 not works

2016-09-22 Thread csola48
LiDE 220 is listed as "complete" in SANE docs. What doesn't work? Maybe the chips they differ?  old: gl124 < > now: gl847 ? csola48 -- sane-devel mailing list: sane-devel@lists.alioth.debian.org

Re: [sane-devel] CanoScan Lide 220 not works

2016-09-22 Thread csola48
LiDE 220 is listed as "complete" in SANE docs. What doesn't work? Maybe the chips they differ?  old: gl124 < > now: gl847 ? csola48 -- sane-devel mailing list: sane-devel@lists.alioth.debian.org

Re: [sane-devel] [Janitorial] Zero(!) compiler warnings

2016-09-22 Thread Olaf Meeuwissen
Hi Johannes, Johannes Meixner writes: > Hello Olaf, > > On Sep 21 22:12 Olaf Meeuwissen wrote (excerpt): >> About a year ago, I set out trying to get rid of *all* >> compiler warnings on a "well-defined" build platform. >> I'm happy to report that we've made it! > > Awesome! Thanks! > I

Re: [sane-devel] CanoScan Lide 220 not works

2016-09-22 Thread csola48
LiDE 220 is listed as "complete" in SANE docs. What doesn't work? Maybe the chips they differ?  old: gl124 < > now: gl847 ? csola48 -- sane-devel mailing list: sane-devel@lists.alioth.debian.org

Re: [sane-devel] [Janitorial] Zero(!) compiler warnings

2016-09-22 Thread ABC
Hello, To what mktemp() should be replaced? Will there be sanei function to drop-in replace it? On Wed, Sep 21, 2016 at 10:12:27PM +0900, Olaf Meeuwissen wrote: > Looking over the build log (love how clean those compile commands look, > BTW), next are four linker warnings about the use of

Re: [sane-devel] CanoScan Lide 220 not works

2016-09-22 Thread csola48
Hi, Is a hope that way, that the Lide220 scanner will work well ? Pls, help or ask a question... csola48 -- 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

Re: [sane-devel] [Janitorial] Zero(!) compiler warnings

2016-09-22 Thread Olaf Meeuwissen
m. allan noah writes: > On Wed, Sep 21, 2016 at 9:12 AM, Olaf Meeuwissen > wrote: >> Hi devs, >> >> About a year ago, I set out trying to get rid of *all* compiler warnings >> on a "well-defined" build platform. I'm happy to report that we've made >> it! With the

Re: [sane-devel] [Janitorial] Zero(!) compiler warnings

2016-09-22 Thread Olaf Meeuwissen
Hi Louis, Louis Lagendijk writes: > On Wed, 2016-09-21 at 22:12 +0900, Olaf Meeuwissen wrote: >> Hi devs, >> >> About a year ago, I set out trying to get rid of *all* compiler >> warnings >> on a "well-defined" build platform.I'm happy to report that we've >> made >> it!With the commit of