Re: [sane-devel] libsane-imagescan.so.1' (No such file or directory)
Hello Olaf, FYI On Feb 18 17:08 Olaf Meeuwissen wrote (excerpt): Richard Ryniker writes: libsane-imagescan.so.1 is in the rpm package at: http://ftp.gwdg.de/pub/opensuse/repositories/home:/zhonghuaren/Fedora_27/x86_64/imagescan-3.32.0-8.1.x86_64.rpm # Curious, hosting Fedora packages under an opensuse directory ... This is because the Open (SUSE) Build Service can build and is used to build binary packages from source packages for various Linux distributions, cf. https://build.opensuse.org/ https://en.opensuse.org/Portal:Build_Service http://openbuildservice.org/ Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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
Hello, On Jan 8 16:46 Olaf Meeuwissen wrote (excerpt): So we have to move some place else for our project hosting but where? ... [10]: https://github.com/sane-project ... What are your preferences? my personal selfish preference is GitHub because so much other stuff is already there ( "billions of flies can't be wrong" ;-) which makes it easier to work on various different things: "One Place to rule them all, One Place to find them, One Place to bring them all and in the darkness bind them. In the land of GitHub where the Sources lie." Of course I know "easier" does not mean it is "better" in particular not from a strict free software point of view: https://www.gnu.org/software/repo-criteria-evaluation.html But I think because in the end it is plain 'git' nothing really evil could happen if at some day GitHub might become unusable for free software (in this case things could be hosted anywhere else) and because it is free software I don't care if GitHub monitors and evaluates all what goes on in GitHub because all is public anyway (I see no real differece compared to a public mailing list with public archives). Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] SANE needs a GUI like CUPS's 'system-config-printer' to manually add a network scanner.
Hello, On Nov 25 15:31 Hans Deragon wrote (excerpt): If a printer is not found, I can add it with system-config-printer. But if the magic of automatic detection of Sane fails, I cannot add a scanner manually. I did not read all the details in this mail thread but in general as far as I understand how the scanner drivers in SANE work it is not possible for the user to add a scanner manually. Either a scanner driver can detect the scanner or not. In general you may have a look at https://en.opensuse.org/SDB:Configuring_Scanners and therein see in particular the sections "Scanning via Network" and perhaps also "Third-Party Scanner Drivers". I think with scanners it is basically same as with things like harddisks. Either a kernel driver can detect a harddisk or not. It is not possible for the user to add a harddisk manually because when no kernel driver can detect a special harddisk there is nothing what the user could do any further, except update his kernel to get hopefully a new/updated driver that can detect (and use) his special harddisk. Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Fuji Xerox M225 dw scanner visible via avahi, sane-find-scanner but not scanimage (Ubuntu 17.04)
Hello, On Aug 6 17:05 Jason Heeris wrote (excerpt): I'll set things up for scan-to-email like you suggest. depending on how good the user interface of that device is "stand-alone scanning to e-mail" directly at the device could be even more convenient to use in practice than scanning from a workstation via a SANE frontend, see the section about "How to use a professional network printer scanner copier all-in-one device" in https://en.opensuse.org/SDB:Configuring_Scanners Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] leading whitespace: spaces XOR tabs
Hello, only side-notes FYI (and somewhat off-topic): On Jul 12 10:23 m. allan noah wrote (excerpt): 1. I routinely use git blame to find out when I changed some line of code. A massive whitespace commit would wreck that. Yes, there are other ways to get that info after such a cleanup, but I'm lazy :) Because there are also various other reasons why 'git blame' does not show who made substantial code changes, I personally use meanwhile only git log -p --follow | less to find out who relly changed what in a substantial way and even more at the same time I can easily see how a part of code changed over the time (e.g. to find out possibly "false fixes" in the past). 2. I've read a great deal of other people's code over the years, and I am generally stumped by their logic and lack of comments. Whitespace is rarely a concern, even when they used a weird layout. I cannot agree more with "stumped by ... lack of comments", cf. https://github.com/rear/rear/wiki/Coding-Style In my opinion first and foremost source code is there to tell others (humans) what the author had meant that the machine should do. It is of secondary importance that source code tells the machine what to do. Strictly speaking source code never tells the machine what to do. Only machine code tells the machine what to do. Humans make source code. Tools make machine code from source code. Source code tells tools what machine code to make. I used simply "source code tells the machine what to do". Reasoning: If source code tells humans what is meant that the machine should do but that source code tells the machine to do something different (i.e. there is a bug in that source code), then other humans can see the bug (i.e. understand the issue) and fix it. In contrast when source code only tells the machine what to do nobody can properly fix that source code in case of issues (at least not with reasonable effort). When there are issues with such source code, the proper way out is to replace that useless source code with useful source code that first and foremost tells humans what is meant that it should do. Simply put: Source code that is for machines but not for humans will die out. Or in other words: Humans will delete source code that is for machines but not for humans. See also Eric Raymond's "Rule of Clarity" at https://en.wikipedia.org/wiki/Unix_philosophy or directly at http://www.catb.org/~esr/writings/taoup/html/ch01s06.html#id2877610 3. There are patches floating around in private repos that may not apply cleanly after such a change. On the other had when only using spaces (but no tabs) all indentations look well even in 'diff' output (i.e. in patches) which aids readability of patches for humans. Finally I think Olaf Meeuwissen should do us all a favour and let make us all more money by using spaces instead of tabs ;-) Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Sane-backends 1.0.27 has been released
Hello, On May 22 18:51 m. allan noah wrote (excerpt): SANE-Backends-1.0.27 has been released: many thanks to all developers and contributors for the new SANE-Backends-1.0.27 release! FYI: sane-backends-1.0.27 RPM packages for openSUSE users are now available in the openSUSE Build Service development project "graphics" for manual download for openSUSE Leap and openSUSE Tumbleweed from http://download.opensuse.org/repositories/graphics/ In general see the section "RPM packages of the 'sane-backends' scanner drivers" at https://en.opensuse.org/SDB:Configuring_Scanners Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Getting ready for sane-backends release
Hello Olaf, On May 14 20:11 Olaf Meeuwissen wrote (excerpt): Please run autoreconf on Debian GNU/Linux 8.8, but only if you really, really have to. It seems the leading "Please" tells one should do it while the rest tells one should better not do it. Simply put: Is running autoreconf good or bad in general? Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Version numbering (was Re: Fix PPA build)
Hello, On May 12 19:18 allan noahwrote (excerpt): They are already 1.0.26+git, Simply put: A version number like 1.0.26+git should have never been used for somethig after 1.0.25 but before 1.0.26 because 1.0.26+git means that it is after 1.0.26. I.e. 1.0.26+git is wrong, cf. my explanation below about Ghostscript release candidates where the Ghostscript upstream release candidate version number is also just wrong like 9.15rc1 for the first release candidate of the upcoming Ghostscript 9.15 release. On May 13 12:10 Olaf Meeuwissen wrote (excerpt): Distributions can also work around with an "epoch", so you get something like "1:1.0.26+git", but that's a bit ugly. at least not at openSUSE because here RPM "epoch" stuff is "forbidden by policy". I don't know the exact reasons behind but at last one reason is - as far as I know - that once you have set an "epoch" yon could never ever get rid of it later. I.e. basically introducing "epoch" is like introducing a leading "absolute maximum" part of the version i.e. a switch from "major.minor.patchlevel" to "epoch.major.minor.patchlevel". But we could also just admit that we've more or less goofed up on the versioning for our master branch, skip 1.0.26 and release as 1.0.27. Doing so will bypass any of the scenarios you worry about. Yes, please skip 1.0.26 and release as 1.0.27. This is simple, fail safe, and avoids needless complications. FYI: Im general regarding how to keep strictly growing version numbers, here some exceprts from the openSUSE ghostscript.spec file that explain how correct version numbers for intermediate stuff after version 1.2.3. like Git snapshots or release candidates for a next version 1.3.0 should look like: - # Special version needed for Ghostscript release candidates # (e.g. "Version: 9.14pre15rc1" for 9.15rc1). # Version 9.15rc1 would be newer than 9.15 # (run "zypper vcmp 9.15rc1 9.15") # because the rpmvercmp algorithm # would treat 9.15rc1 as 9.15.rc.1 # (alphabetic and numeric sections get separated # into different elements) # and 9.15.rc.1 is newer than 9.15 # (it has one more element in the list while # previous elements are equal) # so that we use an alphabetic prefix 'pre' # to make it older than 9.15 # (numbers are considered newer than letters). # But only with the alphabetic prefix "9.pre15rc1" # would be older than the previous version number "9.14" # because rpmvercmp would treat 9.pre15rc1 as 9.pre.15.rc1 # and letters are older than numbers # so that we keep additionally the previous version number # to upgrade from the previous version: Version:9.14pre15rc1 - This way users can "just upgrade" from Ghostscript release 9.14 to intermediate Ghostscript release candidates like 9.14pre15rc1 and further to 9.14pre15rc2 and 9.14pre15rc3 as they like and finally to the next Ghostscript release 9.15. Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Xerox WorkCentre 6027
Hello, only a side note - I didn't read the details here On Apr 23 15:08 Mayer Landau wrote (excerpt): All I know is I can get scan to work with basic ftp. is that perhaps related to the section about "How to use a professional network printer scanner copier all-in-one device" in https://en.opensuse.org/SDB:Configuring_Scanners Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] genesys : "Error during device I/O"
Hello, On Feb 12 19:33 Pierre Couderc wrote (excerpt): On 02/09/2017 01:49 PM, Johannes Meixner wrote: See "Trouble-Shooting (Debugging)" at https://en.opensuse.org/SDB:Configuring_Scanners ... my USBs are USB2 ... ... I thnk there is a problem with genesys ... ... [genesys] genesys_flatbed_calibration: led calibration failed: Error during device I/O I don't know any details about the genesys driver/backend but I guess it is not the genesys backend itself that fails but it fails because of a lower level error during device I/O. I.e. I guess it fails somewhere in the various USB layers like libusb or kernel USB drivers/modules or USB hardware cf. "Basics" and "USB" at https://en.opensuse.org/SDB:Configuring_Scanners Accordingly I would focus more on USB related debug messages as described in "Trouble-Shooting (Debugging)" at https://en.opensuse.org/SDB:Configuring_Scanners Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] genesys : "Error during device I/O"
Hello, On Feb 9 12:29 Pierre Couderc wrote (excerpt): env SANE_DEBUG_DLL=255 scanimage ... ... [dll] ... ... Is there a way to have more information...? See "Trouble-Shooting (Debugging)" at https://en.opensuse.org/SDB:Configuring_Scanners FYI: Nowadays "xhci_hcd" kernel driver/module issues (a.k.a. "USB 3") are the most often cause of "Error during device I/O", cf. http://lists.alioth.debian.org/pipermail/sane-devel/2016-November/034901.html and follow the links therein. Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Using Find Command in XSane PDF File
Hello, On Jan 31 22:22 Raymond Hanslits wrote (excerpt): I have been scanning and creating PDF files in XSane. However, I cannot get the Find Command to search for words and phrases in PDF files. Because the scanner device does not produce characters (no scanner "understands" what it scans) but only pixels, the data of what is scanned does not contain characters (or even words or phrases) but it contains only pixels regardless what data (container) format is used. See "XSane - Saving scan to text" at http://lists.alioth.debian.org/pipermail/sane-devel/2017-January/035005.html The crucial part is the OCR software, cf. https://en.wikipedia.org/wiki/Optical_character_recognition Personally I do not use OCR software but as far as I noticed it makes a difference regarding how good the OCR result is that appropriate scanning parameters are used specially for OCR. For example things like black and white scanning at a relatively low resolution could help to get better OCR results compared to high resolution photo scanning modes. Perhaps also the data format of what is scanned could make a difference (e.g. PNG versus JPEG or even PDF) for OCR. Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Canon LiDE 220
Hello, On Jan 8 16:44 Torsten Mohr wrote (excerpt): I bought the Canon LiDE 220, it is documented that it is fully supported by the genesys backend: http://www.sane-project.org/sane-mfgs.html#Z-CANON It is documented to be supported by the current SANE release 1.0.25. sane-backends-1.0.24-4.40.x86_64 sane-backends-32bit-1.0.24-4.40.x86_64 sane-backends-autoconfig-1.0.24-4.40.x86_64 Accordingly I would first and foremost upgrade to the current SANE release 1.0.25. See https://en.opensuse.org/SDB:Configuring_Scanners Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] project member list and maintenance status clean up
Hello, On Dec 18 19:01 Olaf Meeuwissen wrote (excerpt): What do you think? Should I just go ahead and make it clear that a *lot* of backends are unmaintained and leave it up to project members to start maintaining the ones they care about? from my point of view an essential part of the ideas behind free software is openness and truthfulness. I.e. from my point of view go ahead and make it very clear and obvious for everybody what the actual state is. I think the worst thing that could happen is that someone may volunteer for an unmaintained backend. In contrast when actually unmaintained code is somehow listed as if it was maintained then someone who does not know the details may never think about to volunteer. Just because people wrote and/or changed a significant chunk of a backend doesn't mean they intend to maintain it. I disagree to some extent: I think the one who wrote a piece of code should also maintain his piece of code - of course not forever - but at least for some reasonable time until it is clear that his piece of code is o.k. FYI: I love things like "git log -p --follow" and "git blame -w -M" for correct assignment of guilt ;-) Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] sane compatible copier
Hello, only a general question: On Nov 20 14:57 jan.p...@gmx-topmail.de wrote (excerpt): i am searching for a multifunction copier, such as a Toshiba eStudio 230 or an older Konica Minolta bizhub copier, that is supported by some sane-backend (via usb or lan). Both the Toshiba eStudio 230 and Konica Minolta bizhub mdels look as if they are professional network printer scanner copier all-in-one devices. If yes, I wonder why you need any SANE driver/backend software to use them? Cf. "How to use a professional network printer scanner copier all-in-one device" at https://en.opensuse.org/SDB:Configuring_Scanners Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] I/O Errors with hp 7400c
Hello, On Nov 14 20:58 Olaf Meeuwissen wrote (excerpt): The mailing list archives have a number of posts on USB3 issues. FYI: Only "lsusb -t" output shows what kernel driver is actually used. Regarding "USB 2" versus "USB 3" see http://lists.alioth.debian.org/pipermail/sane-devel/2015-December/034197.html and http://lists.alioth.debian.org/pipermail/sane-devel/2015-December/034207.html See also https://bugzilla.opensuse.org/show_bug.cgi?id=955079#c2 and https://bugzilla.opensuse.org/show_bug.cgi?id=856794 in particular https://bugzilla.opensuse.org/show_bug.cgi?id=856794#c50 Finally see http://bugzilla.opensuse.org/show_bug.cgi?id=975866 for possible workarounds by using an appropriate version of the sane-backends software that may (hopefully) work with your currently used "xhci_hcd" driver from your currently installed kerenel. Alternatively: If possible connect scanners at a traditional real "USB 2" port. If at all possible, use the device via USB2.0, by blacklisting the xhci kernel modules for example. Usually it is not possible to use USB 3 hardware as if it was USB 2 hardware (i.e. it is not possible to use USB 3 hardware without the xhci kernel module), see https://bugzilla.opensuse.org/show_bug.cgi?id=920067#c23 On nowadays computers there is often only USB 3 hardware so that blacklisting the xhci kernel module would make the whole USB no longer working which is in particular bad when keyboard and mouse are connected via USB 3 hardware, (have fun with un-blacklisting the xhci kernel module ;-). One needs real traditional USB 2 hardware in the computer to use a scanner device without the xhci kernel module. As far as I know only few particular USB 3 capable chipsets provide both real USB 3 hardware and real USB 2 hardware. An ultimate way out: Some users bought additional real USB 2 hardware for less than 10 Euros to escape from the current USB 3 mess, see https://bugzilla.opensuse.org/show_bug.cgi?id=856794#c49 I think about 10 Euros to get this issue out of sight is an acceptable price compared to the currently still ongoing annoyance with this issue (independent of when the issue may get solved at some time in the future). Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] new Backenddriver
Hello, On Oct 19 21:51 Olaf Meeuwissen wrote (excerpt): Michael Rall writes: ... So basically my SANE Backend needs to call a Webservice an will receive an Image as result. ... ... I mentioned the pnm backend is because it reads an image from file. I have a - perhaps stupid - generic question: What is the reason for a SANE backend when one already has an image as a file? I assumed the reason for a SANE backend is to create an image file in a known image data format from whatever special bits of data that a scanner hardware can deliver. For example when a network scanner can deliver an e-mail with the scanned image(s) e.g. as JPEG or PDF attachment, then I think there is no need for a SANE backend. In other words: When that Webservice cannot deliver known image data formats but only whatever special bits of data that need to be converted into a known image data format, then I would understand a SANE backend for it. Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Degrading images: Plustek OpticPro UT16
Hello, On Sep 22 18:33 rhn wrote (excerpt): 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 necessary, regardless of options. The backend for this scanner is plustek. at openSUSE we have an issue report with similar symptoms but different backend (HP Scanjet 2400, genesys backend): https://bugzilla.opensuse.org/show_bug.cgi?id=905034 I was unable to reproduce it or debug the root cause so that all I did was basically blind guess, e.g. see: https://bugzilla.opensuse.org/show_bug.cgi?id=905034#c18 Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] musl builder, PDF SANE Standard, __sane_unused__
Hello, On Jul 18 22:18 Olaf Meeuwissen wrote (excerpt): I had expected at least some reaction to my announcement[1] of the switch to libusb-1.0 as the new default for USB but, failing any, I assume that everyone is happy and all is well. [1] http://lists.alioth.debian.org/pipermail/sane-devel/2016-July/034654.html only for confirmation that I am happy, see http://lists.alioth.debian.org/pipermail/sane-devel/2015-October/034039.html (excerpt): At openSUSE we use libusb-1 since openSUSE 12.2 (i.e. we use libusb-1 since about April 2012) via "configure --enable-libusb_1_0". I am not aware of issues because of this. Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Canon Lide scanners stopped working in Ubuntu 16.04
Hello, On Jun 21 21:31 Dmitry B wrote (excerpt): Canon Lide scanners 110 and 220. They used to work in Ubuntu 14.04. In 16.04 they stopped working. I see an error message "Device I/O error". Is the xhci_hcd kernel module (a.k.a. USB 3) used for the USB port where the scanner is connected to? See what "lsusb" and "lsusb -t" reports to find out to what USB bus and port the scanner is connected to and then to find out what kernel driver (i.e. kernel module) is used for that USB bus and port. If "lsusb -t" reports "Driver=xhci_hcd" for the USB bus and port where the scanner is connected to you are hit by the current general USB 3 issues in the kernel. Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] xsane root only
Hello, On May 8 12:15 tom wrote (excerpt): ... does not work for me with out root permissions ... In particular when you alone use your own scanner connected to your own computer (i.e. when you do not need to care very much about other persons in a multi-user environment who should be allowed to access your scanner) and when you do not like to fiddle about udev access permission settings, have a look at what I wrote in the section about "USB scanner access permissions via udev" in https://en.opensuse.org/SDB:Configuring_Scanners as a "workaround to get those kind of issues out of sight" that should also work for SCSI scanners. Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Is the Iscan backend "epkowa" also affected by USB3 issues?
Hello Olaf, On Apr 28 08:45 Olaf Meeuwissen wrote (excerpt): The epkowa backend uses its own *copy* of the sanei_usb code. There was a minor fix for USB 3.0 connected scanners in 2.30.1 (dated 2014-12-03). That same fix was applied to sane-backends on 2014-12-10. Please note that iscan does *not* actively track changes to the sane-backends version of the sanei_usb code. Also, iscan-2.30.1 is the most recent version. In the end I like to understand if a version change of the installed sane-backends software on the user's computer could make a difference whether or not the "epkowa" backend works with the xhci_hcd kernel module. That is rather unlikely but not impossible as it may depend on what other backends do during their sane_init() and sane_get_devices(). If all other backends are disabled, changing the version of the installed sane-backends should not make a difference. That is because the dll backend doesn't do anything USB related itself. Hope this helps, Many thanks for your explanation. It helps a lot! Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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 the Iscan backend "epkowa" also affected by USB3 issues?
Hello Olaf Meeuwissen, we (i.e. openSUSE) got an issue report of a user who uses the "epkowa" backend for an Epson GT-X770 / Perfection V500 at a USB port with the xhci_hcd kernel driver module which does not work, cf. https://bugzilla.opensuse.org/show_bug.cgi?id=976813 Now I wonder if the "epkowa" backend could be also affected by the current sane-backends 1.0.25 "Workaround for USB3 problems in Linux kernel" that seems to no longer work with newest kernels, cf. http://lists.alioth.debian.org/pipermail/sane-devel/2016-January/034254.html In other words, I wonder if the "epkowa" backend uses the sane-backends USB code or if the "epkowa" backend implements USB communication on its own. In the end I like to understand if a version change of the installed sane-backends software on the user's computer could make a difference whether or not the "epkowa" backend works with the xhci_hcd kernel module. Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] HP ScanJet 7400c open of device faled: invalid arguement
Hello, On Apr 26 16:47 Chen, Xianwen wrote (excerpt): 'lsusb' returns: ... Bus 003 Device 033: ID 03f0:0801 Hewlett-Packard ScanJet 7400c ... 'lsusb -t' returns: ... /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M ... |__ Port 6: Dev 33, If 0, Class=, Driver=, 12M You scanner is connected at a USB bus/port where the kernel module/driver "xhci_hcd" (a.k.a. "USB 3") is used. There are currently isues when the xhci kernel module is used for USB ports where the scanner is connected. Only "lsusb -t" will tell you what kernel module/driver is actually used for the USB bus and port where your scanner is connected to. Neither the color nor what the port/connector is labeled on the computer is reliable regarding what kernel driver is used for the port/connector. For example my testing machine has 4 USB connectors, two labeled with the "super speed" USB logo (a.k.a. USB 3) and two labeled with the normal USB logo (a.k.a. USB 2) but for all 4 ports xhci is used. Furthermore all USB connectors on my testing machine have same dark color. Also the "super speed" (USB 3) labeled connectors are basically black. Their color is "very dark" but not "100% black" and neither blue (USB 3.0) nor teal blue (USB 3.1), cf. https://en.wikipedia.org/wiki/USB#Colors Only "lsusb -t" output shows what kernel driver is actually used. Regarding "USB 2" versus "USB 3" see http://lists.alioth.debian.org/pipermail/sane-devel/2015-December/034197.html and http://lists.alioth.debian.org/pipermail/sane-devel/2015-December/034207.html See also https://bugzilla.opensuse.org/show_bug.cgi?id=955079#c2 and https://bugzilla.opensuse.org/show_bug.cgi?id=856794 in particular https://bugzilla.opensuse.org/show_bug.cgi?id=856794#c50 and finally see http://bugzilla.opensuse.org/show_bug.cgi?id=975866 for possible workarounds by using an appropriate version of the sane-backends software that may (hopefully) work with your currently used "xhci_hcd" driver from your currently installed kerenel. With newest kernels a current development snapshot of the sane-backends software should also work but you may have to compile that on your own when your Linux distributor does not provide ready-to-use software packages of sane-backends development snapshots. Alternatively: If possible connect scanners at a traditional "USB 2" port. It seems your computer also has USB ports where it seems traditional "USB 2" kernel modules/drivers are used (from your "lsusb -t" output): /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M ... /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M I would expect "Driver=ehci_hci" not "Driver=ehci-pci" but I am not at all a kernel expert to know details. If those USB ports have connectors at the outside of your computer so that you could connect the scanner at such a USB 2 port, then the scanner should probably "just work". Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] HP ScanJet 7400c open of device faled: invalid arguement
Hello, On Apr 24 11:58 Chen, Xianwen wrote (excerpt): lsusb recognizes the scanner: Bus 003 Device 008: ID 03f0:0801 Hewlett-Packard ScanJet 7400c What do both commands lsusb and lsusb -t show (the full "lsusb -t" output is needed). What can I do to (1) provide more debug information See "Trouble-Shooting (Debugging)" at https://en.opensuse.org/SDB:Configuring_Scanners Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Xerox Workcentre 3225 support?
Hello, On Mar 21 14:21 Bernhard Reiter wrote (excerpt): [..] then have a look at "Trouble-Shooting (Debugging)" in https://en.opensuse.org/SDB:Configuring_Scanners Thanks for pointing to this page, too. (I did search for a page like this and however did not manage to find it. Maybe a search entry point for all OpenSuse related information easily reachable from https://www.opensuse.org/ would be helpful, I've looked for it there.) When I search for openSUSE articles I simply use Google. For example when I enter in Google scanner debug openSUSE then I get topmost in Google's list the above article: -- SDB:Configuring Scanners - openSUSE https://en.opensuse.org/SDB:Configuring_Scanners ... Trouble-Shooting (Debugging) ... -- Is there a point where I can financially voluntarily pay a small amount to you for this support you have given me. I think it is perfectly o.k. and greatly appreciated when you contribute to openSUSE in any way you like as described at https://en.opensuse.org/Portal:How_to_participate In other words: I think the openSUSE project benefits most when you "pay" with some of your time. Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Xerox Workcentre 3225 support?
Hello, On Mar 20 00:17 Bernhard Reiter wrote (excerpt): Xerox WorkCentre 3225 connected with USB. In general when your scanner is connected via USB: There are currently isues when the xhci kernel module is used for USB ports where the scanner is connected. Only "lsusb -t" will tell you what kernel module/driver is actually used for the USB bus and port where your scanner is connected to. Check the "lsusb -t" output if the "xhci_hcd" USB kernel driver (a.k.a. "USB 3") is used. Neither the color nor what the port is labeled on the computer is reliable regarding what kernel driver is used for the port. For example my testing machine has 4 USB ports, two labeled with the "super speed" USB logo (a.k.a. USB 3) and two labeled with the normal USB logo (a.k.a. USB 2) but for all 4 ports xhci is used. Furthermore all USB ports on my testing machine have same dark color. Also the "super speed" (USB 3) labeled ports are basically black. Their exact color is "very dark" but not "100% black" and neither blue (USB 3.0) nor teal blue (USB 3.1), cf. https://en.wikipedia.org/wiki/USB#Colors Only "lsusb -t" output shows what kernel driver is actually used. See https://bugzilla.suse.com/show_bug.cgi?id=955079#c2 and https://bugzilla.opensuse.org/show_bug.cgi?id=856794 in particular see https://bugzilla.opensuse.org/show_bug.cgi?id=856794#c50 Regarding "USB 2" versus "USB 3" see also http://lists.alioth.debian.org/pipermail/sane-devel/2015-December/034197.html and http://lists.alioth.debian.org/pipermail/sane-devel/2015-December/034207.html In particular in http://lists.alioth.debian.org/pipermail/sane-devel/2015-December/034197.html there is: When your scanner is not connected at a USB port where the kernel module xhci_hcd is used as kernel driver (e.g. when your scanner is connected at a USB port where the kernel module uhci_hcd or ehci_hcd is used as kernel driver), then have a look at "Trouble-Shooting (Debugging)" in https://en.opensuse.org/SDB:Configuring_Scanners For example to get USB debugging information you could use comands (as root) like export SANE_DEBUG_SANEI_USB=128 scanimage -L unset SANE_DEBUG_SANEI_USB Source RPM : sane-backends-1.0.23-9.2.3.src.rpm You may try out if the current sane-backends-1.0.25 perhaps works better. For direct RPM download of sane-backends-1.0.25 from the OBS "graphics" project, use http://download.opensuse.org/repositories/graphics/ and select your exact operating system and architecture. In particular see https://bugzilla.suse.com/show_bug.cgi?id=856794#c30 and subsequent comments. The current sane-backends-1.0.25 RPM from the OBS "graphics" project should no longer have issues with "libgphoto2" on released openSUSE versions because meanwhile the gphoto2 backend was removed because its usefulness is highly questionable, but adds many (indirect) build and runtime dependencies, see the current RPM changelog: https://build.opensuse.org/package/view_file/graphics/sane-backends/sane-backends.changes?expand=1 Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] external backend license
Hello, On Mar 15 07:40 m. allan noah wrote (excerpt): ... we have seen time and again that your users will be better served by an open backend. If you keep the code closed, you will be unable to support users on fringe platforms I think one cannot overemphasize that point! I would even say: If you keep the code closed, you will be unable to really support your users on any platform. Reason (here only for Linux because I only know about Linux): The advantage of a free software driver for a manufacturer is that he will receive comprehensive out-of-the-box support for his devices * in all Linux distributions that contain the SANE software * on all hardware platforms for which those Linux distributions are available * continuously also in new versions of that Linux distributions without extra expenses for the manufacturer because only a free software driver can be included in the SANE upstream source code tarball that is used by all Linux distributions to make the sane-backends software packages that the Linux distributions provide to their users. In short: With a free software driver you get out-of-the-box support for basically all Linux users. In contrast: With a non-free software driver you are totally on your own how you provide your non-free software to your users and how you keep your non-free software working on all those various Linux distributions over the time while arbitrary changes are continuously happening in the whole Linux world. In particular for openSUSE you may have a look at "Third-Party Scanner Drivers" at https://en.opensuse.org/SDB:Configuring_Scanners Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Problem getting Epson V370 Photo working under OpenSuSE
Hello, On Mar 10 08:17 Graham Freeman wrote (excerpt): I used YaST/scanner to configure the scanner. It presents two items in its list: epkowa Epson (unknown model) at epkowa:usb:003:004 EPSON Perfection V37/V370 USB scanner (vendor=0x04b8 [EPSON], product=0x014a [EPSON Perfecttion V37/V370]) at libusb:003:004 If I attempt to edit the second to configure it, I get a popup message "Possibly Problematic Driver The epkowa driver may cause problems on 64-bit x86_64 architecture" When you click [Continue] on that popup you get a subsequent popup message that reads: -- The third-party Image Scan driver software from Epson/Avasys is required. The Image Scan driver software is made and provided by Epson (formerly Avasys) http://download.ebz.epson.net/dsc/search/01/search/?OSC=LXEpson (formerly Avasys http://avasys.jp/eng/linux_driver/) where RPM packages for 32-bit (i386) and 64-bit (x86_64) architecture can be downloaded (if you accept the Epson/Avasys license agreements). The Image Scan driver contains proprietary binary-only software. For some models it is only available for 32-bit (i386) architecture which does not work when you have a 64-bit system installation. Some scanners are also supported by another (free-software) driver. When your scanner model requires a DFSG non-free (proprietary) module, you have to download and install two packages from Epson/Avasys: The 'iscan' package for the base software and an additional model dependant 'iscan-plugin' package with the proprietary module. -- That message is shown a bit unfortunate as an "Error" popup because you cannot successfully continue the scanner setup here which means there is some kind of "Error" at that point. The text is a bit old (from May 08 2012) and perhaps somewhat outdated but I cannot continuously verify if all the details are still 100% correct. But the most important thing seems to be still correct: You can get the driver software from Epson via http://download.ebz.epson.net/dsc/search/01/search/?OSC=LXEpson In general regarding third-party drivers see "Third-Party Scanner Drivers" at https://en.opensuse.org/SDB:Configuring_Scanners FYI: Since a longer time I do no longer have time to actively maintain and update the YaST scanner module. Therefore (as long as nobody else cares about it) it stays in its current form (frankly: it bitrots). My last real adaption dated May 08 2012 (cf. "rpm -q --changelog yast2-scanner") because of https://bugzilla.opensuse.org/show_bug.cgi?id=746038 Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Scanner Lide 210 working with old and bleeding edge distro, but not with current stable distro
Hello, On Mar 3 15:58 Sebastian Weber wrote (excerpt): By "clean" installation I meant I installed Leap42 on an empty disk, using the official NET-installer ISO, and without touching the repositories. It might even be an update of an openSUSE RPM that makes your scanner no longer work. When you installed from the ISO the RPMs there are probably not the newest openSUSE updated RPMs but the RPMs from the time when openSUSE Leap 42.1 was initially released. Perhaps later you got the openSUSE update RPMs and that may have made your scanner no longer work. Suspicious could be the kernel because canges in recent kernels had caused some issues regarding USB scanner communication in sane-backends - but I am not at all a sufficient USB expert to know the details here. Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Scanner Lide 210 working with old and bleeding edge distro, but not with current stable distro
Hello, On Mar 3 15:58 Sebastian Weber wrote (excerpt): Meanwhile I had to add repositories to install some other software, and now, my scanner doesn't work again. I agree that most probably something from this software has broken my scanner, and I'll try to find out what it was. Use the command rpm -qa --last to show all installed RPMs sorted by installation date with the latest ones topmost. This could help you to find out what new RPMs could be suspicious regarding the scanner. Furthermore you may experiment with the zypper command to find out what RPMs are from official openSUSE Leap 42.1 versus what RPMs are from other repositories. You may use something like (see "man zypper" for details) zypper dup -D -r openSUSE-Leap-42.1-Oss --no-recommends and look in its output in particular for those packages that would change vendor from something non-openSUSE back to openSUSE to identify suspicious packages from non-openSUSE that had replaced ones from openSUSE. The '-D' option "dry-run" does not actually install or update any package. Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Scanner Lide 210 working with old and bleeding edge distro, but not with current stable distro
Hello, first and foremost many thanks for your feedback. Such feedback happens not always. When it is missing, it leaves the others with unanswered questions what the heck could be wrong why something fails for one particular user. On Mar 2 18:46 Sebastian Weber wrote (excerpt): Though I reinstalled all sane components and also the Kernel and other components, I didn't manage to get my scanner working. As a last resort, I did a clean re-installation of the entire operating system. My scanner worked out of the box... What exactly does "clean" mean here? Did you perhaps use various kind of additional non-openSUSE:Leap:42.1 software repositories? If yes, software packages from non-openSUSE:Leap:42.1 repositories could have messed up something. But if you used only openSUSE:Leap:42.1 software repositories it would be stange and unexpected and also a bit scaring because I would not like what that could mean in the end: "When something does not work and you don't find a solution, just try a complete re-installation of your entire operating system from scratch." Again: It makes a crucial difference whether or not you used only openSUSE:Leap:42.1 software repositories. Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Scanner Lide 210 working with old and bleeding edge distro, but not with current stable distro
Hello, On Feb 22 17:01 Sebastian Weber wrote (excerpt): # lsusb Bus 001 Device 005: ID 04a9:190a Canon, Inc. CanoScan LiDE 210 ... # lsusb -t ... /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/10p, 480M ... | |__ Port 6: Dev 5, If 0, Class=Vendor Specific Class, Driver=, Your scanner is connected at USB "Bus 001" as "Device 005" and for the USB "Bus 01" the kernel "Driver=ehci-pci" is used which means so called "USB 2" is used for your scanner. For further information see my previous mail where I wrote: Regarding "USB 2" versus "USB 3" see also http://lists.alioth.debian.org/pipermail/sane-devel/2015-December/034197.html and http://lists.alioth.debian.org/pipermail/sane-devel/2015-December/034207.html In http://lists.alioth.debian.org/pipermail/sane-devel/2015-December/034207.html there is: Scanners usually belong to the generic "Vendor Specific Class" because there is no specific USB device class "scanner". In http://lists.alioth.debian.org/pipermail/sane-devel/2015-December/034197.html there is: When your scanner is not connected at a USB port where the kernel module xhci_hcd is used as kernel driver (e.g. when your scanner is connected at a USB port where the kernel module uhci_hcd or ehci_hcd is used as kernel driver), then have a look at "Trouble-Shooting (Debugging)" in https://en.opensuse.org/SDB:Configuring_Scanners For example to get USB debugging information you could use comands (as root) like export SANE_DEBUG_SANEI_USB=128 scanimage -L unset SANE_DEBUG_SANEI_USB Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Scanner Lide 210 working with old and bleeding edge distro, but not with current stable distro
Hello Sebastian,
On Feb 21 01:43 Sebastian Weber wrote (excerpt):
Canon LIDE 210 ... genesys backend
...
So far, I have been using the scanner connected to my PC,
which did run openSuse 13.2 (And SANE 1.0.24 or .25)
Now I upgraded to openSuse Leap 42.1 ("stable release"),
and the scanner does not work. (SANE 1.0.24 and .25)
However, my laptop runs openSuse Tumbleweed ("bleeding
edge release"), and the scanner works fine. (SANE 1.0.25)
...
I tried other USB ports, but the scanner was definitely
working at them before
I guess "lsusb" and then "lsusb -t" will tell you that
for the USB bus and port where your scanner is connected to
the "xhci_hcd" USB kernel driver (a.k.a. "USB 3") is used.
See
https://bugzilla.suse.com/show_bug.cgi?id=955079#c2
and
https://bugzilla.opensuse.org/show_bug.cgi?id=856794
in particular see
https://bugzilla.opensuse.org/show_bug.cgi?id=856794#c50
Regarding "USB 2" versus "USB 3" see also
http://lists.alioth.debian.org/pipermail/sane-devel/2015-December/034197.html
and
http://lists.alioth.debian.org/pipermail/sane-devel/2015-December/034207.html
Kind Regards
Johannes Meixner
--
SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard,
Graham Norton - HRB 21284 (AG Nuernberg)
--
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] Some weirdness with a Canon LiDE 220
Hello, On Dec 16 12:45 Scott Alfter wrote (excerpt): ... lsusb -t shows the following for the home system: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M |__ Port 3: Dev 2, If 0, Class=Wireless, Driver=, 12M |__ Port 3: Dev 2, If 1, Class=Wireless, Driver=, 12M |__ Port 4: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M |__ Port 5: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 9: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 13: Dev 6, If 0, Class=Video, Driver=, 480M |__ Port 13: Dev 6, If 1, Class=Video, Driver=, 480M |__ Port 13: Dev 6, If 2, Class=Audio, Driver=snd-usb-audio, 480M |__ Port 13: Dev 6, If 3, Class=Audio, Driver=snd-usb-audio, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M At this time, it has a keyboard, mouse, webcam, Bluetooth dongle, and ANT+ dongle plugged in. I filled the "USB 2.0" (black) ports up before I started plugging things into USB 3.0 (blue) ports, yet it looks like everything's going through the xhci_hcd driver. All the following devices (each with one or more interfaces) are going through the xhci_hcd driver: /: Bus 03 |__ Port 3: Dev 2 |__ Port 4: Dev 3 |__ Port 5: Dev 4 |__ Port 9: Dev 5 |__ Port 13: Dev 6 You did not tell what of those devices the scanner is. I guess it is /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M ... |__ Port 4: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M Scanners usually belong to the generic "Vendor Specific Class" because there is no specific USB device class "scanner". Regarding "USB 2.0 (black) and USB 3.0 (blue)": Neither the color nor what the port is labeled on the computer is reliable regarding what kernel driver is used for the port. Only the "lsusb -t" output shows what kernel driver is used. For example all USB ports on my testing machine have same dark color. Also the "super speed" (USB 3) labeled ports are basically black. Their exact color is "very dark" but not "100% black" and neither blue (USB 3.0) nor teal blue (USB 3.1), cf. https://en.wikipedia.org/wiki/USB#Colors On my testing machine xhci_hcd is used for all USB ports where I can connect devices (i.e. all external USB ports). Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Some weirdness with a Canon LiDE 220
On Dec 15 13:29 Scott Alfter wrote (excerpt): The new motherboard supports USB 3.0 as well as 2.0 Really pure traditional USB 2 hardware? In general when your scanner is connected via USB: There are currently issues with USB ports where the kernel module "xhci" is used as kernel driver. When "lsusb -t" shows "Driver=xhci_hcd" for the USB bus and port where the USB scanner is connected (see "lsusb" where the scanner is connected), then there could be issues depending on the computer hardware and firmware. In this case see https://bugzilla.opensuse.org/show_bug.cgi?id=856794 In particular see https://bugzilla.opensuse.org/show_bug.cgi?id=856794#c24 that reads (excerpt): - My machine has 4 USB ports, two labeled with the "super speed" USB logo (a.k.a. USB 3) and two labeled with the normal USB logo (a.k.a. USB 2) but for all 4 ports xhci is used and it fails on all 4 ports. - and see https://bugzilla.opensuse.org/show_bug.cgi?id=856794#c40 When your scanner is not connected at a USB port where the kernel module xhci_hcd is used as kernel driver (e.g. when your scanner is connected at a USB port where the kernel module uhci_hcd or ehci_hcd is used as kernel driver), then have a look at "Trouble-Shooting (Debugging)" in https://en.opensuse.org/SDB:Configuring_Scanners For example to get USB debugging information you could use comands (as root) like - export SANE_DEBUG_SANEI_USB=128 scanimage -L unset SANE_DEBUG_SANEI_USB ----- Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] multiple, identical scanners?
Hello, On Nov 10 14:09 Jeremy Chacon wrote (excerpt): ... sometimes gives an I/O Error ... In general "sometimes I/O Error" indicates that the root cause is somehow hardware related where "hardware" means the actual computer hardware plus the computer's built-in firmware (i.e. BIOS or UEFI) and "hardware related" means computer hardware plus firmware plus Linux kernel driver plus low-level hardware related software (e.g. libusb). You may have a look at "a stack consisting of various layers must be functional in its entirety" in https://en.opensuse.org/SDB:Configuring_Scanners#Basics You did not tell how your scanners are connected to your computer. If your scanners are connected via USB: There are currently issues with USB ports where the kernel module "xhci" is used as kernel driver. When "lsusb -t" shows "Driver=xhci_hcd" for the USB bus and port where the USB scanner is connected (see "lsusb" where the scanner is connected), then there could be issues depending on the computer hardware and firmware. In this case see https://bugzilla.opensuse.org/show_bug.cgi?id=856794 in particular see https://bugzilla.opensuse.org/show_bug.cgi?id=856794#c24 that reads (excerpt): - My machine has 4 USB ports, two labeled with the "super speed" USB logo (a.k.a. USB 3) and two labeled with the normal USB logo (a.k.a. USB 2) but for all 4 ports xhci is used and it fails on all 4 ports. - and see https://bugzilla.opensuse.org/show_bug.cgi?id=856794#c40 When your scanner is not connected at a USB port where the kernel module xhci_hcd is used as kernel driver (e.g. when your scanner is connected at a USB port where the kernel module uhci_hcd or ehci_hcd is used as kernel driver), then have a look at "Trouble-Shooting (Debugging)" in https://en.opensuse.org/SDB:Configuring_Scanners For example in your case to get USB debugging information you could use comands (as root) like - export SANE_DEBUG_SANEI_USB=128 scanimage -L unset SANE_DEBUG_SANEI_USB - Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Xsane can't find scanner - again, but this one is USB
Hello, an addendum FYI: On Nov 3 07:29 m. allan noah wrote (excerpt): When I run xsane with no scanners connected, I get a dialog which says so- it does not just quit. I like to confirm that xsane behaviour also on my system and even more when I run xsane when "scanimage -L" shows "No scanners were identified", then xsane first shows this notification popup: No devices no devices available [Close] [Help] and after clicking [Help] xsane shows a subsequent notification popup: No devices available Possible reasons: 1) There really is no device that is supported by SANE 2) Supported devices are busy 3) The permissions for the device file do not allow you to use it - try as root 4) The backend is not loaded by SANE (man sane-dll) 5) The backend is not configured correctly (man sane-"backendname") 6) Possibly there is more than one SANE version installed [Close] clicking [Close] finishes xsane. Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Xsane can't find scanner - again, but this one is USB
Hello, an addedum FYI On Nov 2 22:50 MR ZenWiz wrote (excerpt): On Fri, Oct 30 Olaf Meeuwissen <paddy-h...@member.fsf.org> wrote: Others have already commented on the fact the USB3 support and the xhci kernel driver may be causing your trouble. This could very well be - it's one of the white m/b ports labeled USB (not USB3), so I have to trust that--sort of. Neither the color nor what the port is labeled on the computer is reliable regarding what kernel driver is used for the port. Only the "lsusb -t" output shows what kernel driver is used. When "lsusb -t" shows "Driver=xhci_hcd" for the USB bus and port where the USB scanner is connected, then there could be issues depending on the computer hardware and firmware (BIOS or UEFI). See https://bugzilla.opensuse.org/show_bug.cgi?id=856794#c24 that reads (excerpt): - My machine has 4 USB ports, two labeled with the "super speed" USB logo (a.k.a. USB 3) and two labeled with the normal USB logo (a.k.a. USB 2) but for all 4 ports xhci is used and it fails on all 4 ports. - All 4 USB ports on my testing machine have same dark color. Also the "super speed" labeled ports are basically black. Their exact color is "very dark" but not "100% black" and neither blue (USB 3.0) nor teal blue (USB 3.1), cf. https://en.wikipedia.org/wiki/USB#Colors And see https://bugzilla.opensuse.org/show_bug.cgi?id=856794#c40 that reads (excerpt): - It depends on the computer hardware where "hardware" includes the computer's firmware (BIOS or UEFI). There are computers where USB3 always "just works". There are computers where USB3 fails under certain conditions. Perhaps there are computers where USB3 always fails. - Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Xsane can't find scanner - again, but this one is USB
Hello, On Oct 29 23:12 MR ZenWiz wrote (excerpt): I run Xubuntu 14.04.3 with an HP 5740 all-in-one attached on the USB (bus 3, device 14). Is it connected at USB3 i.e. via the kernel module xhci? Does "lsusb -t" show the "Driver=xhci" for this device? If yes, there are curently issues with USB3. For example see https://bugzilla.opensuse.org/show_bug.cgi?id=856794 This is most frustrating. I hate to say it, but Windows never has this problem, and I'm no fan of that PoS. I cannot describe sufficiently in words how much I hate it to read such frustrating useless stuff again and again. Why do you think you are in a position to complain on a public accessible free software developer mailing list? It seems you think you are in a position to demand from free software developers that they make their software so that it supports your selfish "no fan of" needs? Just buy whatever you like wherefrom you like and then you might have some (limited) rights to complain there. Alternatively - if you really want free software (and not only something for free) - you yourself are responsible to support freedom which means you must contribute real value to free software projects. Everybody can contribute real value to free software projects. Even a totally unexperienced end-user can for example provide meaningful issue reports that support and help free software developers to make their software better, cf. "Basics" at https://en.opensuse.org/SDB:How_to_Report_a_Printing_Issue In general if you are really interested in free software read the various articles at the Free Software Foundation. Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Xsane can't find scanner - again, but this one is USB
Hello, On Oct 30 15:38 Gernot Hassenpflug wrote (excerpt): Does your computer have a USB3 port and are you using it? Or does it have standard older USB2 ports only? Attention: One needs to be careful with things that only look like USB2 ports, cf https://bugzilla.opensuse.org/show_bug.cgi?id=856794#c24 (excerpt) -- My machine has 4 USB ports, two labeled with the "super speed" USB logo (a.k.a. USB 3) and two labeled with the normal USB logo (a.k.a. USB 2) but for all 4 ports xhci is used and it fails on all 4 ports. -- FYI, see also https://bugzilla.opensuse.org/show_bug.cgi?id=856794#c40 Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] 1.0.25 is out, now what?
Hello, On Oct 29 20:13 Stef wrote (excerpt): - drop support for parallel port scanners rather than dropping support for working hardware (and which doesn't require any work), I'd prefer an option to optionally compile them in (or out). That would give the package builder the final choice and keep support for them for those who still use them (still got 2 of them). See what I had written here: -- Date: Wed, 21 Oct 2015 13:43:17 +0200 (CEST) ... Subject: Re: [sane-devel] 1.0.25 is out, now what? . . . My current plan how to drop it is to keep the backends for parallel port scanners but to only remove the entries for parallel port scanners from the description files which results that the YaST scanner setup no longer shows parallel port scanners. This way I could get end-user feedback if parallel port scanners are still of any interest and if yes, I could tell the user how to enable the matching backend manually without the need to install a different sane-backends package to get a parallel port scanner working. -- I.e. I have no plans to remove the actual backends (driver libraries) all of a sudden. Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Xsane can't find scanner - again, but this one is USB
Hello Gernot, On Oct 30 18:29 Gernot Hassenpflug wrote (excerpt): So the question one needs to keep in mind is not USB3 per se, but whether the xhci kernel module is being used. Yes. As far as I know (but I am neither a USB expert nor a Linux kernel expert) - the xhci kernel module is always used for USB3 and sometimes also for what is labeled as USB2 on the computer. As far as I know the reason why xhci is used for what is labeled as USB2 on the computer is that internally it is one same chip (or perhaps even only a chip-like sub-component of a bigger hardware thingy). When xhci is used it cannot be replaced by a kernel module for traditional USB2, see https://bugzilla.opensuse.org/show_bug.cgi?id=920067#c23 Furthermore sometimes the xhci kernel module "just works" and sometimes not depending on weird circumstances, see https://bugzilla.opensuse.org/show_bug.cgi?id=856794#c40 Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] 1.0.25 is out, now what?
Hello
On Oct 28 20:18 Olaf Meeuwissen wrote (excerpt):
Johannes Meixner writes:
...
Suggestion for an additional goal for sane-backends-1.0.26:
- drop support for parallel port scanners
Low priority for 1.0.26 at best.
Also for me this is low priority because I have zero
issue reports regarding parallel port scanners.
I will report my experience when I have droped support
for parallel port scanners in openSUSE Tumbleweed.
But your suggestion made me think of
something more important:
- integrate distribution patches
The openSUSE patches are public available via the
openSUSE Build Service (OBS) development project "graphics"
therein the source package "sane-backends" at
https://build.opensuse.org/package/show/graphics/sane-backends
Currently the only patch which is of interest for
SANE upstream is dell1600n_net-fix-strncat.patch
which is already fixed at SANE upstream
https://alioth.debian.org/tracker/index.php?func=detail=315198_id=30186=410366
All others are only for SUSE-specific needs.
RFC for an additional goal for sane-backends-1.0.26:
- switch to group "lp" instead of "scanner"
...
I think it best to leave this to the individual distributions to decide.
My hope is that the individual distributions might even be able
to agree on a common default so that all Linux users could have
the same default base of operations.
What can be done fairly easily, however, is to make it easier for them
to override/customize the DEVMODE, DEVOWNER and DEVGROUP values in
tools/sane-desc.c.
Perhaps a configure option to specify that would be nice?
FYI, Debian has
ENV{libsane_matched}=="yes", RUN+="/bin/setfacl -m g:scanner:rw $env{DEVNAME}"
I like to understand the reson behind why Debian uses
the "scanner" group.
Is it that for Debian use of consumables (paper and ink/toner)
in a printer is more strictly controlled than scanners?
Regardless what the reason is, I also like to understand how
Debian deals with multifunction devices because - as far as
I understand it - there is the conflict that multifunction devices
would have to belong both to the "lp" and the "scanner" group.
Kind Regards
Johannes Meixner
--
SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard,
Graham Norton - HRB 21284 (AG Nuernberg)
--
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] 1.0.25 is out, now what?
Hello, On Oct 21 21:32 Olaf Meeuwissen wrote (excerpt): Alessandro Zummo writes: There's probably still some bug in the usb code. I have intermittent results with some scanners on usb2 and with others on usb3. switching among the two usb standards solves them all. I'm curious about USB related issues that other backends are facing that might be solved by switching to libusb-1 as the default. At openSUSE we use libusb-1 since openSUSE 12.2 (i.e. we use libusb-1 since about April 2012) via "configure --enable-libusb_1_0". I am not aware of issues because of this. Regarding USB 3, see https://bugzilla.opensuse.org/show_bug.cgi?id=856794 Summary: It seems one needs a very current kernel for USB 3. For me kernel 4.1.6 did not work with sane-backends-1.0.25. For me kernel-vanilla-4.3.rc5 works where it seems the xhci USB driver is now at least somewhat fixed. But I needed additionally the workarounds for the broken xhci driver in sane-backends-1.0.25 i.e. sane-backends-1.0.24 did not work for me with kernel-vanilla-4.3.rc5, see https://bugzilla.opensuse.org/show_bug.cgi?id=856794#c28 Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] 1.0.25 is out, now what?
Hello Olaf, first and foremost many thanks for all your "SANE Project Janitor" work. On Oct 19 22:20 Olaf Meeuwissen wrote (excerpt): ... unofficial ... goals for sane-backends-1.0.26. - modernize the autofoo bits - fix all compiler warnings - bump language level to C99 - default to libusb-1.0 ... release by early February 2016. ... Feedback and suggestions are welcome. Suggestion for an additional goal for sane-backends-1.0.26: - drop support for parallel port scanners My plan is to do this for sane-backends-1.0.25 for openSUSE Tumbleweed but currently I provide sane-backends-1.0.25 with parallel port scanner support because I simply had no time yet to do it. My current plan how to drop it is to keep the backends for parallel port scanners but to only remove the entries for parallel port scanners from the description files which results that the YaST scanner setup no longer shows parallel port scanners. This way I could get end-user feedback if parallel port scanners are still of any interest and if yes, I could tell the user how to enable the matching backend manually without the need to install a different sane-backends package to get a parallel port scanner working. RFC for an additional goal for sane-backends-1.0.26: - switch to group "lp" instead of "scanner" Currently SANE upstream creates udev rules with MODE="0664", GROUP="scanner". Hereby I ask for comments whether or not SANE upstream should switch to group "lp" instead of "scanner". The reason for using "lp" instead of "scanner" is described at "USB scanner access permissions via udev" in https://en.opensuse.org/SDB:Configuring_Scanners (excerpt): -- For USB multifunction devices the multifunction aspect could make it troublesome in other Linux distributions that may use the SANE upstream way to set scanner device nodes to group "scanner" and add the users to that "scanner" group which conflicts with the CUPS backend that usually needs "lp" group read/write access to access the printer unit so that special setup is needed to make printing work. In openSUSE there is no group "scanner". Only the "lp" group exists and is used in /etc/udev/rules.d/55-libsane.rules as MODE="0664", GROUP="lp". It is sufficiently secure and reasonable easy to use by default the same group "lp" for printers and scanners because both kind of devices usually require physical user access (to get the printed paper or to place a paper on the scanner) so that both kind of devices should usually require the same kind of security and for multifunction devices only one group can be set and then the "lp" group is the more reasonable default setting. -- I do not know how read/write access for USB scanners is done in other Linux distributions. If also other Linux distributions set normal-user read/write access for the device node by the udev "uaccess" tool that sets device node user ACLs, then the "scanner" group should be no longer actually needed because normal-user read/write access via ACL is independent of the device node group so that the device node group could be changed to "lp" without regressions for normal-user read/write access. Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Scanner CanoScan9000 Mk2
Hello, On Oct 21 07:36 Hans-Christoph Paul wrote (excerpt): CanoScan9000 Mk2 USB scanner I neither not have this one nor a similar model so that I cannot help with model-specific issues. In general regarding "Trouble-Shooting (Debugging)" see https://en.opensuse.org/SDB:Configuring_Scanners OpenSuse 13.1 openSUSE 13.1 provides sane-backends-1.0.23 where this model in not listed as supported. I updated to 0.17.25 backend SANE driver Strange - according to http://www.sane-project.org/cgi-bin/driver.pl?manu=canon=9000F=any== the "CanoScan 9000F Mark II" is listed as supported by the pixma backend versions 0.17.23 and 0.17.24 but 0.17.25 is not (yet?) listed there. In my current sane-backends-1.0.25 "man sane-pixma" shows that the "CanoScan 9000F Mark II" works with this backend. I assume you have sane-backends-1.0.25 installed. The Scanner setup in Yast shows the scanner driver, but shows is not configured. And what does it show when you configure it? I could find 2 cases in Forums with similar problems. What are the URLs of those "2 cases in Forums" so that we could understand what you are talking about? Only a guess: Is your scanner connected to a USB 3 port at the computer? If yes, this does not work, see https://bugzilla.opensuse.org/show_bug.cgi?id=856794 You need a newer kernel for USB 3 where the xhci USB driver is somewhat fixed. But you need additionally sane-backends-1.0.25 that has some additional workarounds for the broken xhci driver. If possible connect the scanner to a true USB 2 port this is a USB port where "lsusb -t" does not list that the kernel-"Driver=xhci" is used for it, cf. https://bugzilla.opensuse.org/show_bug.cgi?id=856794#c24 (excerpt): -- For the fun of it: My machine has 4 USB ports, two labeled with the "super speed" USB logo (a.k.a. USB 3) and two labeled with the normal USB logo (a.k.a. USB 2) but for all 4 ports xhci is used and it fails on all 4 ports. ------ Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] root can scan, user not...
Hello, On Oct 20 22:56 Thomas Dahlén wrote (excerpt): udev ... I am stucked here In general regarding "USB scanner access permissions via udev" and a "workaround to get those kind of issues out of sight" you may have a look at https://en.opensuse.org/SDB:Configuring_Scanners Regardless that this article is for openSUSE the general ideas behind should be same on other Linux distributions. Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Fixing sequencing issues (was Re: Proposed Upgrade (pu) branches on GitLab)
Hello,
an addendum only for the fun of it that is not meant
as starting point for a discussion about coding style:
On Sep 28 21:07 m. allan noah wrote (excerpt):
On Mon, Sep 28, 2015 at 7:04 AM, Johannes Meixner <jsm...@suse.de> wrote:
In sane-backends-git20150928 in backend/microtek2.c
there is line 7456:
ms->buf.current_src = ++ms->buf.current_src % 2;
My "decent educated guess" is that
++ms->buf.current_src;
ms->buf.current_src = ms->buf.current_src % 2;
is meant.
I'd guess it is just trying to swap 0 and 1, since all it is used for
is an index into ms->buf.src_buffer, which is defined as:
uint8_t *src_buffer[2]; /* two buffers because of CCD gap */
So all the code should do is:
ms->buf.current_src = ! ms->buf.current_src;
A perfect example for a "source code extremist" (TM Olaf Meeuwissen)
point of view ;-)
I think when the actual meaning is to toggle between
using src_buffer[0] and src_buffer[1] then the toggling
should be made obvious by explicit coding.
For the fun of it here an example what I mean:
--
// array[size > 2] cyclic access versus array[2] access via toggling:
#include
#include
#define array_size 3
int
main (int argc, char *argv[])
{
int i;
int array[array_size];
int array_index;
for (array_index = 0; array_index < array_size; ++array_index)
{ array[array_index] = array_index * 2;
}
array_index = 0;
for (i = 0; i < 6; ++i)
{ fprintf (stdout, "array[%i]=%i\n", array_index, array[array_index]);
// next array element and wrap around:
array_index = (array_index + 1) % array_size;
}
char toggle[] = { 'a', 'b' };
int toggle_state = 0;
for (i = 1; i <= 6; ++i)
{ fprintf (stdout, "toggle[%i]=%c\n", toggle_state, toggle[toggle_state]);
// Bad because fragile dependency on i (fails for i=0..5)
// and obscure constant 2:
// toggle_state = i % 2;
// Better but obscure not operation insted of explicit value setting:
// toggle_state = ! toggle_state;
// Explicit toggling "if it is 0 make it 1 otherwise make it 0":
toggle_state = (toggle_state == 0) ? 1 : 0;
}
return EXIT_SUCCESS;
}
--
So from my "source code extremist" point of view
explicite coding should be:
ms->buf.current_src = (ms->buf.current_src == 0) ? 1 : 0;
Again: This is only for the fun of it and not intended
to have microtek2.c changed again.
Kind Regards
Johannes Meixner
--
SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard,
Graham Norton - HRB 21284 (AG Nuernberg)
--
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] Fixing sequencing issues (was Re: Proposed Upgrade (pu) branches on GitLab)
Hello, On Sep 28 18:59 Olaf Meeuwissen wrote (excerpt): With the sequencing issues, we can only speculate at what the intended behaviour is, so we can't really fix things. That notwithstanding, I think we can make a decent, educated guess at a fix for both cases and make the warning go away :-| I don't know if the following sequencing bug was already found: In sane-backends-git20150928 in backend/microtek2.c there is line 7456: ms->buf.current_src = ++ms->buf.current_src % 2; My "decent educated guess" is that ++ms->buf.current_src; ms->buf.current_src = ms->buf.current_src % 2; is meant. For sequencing issues I would assume the original author was not actually a sufficient C expert who fully understood those issues (otherwise he would not have made ambiguous code) so that to fix those issues one could assume that any kind of foo = something where ++foo is used; was meant as foo++; /* or "++foo;" or "foo = foo + 1;" as one likes */ foo = something where foo is used; and any kind of foo = something where foo++ is used; was meant as foo = something where foo is used; foo++; /* or "++foo;" or "foo = foo + 1;" as one likes */ and same reasoning for "--foo" and "foo--". Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Proposed Upgrade (pu) branches on GitLab
Hello, On Sep 24 22:22 Olaf Meeuwissen wrote (excerpt): One, in sanei_ir.c, deserves some attention as it produces potentially undefined behaviour. It's really the same issue as reported in 311857, which I recently reopened. ../../../sanei/sanei_ir.c:481:11: warning: multiple unsequenced modifications to 'outi' [-Wunsequenced] *outi++ = *outi++ >> is; The two increments may occur in any given order, IIUC[3]. [3] http://c-faq.com/expr/seqpoints.html In general I would even demand that nowadays such kind of fancy coding stlye should no longer be done at all. With nowadays compiler optimizations it does not matter if one writes y = x++ * 2; or y = x * 2; x++; The former is selfish and oversophisticated coding. In this case it is a mix-up of two separated things. The latter is altruistic and explicit coding that makes it obvious for others what actually is meant. If the two separated things are meant as one statement one might (ab)use the "one statement per line" rule y = x * 2; x++; which is still much more obvious than "y = x++ * 2;". Of course everybody understands what "y = x++ * 2;" means. This is only used here as a simple example. Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Fixing sequencing issues (was Re: Proposed Upgrade (pu) branches on GitLab)
Hello, On Sep 25 21:02 Olaf Meeuwissen wrote (excerpt): I'm just chiming in to make a point to the list in general here. Nothing personal ;-) Perfectly o.k. - and I fully agree with your findings. Many thanks for your real test! In the mean time, I think we should any code that is flagged as -Wunsequenced (by clang) or -Wsequence-point (by gcc). I assume the meaning is clear but there is an omission. What exactly should be done with such code? the (self-invented?) AWARE principle: All Warnings Are Really Errors I cannot agree more. It happened to me more than once that "this stupid compiler shows me one of its stupid warnings" but after looking a bit closer - how embarassing - that "stupid compiler" was even smarter than me ;-) It even happened to me once that a warning had actually pointed out a fundamental flaw in the design. In other words: When something is not 100% clear/clean for the compiler, it is actually not clear/clean. Kind regards and have a nice weekend! Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Preparing for a sane-backends release
Hello Olaf On Sep 12 17:30 Olaf Meeuwissen wrote (excerpt): Johannes Meixner writes: ... I wonder if support for parallel port scanners is still needed? Me wonders too. ... You could build your SANE library packages without the backends for parallel scanners and see how many bug reports you get. I think I will do this. Reason: Since May 19 2015 I had disabled build for parallel port for our HPLIP package (HP's printer and scanner drivers) and up to now I did not get a single question or complaint from openSUSE Tumbleweed users - Tumbleweed is a rolling release, see https://en.opensuse.org/Portal:Tumbleweed In openSUSE 13.2 our HPLIP package has parallel port support. I assume that openSUSE Tumbleweed users are not too different compared to openSUSE 13.2 users regarding what kind of scanners they use so that in the end I assume nobody would complain when parallel port scanners are no longer supported. As a first step parallel port scanner drivers could be no longer built by default e.g. via something like configure --without-parport by default. Having such an option would make the above a lot easier. I think when there is not yet such an option it is not really needed to introduce it now for something that will be sooner or later completely dropped. Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Unsupported scanner
Hello, On Sep 13 15:50 Zdravko Nikolov wrote (excerpt): Canon Canoscan LiDE 700F OpenSUSE 13.2 In general regarding "Configuring Scanners" see https://en.opensuse.org/SDB:Configuring_Scanners You didn't tell what version of sane-backends you use. In OpenSUSE 13.2 we provide the sane-backends 1.0.24 release but perhaps you might need a newer sane-backends development version. I provide sane-backends version git20150804 RPMs an unstable development source only for testing, without any guarantee or warranty, and without any support in my openSUSE build service home project "home:jsmeix". Please carefully read https://build.opensuse.org/project/show?project=home:jsmeix You can get the packages in the "home:jsmeix" project for example for openSUSE 13.2 via this direct URL http://download.opensuse.org/repositories/home:/jsmeix/openSUSE_13.2/ When you like to upgrade an installed sane-backends 1.0.24 release to sane-backends development version git20150804 you need to install version git20150804 with plain rpm using "--force" e.g. like # rpm -Uhv --force sane-backends-git20150804-3.1.x86_64.rpm because for rpm the version number git20150804 is lower than the installed version number 1.0.24. Only if your scanner is connected to a USB3 port at the computer: There are currently issues with USB3 ports at the computer. Basically the xhci kernel module that is used as driver for USB3 ports has issues. It seems at least kernel 4.1.1-040101 is needed to have this particular issues fixed in the kernel. There are some workarounds in newer sane-backends development versions to deal with the USB3 xhci kernel module issues in older kernels. Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] plustek backend failing to open device under non-root
Hello, On Sep 10 22:40 Yury Tarasievich wrote (excerpt): ... failing to open the device under a non-root account ... Scanning under root works fine. In general for a possible "workaround to get those kind of issues out of sight" you may have a look at the section "USB scanner access permissions via udev" in https://en.opensuse.org/SDB:Configuring_Scanners Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] SANE_CAP_ALWAYS_SETTABLE (was Re: Preparing for a sane-backends release)
Hello, On Aug 5 08:21 Olaf Meeuwissen wrote (excerpt): Johannes Meixner writes: ... My re-add-SANE_CAP_ALWAYS_SETTABLE.patch re-adds SANE_CAP_ALWAYS_SETTABLE to sane.h which was erroneously removed in sane-backends-1.0.20 so that sane-frontends and xsane can no longer build, see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527675 Hmm, SANE_CAP_ALWAYS_SETTABLE is not part of the SANE Standard. And what should a Linux distributor do when other programs (in this case sane-frontends and xsane) use something against the SANE Standard? A Linux distributor cannot just tell their users: Hey, sorry, sane-frontends and xsane are dropped for now from our Linux distribution. They can no longer be built because they use something against the SANE Standard. Just use 'scanimage' as frontend for now. Linux distributors cannot provide broken stuff to their users. When things break Linux distributors must do something quickly (usually the easiest way) to ensure the whole stuff still works. Then a (possibly lengthy) process might start at various upstream projects to clean it up until at some later time it works again. Or such a process does not start because nobody notices that actually things are broken because Linux distributors had done some adaptions to keep it still working. Later by chance someone might have a closer look again at old adaptions/patches of the Linux distributors and then finally things might get really solved. I did not verify whether or not meanwhile all SANE frontends also no longer use SANE_CAP_ALWAYS_SETTABLE so that it could meanwhile be really removed in sane-backends. The sane-frontends have it in an #ifdef conditional (in src/gtkglue.c) that was added in 5e96223, apparently to switch to SANE 1.1 which never materialized. I meant all SANE frontends - not only sane-frontends. I.e. also xsane and whatever else there is nowadays, cf. http://www.sane-project.org/sane-frontends.html Since openSUSE 11.1 sane-frontends is no longer provided by us. I do not maintain any SANE frontend packages in openSUSE. I maintain only sane-backends and when that causes breakage in other packages then I will get a bug report and then I must fix (see above what this means) my sane-backends package to make things work again in openSUSE. I checked now xsane in openSUSE and its RPM changelog contains: Mon Jul 27 18:06:04 CEST 2009 - dominique-...@leuenberger.net - Update to version 0.997: + removed SANE_CAP_ALWAYS_SETTABLE (not SANE1) Accordingly xsane should have been fixed since a long time. But I cannot tell about the other SANE frontends and right now I do not have the spare time to check them all. Should I now just remove my old patch to see what happens? But I really do not like it when then I get blamed if something does no longer work so that for me personally it would be better to just keep that old patch. Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Dilip Upmanyu, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] SANE_CAP_ALWAYS_SETTABLE (was Re: Preparing for a sane-backends release)
Hello, On Aug 5 09:53 Olaf Meeuwissen wrote (excerpt): m. allan noah writes: I removed SANE_CAP_ALWAYS_SETTABLE because it was not in the sane standard ... Distributions don't get to decide the SANE standard ;-) Of course not! Distributions only try to keep things working when things break between various upstream projects (see my other mail). If any frontends still use it, it is those frontends that need fixing. In theory yes. I practice it is me who is blamed when sane-backends break other frontends and then I must fix sane-backends (see my other mail). Only for the fun: It is the same when other programs use undocumented private API calls from CUPS (e.g. by blind copy and paste CUPS source code). When later the other programs break because CUPS' private API changed, then they cry CUPS is to blame: CUPS is broken ;-) Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Dilip Upmanyu, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] SANE_CAP_ALWAYS_SETTABLE (was Re: Preparing for a sane-backends release)
Hello, On Aug 5 07:47 m. allan noah wrote (excerpt): What are they using it to signify? I cannot answer this right now because I do not maintain SANE frontends packages for openSUSE (see my other mail). Right now I checked skanlite and there is no SANE_CAP_ALWAYS_SETTABLE in its sources. But I cannot check all possible SANE frontends packages in openSUSE with reasonable effort because I do not know how to find out (with reasonable effort) in which openSUSE packages SANE frontends might exist. But I have a plan now: Because the issue with SANE_CAP_ALWAYS_SETTABLE happened in 2009 I can (hopefully) safely assume that meanwhile all (relevant) SANE frontends upstream projects have adapted their sources (as needed) to work without it. Therefore when the next sane-backends version is released I will again mercilessly clean up the openSUSE sane-backends package to the furthest possible extent to be in compliance with SANE upstream. (I had done such a reset to compliance with upstream in about 2004 when I became maintainer of sane-backends). By the way - if you agree - I would like to drop support for parallel port scanners, see my other mail. Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Dilip Upmanyu, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Preparing for a sane-backends release
Hello, On Aug 3 14:08 m. allan noah wrote (excerpt): ... I know that Gentoo has some systemd compilation fixes. Everey Linux distribution should submit their patches to SANE upstream (provided their changes make sense for upstream). Here our (i.e. openSUSE) patches that we still have: 1) Right now I filed https://alioth.debian.org/tracker/index.php?group_id=30186atid=410366 with my fix-buffer-overflow.patch attached that fixes a too small array in backend/niash.c 2) My re-add-SANE_CAP_ALWAYS_SETTABLE.patch re-adds SANE_CAP_ALWAYS_SETTABLE to sane.h which was erroneously removed in sane-backends-1.0.20 so that sane-frontends and xsane can no longer build, see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527675 re-add-SANE_CAP_ALWAYS_SETTABLE.patch - --- include/sane/sane.h.orig2009-06-12 10:19:19.0 +0200 +++ include/sane/sane.h 2009-06-12 10:20:12.0 +0200 @@ -115,6 +115,7 @@ SANE_Device; #define SANE_CAP_AUTOMATIC (1 4) #define SANE_CAP_INACTIVE (1 5) #define SANE_CAP_ADVANCED (1 6) +#define SANE_CAP_ALWAYS_SETTABLE (1 7) #define SANE_OPTION_IS_ACTIVE(cap) (((cap) SANE_CAP_INACTIVE) == 0) #define SANE_OPTION_IS_SETTABLE(cap) (((cap) SANE_CAP_SOFT_SELECT) != 0) - The re-add-SANE_CAP_ALWAYS_SETTABLE.patch still applies for current sane-backends-git20150804.tar.gz so that I assume SANE_CAP_ALWAYS_SETTABLE is still missing in sane-backends. I did not verify whether or not meanwhile all SANE frontends also no longer use SANE_CAP_ALWAYS_SETTABLE so that it could meanwhile be really removed in sane-backends. 3) My fix-mustek_pp_ccd300.c.patch fixes undefined 'foo = ++foo modulo bar' operations in mustek_pp_ccd300.c see https://bugzilla.opensuse.org/show_bug.cgi?id=498435 and https://alioth.debian.org/tracker/index.php?func=detailaid=311857group_id=30186atid=410366 where the upstream maintainer did not understand what is wrong and closed it as Wont Fix so that we must keep this patch forever to make at least the code somehow valid for the compiler. fix-mustek_pp_ccd300.c.patch is attached to the above alioth.debian.org bug tracker issue. Of course because the result of 'foo = ++foo' is undefined I cannot know if my patch implements what is actually intended. My patch implements an arbitrary result that only makes the compiler happy. 4) My install-umax_pp-tool.patch installs tools/umax_pp as /usr/bin/umax_pp which is built but not installed but it is needed to recover from a failed scan with scanners which use the umax_pp backend, see http://bugs.debian.org/496833 install-umax_pp-tool.patch --- tools/Makefile.am.orig 2009-02-20 17:51:09.0 +0100 +++ tools/Makefile.am 2009-06-05 15:08:45.0 +0200 @@ -7,8 +7,8 @@ AM_CPPFLAGS = -I. -I$(srcdir) -I$(top_builddir)/include \ -I$(top_srcdir)/include -bin_PROGRAMS = sane-find-scanner gamma4scanimage -noinst_PROGRAMS = sane-desc umax_pp +bin_PROGRAMS = sane-find-scanner gamma4scanimage umax_pp +noinst_PROGRAMS = sane-desc if CROSS_COMPILING HOTPLUG = The install-umax_pp-tool.patch still applies for current sane-backends-git20150804.tar.gz so that I assume tools/umax_pp is still not installed by default. In general regarding parallel port scanner drivers: The above issues 3) and 4) are about parallel port scanner drivers. I wonder if support for parallel port scanners is still needed? I assume that basically nobody tests parallel port scanners. Probably also basically nobody usues parallel port scanners. In this case parallel port scanner drivers should be dropped because in practice they are no longer maintained. As a first step parallel port scanner drivers could be no longer built by default e.g. via something like configure --without-parport by default. Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Dilip Upmanyu, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Preparing for a sane-backends release
Hello, On Aug 3 14:08 m. allan noah wrote (excerpt): We ... have a large number of open bug reports- sometimes waiting years for reporter responses. Close all of them with a generic no response entry, see What happens if I do not answer my bugs with the NEEDINFO flag set? at https://en.opensuse.org/openSUSE:Bug_reporting_FAQ If some of them are really still of interest they will reopen. Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Dilip Upmanyu, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] SANE not working with Canon Canoscan LiDE N676U
Hello, On Mar 9 15:30 Â wrote (excerpt): sane-backends vesion 1.0.24-2.1.10 on openSUSE 13.2 ... sane-find-scanner reports found USB scanner (vendor=0x04a9 [Canon], product=0x220d [CanoScan]) at libusb:003:005. ... scanimage -L occasionally reports device `plustek:libusb:003:005' is a Canon CanoScan N670U/N676U/LiDE20 flatbed scanner Perhaps a newer SANE version might also help in your case, see https://bugzilla.opensuse.org/show_bug.cgi?id=920067 in particular therein see https://bugzilla.opensuse.org/show_bug.cgi?id=920067#c26 Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Kyocera ECOSYS M6526cdn usable with SANE?
Hello, On Feb 10 00:12 Marco Patzer wrote (excerpt): Kyocera ECOSYS M6526cdn multi function device I got the printer working flawlessly with CUPS. But I struggle with the scanner. It it connected via Ethernet. In the technical data sheet at Kyocera http://cdn.kyostatics.net/dlc/eu/documentation/datasheet/kyocera-m6256cdnseries-datasheet-view-131212.-downloadcenteritem-Single-File.downloadcenteritem.tmp/KYO_Gemini_DS_M...n_ISOc_View.pdf I found in particular (excerpt) SCAN FUNCTIONS ... Functionality: Scan-to-e-mail (and many more). Accordingly I think what I worote about powerful network printer scanner copier all-in-one device in Scanning via Network at https://en.opensuse.org/SDB:Configuring_Scanners matches perfectly here. Only FYI a side note regarding printing: The above mentioned technical data sheet at Kyocera also reads PRINT FUNCTIONS ... Emulations: ... KPDL 3 (PostScript 3 compatible), PDF Direct Print 1.7 See PostScript+PDF printers at https://en.opensuse.org/SDB:Printer_buying_guide As far as I know what is currently missing for direct PDF printing are PPD files that support PDF printing directly, see https://bugs.linuxfoundation.org/show_bug.cgi?id=1234 I don't know if Kyocera perhaps already provides a PPD file for their ECOSYS M6526cdn model that supports direct PDF printing. Cf. HP devices that support direct PDF printing: https://bugs.launchpad.net/hplip/+bug/1385273 Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton - HRB 21284 (AG Nuernberg) -- 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] Imageclass D530 Scanner Support (New Patch?)
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 provide an usable workaround for you -- The best workaround to get those kind of issues out of sight is to use the saned... -- (of course provided you let the saned run as root). Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer -- 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] Imageclass D530 Scanner Support (New Patch?)
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 available device that is not known to the system, the devicename must be specified explicitly. The format of devicename is backendname:devicefile (eg: umax:/dev/sga). --- I did not verify if it actually works but I think for you xsane pixma:04A92775_1144T3603236 should (hopefully) work. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer -- 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] Fujitsu S1500 unable to stay connected
Hello, On Sep 24 17:11 Chris Glasoe wrote (excerpt): I have tried editing the Fujitsu entry to the S1500 driver with no luck and vice versa adding Fujitsu to the driver discovered by Yast. FYI: Regarding how YaST scanner detection works: When the YaST scanner module autodetects scanners, it runs sane-find-scanner via /usr/lib/YaST2/bin/autodetect_scanners and basically scanimage -L (scanimage -f '%d,%v,%m;') via /usr/lib/YaST2/bin/determine_active_scanners I.e. YaST shows you what sane-find-scanner and scanimage -L show you. Regarding USB issues, there is some very generic information at http://en.opensuse.org/SDB:Configuring_Scanners#USB Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer -- 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] Canon D530 scanner
Hello, On Jul 14 00:11 Michael Juster wrote (excerpt): I'm trying to use the Canon imageCLASS D530 with openSUSE 12.3 13.1 KDE: Bus 002 Device 002: ID 04a9:2775. Such a device is not listed at SANE: http://www.sane-project.org/cgi-bin/driver.pl?manu=model=bus=anyv=04a9p=2775 results No matches found and there is no D530 listed at http://www.sane-project.org/cgi-bin/driver.pl?manu=canonmodel=imageCLASS See also http://en.opensuse.org/SDB:Configuring_Scanners#Scanner and http://en.opensuse.org/SDB:Configuring_Scanners#Third-Party_Scanner_Drivers Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer -- 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] canon dr-2580c invalid argument
Hello, On May 8 12:15 gobo wrote (excerpt): this is under SLED 11 sp3. they tend to be behind. i'll have to see if they have anything newer. On 5/8/14, m. allan noah kitno455 at gmail.com wrote: Suggestions- yes. sane-backends 1.0.20 is positively ancient. upgrade. It depends on who they is ;-) If they is the official SUSE Enterprise Customer Support, then they do not have a newer sane-backends RPM package. If they is openSUSE, then I provide in my openSUSE home project sane-backends-1.0.22 RPM packages built for SLE_11_SP3 (i.e. SLES 11 SP3 and SLED 11 SP3) for 32-bit i586 and 64-bit x86_64 architecture. Why no current sane-backends-1.0.24 for SLE11? Because it does no longer build (with reasonable effort for me) in the positively ancient SLE11 environment. For direct RPM download go to http://download.opensuse.org/repositories/home:/jsmeix/SLE_11_SP3/ Before you install such RPM packages, carefully read https://build.opensuse.org/project/show?project=home%3Ajsmeix -- Home Project of Johannes Meixner http://en.opensuse.org/User:Jsmeix This is my personal playground where packages could be severely incompatible with official openSUSE packages. Do not somehow add the whole home:jsmeix repository to be used by your package installer (e.g. via YaST). Using the whole home:jsmeix repository could be a perfect way to mess up your system. Instead only download the packages of your particular interest which match your excat system from the appropriate sub-directory in http://download.opensuse.org/repositories/home:/jsmeix/ and install them manually (e.g. using plain rpm). If you are unexperienced with manual installation, do not install any package from home:jsmeix. Packages in the home:jsmeix project might neither be in usable state nor fit into currently installed systems. Have this in mind if you think about to install packages from home:jsmeix into your currently running system. Do not use Factory if your system is not Factory. Use the matching packages for your particular system. The packages in the home:jsmeix project are only for testing, without any guarantee or warranty, and without any support. As an extreme example, this means if your complete computer center crashes because of those packages, it is only your problem. On the other hand this does not mean that all those packages are known to be terrible broken (but some of those packages could be really broken) and none of those packages are thoroughly tested so that any unexpected issue can happen. -- Personally - without any guarantee or warranty - I assume sane-backends-1.0.22 from the home:jsmeix project should just work for SLE 11 SP3 - but I have not verified it. When you have a support contract with our official SUSE Enterprise Customer Support, then check with them whether or not installing sane-backends-1.0.22 from the home:jsmeix project might somehow invalidate your support contract. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer
[sane-devel] MX925: Scan via Display to SANE??
Hello, On May 3 11:51 Louis Lagendijk wrote (excerpt): On Fri, 2014-05-02 at 21:55 +, Thomas Escher wrote: One question ? I own a Canon MX925. It's possible to scan from the display directly to the Windows-Machines. Is SANE the right software to scan from the display directly to a debian-machine? ... Yes, Sane can be the base for button-based scanning, but you will also need scanbd. Sane provides the interface to the scanner, scanbd will handle the logic. Scanbd cab be found here: http://sourceforge.net/projects/scanbd/?source=directory First things first: A precondition is that SANE supports the device. But according to http://www.sane-project.org/cgi-bin/driver.pl?manu=canonmodel=mxbus=anyv=p= it seems no Canon MX925 is listed at SANE which indicates that SANE does not support it. First of all scanning from the computer must work with SANE when the device is connected directly via USB to the computer. When this works, button-based scanning could be set up and/or the device might be connected via (wireless) network. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer
[sane-devel] Sane problem with Brother MFC J6710DW scanner.
Hello, On Dec 10 07:59 upscope wrote (excerpt): rpl7:~ scanimage -L device `brother4:bus3;dev6' is a Brother MFC-J6710DW USB scanner ... linux-rpl7:~ lsusb Bus 003 Device 006: ID 04f9:0263 Brother Industries, Ltd As far as I see there is neither a brother4 driver (backend) in SANE nor does SANE know about your USB scanner model. http://www.sane-project.org/cgi-bin/driver.pl?manu=model=bus=usbv=04f9p=0263 results No matches found. and http://www.sane-project.org/cgi-bin/driver.pl?manu=Brothermodel=bus=usbv=p= does not list a Brother MFC-J6710DW and even http://www.sane-project.org/lists/sane-backends-external.html does not list a brother4 driver (backend). Therefore it seems you use a currently unknown third-party driver. Regarding Third-Party Scanner Drivers have a look at http://en.opensuse.org/SDB:Configuring_Scanners Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer
[sane-devel] Brother MFC-420CN via USB connection
Hello, On Dec 11 01:04 Jason H. Fuller wrote (excerpt): ... when I actually try to scan I get a Failed to start scanner: Invalid argument error from xsane. This looks like the other mail here with subject Sane problem with Brother MFC J6710DW scanner., see http://lists.alioth.debian.org/pipermail/sane-devel/2013-December/031906.html that reads in particular: ... Brother MFC-J6710DW USB scanner ... Starting xsane from the command. It starts, the GUI, header says: xsane 0.998 MFC-J6710DW scanner The error pops up: Failed to start scanner: Invalid argument The Brother MFC-420CN is at least listed at http://www.sane-project.org/cgi-bin/driver.pl?manu=Brothermodel=bus=usbv=p= for the brother2 driver/backend but with status untested. The brother2 driver is an external backend for SANE, see http://www.sane-project.org/lists/sane-backends-external.html An external backend for SANE usually means that there is no free source code available so that nobody except those who made that driver can usually help to debug issues with such a driver. Perhaps there is documentation how to get debug messages for the brother2 driver so that you could at least try to find out what the root cause could be here. From my current point of view I don't think there is an issue in XSane or in SANE because otherwise there should have been more such reports and not only for drivers from Brother. From my current point of view it looks more like an issue in the drivers from Brother. I think you should get in contact with Brother because they can find out what the root cause is. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer
[sane-devel] sane-devel Digest, Vol 101, Issue 5
Hello, On Nov 6 15:44 Beau Jamo wrote (excerpt): Does sane support network devices directly? It depends on the scanner driver (the so called backend in SANE) if it can access a scanner directly via network connection, see http://www.sane-project.org/sane-backends.html and look for supported models where the Interface column also lists Network and read the comments. There is in particular the so called extrenal backend (i.e. a SANE compatible scanner driver that is not part of SANE) epkowa which is provided in the Iscan software by Epson (formerly Avasys) that supports several scanners directly via network connection usually by an additional non-free iscan-network-nt package, see http://www.sane-project.org/lists/sane-backends-external.html#S-EPKOWA Note that non-free software packages are usually only availabe for standard PC architecture (e.g. 32-bit i386/x86 Intel compatible or 64-bit x86_64 AMD compatible). I mean can sane scan using a scanner that is not attached to a host computer but is attached directly to the network like big MFP's? Regarding big MFP's see the section about Scanning via Network in http://en.opensuse.org/SDB:Configuring_Scanners In short: For big MFPs, don't use SANE - instead ensure that the device supports stand-alone scan to e-mail. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer
[sane-devel] Contradicting support info for HP ScanJet 2400C/G2410
Hello, by chance I detected right now that http://www.sane-project.org/cgi-bin/driver.pl?manu=model=bus=anyv=03f0p=0a01 shows the HP ScanJet 2400C both as unsupported and as complete and additionaly a clone device HP ScanJet G2410 only as basic. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer
[sane-devel] pthread support
Hello, On Aug 10 17:47 Gerhard Jaeger wrote (excerpt): On Friday 09 August 2013 11:10:59 Rolf Bensch wrote: [...] Why is pthread disabled by default for Linux? this is IIRC a left over from ancient days. A couple of years ago the pthread support was added and it should work... FYI: This is used in Debian since Feb 2009 with no issues so far and accordingly since openSUSE 11.4 (i.e. since Sep 2010) we also use configure ... --enable-pthread and we also had no issues so far, see https://bugzilla.novell.com/show_bug.cgi?id=633780 Perhaps nowadays pthread should be enabled by default for Linux? Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer
[sane-devel] scanner not found
Hello Olaf, On Mar 26 07:57 Olaf Meeuwissen wrote: Albrecht Mehl writes: I want to use the scanner epson perfection v 330 photo within opensuse linux 12.2. ... In yast2, hardware, scanner, configuration the scanner is listed as not configured. Modify opens a long driver's list. For my scanner - see above - there is but one driver, but one is cautioned not to use it. As Yuri mentioned in another post already, this scanner is supported by iscan + non-free plugin. Packages are available via: http://download.ebz.epson.net/dsc/search/01/search/?OSC=LX The reason that yast2 cautions about it use is most likely because the plugin is non-free so you cannot help yourself or have others help you when you have a problem with it. FYI this is the text that the YaST scanner module currently shows: --- The third-party Image Scan driver software from Epson/Avasys is required. The Image Scan driver software is made and provided by Epson (formerly Avasys) http://download.ebz.epson.net/dsc/search/01/search/?OSC=LXEpson (formerly Avasys http://avasys.jp/eng/linux_driver/) where RPM packages for 32-bit (i386) and 64-bit (x86_64) architecture can be downloaded (if you accept the Epson/Avasys license agreements). The Image Scan driver contains proprietary binary-only software. For some models it is only available for 32-bit (i386) architecture which does not work when you have a 64-bit system installation. Some scanners are also supported by another (free-software) driver. When your scanner model requires a DFSG non-free (proprietary) module, you have to download and install two packages from Epson/Avasys: The 'iscan' package for the base software and an additional model dependant 'iscan-plugin' package with the proprietary module. -- I notice that the URL in the YaST text is not correct (it works but the OS is not preselected to be Linux). When I update this text, I may remove the formerly Avasys parts. Are there other errors or inappropriate wording that should be fixed? Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer
[sane-devel] HP All-in-one
Hello, On Mar 13 18:03 DON SMITH wrote (excerpt): ... HP All-In-one printer/scanners ... Use the HPLIP web site. See http://www.sane-project.org/lists/sane-backends-external.html#S-HPAIO which shows a link to http://hpinkjet.sourceforge.net/ which redirects to http://hplip.sourceforge.net/ which redirects to http://hplipopensource.com/ which is actually http://hplipopensource.com/hplip-web/index.html It works but seems the link in http://www.sane-project.org/lists/sane-backends-external.html#S-HPAIO could be updated to point directly to the HPLIP web site. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer
[sane-devel] backend distribution question
Hello, On Jan 25 02:39 Ruell Magpayo wrote (excerpt): I would like to define by what I mean by: Kyocera home based MFP devices It refers to the newly released(2012) low-cost printers from Kyocera; FS-1020, FS-1125, FS-1120 series Some of these products have network interface but because it is low-cost MFP, it does not have the scan to email feature unlike the other Kyocera products. All processing from these devices are done at host PC side including the image processing. We are considering options on how to support linux scan... To support scanning under Linux the only reasonable way is to provide a driver/backend for SANE because scanning via SANE is practically the only way how scanning happens under Linux. The only reasonable way to provide a SANE backend to Linux users is to make the backend in a way so that Linux distributors can include it in the Linux distributions and that means to make the backend as free software. Now you (i.e. Kyocera) has the issue that you need to use confidential/proprietary functionality which cannot be implemented as free software. I.e. you have the issue that you need run proprietary software. As I explained in my previous mail, separation of proprietary software from free software is essential. Therefore you (i.e. Kyocera) must keep your proprietary stuff only on your servers but you would openly release your free software so that others can integrate your free software (and only your free software) into SANE and this way also into Linux distributions. When your SANE backend runs on the end-user's computer and when it needs the proprietary functionality, it has to execute your proprietary stuff preferably as separated process as I explained in my previous mail. This means your proprietary stuff must exist as executable on the end-user's computer. Therefore Kyocera has to provide its proprietary stuff on Kyocera servers for download and installation by end-users. End-user machines are usually x86/i386/i486/i586 (32-bit) or x86_64 (64-bit) so that Kyocera has to provide its proprietary stuff at least for those two architectures. Accordingly Kyocera also has to provide a download and installation tool so that end-users can easily download and install the right proprietary stuff from the right Kyocera servers on the end-user's computer (showing the right license dialogs and all what is needed to do this part correctly). The Kyocera installation tool must also be free software so that Kyocera users get it out of the box in the Linux distributions. At least we (i.e. SUSE/openSUSE) can only provide a free software Kyocera installation tool as is and we could even run such a tool as is if needed (currently our YaST printer setup module can launch HP's hp-setup tool as is to set up HP devices). But we would never ever download and install proprietary stuff from Kyocera on our own (e.g. implement such a tool on our own) because we will never ever risk any kind of legal issue because of proprietary stuff that is required by weak (low-cost) hardware, see http://en.opensuse.org/SDB:GDI_Printers Perhaps the Kyocera installation tool cannot be integrated in SANE. Whether or not this is possible depends on what the SANE developers decide here. If the Kyocera installation tool cannot be integrated in SANE, Kyocera must provide it as separated free source code package so that Linux distributors can build it separated from SANE. If your proprietary executable does not exist on the end-user's computer, your SANE backend must exit appropriately preferably with a meaningful error message that informs the user that your proprietary stuff needs to be downloaded from Kyocera. This way how to deal with the issue when confidential/proprietary functionality is needed by free software is currently used by HPLIP (see http://hplipopensource.com/hplip-web/index.html) when HP printers or all-in-one devices require proprietary functionality, see https://bugzilla.novell.com/show_bug.cgi?id=342704 in particular https://bugzilla.novell.com/show_bug.cgi?id=342704#c3 This way works optimal for end-users, Linux distributors, and free software developers (optimal means at least currently there is no better way known how to deal with the issue). This way is more software programming effort for the manufacturer (keeping separated parts actually strictly separated instead of mixing up everything into one big software monster mess). But on the other hand this way avoids any other trouble in particular legal issues because of the licensing. In particular for software developers at the manufacturer it means that they can just do their job (i.e. just making their software) which they probably like a bit more than to deal with their legal department and the legal department of the Free Software Foundation and the legal departments of various Linux distributors ;-) Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB
[sane-devel] backend distribution question
? Or is bank notes scanning prevention required by laws in this or that countries (in addition to the usual laws that of course generally forbid to counterfeit money regardless of the method)? As far as I understand your description it seems the Kyocera home based MFP devices do not have bank notes scanning prevention functionality built-in in their hardware/firmware so that bank notes scanning prevention happens in the scanner driver software that runs on the end-users machines. Is my understanding correct? Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer
[sane-devel] untested samsung scanners: tried after installation UnifiedLinuxDriver?
Hello, On Jan 18 14:34 Julien Michielsen wrote: Some time ago I bought the Samsung Scx-3400 laser printer. It also has a scanner which I could not install under SuSE 12.1. However, when I installed Samsungs UnifiedLinuxDriver, this also got my scanner working. It is recognised (and installed) by yast and xsane, even though I did give any input to those programs. Installing the UnifiedLinuxDriver might also install other Samsung scanners that are listed as Untested. I am very happy with my (unlisted ;-) ) Scx-3400. I guess you meant even though I did NOT give any input to those programs. Only FYI and perhaps as background information, see Third-Party Scanner Drivers at http://en.opensuse.org/SDB:Configuring_Scanners I have no knowledge about Samsung's UnifiedLinuxDriver. Perhaps it is the one mentioned under Samsung at http://www.sane-project.org/lists/sane-backends-external.html Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer
[sane-devel] using scanners unable to USB_AUTOSUSPEND
Hello,
On Jan 10 16:58 Wilhelm wrote (excerpt):
recently I had problems with my old EPSON 1670 Scanner, because it doesn't
support usb autosuspend that most distros enable by default in the linux
kernel. That causes scanimage or other applications (e.g. like scanner button
daemon scanbd) to freeze or even reading wrong values.
If I remember correctly a longer time ago the usb autosuspend issue
was discussed on this list.
As a consequence the sane-backends libsane.rules file for udev
(it is /etc/udev/rules.d/55-libsane.rules at least in openSUSE)
that is generated by tools/sane-desc.c in the sane-backends sources
contains:
---
# Epson Perfection 1670
ATTR{idVendor}==04b8, ATTR{idProduct}==011f, ... ENV{libsane_matched}=yes
...
# The following rule will disable USB autosuspend for the device
ENV{libsane_matched}==yes, RUN+=/bin/sh -c
'if test -e /sys/$env{DEVPATH}/power/control;
then echo on /sys/$env{DEVPATH}/power/control;
elif test -e /sys/$env{DEVPATH}/power/level;
then echo on /sys/$env{DEVPATH}/power/level; fi'
---
(the actual udev rules are single long lines - only wrapped here)
Accordingly - if your EPSON 1670 matches the idVendor/idProduct - it
should get ENV{libsane_matched}=yes and USB autosuspend should get
disabled for it.
Unfortunately things in udev/sysfs are unstable by design (udev/sysfs is
primarily meant as a helper tool to do kernel related stuff and not
a tool for application programs - sane-backends ia an application
from the kernel point of view) so that it depends on the kernel
and udev version whether or not udev rules actually work.
Kind Regards
Johannes Meixner
--
SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany
HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer
[sane-devel] Other pixma_foo update for LSB
Hello, On Oct 18 10:09 Petrie, Glen wrote (excerpt): Hi Johannes I noticed that you submitted a bug fix request for the pixma_bjnp.c . I did not submit anything for pixma_bjnp.c - at least I am not aware of any such submission. What I recently submitted was https://alioth.debian.org/tracker/?func=detailatid=410366aid=313858group_id=30186 with a tentative fix for a complier warning in kodakaio.c control reaches end of non-void function i.e. when there is an exit path in a non-void function without returning a value. This issue is considered severe by the openSUSE build system which serches the complier output for warnings which are considered to be actually errors. For another example see https://bugs.launchpad.net/hplip/+bug/1017496 No return in non-void function in scan/sane/hpaio.c which additionally shows another issue that is considered severe: Pointer and integer mixed up = not 64-bit safe. In such cases the openSUSE build system aborts the build and then I am forced to somehow fix it regardless that usually I do not have the expert knowledge hwo each individual scanner driver works (e.g. what value to return when a non-void function exits without returning a value). Therefore I file a bug report at the SANE bug tracker according to http://www.sane-project.org/bugs.html to get the author/maintainer of the particular scanner driver involved so that he can either use my tentative fix as is or provide a real fix based on his expert knowledge. For the external SANE backend hpaio I file a bug report at the HPLIP bug tracker, see Report a Bug at http://hplipopensource.com/hplip-web/support.html Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer
[sane-devel] Linux-update: scanner no more recognized
Hello, On Jul 27 21:41 M.B. Schiekel wrote (excerpt): export SANE_DEBUG_UMAX1220U=128 export SANE_DEBUG_SANEI_USB=128 scanimage -L ... [sanei_usb] sanei_usb_init: found 1 devices [sanei_usb] sanei_usb_init: device 00 is libusb:003:002 [umax1220u] reading configure file umax1220u.conf [umax1220u] attach_matching_devices(usb 0x1606 0x0010) [sanei_usb] sanei_usb_find_devices: vendor=0x1606, product=0x0010 [umax1220u] attach_scanner: libusb:003:002 [umax1220u] attach_scanner: opening libusb:003:002 [umax1220u] UMAX_open_device: `libusb:003:002' [sanei_usb] sanei_usb_open: trying to open device `libusb:003:002' libusb:error [op_set_configuration] failed, error -1 errno 110 [sanei_usb] sanei_usb_open: libusb complained: Numerical result out of range [umax1220u] UMAX_open_device: couldn't open device `libusb:003:002': Invalid argument [umax1220u] ERROR: attach_scanner: opening libusb:003:002 failed [umax1220u] attach_matching_devices(usb 0x1606 0x0030) [sanei_usb] sanei_usb_find_devices: vendor=0x1606, product=0x0030 [umax1220u] attach_matching_devices(usb 0x1606 0x0130) [sanei_usb] sanei_usb_find_devices: vendor=0x1606, product=0x0130 [umax1220u] finished reading configure file [umax1220u] sane_get_devices(local_only = 0) FYI: A libusb complained: Numerical result out of range issue (but with errno 32) was also reported via https://bugzilla.novell.com/show_bug.cgi?id=735424 Usually in such cases no (negative) response from the one who reported the issue means that it works for him. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer
[sane-devel] Linux-update: scanner no more recognized
Hello, On Jul 28 10:38 Stef wrote (excerpt): I would try to compile with libusb-1.0 by giving the '--enable-libusb_1_0' option to configure. For openSUSE I build our sane-backends RPM package recently (i.e. since Fri Apr 20) with --enable-libusb_1_0 in the openSUSE build service development project graphics. sane-backends RPMs for openSUSE_11.4 and openSUSE_12.1 for 32-bit i586 and 64-bit x86_64 platforms are available from the openSUSE build service development project graphics download repository at http://download.opensuse.org/repositories/graphics/ On 64-bit x86_64 platforms you may need additionally the sane-backends-32bit RPM. Check what rpm -qa | grep sane-backends results on your system. The package sane-backends-autoconfig is only optional. Have in mind that graphics is a development project where packages might neither be in a stable state nor fit well into currently installed systems. The packages in the graphics project are only for testing, without any guarantee or warranty, and without any official support. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer
[sane-devel] ScanImage -L fails as user
Hello, On Sun, Jun 10, 2012 at 9:42 AM, Per Dalgas Jakobsen pdj at knaldgas.dk wrote: scanimage -L fails as user (succeeds as root). On Jun 11 20:34 m. allan noah wrote (excerpt): You will have to adjust the device permissions, using something like udev, or hal. Unfortunately, the mechanism seems to change frequently with linux distros... It is not the Linux distros but in the upstream kernel-related area where such changes happen frequently. The traditional persistent device node files (where chown/chmod worked persistently as it works since ever for all files in Unix systems) were replaced by dynamically created device nodes (where chown/chmod does no longer work persistently). The dynamic device nodes are managed by various changing stuff like hotplug/devfs that was replaced by HAL plus udev/sysfs but HAL is dropped since some time and recently udev was merged into systemd... Currently it should be udev that is used by a current Linux distro to manage device nodes. But do not expect that there is THE udev with a common stable set of udev rules for all Linux distros because udev depends in some way on the kernel version. You may have a look at http://en.opensuse.org/SDB:Configuring_Scanners the section USB scanner access permissions via udev which reads in particular: -- The best workaround to get those kind of issues out of sight is to use the saned which is a service for scanning via network. On the server the saned is set up and launched via xinetd. On the client the net meta-backend is used for scanning via network. See man saned and man sane-net. By using the loopback network this can be used on the local host too. In this case server and client are the same machine localhost. To access a scanner via the saned on the local host you may set up the following: 1. Let the saned run as root (default in /etc/xinetd.d/sane-port) 2. Allow access from localhost in /etc/sane.d/saned.conf 3. Specify the server localhost in /etc/sane.d/net.conf 4. Activate the net meta-backend in /etc/sane.d/dll.conf -- Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer
[sane-devel] Could blacklisting USB devices make sense?
Hello,
we (i.e. openSUSE) got a special issue report
https://bugzilla.novell.com/show_bug.cgi?id=701368
A particular USB mouse model gets disabled when finding USB devices
via libusb e.g. by running sane-find-scanner.
There is now the question whether or not it could make sense
if there was a config file for SANE where particular USB devices
could be blacklisted (by idVendor and/or idProduct and/or DeviceClass
and/or whatever else) so that SANE would leave such devices alone?
I think in general it could make sense to avoid issues
in particular exceptional cases.
Details:
As far as I understand what goes on (but I am not at all a USB expert)
in the SANE sources the sanei_usb_init function in sanei/sanei_usb.c
calls the libusb functions usb_init usb_find_busses usb_find_devices
before it loops through all of the busess and all of the devices
to find USB devices which are of interest for SANE:
---
sanei_usb_init
...
DBG (4, sanei_usb_init: Looking for libusb devices\n);
usb_init ();
#ifdef DBG_LEVEL
if (DBG_LEVEL 4)
usb_set_debug (255);
#endif /* DBG_LEVEL */
usb_find_busses ();
usb_find_devices ();
/* Check for the matching device */
for (bus = usb_get_busses (); bus; bus = bus-next)
{
for (dev = bus-devices; dev; dev = dev-next)
{
---
As far as I see SANE works basically as described in
http://libusb.sourceforge.net/doc/examples-code.html
If in this particular case the USB mouse gets disabled when
the libusb functions usb_init usb_find_busses usb_find_devices
are called, blacklisting the USB mouse in SANE cannot help
because those libusb functions are not device specific.
Nevertheless I think in general it could make sense to avoid issues
in other exceptional cases if devices could be blacklisted in SANE.
Perhaps for USB and also for SCSI in files like
/etc/sane.d/sanei-usb.conf and /etc/sane.d/sanei-scsi.conf
What do you think?
Kind Regards
Johannes Meixner
--
SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany
HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer
[sane-devel] Could blacklisting USB devices make sense?
Hello, On Apr 19 10:11 m. allan noah wrote (excerpt): This in interesting. If you have the user compile a simple test program which just calls the 3 libusb functions, does his mouse stop? If so, there is nothing that can be done in sane. Yes, as I wrote in my initial mail, if this is the case, blacklisting in SANE cannot help in this particular case. For me this particular issue was only a trigger to think about whether or not blacklisting devices could make sense at all to be prepared to avoid other problematic cases. For example: Assume there are several USB devices connected with USB device class 255 Vendor Specific Class but only one of them is a scanner. As far as I understand the check_libusb_device function in tools/sane-find-scanner.c it runs check_usb_chip for all USB devices with class 255. Assume some particular USB devices with class 255 (which are no scanners) do not like what check_usb_chip does. Then it should help in this case if USB devices could be blacklisted in SANE so that sane-find-scanner would not run check_usb_chip on them. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer
[sane-devel] Scanner Database
Hello, On Feb 17 09:51 Michael Nagel wrote (excerpt): This is not about replacing the list of supported devices available at: http://www.sane-project.org/sane-supported-devices.html primarily for the following two reasons: 1) It's about making it easy for as many people as possible to submit data. 2) It is about measuring the real-world, end-user experience, not about what should theoretically work. Unfortunately at least for Simple Scan on Ubuntu we regularly see regressions with scanners that should work and *have worked*. As a basis for discussion I created the following mockup: http://nailor.devzero.de/tmp/scandb/loop/hardware.htm ... ... tell me what you think about it as a ... packager for a distribution, debugger, supporter Nowadays scanners are more and more used as built-in components of an all-in-one printer-scanner-copier-whatever device. From the end-users point of view it is all about one single device. Therefore I suggest to get in touch with the OpenPrinting workgroup of the Linux Foundation at http://www.linuxfoundation.org/collaborate/workgroups/openprinting For printers the OpenPrinting workgroup provides since ever a database together with a full ecosystem so that end-users can contribute. The OpenPrinting database is already well known as THE database so that from my point of view it would be the logical step forward when THE printer database could move forward into THE printer and scanner database - in particular for end-users. In the past various individual attempts with sepatated databases died out. If you like to make a new scanner database, I think it is better to work together with the OpenPrinting workgroup and enhance the existing database. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer
[sane-devel] 55-libsane.rules
Hello,
very late reply but meanwhile I got a similar issue report
from a user with a SCSI processor EPSON Perfection1640:
On Jun 22 08:13 Olaf Meeuwissen wrote (excerpt):
Julien BLACHE jb at jblache.org writes:
Simon Becherer simon at becherer.de wrote:
here there is the line for my epson gt 1+ scanner (scsi):
# Epson GT-1+
ATTRS{type}==3, ATTRS{vendor}==EPSON,
ATTRS{model}==SCANNER GT-1
Added, thanks for your report!
Hmm, I think we could use a wild card here, like so
ATTRS{type}==3, ATTRS{vendor}==EPSON, ATTRS{model}=SCANNER*
and be done with.
What about one more wild card for any SCSI processor EPSON Perfection*
like
ATTRS{type}==3, ATTRS{vendor}==EPSON, ATTRS{model}=Perfection*
See
https://bugzilla.novell.com/show_bug.cgi?id=681146#c41
---
~ lsscsi -g
...
[11:0:2:0] process EPSONPerfection1640 1.03 - /dev/sg4
.
.
.
# sane-find-scanner
...
found SCSI processor EPSON Perfection1640 1.03 at /dev/sg4
---
Kind Regards
Johannes Meixner
--
SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany
HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer
[sane-devel] [OT?] discussion of front ends?
Hello, an off-topic question On Jul 13 13:55 D. Hugh Redelmeier wrote (excerpt): I want to do what I think is called scan to archive. I have way too many documents on paper and I'd like to capture them and discard the paper. ... I need a format that will still be useful for decades into the future. Right off the bat I would say: Keep the paper. I mean that I cannot imagine a format (perhaps except plain ASCII text) where I am sure as of today that it will stay for decades into the future. Furthermore there is the question to which extent others (in particular administrative offices) would accept whatever kind of data format in the same way as an original paper. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer
[sane-devel] 55-libsane.rules
Hello,
On Jun 21 08:48 Olaf Meeuwissen wrote:
Simon Becherer simon at becherer.de writes:
Hi there, you wrote:
(inside /etc/udev/rules.d/55-libsane-rules)
# If the scanner is supported by sane-backends, please mail the entry to
# the sane-devel mailing list (sane-devel at lists.alioth.debian.org).
here there is the line for my epson gt 1+ scanner (scsi):
# Epson GT-1+
KERNEL==sg[0-9]*, ATTRS{type}==3, ATTRS{vendor}==EPSON,
ATTRS{model}==SCANNER GT-1, MODE=0664, GROUP=lp,
ENV{libsane_matched}=yes
added the line in an suse 11.4 system, because the /dev/sg7 on which
my scanner was was root/root
with that line it is root/lp and i can use it as user.
Access permissions such as mode and group settings are distribution
policy specific things, not something that SANE forces upon anyone.
So this is really a SUSE issue.
IIRC, SUSE wants you to use YaST to configure your scanner. That ought
to take care of whatever is necessary.
Two times no.
Since HAL has gone to hell (hooray!) YaST does no longer need
to do awkward stuff to try to set scanner device permissions.
Nowadays we rely on udev and its rules files to do the right thing.
But when even the right thing fails, YaST provides a workaround,
see ... scanner access permissions via udev at
http://en.opensuse.org/SDB:Configuring_Scanners
We use the udev device entries from the SANE project as is,
i.e. we do not add or remove device entries but we modify
the default permissions from the SANE project for the device entries.
In particular we modify the permissions as Simon Becherer needs:
... MODE=0664, GROUP=lp, ENV{libsane_matched}=yes
Reason for GROUP=lp:
There is no group scanner in /etc/group for openSUSE.
For all-in-one devices (i.e. printer + scanner, e.g. EPSON Stylus devices)
the group must be lp so that the CUPS usb backend which runs
as user lp (who is member of the group lp) can send printing data
to the printer unit (i.e. the printer interface of the USB device).
It is sufficiently secure and reasonable easy to use by default
the same group lp for printers and scanners because both kind of devices
usually require physical user access (to get the printed paper or
to place a paper on the scanner) so that both kind of devices
should usually require the same kind of security.
But sane-backends-1.0.22 does not provide a particular udev rule
for the EPSON SCANNER GT-1 SCSI scanner device.
According to what Simon Becherer wrote, the EPSON SCANNER GT-1
SCSI scanner device is not a generic SCSI scanner with ATTRS{type}==6
instead it is one of those SCSI scanner devices with ATTRS{type}==3.
In contrast to the generic SCSI scanners with ATTRS{type}==6
the SCSI scanner devices which need ATTRS{type}==3
are listed one by one in libsane.rules
Conclusion:
An ATTRS{type}==3 udev rule is missing at the SANE project
for the SCSI scanner device EPSON SCANNER GT-1.
Perhaps the Epson people could provide a list of all their
SCSI scanner devices with ATTRS{type}==3 to the SANE project
so that such issues would be solved by those who initially
cause the trouble by making and selling somewhat crippled devices
which do not fulfill the requirements to be real SCSI scanners.
Kind Regards
Johannes Meixner
--
SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany
HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer
[sane-devel] sane - access problem with debian squeeze
Hello, On Apr 7 21:08 postbote2009-debian at yahoo.com wrote (excerpt): Julien BLACHE wrote (excerpt): postbote2009-debian at yahoo.com wrote (excerpt): device `pixma:04A91725' is a CANON Canon PIXMA MP610 multi-function peripheral Seeing how your device is an MFP, it's probably root:lp instead of root:scanner due to a change in udev itself between Lenny and Squeeze. In Lenny the scanner group would prevail, in Squeeze it's the lp group that prevails. In Lenny the issue was with printing to MFPs, in Squeeze it's with scanning. Two ways to work around this: - add your user to the lp group - use ConsoleKit and any user physically logged into the machine (running the X session) will have access to the scanner Thank you very much - after adding the user to lp everything worked fine. I?m just curious - if you?ve got the time and it isn?t too difficult to explain - why has the user to be in the group lp if in 60-libsane.rules scanner is mentioned? For openSUSE we do not have a group scanner and I change the udev rules in libsane.rules as follows: All GROUP=scanner are replaced by GROUP=lp. There is no group scanner in /etc/group for openSUSE. For all-in-one devices (i.e. printer + scanner, e.g. EPSON Stylus devices) the group must be lp so that the CUPS usb backend which runs as user lp (who is member of the group lp) can send printing data to the printer unit (i.e. the printer interface of the USB device). It is sufficiently secure and reasonable easy to use by default the same group lp for printers and scanners because both kind of devices usually require physical user access (to get the printed paper or to place a paper on the scanner) so that both kind of devices should usually require the same kind of security. Because one same device file cannot be in two traditional groups (i.e. when no advanced stuff like ACLs is used) and because multi function devices are more and more common nowadays, the printing via lp group versus scanning via scanner group conflict will happen more and more often. The solution could be one single traditional group by default. Therefore I suggest to think about if SANE may move away from its special group scanner and use the traditional group lp instead. This would of course not mean that a special group scanner is forbidden or that advanced stuff like ACLs can be used. All I like to suggest is a default which avoids a common conflict so that printing and scanning with multi function devices could work out of the box even in a traditional environment. A drawback when using the group lp by default for scanners is that there is a possible security issue when all normal users would be by default added to the group lp because users in the lp group can read the print spool data files /var/spool/cups/d* so that those users can read possibly confidential print job data. Therefore in openSUSE we do not add normal users by default to the lp group so that by default normal users cannot access scanners in a traditional environment. In openSUSE we use by default udev and its ACLs so that a user who logs in directly at the machine gets sufficient permissions to access scanners. But using the lp group also for scanners in openSUSE avoids the conflict which traditional group a multi function device should get assigned. And the admin in a traditional environment can add trusted users to the lp group if needed in his particular case - considering what is secure in his particular (network) environment. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex
[sane-devel] Detected scanner, proper driver, won't scan
Hello, On Feb 26 21:34 Stan Goodman wrote (excerpt): The scanner is Epson 640U, in recently installed openSuSE v11.3. YaST Scanners finds it and identifies it correctly; I have chosen the epson2 driver. :~ scanimage -L device `epson2:libusb:003:002' is a Epson Perfection640 flatbed scanner :~ scanimage -T scanimage: sane_start: Invalid argument Perhaps it works with the alternative drivers epson from SANE or with epkowa driver from Avasys in our iscan-free package? If not, you may have a look at http://en.opensuse.org/SDB:Configuring_Scanners in particular Trouble-Shooting (Debugging). Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex
[sane-devel] suseLINUX 11.2
Hello, On Feb 7 15:38 John Middlebrook wrote (shortened): Installed a Canon Pixma MX320 about two years ago. This model was supported by Canon for 11.1 and I downloaded the scanner driver. Then 11.2 was released to which I upgraded. The printer function still works, but the scanner driver has changed and is incompatible with that originally installed. Perhaps in your case it is also https://bugzilla.novell.com/show_bug.cgi?id=559697 If you are affected by the problem in this bug, you may need to downgrade libusb package(s), see in particular https://bugzilla.novell.com/show_bug.cgi?id=559697#c50 what you might do. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex
[sane-devel] Detect scan button on ScanSnap S1500 (sane-fujitsu backend)
Hello, On Nov 9 18:39 Wilhelm wrote (shortened): Am 09.11.2010 17:47, schrieb Johannes Meixner: If it really needs HAL, it is probably not very promising because HAL is meanwhile deprecated. yes, I know that! But its not scanbd's fault Of course it is not scanbd's fault! Bottom line: scanbd may use libhal/dbus, but if hal isn't available, it does not hurt: the only consequence is, that newly plugged scanners aren't instantly detected. Then you can send a signal or restart it via udev. Now it looks promising! In particular because udev rules for very most scanners do already exist (a libsane.rules udev rules file from SANE plus generic udev rules like acl.rules) it should be relatively easy to enhance this to send additionally a singal to scanbd. According to http://scanbd.svn.sourceforge.net/viewvc/scanbd/trunk/Makefile?revision=23view=markup LDFLAGS += -lconfuse -lsane -lpthread -ldbus-1 -lhal -lhal-storage it seems it links with HAL libraries in any case so that I got the idea that it actually needs HAL in any case. Because HAL is deprecated, would you mind to change it so that it does no longer link with HAL so that it would compile as is for current Linux distributions? If you like to provide readymade RPMs for the usual current Linux distributions for the usual hardware architectures, I would like to suggest to have a look at the openSUSE build service: https://build.opensuse.org/ It is open and free to our greatest possible extent. All you need to do is to register yourself before you can use it. The only non-free issue is that we (i.e. Novell/openSUSE) do not support building of packages as an anonymous user. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex
[sane-devel] Detect scan button on ScanSnap S1500 (sane-fujitsu backend)
Hello, On Nov 9 09:02 m. allan noah wrote: Wilhelm- This looks very promising! On Sat, Nov 6, 2010 at 3:18 PM, Wilhelm wilhelm.meier at fh-kl.de wrote: FYI: scanbd (scanner button daemon) can be used in such a case: 1) scanbd uses hal dbus-interface ... If it really needs HAL, it is probably not very promising because HAL is meanwhile deprecated. See for example http://en.wikipedia.org/wiki/HAL_%28software%29 As of 2009, distributions such as Ubuntu, Debian, and Fedora, and projects such as GNOME and X.org are in the process of deprecating HAL ... Initially a new daemon DeviceKit was planned to replace certain aspects of HAL, but in March 2009, DeviceKit was deprecated in favor of adding the same code to udev as a package: udev-extras You may follow the links therein. Also we (i.e. Novell/openSUSE) are in the same process, see http://lists.opensuse.org/opensuse-factory/2010-01/msg00055.html Future Development of hal has been stopped. Right, there is no future release planned. The project is dead and the functionality replaced by a bunch of other projects. ... What is replacing it? udev-extras (merge between DeviceKit and udev) There is no udev-extras. It was a temporary solution and no such package exists anymore. At least for me the whole stuff does not look very promising: HAL deprecated - DeviceKit deprecated - udev-extras deprecated Welcome to the hell of udev, HAL and its various replacements... In the end from my point of view only plain udev is what one can assume that it exists on an end-user's Linux system but it does not provide a really stable user interface. See http://www.kernel.org/doc/#sys The maintainers of sysfs do not believe in a stable API, and change userspace-visible elements from release to release. The rationale is that sysfs exports information from inside the kernel to outside the kernel (what API doesn't?) and the kernel internals change, thus sysfs changes to reflect it. ... In reality, sysfs is treated as a private API exported for the use of the udev program You will learn the consequences when you make udev rules. Those are not really stable (it is luck if they are stable for some time) so that you may have to adapt them from kernel release to release so that strictly speaking a userspace application which needs udev rules depends on a particular kernel release. As far as I found out the root cause seems to be that udev is actually meant as a kernel internal tool which is maintained by kernel maintainers so that the udev rules for kernel internal stuff (in particular for device drivers in the kernel) are updated and maintained in compliance to the particular kernel release. As far as I know a userspace application which needs udev rules seems to be currently some kind of misuse of the kernel internal tool udev. But I am not at all a udev expert so that I could be wrong here. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex
[sane-devel] canoscan 300 scsi scanner not detected
Hello, have in mind that on nowadays systems the generic SCSI device node files /dev/sg* do no longer belong only to real SCSI devices but also to whatever other kind of devices, e.g. on my system with a plugged in Spaceloop XL 4GB USB stick - nelson:~ # lsscsi --generic [1:0:0:0]diskATA ST3120022A 3.04 /dev/sda /dev/sg0 [2:0:0:0]cd/dvd PIONEER DVD-RW DVR-106D 1.10 /dev/sr0 /dev/sg1 [2:0:1:0]cd/dvd PIONEER DVD-ROM DVD-121R 1.00 /dev/sr1 /dev/sg2 [4:0:0:0]diskSony UMH-U HS-MS 2.12 /dev/sdb /dev/sg3 [4:0:0:1]diskSony UMH-U HS-CF 2.12 /dev/sdc /dev/sg4 [4:0:0:2]diskSony UMH-U HS-SM 2.12 /dev/sdd /dev/sg5 [5:0:0:0]disk Spaceloop XL 4GB 8.07 /dev/sde /dev/sg6 - so that the number of the generic SCSI device node files /dev/sg* may change depending on which device is plugged in first and/or depending on which device is recognized first by the kernel. Therefore it does no longer work reliable to have a generic SCSI device node file hardcoded in a /etc/sane.d/backend_name.conf file. Instead the backends should do scanner autodetection for USB and SCSI and their /etc/sane.d/backend_name.conf files should have appropriate defaults. In particular for the canon backend we (i.e. Novell/openSUSE) apply this patch: --- backend/canon.conf.in.save 2006-07-21 09:43:08.0 +0200 +++ backend/canon.conf.in 2006-07-21 09:57:03.0 +0200 @@ -1,3 +1,12 @@ -#canon.conf -/dev/scanner +# canon.conf +# +# Activate exactly one of the following choices: +# +# Probe on all /dev/sg* devices: +scsi +# +# Probe for CANON on all /dev/sg* devices: +#scsi CANON +# +# Probe only on one fixed device: #/dev/sg0 For more information regarding the canon backend have a look at https://bugzilla.novell.com/show_bug.cgi?id=177492 in particular https://bugzilla.novell.com/show_bug.cgi?id=177492#c11 Also see the device file for canon backend in sane-backends 1.0.17 mail on this list in May 2006. According to man sane-scsi it seems the SCSI autodetection is not possible for all operating systems? Otherwise it should be possible to have an upstream default /etc/sane.d/canon.conf like --- # canon.conf # # Activate exactly one of the following choices: # # Probe on all /dev/sg* devices: scsi # # Probe for CANON on all /dev/sg* devices: #scsi CANON # # Probe only on one fixed device: #/dev/sg0 --- Or is there another reason why SCSI autodetection should not be done by default? On Oct 28 07:11 m. allan noah wrote (shortened): edit /etc/sane.d/canon.conf put the scanner device file name there. allan On Thu, Oct 28, 2010 at 6:37 AM, Denis Prost denis.prost at wanadoo.fr wrote: ?Hi everyone, I've got a problem with my canoscan 300 scsi scanner. though it appears in sane-find-scanner output : -- ... found SCSI scanner CANON IX-03035B 1.01 at /dev/sg3 ?# Your SCSI scanner was detected. It may or may not be supported by SANE. Try ?# scanimage -L and read the backend's manpage. whatever GUI I use (xsane, kooka, simple-scan...), these softwares don't detect it, the only scanner they detect is my webcam. To solve the problem, I have to do by hand ln -s /dev/scanner /dev/sg3 each time I plug my scanner in. But that does not seem to be a very clean solution. Is that normal ? Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex
[sane-devel] canoscan 300 scsi scanner not detected
Hello, On Oct 28 09:52 m. allan noah wrote: I would need to check the code, but I think the canon backend mostly supports machines who's model name starts with 'IX' so the best solution might be: scsi CANON IX* or some such? I do not have a scanner which is supported by the canon backend so that all what I write here is only based upon what I read somewhere. According to what I read in man sane-scsi --- scsi VENDOR MODEL TYPE BUS CHANNEL ID LUN ... a field's value can be replaced with an asterisk symbol (``*''). An asterisk has the effect that any value is allowed for that particular field. --- so that it seems it is not possible to replace only a part of a particular field with an asterisk. According to http://www.sane-project.org/sane-backends.html#S-CANON the canon backend supports at least one non-CANON scanner, the Apple Color OneScanner 600/27. I have no idea how this device shows up at the SCSI but I assume Apple made sure that their device shows up at the SCSI under a manufacturer name like APPLE. According to my tests in http://lists.alioth.debian.org/pipermail/sane-devel/2006-May/016922.html it seems it is not possible to have something like --- #canon.conf scsi CANON scsi APPLE --- because it seems only the last entry scsi APPLE is used then. According to my tests in http://lists.alioth.debian.org/pipermail/sane-devel/2006-May/016922.html it seems not to cause problems if devices are probed which are no scanners so that in the end our patch results an unrestricted plain scsi by default in /etc/sane.d/canon.conf --- # canon.conf # # Activate exactly one of the following choices: # # Probe on all /dev/sg* devices: scsi # # Probe for CANON on all /dev/sg* devices: #scsi CANON # # Probe only on one fixed device: #/dev/sg0 --- We have this since July 2006 and at least I noticed no bug reports or user complaints because of this - but I have no idea how many users use scanners which are supported by the canon backend. By default we have all backends in /etc/sane.d/dll.conf disabled (to avoid that a SANE frontend lets various backends start up and do needless probing for devices which do not exist) so that the canon backend only runs for those users which actually use a matching scanner. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex
[sane-devel] Print server (Dlink DPR 2000)
Hello, On Oct 6 06:56 Vincent Le Mieux wrote (shortened): I've got a Brother DCP7010 (multifunction Scanner + Laser Printer) connected thru USB to a DLINK DPR2000 (an independant print server 4 USB and Wifi). I can access the printer with my different computers thru Wifi. The printing thru the network is OK but Xsane doesn't see the scanner. Printserver boxes provide only some kind of unidirectional data transfer from the computer to the printer so that plain printing usually works but usually nothing else. As far as I know only HP Jetdirect printservers provide additionally some SNMP stuff to get HP printer device status and whatever else is needed so that in particular HP's own HPLIP printer/scanner driver software can use HP all-in-one devices for printing, device status, scanning, faxing,... For scanning you need a full bidirectional communication between computer and device. In your case this means you should connect the device directly via USB to the computer at least for a test to find out if whatever scanner driver software you use (perhaps you need whatever driver from Brother) works at all. If it works via direct USB connection, you may experiment with your particular printserver box to find out to what extent it supports bidirectional communication to the device. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex
[sane-devel] Trouble with HP Photosmart C4780 on Mac OS X 10.6
Hello, On Sep 9 09:48 m. allan noah wrote (shortened): you also need to install the hpaio backend, which is part of the hplip software. I don't know anything about doing that on a Mac... FYI: http://hplipopensource.com/node/281 reads HP Linux imaging and printing Print, scan and fax drivers for Linux What distributions/operating systems are supported? Answer: HPLIP is designed for use on Linux operating systems. ... We currently do not test BSD, UNIX, Solaris, Mac OS X, or Darwin. It is altogether possible that some advanced users have been successful in modifying HPLIP for use on these systems, but we do not document or provide support on such uses of HPLIP. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex
[sane-devel] Trouble with HP Officejet j4680
Hello, On Sep 6 11:33 m. allan noah wrote (shortened): Very close- just one correction: sane-find-scanner lists all the devices attached to the system which might be a scanner, including ones which are not supported by sane, and ones that are supported but drivers are not installed. scanimage -L on the other hand, will list only those scanners which are detected by the installed backends. Even closer - just one more correction: scanimage -L lists only those scanners which are detected by only those backends which are installed and activated i.e. listed without leading '#' character in /etc/sane.d/dll.conf Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex
[sane-devel] pros and cons regarding --enable-pthread for Linux
Hello, On Aug 28 08:29 Julien BLACHE wrote (shortened): m. allan noah kitno455 at gmail.com wrote: ... became the default for Linux. Honestly, I think it could be changed, but I don't think pthread is as well tested, since most user's use whatever their distro compiles :) sane-backends in Debian has been using pthread since Feb 2009. I assume there have been no issues because of this (otherwise you would have told us). Now I think about --enable-pthread for the next openSUSE version and if there are bug reports because of this I could switch back to the default. I wonder why there is no reply from sane-backends package maintainers of other Linux distributions - perhaps everybody on summer vacation? Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex
