Re: [sane-devel] Sane web GUI issue
Hi Mark, Mark DM writes: > I am converting an existing web GUI to include SANE compatibility . I am > working on getting things like scanner info , etc . > > When the web GUI executes a > > shell_exec(scanimage -T -d scannername) > > from PHP , I get nothing on the web GUI . I can echo the command and paste > into terminal and it works. I can also use Define "works". For concreteness' sake, here what I get using the test backend $ scanimage -T -d test:0 scanimage: scanning image of size 157x196 pixels at 8 bits/pixel scanimage: acquiring gray frame, 8 bits/sample scanimage: reading one scanline, 157 bytes... PASS scanimage: reading one byte...PASS scanimage: stepped read, 2 bytes... PASS scanimage: stepped read, 4 bytes... PASS scanimage: stepped read, 8 bytes... PASS scanimage: stepped read, 16 bytes... PASS scanimage: stepped read, 32 bytes... PASS scanimage: stepped read, 64 bytes... PASS scanimage: stepped read, 128 bytes... PASS scanimage: stepped read, 256 bytes... PASS scanimage: stepped read, 255 bytes... PASS scanimage: stepped read, 127 bytes... PASS scanimage: stepped read, 63 bytes... PASS scanimage: stepped read, 31 bytes... PASS scanimage: stepped read, 15 bytes... PASS scanimage: stepped read, 7 bytes... PASS scanimage: stepped read, 3 bytes... PASS $ scanimage -T -d test:0 2>/dev/null I think your shell_exec() ignores whatever ends up on stderr. > shell_exec(scanimage -L) $ scanimage -L 2>/dev/null device `test:0' is a Noname frontend-tester virtual device device `test:1' is a Noname frontend-tester virtual device device `pnm:0' is a Noname PNM file reader virtual device device `pnm:1' is a Noname PNM file reader virtual device > and > shell_exec(scanimage -V) $ scanimage -V 2>/dev/null scanimage (sane-backends) 1.0.25; backend version 1.0.25 So both -L and -V report back on stdout. > successfully, as well as initiate a scan > > I am using the test backend and maybe this has something to do with it? > > I have added www-data (debian web user) to the groups saned, scanner and > adm and still no luck with the one command from web server Hope this helps, -- 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 -- sane-devel mailing list: sane-devel@alioth-lists.debian.net https://alioth-lists.debian.net/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] PNG support for "scanimage"?
Hi, I just fixed the ppa build dependencies for trusty and xenial. Newer Ubuntu versions are not affected. The ppa is building now. Cheers, Rolf Am 01.06.19 um 03:37 schrieb Olaf Meeuwissen: > Hi Rainer, Rolf, > > Dr Rainer Woitok writes: > >> Greetings, >> >> still using Ubuntu 16.04 I've installed "scanimage" from Rolf's PPA: >> >> $ scanimage --version >> scanimage (sane-backends) 1.0.27git; backend version 1.0.27 >> $ scanimage -d pixma:MX880_new-host --format png >> PNG support not compiled in >> $ >> >> What's the reason for not supporting PNG? Do I have to clone the source >> repository to get PNG support? > > Looks like the build dependencies are missing libpng-dev but I have no > idea why. They do have a libjpeg-dev dependency and JPEG and PNG > support were both added in 1.0.25. > > Rolf> Can you fix this? > > Hope this helps, > -- > 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 > -- sane-devel mailing list: sane-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
[sane-devel] Proposal to remove autoconf-generated files from the source repository
Hi all, I propose we remove files from the source repository that are generated by autoconf and friends and ask the developers to do that. The primary motivation for this change is that the content of the generated files depends on the autotools version. Thus it makes harder for the developers to collaborate as they must use exactly matching autotools versions. Additionally the project history is cluttered by changes to the generated files, but we could perhaps live with that. A PR has been opened here and received some discussion already: https://gitlab.com/sane-project/backends/merge_requests/72 We could keep inclusion of the generated files to the source tarballs that we distribute so that the recipients of the tarballs don't need to have autotools installed. Additionally, this way we could be sure that this change does not break on weird platforms that we don't currently do testing on. The approach suggested in this email is how most projects that use autotools operate. We would be going through a common and tested path. Does anyone know reasons why this wouldn't work in our use case? Does anyone's workflow depend on autotools files being present in the default source checkout? Regards, Povilas -- sane-devel mailing list: sane-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
