From c.a.cook at quantum-sci.com Fri Jul 3 21:41:06 2020 From: c.a.cook at quantum-sci.com (C. Cook) Date: Fri, 3 Jul 2020 13:41:06 -0700 Subject: [sane-devel] IPV6 Only? Message-ID: <3cf27055-49a7-6d40-a7d5-b0345bbb3169@quantum-sci.com> Just installed saned to a raspberry pi running centos.  When I first started saned.socket it failed with "saned.socket failed to listen on sockets: Address family not supported by protocol". Huh? Turns out it will only start in IPV6 and I have that disabled in the kernel. (sysctl)  When I enabled IPV6 the daemon started fine...  but only on IPV6.  And it's disobeying my directive in net.conf to only listen on localhost, instead listening on *. systemd   1   root   43u  IPv6  12327      0t0  TCP *:6566 (LISTEN) Name        : sane-backends Version     : 1.0.24 Release     : 12.el7 Architecture: armv7hl What am I doing wrong? -------------- next part -------------- An HTML attachment was scrubbed... URL: From juergen.mellinger at t-online.de Sun Jul 5 15:37:58 2020 From: juergen.mellinger at t-online.de (=?utf-8?Q?J=C3=BCrgen_Mellinger?=) Date: Sun, 5 Jul 2020 16:37:58 +0200 Subject: [sane-devel] SANE Color Management In-Reply-To: <5fb9df9b-60a6-dcfc-4a1b-609335b75982@apevzner.com> References: <53470749-426a-bee9-8049-3d5d803db2d6@apevzner.com> <51429722-e807-7582-70f4-f5dd219456c9@apevzner.com> <2C114FF2-E43D-4F18-A6AB-193B3AC628D1@t-online.de> <0981307b-e2ab-20d2-5a15-41f396118b03@apevzner.com> <5fb9df9b-60a6-dcfc-4a1b-609335b75982@apevzner.com> Message-ID: <705A50B4-51FD-44D4-9641-3EB9B9ADF2ED@t-online.de> Hi, many SANE backends provide gamma correction options, but I could not find any information about the default color space in which scan data are being sent to sane_read(). I mean, if there is no custom gamma table used, then a backend should be able to use its knowledge about a scanner’s CCD’s gamma value to transform it into a pre-defined color space, such as sRGB, or linear gamma. If there is no such pre-defined color space, then each and every user will have to determine the correct gamma for their each and every scanner, and perform custom gamma correction just to obtain a reasonable image. From this I suspect that SANE backends indeed transform scanner data into a standard color space. My experience with the genesys backend suggests that it’s linear gamma. But I cannot find any documentation on this issue. Could someone point me to more information on this topic? Thank you, Jürgen From kitno455 at gmail.com Sun Jul 5 19:02:51 2020 From: kitno455 at gmail.com (m. allan noah) Date: Sun, 5 Jul 2020 14:02:51 -0400 Subject: [sane-devel] SANE Color Management In-Reply-To: <705A50B4-51FD-44D4-9641-3EB9B9ADF2ED@t-online.de> References: <53470749-426a-bee9-8049-3d5d803db2d6@apevzner.com> <51429722-e807-7582-70f4-f5dd219456c9@apevzner.com> <2C114FF2-E43D-4F18-A6AB-193B3AC628D1@t-online.de> <0981307b-e2ab-20d2-5a15-41f396118b03@apevzner.com> <5fb9df9b-60a6-dcfc-4a1b-609335b75982@apevzner.com> <705A50B4-51FD-44D4-9641-3EB9B9ADF2ED@t-online.de> Message-ID: I believe that most backends are doing no transformation at all. Since most backends are reverse engineered, I think we consider ourselves lucky just to get image data out of the scanner. If the blacks look black, and the whites look white, we ship it :) allan On Sun, Jul 5, 2020 at 10:38 AM Jürgen Mellinger wrote: > > Hi, > > many SANE backends provide gamma correction options, but I could not find any information about the default color space in which scan data are being sent to sane_read(). I mean, if there is no custom gamma table used, then a backend should be able to use its knowledge about a scanner’s CCD’s gamma value to transform it into a pre-defined color space, such as sRGB, or linear gamma. If there is no such pre-defined color space, then each and every user will have to determine the correct gamma for their each and every scanner, and perform custom gamma correction just to obtain a reasonable image. > > From this I suspect that SANE backends indeed transform scanner data into a standard color space. My experience with the genesys backend suggests that it’s linear gamma. But I cannot find any documentation on this issue. > > Could someone point me to more information on this topic? > > Thank you, > Jürgen -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand" From c.a.cook at quantum-sci.com Tue Jul 7 21:18:26 2020 From: c.a.cook at quantum-sci.com (C. Cook) Date: Tue, 7 Jul 2020 13:18:26 -0700 Subject: [sane-devel] IPV6 Only? In-Reply-To: <3cf27055-49a7-6d40-a7d5-b0345bbb3169@quantum-sci.com> References: <3cf27055-49a7-6d40-a7d5-b0345bbb3169@quantum-sci.com> Message-ID: <22bc12cc-7564-a997-758b-490bbd79a5db@quantum-sci.com> Nothing? Nobody knows why I have IPV6 only? On 2020-07-03 13:41, C. Cook wrote: > > Just installed saned to a raspberry pi running centos.  When I first > started saned.socket it failed with "saned.socket failed to listen on > sockets: Address family not supported by protocol". > > Huh? > > Turns out it will only start in IPV6 and I have that disabled in the > kernel. (sysctl)  When I enabled IPV6 the daemon started fine...  but > only on IPV6.  > > And it's disobeying my directive in net.conf to only listen on > localhost, instead listening on *. > > systemd   1   root   43u  IPv6  12327      0t0  TCP *:6566 (LISTEN) > > Name        : sane-backends > Version     : 1.0.24 > Release     : 12.el7 > Architecture: armv7hl > > What am I doing wrong? > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From simon.matter at invoca.ch Wed Jul 8 07:08:44 2020 From: simon.matter at invoca.ch (Simon Matter) Date: Wed, 8 Jul 2020 08:08:44 +0200 Subject: [sane-devel] IPV6 Only? In-Reply-To: <3cf27055-49a7-6d40-a7d5-b0345bbb3169@quantum-sci.com> References: <3cf27055-49a7-6d40-a7d5-b0345bbb3169@quantum-sci.com> Message-ID: > Just installed saned to a raspberry pi running centos.  When I first > started saned.socket it failed with "saned.socket failed to listen on > sockets: Address family not supported by protocol". > > Huh? > > Turns out it will only start in IPV6 and I have that disabled in the > kernel. (sysctl)  When I enabled IPV6 the daemon started fine...  but > only on IPV6.  > > And it's disobeying my directive in net.conf to only listen on > localhost, instead listening on *. > > systemd   1   root   43u  IPv6  12327      0t0  TCP *:6566 (LISTEN) > > Name        : sane-backends > Version     : 1.0.24 > Release     : 12.el7 > Architecture: armv7hl > > What am I doing wrong? You are using systemd :-) What you see listening is not saned but systemd, that's why it doesn't obey to what you have configured in net.conf. I guess you have to fiddle with the systemd config now. Regards, Simon From louis at fazant.net Thu Jul 9 20:16:13 2020 From: louis at fazant.net (Louis Lagendijk) Date: Thu, 09 Jul 2020 21:16:13 +0200 Subject: [sane-devel] IPV6 Only? In-Reply-To: References: <3cf27055-49a7-6d40-a7d5-b0345bbb3169@quantum-sci.com> Message-ID: On Wed, 2020-07-08 at 08:08 +0200, Simon Matter via sane-devel wrote: > > Just installed saned to a raspberry pi running centos. When I > > first > > started saned.socket it failed with "saned.socket failed to listen > > on > > sockets: Address family not supported by protocol". > > > > Huh? > > > > Turns out it will only start in IPV6 and I have that disabled in > > the > > kernel. (sysctl) When I enabled IPV6 the daemon started fine... > > but > > only on IPV6. > > > > And it's disobeying my directive in net.conf to only listen on > > localhost, instead listening on *. > > > > systemd 1 root 43u IPv6 12327 0t0 TCP *:6566 (LISTEN) > > > > Name : sane-backends > > Version : 1.0.24 > > Release : 12.el7 > > Architecture: armv7hl > > > > What am I doing wrong? > > You are using systemd :-) > > What you see listening is not saned but systemd, that's why it > doesn't > obey to what you have configured in net.conf. > > I guess you have to fiddle with the systemd config now. > > Regards, > Simon > Should be simple: change the ListenStream line in the sample socket file as described in the man-page for saned to: ListenStream=
:6566 that should do the trick /Louis From jffry at posteo.net Sat Jul 11 11:17:28 2020 From: jffry at posteo.net (Jeff) Date: Sat, 11 Jul 2020 12:17:28 +0200 Subject: [sane-devel] gscan2pdf v2.8.1 released Message-ID: <1ab42f34-05dd-2995-06d0-6243efe5fbe4@posteo.net> gscan2pdf - A GUI to produce a multipage PDF or DjVu from a scan. http://gscan2pdf.sourceforge.net/ Five clicks are required to scan several pages and then save all or a selection as a PDF or DjVu file, including metadata if required. gscan2pdf can control regular or sheet-fed (ADF) scanners with SANE via libimage-sane-perl, scanimage or scanadf, and can scan multiple pages at once. It presents a thumbnail view of scanned pages, and permits simple operations such as cropping, rotating and deleting pages. OCR can be used to recognise text in the scans, and the output embedded in the PDF or DjVu. PDF conversion is done by PDF::API2. The resulting document may be saved as a PDF, DjVu, multipage TIFF file, or single page image file. Changelog for 2.8.1: * Pass resolution to tesseract to avoid messages like "Warning! Invalid resolution 0 dpi. Using 70 instead" * Cope better if data model becomes corrupted * + restart option to 'device not found' mini-wizard & if tmp directory changed. * When saving a session file, note that pages have been saved to avoid 'Some pages have not been saved. Do you really want to quit?' message. * Improvements to the Crashed sessions dialog to make it more intuitive. * Update position of OCR text when cropping * Create PS level 3 instead of 1. * Fix check for unpaper version. Closes #285 (Scan fails if unpaper is not installed but selected in post processing) * Fix check for tesseract version. Remove support for tesseract < 3.04.00. * Update to Hungarian translation (thanks to csola) * Update to Brazilian Portuguese translation (thanks to Arthur Rodrigues) * Update to German translation (thanks to Matthias Sprau) * Update to Ukrainian translation (thanks to Yuri Chornoivan) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From paddy-hack at member.fsf.org Sun Jul 12 04:52:55 2020 From: paddy-hack at member.fsf.org (Olaf Meeuwissen) Date: Sun, 12 Jul 2020 12:52:55 +0900 Subject: [sane-devel] SANE Color Management In-Reply-To: References: <53470749-426a-bee9-8049-3d5d803db2d6@apevzner.com> <51429722-e807-7582-70f4-f5dd219456c9@apevzner.com> <2C114FF2-E43D-4F18-A6AB-193B3AC628D1@t-online.de> <0981307b-e2ab-20d2-5a15-41f396118b03@apevzner.com> <5fb9df9b-60a6-dcfc-4a1b-609335b75982@apevzner.com> <705A50B4-51FD-44D4-9641-3EB9B9ADF2ED@t-online.de> Message-ID: <87tuydfkyw.fsf@member.fsf.org> Hi, m. allan noah writes: > I believe that most backends are doing no transformation at all. Since > most backends are reverse engineered, I think we consider ourselves > lucky just to get image data out of the scanner. If the blacks look > black, and the whites look white, we ship it :) Some of us also check the RGBs :-) > On Sun, Jul 5, 2020 at 10:38 AM Jürgen Mellinger > wrote: >> >> Hi, >> >> many SANE backends provide gamma correction options, but I could not >> find any information about the default color space in which scan data >> are being sent to sane_read(). I mean, if there is no custom gamma >> table used, then a backend should be able to use its knowledge about >> a scanner’s CCD’s gamma value to transform it into a pre-defined >> color space, such as sRGB, or linear gamma. If there is no such >> pre-defined color space, then each and every user will have to >> determine the correct gamma for their each and every scanner, and >> perform custom gamma correction just to obtain a reasonable image. >> >> From this I suspect that SANE backends indeed transform scanner data >> into a standard color space. My experience with the genesys backend >> suggests that it’s linear gamma. But I cannot find any documentation >> on this issue. It's backend specific and likely even model specific. I vaguely recall the epson and epson2 backends using a gamma of 2.2 by default. >> Could someone point me to more information on this topic? The best I can think of is the "Image Data Format" section in the SANE Standard at https://sane-project.gitlab.io/standard/environment.html#image-data-format but that doesn't say anything about standard color spaces. Hope this helps, -- Olaf Meeuwissen, LPIC-2 FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Software https://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join From jfdsmit at gmail.com Tue Jul 14 20:45:30 2020 From: jfdsmit at gmail.com (Jens de Smit) Date: Tue, 14 Jul 2020 21:45:30 +0200 Subject: [sane-devel] Canon iSENSYS MF8030Cn support Message-ID: Hello all, I have a Canon MF8030Cn network laser multifunctional that I used under Win10 to scan. I have gotten it to work as a printer under Linux, but SANE does not find the scanner part of the device. If I add the scanner's details to pixma.conf manually I get the following message: [21:34:32.750890] [bjnp] add_scanner: Scanner MF8000 Series is not supported, model is unknown! Please report upstream I see that many other printers in the Canon MF range are supported, so I was hoping to get this one to work as well. Any pointers on where/how I should get started? Best regards, Jens -------------- next part -------------- An HTML attachment was scrubbed... URL: From pzz at apevzner.com Tue Jul 14 21:38:11 2020 From: pzz at apevzner.com (Alexander Pevzner) Date: Tue, 14 Jul 2020 23:38:11 +0300 Subject: [sane-devel] Canon iSENSYS MF8030Cn support In-Reply-To: References: Message-ID: Hi Jens, > I have a Canon MF8030Cn network laser multifunctional that I used under > Win10 to scan. I have gotten it to work as a printer under Linux, but > SANE does not find the scanner part of the device. If I add the > scanner's details to pixma.conf manually I get the following message: your device may support WSD scan. At this case it will work with the sane-airscan driver: https://github.com/alexpevzner/sane-airscan - project page https://download.opensuse.org/repositories/home:/pzz/ - binary packages for many distros Please let me know if it really works, I'll update a list of supported devices to help other users with the similar printer model. -- Wishes, Alexander Pevzner (pzz at apevzner.com) From bardo1950 at fastwebnet.it Fri Jul 17 11:01:15 2020 From: bardo1950 at fastwebnet.it (valerio) Date: Fri, 17 Jul 2020 12:01:15 +0200 Subject: [sane-devel] Canon Canoscan LiDE 400 support in Slackware In-Reply-To: References: Message-ID: Il 11/01/20 15:00, Rich Shepard ha scritto: > On Sat, 11 Jan 2020, Kelly Price wrote: > >> You fall into the same category I do with my LiDE 220. It somehow just >> doesn't like USB 3.x ports. I think we were working on the issue still. >> Olaf can remind me (as it's early and coffee is just being had here). > > Kelly, > > I recall reading somewhere that the LiDE 400 required USB 3.x ports. And, > when connected to a 3.0 port I could press the 'PDF' button on the front > edge of the scanner, which brought up a simple GUI interface, and was able > to scan a page. So it must accept the USB 3.0 ports when used by itself but > even after adding it to /etc/scan.c/genesis.conf it's not found by > 'scanimage -L'. > hi Rich, i have a canon lide 400 too, just bought... as for you, sane-find-scanner find the scanner, but not scanimage -L my scanner doesn't work, no button works: is normal? with lsusb -t, show this: /: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 10000M /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M |__ Port 1: Dev 4, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 1: Dev 4, If 1, Class=Video, Driver=uvcvideo, 480M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M |__ Port 2: Dev 4, If 0, Class=Hub, Driver=hub/4p, 5000M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 2: Dev 8, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 3: Dev 9, If 0, Class=Vendor Specific Class, Driver=, 480M |__ Port 3: Dev 9, If 1, Class=Vendor Specific Class, Driver=, 480M |__ Port 3: Dev 9, If 2, Class=Vendor Specific Class, Driver=, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/3p, 10000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/9p, 480M |__ Port 9: Dev 3, If 0, Class=Printer, Driver=, 480M |__ Port 9: Dev 3, If 1, Class=Vendor Specific Class, Driver=, 480M |__ Port 9: Dev 3, If 2, Class=Mass Storage, Driver=usb-storage, 480M did you solve your problem? valerio >> As a work-around, I ended up putting this in my PC: >> https://smile.amazon.com/gp/product/B002RL8V7E/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 >> > > Did it solve the problem? > > I don't know about other Canon scanners but the LiDE 400 has no power > switch. It turns on when the USB cable is inserted. > > Regards, > > Rich > > From rolf at bensch-online.de Fri Jul 17 15:43:26 2020 From: rolf at bensch-online.de (Rolf Bensch) Date: Fri, 17 Jul 2020 16:43:26 +0200 Subject: [sane-devel] Canon Canoscan LiDE 400 support in Slackware In-Reply-To: References: Message-ID: <16885b2f-11ce-403d-4f67-c02293b88e56@bensch-online.de> Hi, My LiDE 400 is working with recent SANE version 1.0.30-914-g8bdd27d14. You need at lease SANE version 1.0.28. Please check your installed SANE version with 'scanimage -V'. This scanner has problems working via USB hosts. You need to connect it directly to your computer. And I can scan via USB3. But it's not faster than USB2. It's still connected as USB2 device. Hopr this helps. Cheers, Rolf Am 17.07.20 um 12:01 schrieb valerio: > > > Il 11/01/20 15:00, Rich Shepard ha scritto: >> On Sat, 11 Jan 2020, Kelly Price wrote: >> >>> You fall into the same category I do with my LiDE 220. It somehow just >>> doesn't like USB 3.x ports. I think we were working on the issue still. >>> Olaf can remind me (as it's early and coffee is just being had here). >> >> Kelly, >> >> I recall reading somewhere that the LiDE 400 required USB 3.x ports. >> And, >> when connected to a 3.0 port I could press the 'PDF' button on the front >> edge of the scanner, which brought up a simple GUI interface, and was >> able >> to scan a page. So it must accept the USB 3.0 ports when used by >> itself but >> even after adding it to /etc/scan.c/genesis.conf it's not found by >> 'scanimage -L'. >> > > hi Rich, > i have a canon lide 400 too, just bought... > as for you, sane-find-scanner find the scanner, but not scanimage -L > my scanner doesn't work, no button works: is normal? > > with lsusb -t, show this: > > /:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 10000M > /:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M >     |__ Port 1: Dev 4, If 0, Class=Video, Driver=uvcvideo, 480M >     |__ Port 1: Dev 4, If 1, Class=Video, Driver=uvcvideo, 480M > /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M >     |__ Port 2: Dev 4, If 0, Class=Hub, Driver=hub/4p, 5000M > /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M >     |__ Port 2: Dev 8, If 0, Class=Hub, Driver=hub/4p, 480M >         |__ Port 3: Dev 9, If 0, Class=Vendor Specific Class, Driver=, > 480M >         |__ Port 3: Dev 9, If 1, Class=Vendor Specific Class, Driver=, > 480M >         |__ Port 3: Dev 9, If 2, Class=Vendor Specific Class, Driver=, > 480M > /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/3p, 10000M > /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/9p, 480M >     |__ Port 9: Dev 3, If 0, Class=Printer, Driver=, 480M >     |__ Port 9: Dev 3, If 1, Class=Vendor Specific Class, Driver=, 480M >     |__ Port 9: Dev 3, If 2, Class=Mass Storage, Driver=usb-storage, 480M > > did you solve your problem? > > valerio > > > >>> As a work-around, I ended up putting this in my PC: >>> https://smile.amazon.com/gp/product/B002RL8V7E/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 >>> >> >> Did it solve the problem? >> >> I don't know about other Canon scanners but the LiDE 400 has no power >> switch. It turns on when the USB cable is inserted. >> >> Regards, >> >> Rich >> >> > > From pzz at apevzner.com Fri Jul 17 15:48:00 2020 From: pzz at apevzner.com (Alexander Pevzner) Date: Fri, 17 Jul 2020 17:48:00 +0300 Subject: [sane-devel] Canon Canoscan LiDE 400 support in Slackware In-Reply-To: References: Message-ID: Hi Valerio. May be, I'm missing something, but I don't see something that looks like scanner in your list of devices. May be, something wrong with USB port or cable... BTW, Lide 400 known to work via IPP over USB, and in this mode it supports eSCL protocol. You may try to install the following program for IPP over USB: https://github.com/OpenPrinting/ipp-usb Sorry, there are no Slackware binary packages, but this program is easy to build. After that program is installed, there are chances that it will work with sane-escl, included officially into SANE. If not, there are alternative eSCL/WSD backend, known to work (based on 2 user's reports) with this device: https://github.com/alexpevzner/sane-airscan -- Wishes, Alexander Pevzner (pzz at apevzner.com) From bardo1950 at fastwebnet.it Fri Jul 17 16:21:20 2020 From: bardo1950 at fastwebnet.it (valerio) Date: Fri, 17 Jul 2020 17:21:20 +0200 Subject: [sane-devel] Canon Canoscan LiDE 400 support in Slackware In-Reply-To: <16885b2f-11ce-403d-4f67-c02293b88e56@bensch-online.de> References: <16885b2f-11ce-403d-4f67-c02293b88e56@bensch-online.de> Message-ID: hi Rolf, Il 17/07/20 16:43, Rolf Bensch ha scritto: > Hi, > > My LiDE 400 is working with recent SANE version 1.0.30-914-g8bdd27d14. > You need at lease SANE version 1.0.28. > > Please check your installed SANE version with 'scanimage -V'. root at anarres:~# scanimage -V scanimage (sane-backends) 1.0.30-914-g8bdd27d14; backend version 1.0.27 > > This scanner has problems working via USB hosts. You need to connect it > directly to your computer. And I can scan via USB3. But it's not faster > than USB2. It's still connected as USB2 device. i imagined, but doesn't work > > Hopr this helps. > > Cheers, > Rolf thanks valerio From bardo1950 at fastwebnet.it Fri Jul 17 16:27:25 2020 From: bardo1950 at fastwebnet.it (valerio) Date: Fri, 17 Jul 2020 17:27:25 +0200 Subject: [sane-devel] Canon Canoscan LiDE 400 support in Slackware In-Reply-To: References: Message-ID: Hi Alexander, Il 17/07/20 16:48, Alexander Pevzner ha scritto: > Hi Valerio. > > May be, I'm missing something, but I don't see something that looks like > scanner in your list of devices. May be, something wrong with USB port > or cable... > so: Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 004: ID 1e4e:0102 Cubeternet GL-UPC822 UVC WebCam Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 004: ID 05e3:0616 Genesys Logic, Inc. hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 008: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 03f0:c202 HP, Inc PhotoSmart 8200 series Bus 001 Device 005: ID 04a9:1912 Canon, Inc. LiDE 400 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > BTW, Lide 400 known to work via IPP over USB, and in this mode it > supports eSCL protocol. i don't understand > > You may try to install the following program for IPP over USB: > >     https://github.com/OpenPrinting/ipp-usb > > Sorry, there are no Slackware binary packages, but this program is easy > to build. but i have debian... > > After that program is installed, there are chances that it will work > with sane-escl, included officially into SANE. If not, there are > alternative eSCL/WSD backend, known to work (based on 2 user's reports) > with this device: > >     https://github.com/alexpevzner/sane-airscan > there is no connector. thanks valerio From pzz at apevzner.com Fri Jul 17 16:31:27 2020 From: pzz at apevzner.com (Alexander Pevzner) Date: Fri, 17 Jul 2020 18:31:27 +0300 Subject: [sane-devel] Canon Canoscan LiDE 400 support in Slackware In-Reply-To: <16885b2f-11ce-403d-4f67-c02293b88e56@bensch-online.de> References: <16885b2f-11ce-403d-4f67-c02293b88e56@bensch-online.de> Message-ID: <019b4046-6f67-b3f9-2e63-d6befda0804d@apevzner.com> Hi Rolf, > This scanner has problems working via USB hosts. You need to connect it > directly to your computer. And I can scan via USB3. But it's not faster > than USB2. It's still connected as USB2 device. AFAIR, this scanner is powered from USB, which implies particular requirements on amount of power that USB port can give away, may be somehow above standards. USB 3.0 ports can give more power, which may make them more reliable with this device. -- Wishes, Alexander Pevzner (pzz at apevzner.com) From sedat.dilek at gmail.com Fri Jul 17 16:39:42 2020 From: sedat.dilek at gmail.com (Sedat Dilek) Date: Fri, 17 Jul 2020 17:39:42 +0200 Subject: [sane-devel] Canon Canoscan LiDE 400 support in Slackware In-Reply-To: References: Message-ID: > BTW, Lide 400 known to work via IPP over USB, and in this mode it > supports eSCL protocol. > > You may try to install the following program for IPP over USB: > > https://github.com/OpenPrinting/ipp-usb > Hi Alexander, thanks for your offer of ipp-usb as an alternative. Can you update the "debian" directory - maybe to reflect the latest 0.9.10 release? Thanks. Regards, - Sedat - [1] https://github.com/OpenPrinting/ipp-usb/releases/tag/0.9.10 [2] https://github.com/OpenPrinting/ipp-usb/tree/0.9.10/debian From pzz at apevzner.com Fri Jul 17 16:50:14 2020 From: pzz at apevzner.com (Alexander Pevzner) Date: Fri, 17 Jul 2020 18:50:14 +0300 Subject: [sane-devel] Canon Canoscan LiDE 400 support in Slackware In-Reply-To: References: Message-ID: Hi Valerio, >> BTW, Lide 400 known to work via IPP over USB, and in this mode it >> supports eSCL protocol. > > i don't understand I'll explain :-) There is such a thing, that driverless printing and scanning. "Driverless" means that device implements vendor-neutral protocol, and driver is very generic and works with a large class of compatible devices, regardless of their models and manufacturers. Normally, driverless printing and scanning were protocols designed for network-connected devices. IPP over USB is a technology, that allows to "speak" with compatible USB devices as if they were connected to the network. IPP over USB requires additional piece of software, the ipp-usb daemon, which connects to device via USB and exposes it to the network (by default to localhost only). eSCL is a scanning protocol, supported by many devices from many vendors. It is also known as Apple AirScan. Both protocols (IPP over USB and eSCL) are supported by your device. You will need ipp-usb daemon, to enable IPP over USB, and sane-escl or sane-airscan, to utilize eSCL scanning. I don't know if somebody tested sane-escl with your device, but regarding sane-airscan, two independent users reported that it works with Lide 400. >> You may try to install the following program for IPP over USB: >> >>      https://github.com/OpenPrinting/ipp-usb >> >> Sorry, there are no Slackware binary packages, but this program is >> easy to build. > > but i have debian... I was confused by "Slackware" in the message subject :-) For Debian I provide binary packages for both ipp-usb and sane-airscan: https://download.opensuse.org/repositories/home:/pzz/ -- Wishes, Alexander Pevzner (pzz at apevzner.com) From pzz at apevzner.com Fri Jul 17 16:58:21 2020 From: pzz at apevzner.com (Alexander Pevzner) Date: Fri, 17 Jul 2020 18:58:21 +0300 Subject: [sane-devel] Canon Canoscan LiDE 400 support in Slackware In-Reply-To: References: Message-ID: Hi, Sedat, > Can you update the "debian" directory - maybe to reflect the latest > 0.9.10 release? The content of this directory is hysterical artifact. AFAIK, nobody uses these files directly, they are used only as a template. Debian seems to officially include ipp-usb since the next Debian release. For their official builds, release version will be set properly by their build infrastructure. For packages that I generate by myself (for many distros) setting correct release number is handled automatically by OpenSUSE Build Services: https://download.opensuse.org/repositories/home:/pzz/Debian_10/ -- Wishes, Alexander Pevzner (pzz at apevzner.com) From sedat.dilek at gmail.com Fri Jul 17 17:13:29 2020 From: sedat.dilek at gmail.com (Sedat Dilek) Date: Fri, 17 Jul 2020 18:13:29 +0200 Subject: [sane-devel] Canon Canoscan LiDE 400 support in Slackware In-Reply-To: References: Message-ID: On Fri, Jul 17, 2020 at 5:58 PM Alexander Pevzner wrote: > > Hi, Sedat, > > > Can you update the "debian" directory - maybe to reflect the latest > 0.9.10 release? > The content of this directory is hysterical artifact. AFAIK, nobody uses > these files directly, they are used only as a template. > You mean hysterical or historical :-)... > Debian seems to officially include ipp-usb since the next Debian > release. For their official builds, release version will be set properly > by their build infrastructure. > OK, I see Debian/unstable offers as an installation candidate: root at iniza:~# LC_ALL=C apt-cache policy ipp-usb ipp-usb: Installed: (none) Candidate: 0.9.10-1 Version table: 0.9.10-1 99 99 https://incoming.debian.org/debian-buildd buildd-unstable/main amd64 Packages 99 http://ftp.debian.org/debian unstable/main amd64 Packages 99 https://deb.debian.org/debian unstable/main amd64 Packages Hmm, the available sane and libsane (no version 1.0.28) are not suitable: root at iniza:~# LC_ALL=C apt-cache policy sane sane: Installed: (none) Candidate: 1.0.14-15 Version table: 1.0.14-15 500 500 http://ftp.debian.org/debian testing/main amd64 Packages 500 https://deb.debian.org/debian testing/main amd64 Packages 99 http://ftp.debian.org/debian unstable/main amd64 Packages 99 https://deb.debian.org/debian unstable/main amd64 Packages root at iniza:~# LC_ALL=C apt-cache policy libsane libsane: Installed: 1.0.27-3.2+b1 Candidate: 1.0.27-3.2+b1 Version table: *** 1.0.27-3.2+b1 500 500 http://ftp.debian.org/debian testing/main amd64 Packages 500 https://deb.debian.org/debian testing/main amd64 Packages 99 http://ftp.debian.org/debian unstable/main amd64 Packages 99 https://deb.debian.org/debian unstable/main amd64 Packages 100 /var/lib/dpkg/status - Sedat - > For packages that I generate by myself (for many distros) setting > correct release number is handled automatically by OpenSUSE Build Services: > > https://download.opensuse.org/repositories/home:/pzz/Debian_10/ > Ah, cool. Thanks. - Sedat - From pzz at apevzner.com Fri Jul 17 17:34:48 2020 From: pzz at apevzner.com (Alexander Pevzner) Date: Fri, 17 Jul 2020 19:34:48 +0300 Subject: [sane-devel] Canon Canoscan LiDE 400 support in Slackware In-Reply-To: References: Message-ID: <6d1fe675-64c8-1b79-2e34-e32ccb2288ab@apevzner.com> > You mean hysterical or historical :-)... Seems that I should more carefully check after spellchecker :-) -- Wishes, Alexander Pevzner (pzz at apevzner.com) From rolf at bensch-online.de Fri Jul 17 19:51:34 2020 From: rolf at bensch-online.de (Rolf Bensch) Date: Fri, 17 Jul 2020 20:51:34 +0200 Subject: [sane-devel] Canon Canoscan LiDE 400 support in Slackware In-Reply-To: References: <16885b2f-11ce-403d-4f67-c02293b88e56@bensch-online.de> Message-ID: Hi Valerio, Am 17.07.20 um 17:21 schrieb valerio: > [...] > > root at anarres:~# scanimage -V > scanimage (sane-backends) 1.0.30-914-g8bdd27d14; backend version 1.0.27 > > [...] I can see your problem. You have a mixed SANE installation: Recent frontend but ancient backend. If you've installed SANE from source, however please follow "2.3.1. SANE library" in INSTALL.linux from your sources folder or from here: http://www.sane-project.org/docs.html . Then you should be able to switch to recent backend. Hope this helps. Cheers, Rolf From bardo1950 at fastwebnet.it Sat Jul 18 08:10:28 2020 From: bardo1950 at fastwebnet.it (valerio) Date: Sat, 18 Jul 2020 09:10:28 +0200 Subject: [sane-devel] Canon Canoscan LiDE 400 support in Slackware In-Reply-To: References: Message-ID: <3f6d86ec-a9ed-6e1e-0a16-7364c7d474f5@fastwebnet.it> hi Alexander and all, Il 17/07/20 17:50, Alexander Pevzner ha scritto: > Hi Valerio, > >>> BTW, Lide 400 known to work via IPP over USB, and in this mode it >>> supports eSCL protocol. >> >> i don't understand > > I'll explain :-) > > There is such a thing, that driverless printing and scanning. > "Driverless" means that device implements vendor-neutral protocol, and > driver is very generic and works with a large class of compatible > devices, regardless of their models and manufacturers. > > Normally, driverless printing and scanning were protocols designed for > network-connected devices. IPP over USB is a technology, that allows to > "speak" with compatible USB devices as if they were connected to the > network. > > IPP over USB requires additional piece of software, the ipp-usb daemon, > which connects to device via USB and exposes it to the network (by > default to localhost only). > > eSCL is a scanning protocol, supported by many devices from many > vendors. It is also known as Apple AirScan. > > Both protocols (IPP over USB and eSCL) are supported by your device. > > You will need ipp-usb daemon, to enable IPP over USB, and sane-escl or > sane-airscan, to utilize eSCL scanning. > > I don't know if somebody tested sane-escl with your device, but > regarding sane-airscan, two independent users reported that it works > with Lide 400. > that scanner has no connection with the net, so they said. but i have solved: i installed again the package i found in http://www.sane-project.org/snapshots/ following the instructions: with no root privilege for ./configure and make, and make install as root. the first time i had done all as root. scanimage -L device `pixma:04A91912_43C82A' is a CANON CanoScan LiDE 400 multi-function peripheral scanimage -V scanimage (sane-backends) 1.0.30-914-g8bdd27d14; backend version 1.0.30 thanks all valerio From paddy-hack at member.fsf.org Tue Jul 21 12:45:17 2020 From: paddy-hack at member.fsf.org (Olaf Meeuwissen) Date: Tue, 21 Jul 2020 20:45:17 +0900 Subject: [sane-devel] [janitorial] Let's release 1.0.31 in August Message-ID: <871rl5xfaq.fsf@member.fsf.org> Hi all, I've been dragging my feet of late. Not just as far as the SANE Project is concerned but in general. For one reason or another I just can't get myself to do much after I get home from work ... :-/ Let's see if I can change that a bit by upping the pressure (on myself) and announce intent to release sane-backend-1.0.31 sometime next month. That would keep us on track for a roughly half-yearly release cycle, not counting security bug fix releases like 1.0.30. In keeping with what's in our `doc/release.txt` (minus a day or two), I would like to proceed along the following timeline 2020-07-21 Kick-off 2020-08-02 Feature Freeze (-> cut release/1.0.31 branch) 2020-08-16 Code Freeze 2020-08-23 Release You can find a milestone for 1.0.31 at https://gitlab.com/sane-project/backends/-/milestones/4 I'll be adding issues fixed and merge requests to be included or already included in the coming weeks and hope to finish that before the feature freeze. Help with that chore is welcome by the way. # FTR, I'll be mostly off-line during the August 12-16 period. Hope this helps, -- Olaf Meeuwissen, LPIC-2 FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Software https://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join From sedat.dilek at gmail.com Tue Jul 21 15:33:35 2020 From: sedat.dilek at gmail.com (Sedat Dilek) Date: Tue, 21 Jul 2020 16:33:35 +0200 Subject: [sane-devel] [janitorial] Let's release 1.0.31 in August In-Reply-To: <871rl5xfaq.fsf@member.fsf.org> References: <871rl5xfaq.fsf@member.fsf.org> Message-ID: On Tue, Jul 21, 2020 at 1:45 PM Olaf Meeuwissen wrote: > > Hi all, > > I've been dragging my feet of late. Not just as far as the SANE Project > is concerned but in general. For one reason or another I just can't get > myself to do much after I get home from work ... :-/ > > Let's see if I can change that a bit by upping the pressure (on myself) > and announce intent to release sane-backend-1.0.31 sometime next month. > That would keep us on track for a roughly half-yearly release cycle, not > counting security bug fix releases like 1.0.30. > > In keeping with what's in our `doc/release.txt` (minus a day or two), I > would like to proceed along the following timeline > > 2020-07-21 Kick-off > 2020-08-02 Feature Freeze (-> cut release/1.0.31 branch) > 2020-08-16 Code Freeze > 2020-08-23 Release > > You can find a milestone for 1.0.31 at > > https://gitlab.com/sane-project/backends/-/milestones/4 > > I'll be adding issues fixed and merge requests to be included or already > included in the coming weeks and hope to finish that before the feature > freeze. Help with that chore is welcome by the way. > > # FTR, I'll be mostly off-line during the August 12-16 period. > > Hope this helps, I am not 100% following this mailing-list, so I can miss fundamental informations. As I had a Canon LIDE 70 I wanted to ask what is the status of support for it? While searching for informations myself: 1. Its man-page [2] points to nirvana. 2. The ChangeLogs file [3] ends with release 1.0.28. Thanks for a feedback in advance. - Sedat - [1] http://www.sane-project.org/lists/sane-backends-cvs.html#S-CANON-LIDE70 [2] http://www.sane-project.org/man/sane-canon_lide70.5.html [3] https://gitlab.com/sane-project/backends/-/tree/master/ChangeLogs [4] https://gitlab.com/sane-project/backends/-/merge_requests/247 From skelband at gmail.com Tue Jul 21 16:05:57 2020 From: skelband at gmail.com (Ralph Little) Date: Tue, 21 Jul 2020 08:05:57 -0700 Subject: [sane-devel] [janitorial] Let's release 1.0.31 in August In-Reply-To: <871rl5xfaq.fsf@member.fsf.org> References: <871rl5xfaq.fsf@member.fsf.org> Message-ID: <12475cf9-1f68-dc54-f38c-86700a556343@gmail.com> Hi, On 2020-07-21 4:45 a.m., Olaf Meeuwissen wrote: > Hi all, > > I've been dragging my feet of late. Not just as far as the SANE Project > is concerned but in general. For one reason or another I just can't get > myself to do much after I get home from work ... :-/ I know just what you mean :( > Let's see if I can change that a bit by upping the pressure (on myself) > and announce intent to release sane-backend-1.0.31 sometime next month. > That would keep us on track for a roughly half-yearly release cycle, not > counting security bug fix releases like 1.0.30. > > In keeping with what's in our `doc/release.txt` (minus a day or two), I > would like to proceed along the following timeline > > 2020-07-21 Kick-off > 2020-08-02 Feature Freeze (-> cut release/1.0.31 branch) I will be away for a few days beginning the week of the 2nd. > 2020-08-16 Code Freeze > 2020-08-23 Release > > You can find a milestone for 1.0.31 at > > https://gitlab.com/sane-project/backends/-/milestones/4 > > I'll be adding issues fixed and merge requests to be included or already > included in the coming weeks and hope to finish that before the feature > freeze. Help with that chore is welcome by the way. I noticed the other day that some changes that I did in the hp5400 backend created a compile warning about an initialization bug. I don't know how I missed that but I will fix it in the next couple of days. Put me down for en_GB translations. I will check in with my daughter on the French translations but don't hold your breath. If someone else would like to take them on, then please feel free. Cheers, Ralph From paddy-hack at member.fsf.org Wed Jul 22 13:12:48 2020 From: paddy-hack at member.fsf.org (Olaf Meeuwissen) Date: Wed, 22 Jul 2020 21:12:48 +0900 Subject: [sane-devel] [janitorial] Let's release 1.0.31 in August In-Reply-To: References: <871rl5xfaq.fsf@member.fsf.org> Message-ID: <87sgdjiw8v.fsf@member.fsf.org> Hi Sedat, Sedat Dilek writes: > On Tue, Jul 21, 2020 at 1:45 PM Olaf Meeuwissen > wrote: >> >> Hi all, >> >> I've been dragging my feet of late. Not just as far as the SANE Project >> is concerned but in general. For one reason or another I just can't get >> myself to do much after I get home from work ... :-/ >> >> Let's see if I can change that a bit by upping the pressure (on myself) >> and announce intent to release sane-backend-1.0.31 sometime next month. >> That would keep us on track for a roughly half-yearly release cycle, not >> counting security bug fix releases like 1.0.30. >> >> In keeping with what's in our `doc/release.txt` (minus a day or two), I >> would like to proceed along the following timeline >> >> 2020-07-21 Kick-off >> 2020-08-02 Feature Freeze (-> cut release/1.0.31 branch) >> 2020-08-16 Code Freeze >> 2020-08-23 Release >> >> You can find a milestone for 1.0.31 at >> >> https://gitlab.com/sane-project/backends/-/milestones/4 >> >> I'll be adding issues fixed and merge requests to be included or already >> included in the coming weeks and hope to finish that before the feature >> freeze. Help with that chore is welcome by the way. >> >> # FTR, I'll be mostly off-line during the August 12-16 period. >> >> Hope this helps, > > I am not 100% following this mailing-list, so I can miss fundamental > informations. > > As I had a Canon LIDE 70 I wanted to ask what is the status of support for it? Support will be added in 1.0.31. It's already mentioned in the NEWS file https://gitlab.com/sane-project/backends/-/blob/master/NEWS > While searching for informations myself: > 1. Its man-page [2] points to nirvana. That's because the backend has not been included in a release yet and is something that we might want to fix. Please submit an issue. > 2. The ChangeLogs file [3] ends with release 1.0.28. Actually, that points to a ChangeLogs *directory*. We decided to stop updating the ChangeLog in the repository itself because `git log` will tell you anyway. Of course that assumes you have cloned the repository but if you haven't, you can check https://gitlab.com/sane-project/backends/-/commits/master Our source tarballs, both release and snapshots, include a generated ChangeLog file though. There's also an issue about this https://gitlab.com/sane-project/backends/-/issues/313 > Thanks for a feedback in advance. > > - Sedat - > > [1] http://www.sane-project.org/lists/sane-backends-cvs.html#S-CANON-LIDE70 > [2] http://www.sane-project.org/man/sane-canon_lide70.5.html > [3] https://gitlab.com/sane-project/backends/-/tree/master/ChangeLogs > [4] https://gitlab.com/sane-project/backends/-/merge_requests/247 As for that last merge request, you want to look at 315 instead (as mentioned at the bottom of the feedback on 247). Hope this helps, -- Olaf Meeuwissen, LPIC-2 FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Software https://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join From ola.andersson at ymail.com Wed Jul 22 15:10:20 2020 From: ola.andersson at ymail.com (Ola Andersson) Date: Wed, 22 Jul 2020 14:10:20 +0000 (UTC) Subject: [sane-devel] Any love for Mac OS 10.15 (Catalina) and a PIXMA-scanner (Canoscan 8800F)? References: <255574007.8327268.1595427020214.ref@mail.yahoo.com> Message-ID: <255574007.8327268.1595427020214@mail.yahoo.com> I would really like to get my old Canoscan 8800F to work with my MacMini Mac OS 10.15.6 Catalina (latest) and when I discovered SANE-Project I was initally very happy since my scanner was on the list of supported devices.  Several days later after trying a bunch of different things, the scanimage command, or XSANE GUI, it just doesn't work. Any help is appreciated! Below is a list of what I have tried, but I suspect this is some form of permission problem with Mac OS >10.13, that has a new security model. For instance developer need to place their software outside of protected folders that are usually available on other OS's. Also as a user you sometimes need to give apps access to folders, disk and other things in the Security control panel. Another thing could be something strange in the USB-communication, or that maybe the OS is marking the scanner as busy with for some reason ( I have no way of finding that out). But theese are just guesses. Things I did: - Installed sane-backends using Brew. Brew is a package manager for Mac OS that also installs any other library that is needed, and it is regularly updated. This particualar package has support for Mac OS 10.15, and installs sane 1.0.30, the very latest version. Source is available at Github and the link to Brew shows what other libraries are installed. libusb for instance. - Some commands work now:  - man sane - man sane-pixma (In the list of supported scanners are my scanner, Canoscan 8800F.) - sane-find-scanner (output pasted below) - sane-find-scanner -v -v (This gives very detailed output about all connected USB-devices, incl my Caonscan 8800F , with same manufacturer and model ID, but not serial number) as the next command. - scanimage -L (gives this output: "device `pixma:04A91901' is a CANON Canoscan 8800F multi-function peripheral - This command doesn't work:  - scanimage --format="jpeg" --progress --output-file="scan1.jpg" --resolution="600" --mode="color" --source="Flatbed" --button-controlled="no" "scanimage: sane_read: Error during device I/O"  - Same result with sudo ifront. Dunno why. - Installed XSANE (also installed with Brew).  - Tried scanning with this program, and I get this error message: "Could not create file: Permission denied.  - I click Close, and get to the gui, click the button "Get preview" and get the error message: "Error during reading: Error under unit I/O)". The wording might differ, since my error messages are in swedish. - Also tried starting xsane in the terminal with sudo xsane, same difference. - Output pasted below. - Tried getting debug-info with theese commands - export SANE_DEBUG_PIXMA=21  - (This logs all USB-communication) - scanimage 2> canonscan8800F.log > test.pnm  - (This tries scanning and creates an error log, pasted below) - Also tried changing settings in the config-file, and also turned them off again located here: /usr/local/Cellar/sane-backends/1.0.30/etc/sane.d/pixma.conf. Some lines that are now commented out again since they don't seem to matter.  - # Dunno what the correct name is for this param, but since my scanner is connected with USB, I don't think it is this: bjnp-timeout=5000 - pixma-timeout=5000 - usb-timeout=5000 - timeout=5000 - # Turned off networking - networking=no - # This is a suggestion from man sane-pixma, can't see it makes any difference. - usb 0x04a9 0x1901 - I have also, per suggestion from man sane-pixma tried this command:  - export SANE_USB_WORKAROUND=1  - Wich doesn't seem to help, so I have run same with a zero in the end.  - Lastly I have also tried installing the installers from this page, they don't work either.  - Mattias Ellert's binary installer packages of sane-backends, the TWAIN SANE interface and related software.  - They are very old (over three years) and seems pretty useless, even with Gimp.  - Also several restarts, uninstalls and reinstalls. - Tried two usb-cables. So, any help or tips or tricks to try or things to check? Appreciate all help! /Ola Here are the outputs:  Output from sane-find-scanner > sane-find-scanner   # sane-find-scanner will now attempt to detect your scanner. If the   # result is different from what you expected, first make sure your   # scanner is powered up and properly connected to your computer.   # No SCSI scanners found. If you expected something different, make sure that   # you have loaded a kernel SCSI driver for your SCSI adapter. found USB scanner (vendor=0x04a9 [Canon], product=0x1901 [CanoScan]) at libusb:020:010 could not fetch string descriptor: Pipe error could not fetch string descriptor: Pipe error   # Your USB scanner was (probably) detected. It may or may not be supported by   # SANE. Try scanimage -L and read the backend's manpage.   # Not checking for parallel port scanners.   # Most Scanners connected to the parallel port or other proprietary ports   # can't be detected by this program.   # You may want to run this program as root to find all devices. Once you   # found the scanner devices, be sure to adjust access permissions as   # necessary. I get the same result with sudo sane-find-scanner. canonscan8800F.log contents This is the content of the created log-file, from 5.2 above. Output format is not set, using pnm as a default.[15:42:34.787160] [sanei_debug] Setting debug level of pixma to 21.[15:42:34.788373] [pixma] pixma is compiled without pthread support.[15:42:34.788782] [pixma] pixma version 0.27.0[15:42:34.791163] [pixma] pixma_collect_devices() found Canoscan 8800F at libusb:020:010[15:42:34.791879] [pixma] WARNING:No serial number[15:42:34.792158] [pixma] pixma_find_scanners() found 1 devices[15:42:39.924269] [pixma] pixma_collect_devices() found Canoscan 8800F at libusb:020:010[15:42:39.925280] [pixma] WARNING:No serial number[15:42:39.925672] [pixma] pixma_open(): Canoscan 8800F[15:42:39.926504] [pixma] OUT  T=5.137 len=16[15:42:39.926541] [pixma]  00000000:ef 20 00 00 00 00 00 00  00 00 00 00 00 00 00 00 [15:42:39.926558] [pixma] [15:42:39.943538] [pixma] IN   T=5.154 len=8[15:42:39.943584] [pixma]  00000000:06 06 00 00 00 00 00 00  [15:42:39.943597] [pixma] [15:42:39.944638] [pixma] Reader task id=11001 (forked)[15:42:39.945097] [pixma] Reader task started[15:42:39.945377] [pixma] [15:42:39.945542] [pixma] pixma_scan(): start[15:42:39.945686] [pixma]   line_size=1914 image_size=1678578 channels=3 depth=8[15:42:39.945826] [pixma]   dpi=75x75 offset=(0,0) dimension=638x877[15:42:39.945965] [pixma]   gamma_table=0x7fb98000ee40 source=0[15:42:39.946103] [pixma]   threshold=127 threshold_curve=0[15:42:39.946242] [pixma]   adf-wait=0[15:42:39.946380] [pixma]   ADF page count: 0[15:42:39.946592] [pixma] WARNING:pixma_write(): count(0) != len(16)[15:42:39.946740] [pixma] OUT  T=5.157 len=-1[15:42:39.946880] [pixma]  00000000:db 20 00 00 00 00 00 00  00 00 00 00 00 00 00 00 [15:42:39.947020] [pixma]   ERROR: EIO[15:42:39.947175] [pixma] [15:42:39.947321] [pixma] WARNING:pixma_write(): count(0) != len(16)[15:42:39.947466] [pixma] OUT  T=5.158 len=-1[15:42:39.947638] [pixma]  00000000:ef 20 00 00 00 00 00 00  00 00 00 00 00 00 00 00 [15:42:39.947813] [pixma]   ERROR: EIO[15:42:39.947989] [pixma] [15:42:39.948163] [pixma] WARNING:abort_session() failed -1[15:42:39.948341] [pixma] pixma_scan() failed EIO[15:42:39.948528] [pixma] read_image():reader task closed the pipe:0 bytes received, 1678578 bytes expected[15:42:39.948519] [pixma] Reader task terminated: EIOscanimage: sane_read: Error during device I/O[15:42:39.949291] [pixma] pixma_close(): Canoscan 8800F Output in terminal from command xsane and also trying to get preview. > xsane [15:54:47.039943] [sanei_debug] Setting debug level of pixma to 21. [15:54:47.039992] [pixma] pixma is compiled without pthread support. [15:54:47.040162] [pixma] pixma version 0.27.0 [15:54:47.042920] [pixma] pixma_collect_devices() found Canoscan 8800F at libusb:020:010 [15:54:47.043776] [pixma] WARNING:No serial number [15:54:47.044083] [pixma] pixma_find_scanners() found 1 devices [15:54:51.347757] [pixma] pixma_collect_devices() found Canoscan 8800F at libusb:020:010 [15:54:51.348781] [pixma] WARNING:No serial number [15:54:51.349463] [pixma] pixma_open(): Canoscan 8800F [15:54:51.350895] [pixma] OUT  T=4.310 len=16 [15:54:51.350915] [pixma]  00000000:ef 20 00 00 00 00 00 00  00 00 00 00 00 00 00 00  [15:54:51.350923] [pixma]  [15:54:51.367958] [pixma] IN   T=4.327 len=8 [15:54:51.367988] [pixma]  00000000:06 06 00 00 00 00 00 00   [15:54:51.367996] [pixma]  [15:55:18.241453] [pixma] Reader task id=39449 (forked) [15:55:18.242043] [pixma] Reader task started [15:55:18.242643] [pixma]  [15:55:18.242898] [pixma] pixma_scan(): start [15:55:18.243131] [pixma]   line_size=1914 image_size=1678578 channels=3 depth=8 [15:55:18.243361] [pixma]   dpi=75x75 offset=(0,0) dimension=638x877 [15:55:18.243624] [pixma]   gamma_table=0x7fdffd021a40 source=0 [15:55:18.243892] [pixma]   threshold=127 threshold_curve=0 [15:55:18.244218] [pixma]   adf-wait=0 [15:55:18.244508] [pixma]   ADF page count: 0 [15:55:18.244884] [pixma] Setting non-blocking mode [15:55:18.244989] [pixma] WARNING:pixma_write(): count(0) != len(16) [15:55:18.245251] [pixma] OUT  T=31.205 len=-1 [15:55:18.245588] [pixma]  00000000:db 20 00 00 00 00 00 00  00 00 00 00 00 00 00 00  [15:55:18.245817] [pixma]   ERROR: EIO [15:55:18.246026] [pixma]  [15:55:18.246278] [pixma] WARNING:pixma_write(): count(0) != len(16) [15:55:18.246493] [pixma] OUT  T=31.206 len=-1 [15:55:18.246749] [pixma]  00000000:ef 20 00 00 00 00 00 00  00 00 00 00 00 00 00 00  [15:55:18.246980] [pixma]   ERROR: EIO [15:55:18.247209] [pixma]  [15:55:18.247461] [pixma] WARNING:abort_session() failed -1 [15:55:18.248018] [pixma] pixma_scan() failed EIO [15:55:18.248328] [pixma] Reader task terminated: EIO [15:55:18.344655] [pixma] read_image():reader task closed the pipe:0 bytes received, 1678578 bytes expected [15:59:25.269328] [pixma] pixma_close(): Canoscan 8800F -------------- next part -------------- An HTML attachment was scrubbed... URL: From kitno455 at gmail.com Fri Jul 24 01:53:02 2020 From: kitno455 at gmail.com (m. allan noah) Date: Thu, 23 Jul 2020 20:53:02 -0400 Subject: [sane-devel] Canon DR-C225 II - black scan In-Reply-To: <20200626203316.ik45i2g4n7zeknu2@nur.localdomain> References: <20200626203316.ik45i2g4n7zeknu2@nur.localdomain> Message-ID: Marek, I'm sorry it has taken me a month to reply, life is a little 'different' these days :) So I have gone back through every email thread I have had about the DR-C225, and do have a set of logs from the windows driver. I will attempt to determine which bit of magic we are missing. It will take me some time, as I am travelling now. If you do not hear from me soon, please feel free to reach out. Also, if you want to study up on rebuilding sane-backends from source in the meantime, we will need it. allan On Fri, Jun 26, 2020 at 4:33 PM Marek wrote: > > Dear developers, > I wonder if you could help me with resolving a problem with Canon > DR-C225 II scanner (canon_dr backend). The output scan is all black. In > 2015 there was a thread on the predecessor of this scanner: DR-C225 > (without 'II'), which suffered from similar problem. Unfortunately that > thread seems to be prematurely abandoned without solving the issue. > I'm attaching a scanimage log for a page scanned in a grayscale mode (for > the color mode the output scan is black as well). > Best regards, > Marek -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand" From threestags at gmail.com Fri Jul 24 07:13:20 2020 From: threestags at gmail.com (Graham) Date: Fri, 24 Jul 2020 16:13:20 +1000 Subject: [sane-devel] Xerox PE220 scanner not detected Message-ID: <6787f96a-5642-944d-e68e-e171319f1e0b@gmail.com> I have not been able to use my scanner with Linux for some years now (it works find with windows).  I am currently using Linux Mint 19. All connections are good, printer is powered and operates normally (except scan). sane-find-scanner found USB scanner (vendor=0x0924 [Xerox], product=0x420f [Xerox WorkCentre PE220 Series]) at libusb:001:004 scanimage -L No scanners were identified. edited file /etc/sane.d/xerox_mfp.conf added #Xerox MFP usb 0x0924 0x420f I suspect it may be a permissions issue but I am unable to resolve. Any ideas please. Cheers Graham From jffry at posteo.net Sun Jul 26 10:35:11 2020 From: jffry at posteo.net (Jeff) Date: Sun, 26 Jul 2020 11:35:11 +0200 Subject: [sane-devel] gscan2pdf v2.8.2 released Message-ID: <521d2138-efc3-bab4-c3ae-bc13f06f3bd5@posteo.net> gscan2pdf - A GUI to produce a multipage PDF or DjVu from a scan. http://gscan2pdf.sourceforge.net/ Five clicks are required to scan several pages and then save all or a selection as a PDF or DjVu file, including metadata if required. gscan2pdf can control regular or sheet-fed (ADF) scanners with SANE via libimage-sane-perl, scanimage or scanadf, and can scan multiple pages at once. It presents a thumbnail view of scanned pages, and permits simple operations such as cropping, rotating and deleting pages. OCR can be used to recognise text in the scans, and the output embedded in the PDF or DjVu. PDF conversion is done by PDF::API2. The resulting document may be saved as a PDF, DjVu, multipage TIFF file, or single page image file. Changelog for 2.8.2: * If previously used font no longer exists, automatically pick another one. * Delete temporary files that fall off the undo buffer. Closes #350 (When delete photos the files in /tmp are not deleted) * Fix reload-recursion-limit problems after device-not-found mini- wizard. Closes Debian bug #965153 ("fails to open device" for Epson NX100) * Update to German translation (thanks to Matthias Sprau) * Update to Ukrainian translation (thanks to Yuri Chornoivan) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From paddy-hack at member.fsf.org Sun Jul 26 13:04:08 2020 From: paddy-hack at member.fsf.org (Olaf Meeuwissen) Date: Sun, 26 Jul 2020 21:04:08 +0900 Subject: [sane-devel] Any love for Mac OS 10.15 (Catalina) and a PIXMA-scanner (Canoscan 8800F)? In-Reply-To: <255574007.8327268.1595427020214@mail.yahoo.com> References: <255574007.8327268.1595427020214.ref@mail.yahoo.com> <255574007.8327268.1595427020214@mail.yahoo.com> Message-ID: <87v9iascsn.fsf@member.fsf.org> Hi Ola, There aren't too many Mac users out here so don't hold your breath. Not a Mac user myself but I'll try to help anyway. TL;DR: Ask the folks who maintain the sane-backends brew packages. Apologies for re-organizing your post a bit. I just find it easier to reply when the significant bits of the logs are inlined. Ola Andersson via sane-devel writes: > I would really like to get my old Canoscan 8800F to work with my > MacMini Mac OS 10.15.6 Catalina (latest) and when I discovered > SANE-Project I was initally very happy since my scanner was on the > list of supported devices. > Several days later after trying a bunch of different things, the > scanimage command, or XSANE GUI, it just doesn't work. Any help is > appreciated! > Below is a list of what I have tried, but I suspect this is some form > of permission problem with Mac OS >10.13, that has a new security > model. For instance developer need to place their software outside of > protected folders that are usually available on other OS's. Also as a > user you sometimes need to give apps access to folders, disk and other > things in the Security control panel. Another thing could be something > strange in the USB-communication, or that maybe the OS is marking the > scanner as busy with for some reason ( I have no way of finding that > out). But theese are just guesses. > Things I did: > > - Installed sane-backends using Brew. Brew is a package manager for > Mac OS that also installs any other library that is needed, and it > is regularly updated. This particualar package has support for Mac > OS 10.15, and installs sane 1.0.30, the very latest version. Source > is available at Github and the link to Brew shows what other > libraries are installed. libusb for instance. If you really think it's an issue with changes to the Mac OS security model, I think you'd be better of talking to the folks that provide the brew packages for sane-backends. They are sure to be more knowledgeable in that area. Most of us hanging out here are using Linux ... > - Some commands work now: > > - man sane > - man sane-pixma (In the list of supported scanners are my scanner, > Canoscan 8800F.) > - sane-find-scanner (output pasted below) > - sane-find-scanner -v -v (This gives very detailed output about > all connected USB-devices, incl my Caonscan 8800F , with same > manufacturer and model ID, but not serial number) as the next > command. > - scanimage -L (gives this output: "device `pixma:04A91901' is a > CANON Canoscan 8800F multi-function peripheral OK, at least scanimage is able to find your device. That's good news. > - This command doesn't work: > > $ scanimage --format="jpeg" --progress --output-file="scan1.jpg" \ > --resolution="600" --mode="color" --source="Flatbed" \ > --button-controlled="no" > scanimage: sane_read: Error during device I/O > > - Same result with sudo ifront. Dunno why. If you get the same results with sudo preprended, it's unlikely to be a permissions issue but then again I don't know anything about how Mac OS handles read/write access to the device. However, there may be something with the set of options you pass. Have you tried scanning with the defaults? That is, have you tried SANE_DEBUG_PIXMA=127 scanimage -o out.pnm 2> out.log and does that produce a good image in out.pnm? If not, we're interested in the out.log file. Oh, you already included that below. Good! > - Installed XSANE(also installed withBrew). > > - Tried scanning with this program, and I get this error message: > "Could not create file: Permission denied. I *think* that's xsane not being able to create its "state" files below $HOME/.sane/xsane/ (or the $HOME/.sane/xsane directory itself). Does that directory exist? Does it have a xsane.rc and/or xsane.mdf and/or a *.drc file that matches your device? > - I click Close, and get to the gui, click the button "Get preview" > and get the error message:"Error during reading: Error under unit > I/O)".The wording might differ, since my error messages are in > swedish. That's probably the same issue you see when using scanimage. > - Tried getting debug-info with these commands > > $ export SANE_DEBUG_PIXMA=21 > $ scanimage > test.pnm > Output format is not set, using pnm as a default. > [15:42:34.787160] [sanei_debug] Setting debug level of pixma to 21. > [15:42:34.788373] [pixma] pixma is compiled without pthread support. > [15:42:34.788782] [pixma] pixma version 0.27.0 > [15:42:34.791163] [pixma] pixma_collect_devices() found Canoscan 8800F at libusb:020:010 > [15:42:34.791879] [pixma] WARNING:No serial number > [15:42:34.792158] [pixma] pixma_find_scanners() found 1 devices > [15:42:39.924269] [pixma] pixma_collect_devices() found Canoscan 8800F at libusb:020:010 > [15:42:39.925280] [pixma] WARNING:No serial number > [15:42:39.925672] [pixma] pixma_open(): Canoscan 8800F > [15:42:39.926504] [pixma] OUT T=5.137 len=16 > [15:42:39.926541] [pixma] 00000000:ef 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > [15:42:39.926558] [pixma] > [15:42:39.943538] [pixma] IN T=5.154 len=8 > [15:42:39.943584] [pixma] 00000000:06 06 00 00 00 00 00 00 > [15:42:39.943597] [pixma] > [15:42:39.944638] [pixma] Reader task id=11001 (forked) > [15:42:39.945097] [pixma] Reader task started > [15:42:39.945377] [pixma] > [15:42:39.945542] [pixma] pixma_scan(): start > [15:42:39.945686] [pixma] line_size=1914 image_size=1678578 channels=3 depth=8 > [15:42:39.945826] [pixma] dpi=75x75 offset=(0,0) dimension=638x877 > [15:42:39.945965] [pixma] gamma_table=0x7fb98000ee40 source=0 > [15:42:39.946103] [pixma] threshold=127 threshold_curve=0 > [15:42:39.946242] [pixma] adf-wait=0 > [15:42:39.946380] [pixma] ADF page count: 0 > [15:42:39.946592] [pixma] WARNING:pixma_write(): count(0) != len(16) This looks like the pixma backend doesn't have write permissions to the device file. I would have expected `sudo` to "fix" this but there may be other, Mac OS specific, access controls at play. Again, I guess the brew folks would be your best bet. They ought to know much more about this than this Linux-only user of two decades and counting ;-) > Output in terminal from command xsane and also trying to get preview. If scanimage doesn't work for some reason, xsane is almost certainly not to work for the same reason. > - Also tried changing settings in the config-file, and also turned > them off again located > here:/usr/local/Cellar/sane-backends/1.0.30/etc/sane.d/pixma.conf. Some > lines that are now commented out again since they don't seem to > matter. > > - # Dunno what the correct name is for this param, but since my > scanner is connected with USB, I don't think it is > this:bjnp-timeout=5000 > - pixma-timeout=5000 > - usb-timeout=5000 > - timeout=5000 > - # Turned off networking > - networking=no As long as you are using USB, the above changes have no effect, AFAIK. > - # This is a suggestion from man sane-pixma, can't see it makes > any difference. > - usb 0x04a9 0x1901 This should not be needed for 1.0.30. The Canoscan8800F has been supported since sane-backends-1.0.21. > - I have also, per suggestion from man sane-pixma tried this command: > > - export SANE_USB_WORKAROUND=1 > - Which doesn't seem to help, so I have run same with a zero in the > end. > > - Lastly I have also tried installing the installers from this > page, they don't work either. > > - Mattias Ellert's binary installer packages of sane-backends, the > TWAIN SANE interface and related software. > - They are very old (over three years) and seems pretty useless, > even with Gimp. Mattias is no longer updating these :-/ > - Also several restarts, uninstalls and reinstalls. > - Tried two usb-cables. Hope this helps, -- Olaf Meeuwissen, LPIC-2 FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Software https://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join From paddy-hack at member.fsf.org Sun Jul 26 13:11:13 2020 From: paddy-hack at member.fsf.org (Olaf Meeuwissen) Date: Sun, 26 Jul 2020 21:11:13 +0900 Subject: [sane-devel] [janitorial] Let's release 1.0.31 in August In-Reply-To: <12475cf9-1f68-dc54-f38c-86700a556343@gmail.com> References: <871rl5xfaq.fsf@member.fsf.org> <12475cf9-1f68-dc54-f38c-86700a556343@gmail.com> Message-ID: <87tuxuscgu.fsf@member.fsf.org> Hi Ralph, Ralph Little writes: > On 2020-07-21 4:45 a.m., Olaf Meeuwissen wrote: >> I'll be adding issues fixed and merge requests to be included or already >> included in the coming weeks and hope to finish that before the feature >> freeze. Help with that chore is welcome by the way. > I noticed the other day that some changes that I did in the hp5400 > backend created a compile warning about an initialization bug. > I don't know how I missed that but I will fix it in the next couple of days. Don't sweat it, master is still without warnings on Debian 10, which is all we really care about (at the moment). Our CI pipeline would have failed if it wasn't. > Put me down for en_GB translations. > I will check in with my daughter on the French translations but don't > hold your breath. > If someone else would like to take them on, then please feel free. Ordissimo submitted !493 which I merged already. But you should have gotten a notification about that as I /cc'd you on the MR. Hope this helps, -- Olaf Meeuwissen, LPIC-2 FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Software https://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join From Ulf.Zibis at gmx.de Mon Jul 27 18:21:30 2020 From: Ulf.Zibis at gmx.de (Ulf Zibis) Date: Mon, 27 Jul 2020 19:21:30 +0200 Subject: [sane-devel] Place for scanner firmware Message-ID: <9f6d999d-cf5a-dd13-5fc5-9ab6ad20c126@gmx.de> Hi all, is there any place on sane web site to share scanner firmware? E.g. for Mustek ScanExpress 1200 UB Plus I could share *SBfw.usb* (got from here: http://www.meier-geinitz.de/sane/gt68xx-backend/) -Ulf -- Von meinem Seibert gesendet -------------- next part -------------- An HTML attachment was scrubbed... URL: From sedat.dilek at gmail.com Mon Jul 27 19:33:47 2020 From: sedat.dilek at gmail.com (Sedat Dilek) Date: Mon, 27 Jul 2020 20:33:47 +0200 Subject: [sane-devel] [janitorial] Let's release 1.0.31 in August In-Reply-To: <87sgdjiw8v.fsf@member.fsf.org> References: <871rl5xfaq.fsf@member.fsf.org> <87sgdjiw8v.fsf@member.fsf.org> Message-ID: On Wed, Jul 22, 2020 at 2:12 PM Olaf Meeuwissen wrote: > > Hi Sedat, > > Sedat Dilek writes: > > > On Tue, Jul 21, 2020 at 1:45 PM Olaf Meeuwissen > > wrote: > >> > >> Hi all, > >> > >> I've been dragging my feet of late. Not just as far as the SANE Project > >> is concerned but in general. For one reason or another I just can't get > >> myself to do much after I get home from work ... :-/ > >> > >> Let's see if I can change that a bit by upping the pressure (on myself) > >> and announce intent to release sane-backend-1.0.31 sometime next month. > >> That would keep us on track for a roughly half-yearly release cycle, not > >> counting security bug fix releases like 1.0.30. > >> > >> In keeping with what's in our `doc/release.txt` (minus a day or two), I > >> would like to proceed along the following timeline > >> > >> 2020-07-21 Kick-off > >> 2020-08-02 Feature Freeze (-> cut release/1.0.31 branch) > >> 2020-08-16 Code Freeze > >> 2020-08-23 Release > >> > >> You can find a milestone for 1.0.31 at > >> > >> https://gitlab.com/sane-project/backends/-/milestones/4 > >> > >> I'll be adding issues fixed and merge requests to be included or already > >> included in the coming weeks and hope to finish that before the feature > >> freeze. Help with that chore is welcome by the way. > >> > >> # FTR, I'll be mostly off-line during the August 12-16 period. > >> > >> Hope this helps, > > > > I am not 100% following this mailing-list, so I can miss fundamental > > informations. > > > > As I had a Canon LIDE 70 I wanted to ask what is the status of support for it? > > Support will be added in 1.0.31. It's already mentioned in the NEWS > file > > https://gitlab.com/sane-project/backends/-/blob/master/NEWS > > > While searching for informations myself: > > 1. Its man-page [2] points to nirvana. > > That's because the backend has not been included in a release yet and is > something that we might want to fix. Please submit an issue. > > > 2. The ChangeLogs file [3] ends with release 1.0.28. > > Actually, that points to a ChangeLogs *directory*. We decided to stop > updating the ChangeLog in the repository itself because `git log` will > tell you anyway. Of course that assumes you have cloned the repository > but if you haven't, you can check > > https://gitlab.com/sane-project/backends/-/commits/master > > Our source tarballs, both release and snapshots, include a generated > ChangeLog file though. > > There's also an issue about this > > https://gitlab.com/sane-project/backends/-/issues/313 > > > Thanks for a feedback in advance. > > > > - Sedat - > > > > [1] http://www.sane-project.org/lists/sane-backends-cvs.html#S-CANON-LIDE70 > > [2] http://www.sane-project.org/man/sane-canon_lide70.5.html > > [3] https://gitlab.com/sane-project/backends/-/tree/master/ChangeLogs > > [4] https://gitlab.com/sane-project/backends/-/merge_requests/247 > > As for that last merge request, you want to look at 315 instead (as > mentioned at the bottom of the feedback on 247). > > Hope this helps, Hi Olaf, Thanks for commenting. Hope you can clarify in the next announcement and/or within SCM (I read ChangeLogs :-)). As said - currently - I have no scanner or a multi-function device w/ printer+scanner. So SANE has not a high priority for me. I should have kept the Canon LIDE 70 scanner - it was fu**ing cool device. Regards, - Sedat - From strredwolf at gmail.com Mon Jul 27 19:39:49 2020 From: strredwolf at gmail.com (Kelly Price) Date: Mon, 27 Jul 2020 14:39:49 -0400 Subject: [sane-devel] [janitorial] Let's release 1.0.31 in August In-Reply-To: References: <871rl5xfaq.fsf@member.fsf.org> <87sgdjiw8v.fsf@member.fsf.org> Message-ID: Can I agree that the Canon LiDE series have been f**king cool? I should get another for mobile work... On Mon, Jul 27, 2020 at 2:33 PM Sedat Dilek wrote: > > On Wed, Jul 22, 2020 at 2:12 PM Olaf Meeuwissen > wrote: > > > > Hi Sedat, > > > > Sedat Dilek writes: > > > > > On Tue, Jul 21, 2020 at 1:45 PM Olaf Meeuwissen > > > wrote: > > >> > > >> Hi all, > > >> > > >> I've been dragging my feet of late. Not just as far as the SANE Project > > >> is concerned but in general. For one reason or another I just can't get > > >> myself to do much after I get home from work ... :-/ > > >> > > >> Let's see if I can change that a bit by upping the pressure (on myself) > > >> and announce intent to release sane-backend-1.0.31 sometime next month. > > >> That would keep us on track for a roughly half-yearly release cycle, not > > >> counting security bug fix releases like 1.0.30. > > >> > > >> In keeping with what's in our `doc/release.txt` (minus a day or two), I > > >> would like to proceed along the following timeline > > >> > > >> 2020-07-21 Kick-off > > >> 2020-08-02 Feature Freeze (-> cut release/1.0.31 branch) > > >> 2020-08-16 Code Freeze > > >> 2020-08-23 Release > > >> > > >> You can find a milestone for 1.0.31 at > > >> > > >> https://gitlab.com/sane-project/backends/-/milestones/4 > > >> > > >> I'll be adding issues fixed and merge requests to be included or already > > >> included in the coming weeks and hope to finish that before the feature > > >> freeze. Help with that chore is welcome by the way. > > >> > > >> # FTR, I'll be mostly off-line during the August 12-16 period. > > >> > > >> Hope this helps, > > > > > > I am not 100% following this mailing-list, so I can miss fundamental > > > informations. > > > > > > As I had a Canon LIDE 70 I wanted to ask what is the status of support for it? > > > > Support will be added in 1.0.31. It's already mentioned in the NEWS > > file > > > > https://gitlab.com/sane-project/backends/-/blob/master/NEWS > > > > > While searching for informations myself: > > > 1. Its man-page [2] points to nirvana. > > > > That's because the backend has not been included in a release yet and is > > something that we might want to fix. Please submit an issue. > > > > > 2. The ChangeLogs file [3] ends with release 1.0.28. > > > > Actually, that points to a ChangeLogs *directory*. We decided to stop > > updating the ChangeLog in the repository itself because `git log` will > > tell you anyway. Of course that assumes you have cloned the repository > > but if you haven't, you can check > > > > https://gitlab.com/sane-project/backends/-/commits/master > > > > Our source tarballs, both release and snapshots, include a generated > > ChangeLog file though. > > > > There's also an issue about this > > > > https://gitlab.com/sane-project/backends/-/issues/313 > > > > > Thanks for a feedback in advance. > > > > > > - Sedat - > > > > > > [1] http://www.sane-project.org/lists/sane-backends-cvs.html#S-CANON-LIDE70 > > > [2] http://www.sane-project.org/man/sane-canon_lide70.5.html > > > [3] https://gitlab.com/sane-project/backends/-/tree/master/ChangeLogs > > > [4] https://gitlab.com/sane-project/backends/-/merge_requests/247 > > > > As for that last merge request, you want to look at 315 instead (as > > mentioned at the bottom of the feedback on 247). > > > > Hope this helps, > > Hi Olaf, > > Thanks for commenting. > Hope you can clarify in the next announcement and/or within SCM (I > read ChangeLogs :-)). > > As said - currently - I have no scanner or a multi-function device w/ > printer+scanner. > So SANE has not a high priority for me. > > I should have kept the Canon LIDE 70 scanner - it was fu**ing cool device. > > Regards, > - Sedat - > -- Kelly "STrRedWolf" Price http://redwolf.ws From paddy-hack at member.fsf.org Tue Jul 28 12:11:32 2020 From: paddy-hack at member.fsf.org (Olaf Meeuwissen) Date: Tue, 28 Jul 2020 20:11:32 +0900 Subject: [sane-devel] Place for scanner firmware In-Reply-To: <9f6d999d-cf5a-dd13-5fc5-9ab6ad20c126@gmx.de> References: <9f6d999d-cf5a-dd13-5fc5-9ab6ad20c126@gmx.de> Message-ID: <87d04frj17.fsf@member.fsf.org> Hi Ulf, Ulf Zibis writes: > is there any place on sane web site to share scanner firmware? > > E.g. for Mustek ScanExpress 1200 UB Plus I could share *SBfw.usb* (got > from here: http://www.meier-geinitz.de/sane/gt68xx-backend/) No. And for a good reason. Most firmware files are extracted from the vendor's Windows and/or Mac drivers. These drivers come with a license and unless that license explicitly allows redistribution of the firmware file (without the rest of the driver), redistributing it is bound to get you into legal trouble. In addition, the SANE Project's web site is published on servers maintained by GitLab.com so we have to abide by their rules as well. Naturally, GitLab.com doesn't want to get into legal trouble itself and requires that you have permission to publish whatever you publish. If you don't have that permission, you run a the risk of getting "kicked out". # I'm paraphrasing from memory. I had a quick look at the page you mentioned and could not find any mention of licenses for the various firmware files ... Definitely going out on a limb there. Hope this helps, -- Olaf Meeuwissen, LPIC-2 FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Software https://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join From Ulf.Zibis at gmx.de Wed Jul 29 11:28:23 2020 From: Ulf.Zibis at gmx.de (Ulf Zibis) Date: Wed, 29 Jul 2020 12:28:23 +0200 Subject: [sane-devel] Place for scanner firmware In-Reply-To: <87zh7id60e.fsf@member.fsf.org> References: <9f6d999d-cf5a-dd13-5fc5-9ab6ad20c126@gmx.de> <87d04frj17.fsf@member.fsf.org> <87zh7id60e.fsf@member.fsf.org> Message-ID: <5914ed28-2c59-d36e-4bb5-56212c51ca48@gmx.de> Hi Olaf, Am 29.07.20 um 11:28 schrieb Olaf Meeuwissen: > Hi Ulf, > > Ulf Zibis writes: > >> Hi Olaf, >> >> Am 28.07.20 um 13:11 schrieb Olaf Meeuwissen: >>> Hi Ulf, >>> >>> Ulf Zibis writes: >>> >>>> is there any place on sane web site to share scanner firmware? >>>> >>>> E.g. for Mustek ScanExpress 1200 UB Plus I could share *SBfw.usb* (got >>>> from here: http://www.meier-geinitz.de/sane/gt68xx-backend/) >>> No. And for a good reason. >>> >>> Most firmware files are extracted from the vendor's Windows and/or Mac >>> drivers. These drivers come with a license and unless that license >>> explicitly allows redistribution of the firmware file (without the rest >>> of the driver), redistributing it is bound to get you into legal >>> trouble. >>> >>> In addition, the SANE Project's web site is published on servers >>> maintained by GitLab.com so we have to abide by their rules as well. >>> Naturally, GitLab.com doesn't want to get into legal trouble itself and >>> requires that you have permission to publish whatever you publish. If >>> you don't have that permission, you run a the risk of getting "kicked >>> out". >>> >>> # I'm paraphrasing from memory. >>> >>> I had a quick look at the page you mentioned and could not find any >>> mention of licenses for the various firmware files ... >>> Definitely going out on a limb there. >>> >>> Hope this helps, >> Thanks for your explanation. >> >> Yes, it's a difficult subject with these licenses. >> >> I would say, if one owns the hardware, he is automatically legal owner >> of the firmware. > I'm afraid that's where you're wrong. At least in the general case. If > firmware files are needed by any SANE backend, it typically means that > it needs to be sent to the device before said device works. As soon as > you power the device off, whatever was sent to the device just sort of > "evaporates" and needs to be sent again. > > This is different from firmware that is preloaded on the device when you > buy it and a SANE backend works without any firmware file. > > If a firmware file came with a vendor provided driver, it is covered by > the license that came with the driver. You normally don't own anything > and just (barely) get the right to use it. > > Hope this helps, I know, that the firmware must be uploaded to the device on every usage. By "owning" I mean, that I have the vendor driver. If for what ever reason I'm missing this driver, I see no legal problem to use a copy of this driver, I get from elsewhere, because I have the license to use it by owning the hardware. The only problem from my point of view is, if "elsewhere" is allowed to share it to me, even if "elsewhere" has no license to use it, particularly if the vendor has no support for re-shipping the driver. -Ulf From kitno455 at gmail.com Thu Jul 30 21:57:16 2020 From: kitno455 at gmail.com (m. allan noah) Date: Thu, 30 Jul 2020 16:57:16 -0400 Subject: [sane-devel] Canon DR-C225 II - black scan In-Reply-To: References: <20200626203316.ik45i2g4n7zeknu2@nur.localdomain> Message-ID: Marek et al- I've spent a couple evenings looking at all the various logs that I have for the C225, and have discovered that it does a different type of fine calibration from other models. So, I've worked up the attached patch, against the current sane-backends sources. The idea is to re-use some of the existing calibration code instead of writing a new version just for this scanner. I expect this may not work, and if it does, it will only give us poor quality images. But, it should be enough to validate that the issue is caused by calibration. You will need to apply this patch to sane-backends source, and rebuild/reinstall. I don't have access to any Canon scanners at this time, so I have only verified that this compiles, unfortunately. Let me know what you find out, or if you need help. allan On Thu, Jul 23, 2020 at 8:53 PM m. allan noah wrote: > > Marek, I'm sorry it has taken me a month to reply, life is a little > 'different' these days :) > > So I have gone back through every email thread I have had about the > DR-C225, and do have a set of logs from the windows driver. I will > attempt to determine which bit of magic we are missing. It will take > me some time, as I am travelling now. If you do not hear from me soon, > please feel free to reach out. Also, if you want to study up on > rebuilding sane-backends from source in the meantime, we will need it. > > allan > > On Fri, Jun 26, 2020 at 4:33 PM Marek wrote: > > > > Dear developers, > > I wonder if you could help me with resolving a problem with Canon > > DR-C225 II scanner (canon_dr backend). The output scan is all black. In > > 2015 there was a thread on the predecessor of this scanner: DR-C225 > > (without 'II'), which suffered from similar problem. Unfortunately that > > thread seems to be prematurely abandoned without solving the issue. > > I'm attaching a scanimage log for a page scanned in a grayscale mode (for > > the color mode the output scan is black as well). > > Best regards, > > Marek > > > > -- > "well, I stand up next to a mountain- and I chop it down with the edge > of my hand" -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand" -------------- next part -------------- A non-text attachment was scrubbed... Name: c225-a.patch Type: text/x-patch Size: 17491 bytes Desc: not available URL: From c.a.cook at quantum-sci.com Fri Jul 3 21:41:06 2020 From: c.a.cook at quantum-sci.com (C. Cook) Date: Fri, 3 Jul 2020 13:41:06 -0700 Subject: [sane-devel] IPV6 Only? Message-ID: <3cf27055-49a7-6d40-a7d5-b0345bbb3169@quantum-sci.com> Just installed saned to a raspberry pi running centos.? When I first started saned.socket it failed with "saned.socket failed to listen on sockets: Address family not supported by protocol". Huh? Turns out it will only start in IPV6 and I have that disabled in the kernel. (sysctl)? When I enabled IPV6 the daemon started fine...? but only on IPV6.? And it's disobeying my directive in net.conf to only listen on localhost, instead listening on *. systemd?? 1?? root?? 43u? IPv6? 12327????? 0t0? TCP *:6566 (LISTEN) Name??????? : sane-backends Version???? : 1.0.24 Release???? : 12.el7 Architecture: armv7hl What am I doing wrong? -------------- next part -------------- An HTML attachment was scrubbed... URL: From juergen.mellinger at t-online.de Sun Jul 5 15:37:58 2020 From: juergen.mellinger at t-online.de (=?utf-8?Q?J=C3=BCrgen_Mellinger?=) Date: Sun, 5 Jul 2020 16:37:58 +0200 Subject: [sane-devel] SANE Color Management In-Reply-To: <5fb9df9b-60a6-dcfc-4a1b-609335b75982@apevzner.com> References: <53470749-426a-bee9-8049-3d5d803db2d6@apevzner.com> <51429722-e807-7582-70f4-f5dd219456c9@apevzner.com> <2C114FF2-E43D-4F18-A6AB-193B3AC628D1@t-online.de> <0981307b-e2ab-20d2-5a15-41f396118b03@apevzner.com> <5fb9df9b-60a6-dcfc-4a1b-609335b75982@apevzner.com> Message-ID: <705A50B4-51FD-44D4-9641-3EB9B9ADF2ED@t-online.de> Hi, many SANE backends provide gamma correction options, but I could not find any information about the default color space in which scan data are being sent to sane_read(). I mean, if there is no custom gamma table used, then a backend should be able to use its knowledge about a scanner?s CCD?s gamma value to transform it into a pre-defined color space, such as sRGB, or linear gamma. If there is no such pre-defined color space, then each and every user will have to determine the correct gamma for their each and every scanner, and perform custom gamma correction just to obtain a reasonable image. From this I suspect that SANE backends indeed transform scanner data into a standard color space. My experience with the genesys backend suggests that it?s linear gamma. But I cannot find any documentation on this issue. Could someone point me to more information on this topic? Thank you, J?rgen From kitno455 at gmail.com Sun Jul 5 19:02:51 2020 From: kitno455 at gmail.com (m. allan noah) Date: Sun, 5 Jul 2020 14:02:51 -0400 Subject: [sane-devel] SANE Color Management In-Reply-To: <705A50B4-51FD-44D4-9641-3EB9B9ADF2ED@t-online.de> References: <53470749-426a-bee9-8049-3d5d803db2d6@apevzner.com> <51429722-e807-7582-70f4-f5dd219456c9@apevzner.com> <2C114FF2-E43D-4F18-A6AB-193B3AC628D1@t-online.de> <0981307b-e2ab-20d2-5a15-41f396118b03@apevzner.com> <5fb9df9b-60a6-dcfc-4a1b-609335b75982@apevzner.com> <705A50B4-51FD-44D4-9641-3EB9B9ADF2ED@t-online.de> Message-ID: I believe that most backends are doing no transformation at all. Since most backends are reverse engineered, I think we consider ourselves lucky just to get image data out of the scanner. If the blacks look black, and the whites look white, we ship it :) allan On Sun, Jul 5, 2020 at 10:38 AM J?rgen Mellinger wrote: > > Hi, > > many SANE backends provide gamma correction options, but I could not find any information about the default color space in which scan data are being sent to sane_read(). I mean, if there is no custom gamma table used, then a backend should be able to use its knowledge about a scanner?s CCD?s gamma value to transform it into a pre-defined color space, such as sRGB, or linear gamma. If there is no such pre-defined color space, then each and every user will have to determine the correct gamma for their each and every scanner, and perform custom gamma correction just to obtain a reasonable image. > > From this I suspect that SANE backends indeed transform scanner data into a standard color space. My experience with the genesys backend suggests that it?s linear gamma. But I cannot find any documentation on this issue. > > Could someone point me to more information on this topic? > > Thank you, > J?rgen -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand" From c.a.cook at quantum-sci.com Tue Jul 7 21:18:26 2020 From: c.a.cook at quantum-sci.com (C. Cook) Date: Tue, 7 Jul 2020 13:18:26 -0700 Subject: [sane-devel] IPV6 Only? In-Reply-To: <3cf27055-49a7-6d40-a7d5-b0345bbb3169@quantum-sci.com> References: <3cf27055-49a7-6d40-a7d5-b0345bbb3169@quantum-sci.com> Message-ID: <22bc12cc-7564-a997-758b-490bbd79a5db@quantum-sci.com> Nothing? Nobody knows why I have IPV6 only? On 2020-07-03 13:41, C. Cook wrote: > > Just installed saned to a raspberry pi running centos.? When I first > started saned.socket it failed with "saned.socket failed to listen on > sockets: Address family not supported by protocol". > > Huh? > > Turns out it will only start in IPV6 and I have that disabled in the > kernel. (sysctl)? When I enabled IPV6 the daemon started fine...? but > only on IPV6.? > > And it's disobeying my directive in net.conf to only listen on > localhost, instead listening on *. > > systemd?? 1?? root?? 43u? IPv6? 12327????? 0t0? TCP *:6566 (LISTEN) > > Name??????? : sane-backends > Version???? : 1.0.24 > Release???? : 12.el7 > Architecture: armv7hl > > What am I doing wrong? > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From simon.matter at invoca.ch Wed Jul 8 07:08:44 2020 From: simon.matter at invoca.ch (Simon Matter) Date: Wed, 8 Jul 2020 08:08:44 +0200 Subject: [sane-devel] IPV6 Only? In-Reply-To: <3cf27055-49a7-6d40-a7d5-b0345bbb3169@quantum-sci.com> References: <3cf27055-49a7-6d40-a7d5-b0345bbb3169@quantum-sci.com> Message-ID: > Just installed saned to a raspberry pi running centos.? When I first > started saned.socket it failed with "saned.socket failed to listen on > sockets: Address family not supported by protocol". > > Huh? > > Turns out it will only start in IPV6 and I have that disabled in the > kernel. (sysctl)? When I enabled IPV6 the daemon started fine...? but > only on IPV6.? > > And it's disobeying my directive in net.conf to only listen on > localhost, instead listening on *. > > systemd?? 1?? root?? 43u? IPv6? 12327????? 0t0? TCP *:6566 (LISTEN) > > Name??????? : sane-backends > Version???? : 1.0.24 > Release???? : 12.el7 > Architecture: armv7hl > > What am I doing wrong? You are using systemd :-) What you see listening is not saned but systemd, that's why it doesn't obey to what you have configured in net.conf. I guess you have to fiddle with the systemd config now. Regards, Simon From louis at fazant.net Thu Jul 9 20:16:13 2020 From: louis at fazant.net (Louis Lagendijk) Date: Thu, 09 Jul 2020 21:16:13 +0200 Subject: [sane-devel] IPV6 Only? In-Reply-To: References: <3cf27055-49a7-6d40-a7d5-b0345bbb3169@quantum-sci.com> Message-ID: On Wed, 2020-07-08 at 08:08 +0200, Simon Matter via sane-devel wrote: > > Just installed saned to a raspberry pi running centos. When I > > first > > started saned.socket it failed with "saned.socket failed to listen > > on > > sockets: Address family not supported by protocol". > > > > Huh? > > > > Turns out it will only start in IPV6 and I have that disabled in > > the > > kernel. (sysctl) When I enabled IPV6 the daemon started fine... > > but > > only on IPV6. > > > > And it's disobeying my directive in net.conf to only listen on > > localhost, instead listening on *. > > > > systemd 1 root 43u IPv6 12327 0t0 TCP *:6566 (LISTEN) > > > > Name : sane-backends > > Version : 1.0.24 > > Release : 12.el7 > > Architecture: armv7hl > > > > What am I doing wrong? > > You are using systemd :-) > > What you see listening is not saned but systemd, that's why it > doesn't > obey to what you have configured in net.conf. > > I guess you have to fiddle with the systemd config now. > > Regards, > Simon > Should be simple: change the ListenStream line in the sample socket file as described in the man-page for saned to: ListenStream=
:6566 that should do the trick /Louis From jffry at posteo.net Sat Jul 11 11:17:28 2020 From: jffry at posteo.net (Jeff) Date: Sat, 11 Jul 2020 12:17:28 +0200 Subject: [sane-devel] gscan2pdf v2.8.1 released Message-ID: <1ab42f34-05dd-2995-06d0-6243efe5fbe4@posteo.net> gscan2pdf - A GUI to produce a multipage PDF or DjVu from a scan. http://gscan2pdf.sourceforge.net/ Five clicks are required to scan several pages and then save all or a selection as a PDF or DjVu file, including metadata if required. gscan2pdf can control regular or sheet-fed (ADF) scanners with SANE via libimage-sane-perl, scanimage or scanadf, and can scan multiple pages at once. It presents a thumbnail view of scanned pages, and permits simple operations such as cropping, rotating and deleting pages. OCR can be used to recognise text in the scans, and the output embedded in the PDF or DjVu. PDF conversion is done by PDF::API2. The resulting document may be saved as a PDF, DjVu, multipage TIFF file, or single page image file. Changelog for 2.8.1: * Pass resolution to tesseract to avoid messages like "Warning! Invalid resolution 0 dpi. Using 70 instead" * Cope better if data model becomes corrupted * + restart option to 'device not found' mini-wizard & if tmp directory changed. * When saving a session file, note that pages have been saved to avoid 'Some pages have not been saved. Do you really want to quit?' message. * Improvements to the Crashed sessions dialog to make it more intuitive. * Update position of OCR text when cropping * Create PS level 3 instead of 1. * Fix check for unpaper version. Closes #285 (Scan fails if unpaper is not installed but selected in post processing) * Fix check for tesseract version. Remove support for tesseract < 3.04.00. * Update to Hungarian translation (thanks to csola) * Update to Brazilian Portuguese translation (thanks to Arthur Rodrigues) * Update to German translation (thanks to Matthias Sprau) * Update to Ukrainian translation (thanks to Yuri Chornoivan) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From paddy-hack at member.fsf.org Sun Jul 12 04:52:55 2020 From: paddy-hack at member.fsf.org (Olaf Meeuwissen) Date: Sun, 12 Jul 2020 12:52:55 +0900 Subject: [sane-devel] SANE Color Management In-Reply-To: References: <53470749-426a-bee9-8049-3d5d803db2d6@apevzner.com> <51429722-e807-7582-70f4-f5dd219456c9@apevzner.com> <2C114FF2-E43D-4F18-A6AB-193B3AC628D1@t-online.de> <0981307b-e2ab-20d2-5a15-41f396118b03@apevzner.com> <5fb9df9b-60a6-dcfc-4a1b-609335b75982@apevzner.com> <705A50B4-51FD-44D4-9641-3EB9B9ADF2ED@t-online.de> Message-ID: <87tuydfkyw.fsf@member.fsf.org> Hi, m. allan noah writes: > I believe that most backends are doing no transformation at all. Since > most backends are reverse engineered, I think we consider ourselves > lucky just to get image data out of the scanner. If the blacks look > black, and the whites look white, we ship it :) Some of us also check the RGBs :-) > On Sun, Jul 5, 2020 at 10:38 AM J?rgen Mellinger > wrote: >> >> Hi, >> >> many SANE backends provide gamma correction options, but I could not >> find any information about the default color space in which scan data >> are being sent to sane_read(). I mean, if there is no custom gamma >> table used, then a backend should be able to use its knowledge about >> a scanner?s CCD?s gamma value to transform it into a pre-defined >> color space, such as sRGB, or linear gamma. If there is no such >> pre-defined color space, then each and every user will have to >> determine the correct gamma for their each and every scanner, and >> perform custom gamma correction just to obtain a reasonable image. >> >> From this I suspect that SANE backends indeed transform scanner data >> into a standard color space. My experience with the genesys backend >> suggests that it?s linear gamma. But I cannot find any documentation >> on this issue. It's backend specific and likely even model specific. I vaguely recall the epson and epson2 backends using a gamma of 2.2 by default. >> Could someone point me to more information on this topic? The best I can think of is the "Image Data Format" section in the SANE Standard at https://sane-project.gitlab.io/standard/environment.html#image-data-format but that doesn't say anything about standard color spaces. Hope this helps, -- Olaf Meeuwissen, LPIC-2 FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Software https://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join From jfdsmit at gmail.com Tue Jul 14 20:45:30 2020 From: jfdsmit at gmail.com (Jens de Smit) Date: Tue, 14 Jul 2020 21:45:30 +0200 Subject: [sane-devel] Canon iSENSYS MF8030Cn support Message-ID: Hello all, I have a Canon MF8030Cn network laser multifunctional that I used under Win10 to scan. I have gotten it to work as a printer under Linux, but SANE does not find the scanner part of the device. If I add the scanner's details to pixma.conf manually I get the following message: [21:34:32.750890] [bjnp] add_scanner: Scanner MF8000 Series is not supported, model is unknown! Please report upstream I see that many other printers in the Canon MF range are supported, so I was hoping to get this one to work as well. Any pointers on where/how I should get started? Best regards, Jens -------------- next part -------------- An HTML attachment was scrubbed... URL: From pzz at apevzner.com Tue Jul 14 21:38:11 2020 From: pzz at apevzner.com (Alexander Pevzner) Date: Tue, 14 Jul 2020 23:38:11 +0300 Subject: [sane-devel] Canon iSENSYS MF8030Cn support In-Reply-To: References: Message-ID: Hi Jens, > I have a Canon MF8030Cn network laser multifunctional?that I used under > Win10 to scan. I have gotten it to work as a printer under Linux, but > SANE does not find the scanner part of the device. If I add the > scanner's details to pixma.conf manually I get the following message: your device may support WSD scan. At this case it will work with the sane-airscan driver: https://github.com/alexpevzner/sane-airscan - project page https://download.opensuse.org/repositories/home:/pzz/ - binary packages for many distros Please let me know if it really works, I'll update a list of supported devices to help other users with the similar printer model. -- Wishes, Alexander Pevzner (pzz at apevzner.com) From bardo1950 at fastwebnet.it Fri Jul 17 11:01:15 2020 From: bardo1950 at fastwebnet.it (valerio) Date: Fri, 17 Jul 2020 12:01:15 +0200 Subject: [sane-devel] Canon Canoscan LiDE 400 support in Slackware In-Reply-To: References: Message-ID: Il 11/01/20 15:00, Rich Shepard ha scritto: > On Sat, 11 Jan 2020, Kelly Price wrote: > >> You fall into the same category I do with my LiDE 220. It somehow just >> doesn't like USB 3.x ports. I think we were working on the issue still. >> Olaf can remind me (as it's early and coffee is just being had here). > > Kelly, > > I recall reading somewhere that the LiDE 400 required USB 3.x ports. And, > when connected to a 3.0 port I could press the 'PDF' button on the front > edge of the scanner, which brought up a simple GUI interface, and was able > to scan a page. So it must accept the USB 3.0 ports when used by itself but > even after adding it to /etc/scan.c/genesis.conf it's not found by > 'scanimage -L'. > hi Rich, i have a canon lide 400 too, just bought... as for you, sane-find-scanner find the scanner, but not scanimage -L my scanner doesn't work, no button works: is normal? with lsusb -t, show this: /: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 10000M /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M |__ Port 1: Dev 4, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 1: Dev 4, If 1, Class=Video, Driver=uvcvideo, 480M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M |__ Port 2: Dev 4, If 0, Class=Hub, Driver=hub/4p, 5000M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 2: Dev 8, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 3: Dev 9, If 0, Class=Vendor Specific Class, Driver=, 480M |__ Port 3: Dev 9, If 1, Class=Vendor Specific Class, Driver=, 480M |__ Port 3: Dev 9, If 2, Class=Vendor Specific Class, Driver=, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/3p, 10000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/9p, 480M |__ Port 9: Dev 3, If 0, Class=Printer, Driver=, 480M |__ Port 9: Dev 3, If 1, Class=Vendor Specific Class, Driver=, 480M |__ Port 9: Dev 3, If 2, Class=Mass Storage, Driver=usb-storage, 480M did you solve your problem? valerio >> As a work-around, I ended up putting this in my PC: >> https://smile.amazon.com/gp/product/B002RL8V7E/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 >> > > Did it solve the problem? > > I don't know about other Canon scanners but the LiDE 400 has no power > switch. It turns on when the USB cable is inserted. > > Regards, > > Rich > > From rolf at bensch-online.de Fri Jul 17 15:43:26 2020 From: rolf at bensch-online.de (Rolf Bensch) Date: Fri, 17 Jul 2020 16:43:26 +0200 Subject: [sane-devel] Canon Canoscan LiDE 400 support in Slackware In-Reply-To: References: Message-ID: <16885b2f-11ce-403d-4f67-c02293b88e56@bensch-online.de> Hi, My LiDE 400 is working with recent SANE version 1.0.30-914-g8bdd27d14. You need at lease SANE version 1.0.28. Please check your installed SANE version with 'scanimage -V'. This scanner has problems working via USB hosts. You need to connect it directly to your computer. And I can scan via USB3. But it's not faster than USB2. It's still connected as USB2 device. Hopr this helps. Cheers, Rolf Am 17.07.20 um 12:01 schrieb valerio: > > > Il 11/01/20 15:00, Rich Shepard ha scritto: >> On Sat, 11 Jan 2020, Kelly Price wrote: >> >>> You fall into the same category I do with my LiDE 220. It somehow just >>> doesn't like USB 3.x ports. I think we were working on the issue still. >>> Olaf can remind me (as it's early and coffee is just being had here). >> >> Kelly, >> >> I recall reading somewhere that the LiDE 400 required USB 3.x ports. >> And, >> when connected to a 3.0 port I could press the 'PDF' button on the front >> edge of the scanner, which brought up a simple GUI interface, and was >> able >> to scan a page. So it must accept the USB 3.0 ports when used by >> itself but >> even after adding it to /etc/scan.c/genesis.conf it's not found by >> 'scanimage -L'. >> > > hi Rich, > i have a canon lide 400 too, just bought... > as for you, sane-find-scanner find the scanner, but not scanimage -L > my scanner doesn't work, no button works: is normal? > > with lsusb -t, show this: > > /:? Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 10000M > /:? Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M > ??? |__ Port 1: Dev 4, If 0, Class=Video, Driver=uvcvideo, 480M > ??? |__ Port 1: Dev 4, If 1, Class=Video, Driver=uvcvideo, 480M > /:? Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M > ??? |__ Port 2: Dev 4, If 0, Class=Hub, Driver=hub/4p, 5000M > /:? Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M > ??? |__ Port 2: Dev 8, If 0, Class=Hub, Driver=hub/4p, 480M > ??????? |__ Port 3: Dev 9, If 0, Class=Vendor Specific Class, Driver=, > 480M > ??????? |__ Port 3: Dev 9, If 1, Class=Vendor Specific Class, Driver=, > 480M > ??????? |__ Port 3: Dev 9, If 2, Class=Vendor Specific Class, Driver=, > 480M > /:? Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/3p, 10000M > /:? Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/9p, 480M > ??? |__ Port 9: Dev 3, If 0, Class=Printer, Driver=, 480M > ??? |__ Port 9: Dev 3, If 1, Class=Vendor Specific Class, Driver=, 480M > ??? |__ Port 9: Dev 3, If 2, Class=Mass Storage, Driver=usb-storage, 480M > > did you solve your problem? > > valerio > > > >>> As a work-around, I ended up putting this in my PC: >>> https://smile.amazon.com/gp/product/B002RL8V7E/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 >>> >> >> Did it solve the problem? >> >> I don't know about other Canon scanners but the LiDE 400 has no power >> switch. It turns on when the USB cable is inserted. >> >> Regards, >> >> Rich >> >> > > From pzz at apevzner.com Fri Jul 17 15:48:00 2020 From: pzz at apevzner.com (Alexander Pevzner) Date: Fri, 17 Jul 2020 17:48:00 +0300 Subject: [sane-devel] Canon Canoscan LiDE 400 support in Slackware In-Reply-To: References: Message-ID: Hi Valerio. May be, I'm missing something, but I don't see something that looks like scanner in your list of devices. May be, something wrong with USB port or cable... BTW, Lide 400 known to work via IPP over USB, and in this mode it supports eSCL protocol. You may try to install the following program for IPP over USB: https://github.com/OpenPrinting/ipp-usb Sorry, there are no Slackware binary packages, but this program is easy to build. After that program is installed, there are chances that it will work with sane-escl, included officially into SANE. If not, there are alternative eSCL/WSD backend, known to work (based on 2 user's reports) with this device: https://github.com/alexpevzner/sane-airscan -- Wishes, Alexander Pevzner (pzz at apevzner.com) From bardo1950 at fastwebnet.it Fri Jul 17 16:21:20 2020 From: bardo1950 at fastwebnet.it (valerio) Date: Fri, 17 Jul 2020 17:21:20 +0200 Subject: [sane-devel] Canon Canoscan LiDE 400 support in Slackware In-Reply-To: <16885b2f-11ce-403d-4f67-c02293b88e56@bensch-online.de> References: <16885b2f-11ce-403d-4f67-c02293b88e56@bensch-online.de> Message-ID: hi Rolf, Il 17/07/20 16:43, Rolf Bensch ha scritto: > Hi, > > My LiDE 400 is working with recent SANE version 1.0.30-914-g8bdd27d14. > You need at lease SANE version 1.0.28. > > Please check your installed SANE version with 'scanimage -V'. root at anarres:~# scanimage -V scanimage (sane-backends) 1.0.30-914-g8bdd27d14; backend version 1.0.27 > > This scanner has problems working via USB hosts. You need to connect it > directly to your computer. And I can scan via USB3. But it's not faster > than USB2. It's still connected as USB2 device. i imagined, but doesn't work > > Hopr this helps. > > Cheers, > Rolf thanks valerio From bardo1950 at fastwebnet.it Fri Jul 17 16:27:25 2020 From: bardo1950 at fastwebnet.it (valerio) Date: Fri, 17 Jul 2020 17:27:25 +0200 Subject: [sane-devel] Canon Canoscan LiDE 400 support in Slackware In-Reply-To: References: Message-ID: Hi Alexander, Il 17/07/20 16:48, Alexander Pevzner ha scritto: > Hi Valerio. > > May be, I'm missing something, but I don't see something that looks like > scanner in your list of devices. May be, something wrong with USB port > or cable... > so: Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 004: ID 1e4e:0102 Cubeternet GL-UPC822 UVC WebCam Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 004: ID 05e3:0616 Genesys Logic, Inc. hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 008: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 03f0:c202 HP, Inc PhotoSmart 8200 series Bus 001 Device 005: ID 04a9:1912 Canon, Inc. LiDE 400 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > BTW, Lide 400 known to work via IPP over USB, and in this mode it > supports eSCL protocol. i don't understand > > You may try to install the following program for IPP over USB: > > ??? https://github.com/OpenPrinting/ipp-usb > > Sorry, there are no Slackware binary packages, but this program is easy > to build. but i have debian... > > After that program is installed, there are chances that it will work > with sane-escl, included officially into SANE. If not, there are > alternative eSCL/WSD backend, known to work (based on 2 user's reports) > with this device: > > ??? https://github.com/alexpevzner/sane-airscan > there is no connector. thanks valerio From pzz at apevzner.com Fri Jul 17 16:31:27 2020 From: pzz at apevzner.com (Alexander Pevzner) Date: Fri, 17 Jul 2020 18:31:27 +0300 Subject: [sane-devel] Canon Canoscan LiDE 400 support in Slackware In-Reply-To: <16885b2f-11ce-403d-4f67-c02293b88e56@bensch-online.de> References: <16885b2f-11ce-403d-4f67-c02293b88e56@bensch-online.de> Message-ID: <019b4046-6f67-b3f9-2e63-d6befda0804d@apevzner.com> Hi Rolf, > This scanner has problems working via USB hosts. You need to connect it > directly to your computer. And I can scan via USB3. But it's not faster > than USB2. It's still connected as USB2 device. AFAIR, this scanner is powered from USB, which implies particular requirements on amount of power that USB port can give away, may be somehow above standards. USB 3.0 ports can give more power, which may make them more reliable with this device. -- Wishes, Alexander Pevzner (pzz at apevzner.com) From sedat.dilek at gmail.com Fri Jul 17 16:39:42 2020 From: sedat.dilek at gmail.com (Sedat Dilek) Date: Fri, 17 Jul 2020 17:39:42 +0200 Subject: [sane-devel] Canon Canoscan LiDE 400 support in Slackware In-Reply-To: References: Message-ID: > BTW, Lide 400 known to work via IPP over USB, and in this mode it > supports eSCL protocol. > > You may try to install the following program for IPP over USB: > > https://github.com/OpenPrinting/ipp-usb > Hi Alexander, thanks for your offer of ipp-usb as an alternative. Can you update the "debian" directory - maybe to reflect the latest 0.9.10 release? Thanks. Regards, - Sedat - [1] https://github.com/OpenPrinting/ipp-usb/releases/tag/0.9.10 [2] https://github.com/OpenPrinting/ipp-usb/tree/0.9.10/debian From pzz at apevzner.com Fri Jul 17 16:50:14 2020 From: pzz at apevzner.com (Alexander Pevzner) Date: Fri, 17 Jul 2020 18:50:14 +0300 Subject: [sane-devel] Canon Canoscan LiDE 400 support in Slackware In-Reply-To: References: Message-ID: Hi Valerio, >> BTW, Lide 400 known to work via IPP over USB, and in this mode it >> supports eSCL protocol. > > i don't understand I'll explain :-) There is such a thing, that driverless printing and scanning. "Driverless" means that device implements vendor-neutral protocol, and driver is very generic and works with a large class of compatible devices, regardless of their models and manufacturers. Normally, driverless printing and scanning were protocols designed for network-connected devices. IPP over USB is a technology, that allows to "speak" with compatible USB devices as if they were connected to the network. IPP over USB requires additional piece of software, the ipp-usb daemon, which connects to device via USB and exposes it to the network (by default to localhost only). eSCL is a scanning protocol, supported by many devices from many vendors. It is also known as Apple AirScan. Both protocols (IPP over USB and eSCL) are supported by your device. You will need ipp-usb daemon, to enable IPP over USB, and sane-escl or sane-airscan, to utilize eSCL scanning. I don't know if somebody tested sane-escl with your device, but regarding sane-airscan, two independent users reported that it works with Lide 400. >> You may try to install the following program for IPP over USB: >> >> ???? https://github.com/OpenPrinting/ipp-usb >> >> Sorry, there are no Slackware binary packages, but this program is >> easy to build. > > but i have debian... I was confused by "Slackware" in the message subject :-) For Debian I provide binary packages for both ipp-usb and sane-airscan: https://download.opensuse.org/repositories/home:/pzz/ -- Wishes, Alexander Pevzner (pzz at apevzner.com) From pzz at apevzner.com Fri Jul 17 16:58:21 2020 From: pzz at apevzner.com (Alexander Pevzner) Date: Fri, 17 Jul 2020 18:58:21 +0300 Subject: [sane-devel] Canon Canoscan LiDE 400 support in Slackware In-Reply-To: References: Message-ID: Hi, Sedat, > Can you update the "debian" directory - maybe to reflect the latest > 0.9.10 release? The content of this directory is hysterical artifact. AFAIK, nobody uses these files directly, they are used only as a template. Debian seems to officially include ipp-usb since the next Debian release. For their official builds, release version will be set properly by their build infrastructure. For packages that I generate by myself (for many distros) setting correct release number is handled automatically by OpenSUSE Build Services: https://download.opensuse.org/repositories/home:/pzz/Debian_10/ -- Wishes, Alexander Pevzner (pzz at apevzner.com) From sedat.dilek at gmail.com Fri Jul 17 17:13:29 2020 From: sedat.dilek at gmail.com (Sedat Dilek) Date: Fri, 17 Jul 2020 18:13:29 +0200 Subject: [sane-devel] Canon Canoscan LiDE 400 support in Slackware In-Reply-To: References: Message-ID: On Fri, Jul 17, 2020 at 5:58 PM Alexander Pevzner wrote: > > Hi, Sedat, > > > Can you update the "debian" directory - maybe to reflect the latest > 0.9.10 release? > The content of this directory is hysterical artifact. AFAIK, nobody uses > these files directly, they are used only as a template. > You mean hysterical or historical :-)... > Debian seems to officially include ipp-usb since the next Debian > release. For their official builds, release version will be set properly > by their build infrastructure. > OK, I see Debian/unstable offers as an installation candidate: root at iniza:~# LC_ALL=C apt-cache policy ipp-usb ipp-usb: Installed: (none) Candidate: 0.9.10-1 Version table: 0.9.10-1 99 99 https://incoming.debian.org/debian-buildd buildd-unstable/main amd64 Packages 99 http://ftp.debian.org/debian unstable/main amd64 Packages 99 https://deb.debian.org/debian unstable/main amd64 Packages Hmm, the available sane and libsane (no version 1.0.28) are not suitable: root at iniza:~# LC_ALL=C apt-cache policy sane sane: Installed: (none) Candidate: 1.0.14-15 Version table: 1.0.14-15 500 500 http://ftp.debian.org/debian testing/main amd64 Packages 500 https://deb.debian.org/debian testing/main amd64 Packages 99 http://ftp.debian.org/debian unstable/main amd64 Packages 99 https://deb.debian.org/debian unstable/main amd64 Packages root at iniza:~# LC_ALL=C apt-cache policy libsane libsane: Installed: 1.0.27-3.2+b1 Candidate: 1.0.27-3.2+b1 Version table: *** 1.0.27-3.2+b1 500 500 http://ftp.debian.org/debian testing/main amd64 Packages 500 https://deb.debian.org/debian testing/main amd64 Packages 99 http://ftp.debian.org/debian unstable/main amd64 Packages 99 https://deb.debian.org/debian unstable/main amd64 Packages 100 /var/lib/dpkg/status - Sedat - > For packages that I generate by myself (for many distros) setting > correct release number is handled automatically by OpenSUSE Build Services: > > https://download.opensuse.org/repositories/home:/pzz/Debian_10/ > Ah, cool. Thanks. - Sedat - From pzz at apevzner.com Fri Jul 17 17:34:48 2020 From: pzz at apevzner.com (Alexander Pevzner) Date: Fri, 17 Jul 2020 19:34:48 +0300 Subject: [sane-devel] Canon Canoscan LiDE 400 support in Slackware In-Reply-To: References: Message-ID: <6d1fe675-64c8-1b79-2e34-e32ccb2288ab@apevzner.com> > You mean hysterical or historical :-)... Seems that I should more carefully check after spellchecker :-) -- Wishes, Alexander Pevzner (pzz at apevzner.com) From rolf at bensch-online.de Fri Jul 17 19:51:34 2020 From: rolf at bensch-online.de (Rolf Bensch) Date: Fri, 17 Jul 2020 20:51:34 +0200 Subject: [sane-devel] Canon Canoscan LiDE 400 support in Slackware In-Reply-To: References: <16885b2f-11ce-403d-4f67-c02293b88e56@bensch-online.de> Message-ID: Hi Valerio, Am 17.07.20 um 17:21 schrieb valerio: > [...] > > root at anarres:~# scanimage -V > scanimage (sane-backends) 1.0.30-914-g8bdd27d14; backend version 1.0.27 > > [...] I can see your problem. You have a mixed SANE installation: Recent frontend but ancient backend. If you've installed SANE from source, however please follow "2.3.1. SANE library" in INSTALL.linux from your sources folder or from here: http://www.sane-project.org/docs.html . Then you should be able to switch to recent backend. Hope this helps. Cheers, Rolf From bardo1950 at fastwebnet.it Sat Jul 18 08:10:28 2020 From: bardo1950 at fastwebnet.it (valerio) Date: Sat, 18 Jul 2020 09:10:28 +0200 Subject: [sane-devel] Canon Canoscan LiDE 400 support in Slackware In-Reply-To: References: Message-ID: <3f6d86ec-a9ed-6e1e-0a16-7364c7d474f5@fastwebnet.it> hi Alexander and all, Il 17/07/20 17:50, Alexander Pevzner ha scritto: > Hi Valerio, > >>> BTW, Lide 400 known to work via IPP over USB, and in this mode it >>> supports eSCL protocol. >> >> i don't understand > > I'll explain :-) > > There is such a thing, that driverless printing and scanning. > "Driverless" means that device implements vendor-neutral protocol, and > driver is very generic and works with a large class of compatible > devices, regardless of their models and manufacturers. > > Normally, driverless printing and scanning were protocols designed for > network-connected devices. IPP over USB is a technology, that allows to > "speak" with compatible USB devices as if they were connected to the > network. > > IPP over USB requires additional piece of software, the ipp-usb daemon, > which connects to device via USB and exposes it to the network (by > default to localhost only). > > eSCL is a scanning protocol, supported by many devices from many > vendors. It is also known as Apple AirScan. > > Both protocols (IPP over USB and eSCL) are supported by your device. > > You will need ipp-usb daemon, to enable IPP over USB, and sane-escl or > sane-airscan, to utilize eSCL scanning. > > I don't know if somebody tested sane-escl with your device, but > regarding sane-airscan, two independent users reported that it works > with Lide 400. > that scanner has no connection with the net, so they said. but i have solved: i installed again the package i found in http://www.sane-project.org/snapshots/ following the instructions: with no root privilege for ./configure and make, and make install as root. the first time i had done all as root. scanimage -L device `pixma:04A91912_43C82A' is a CANON CanoScan LiDE 400 multi-function peripheral scanimage -V scanimage (sane-backends) 1.0.30-914-g8bdd27d14; backend version 1.0.30 thanks all valerio From paddy-hack at member.fsf.org Tue Jul 21 12:45:17 2020 From: paddy-hack at member.fsf.org (Olaf Meeuwissen) Date: Tue, 21 Jul 2020 20:45:17 +0900 Subject: [sane-devel] [janitorial] Let's release 1.0.31 in August Message-ID: <871rl5xfaq.fsf@member.fsf.org> Hi all, I've been dragging my feet of late. Not just as far as the SANE Project is concerned but in general. For one reason or another I just can't get myself to do much after I get home from work ... :-/ Let's see if I can change that a bit by upping the pressure (on myself) and announce intent to release sane-backend-1.0.31 sometime next month. That would keep us on track for a roughly half-yearly release cycle, not counting security bug fix releases like 1.0.30. In keeping with what's in our `doc/release.txt` (minus a day or two), I would like to proceed along the following timeline 2020-07-21 Kick-off 2020-08-02 Feature Freeze (-> cut release/1.0.31 branch) 2020-08-16 Code Freeze 2020-08-23 Release You can find a milestone for 1.0.31 at https://gitlab.com/sane-project/backends/-/milestones/4 I'll be adding issues fixed and merge requests to be included or already included in the coming weeks and hope to finish that before the feature freeze. Help with that chore is welcome by the way. # FTR, I'll be mostly off-line during the August 12-16 period. Hope this helps, -- Olaf Meeuwissen, LPIC-2 FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Software https://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join From sedat.dilek at gmail.com Tue Jul 21 15:33:35 2020 From: sedat.dilek at gmail.com (Sedat Dilek) Date: Tue, 21 Jul 2020 16:33:35 +0200 Subject: [sane-devel] [janitorial] Let's release 1.0.31 in August In-Reply-To: <871rl5xfaq.fsf@member.fsf.org> References: <871rl5xfaq.fsf@member.fsf.org> Message-ID: On Tue, Jul 21, 2020 at 1:45 PM Olaf Meeuwissen wrote: > > Hi all, > > I've been dragging my feet of late. Not just as far as the SANE Project > is concerned but in general. For one reason or another I just can't get > myself to do much after I get home from work ... :-/ > > Let's see if I can change that a bit by upping the pressure (on myself) > and announce intent to release sane-backend-1.0.31 sometime next month. > That would keep us on track for a roughly half-yearly release cycle, not > counting security bug fix releases like 1.0.30. > > In keeping with what's in our `doc/release.txt` (minus a day or two), I > would like to proceed along the following timeline > > 2020-07-21 Kick-off > 2020-08-02 Feature Freeze (-> cut release/1.0.31 branch) > 2020-08-16 Code Freeze > 2020-08-23 Release > > You can find a milestone for 1.0.31 at > > https://gitlab.com/sane-project/backends/-/milestones/4 > > I'll be adding issues fixed and merge requests to be included or already > included in the coming weeks and hope to finish that before the feature > freeze. Help with that chore is welcome by the way. > > # FTR, I'll be mostly off-line during the August 12-16 period. > > Hope this helps, I am not 100% following this mailing-list, so I can miss fundamental informations. As I had a Canon LIDE 70 I wanted to ask what is the status of support for it? While searching for informations myself: 1. Its man-page [2] points to nirvana. 2. The ChangeLogs file [3] ends with release 1.0.28. Thanks for a feedback in advance. - Sedat - [1] http://www.sane-project.org/lists/sane-backends-cvs.html#S-CANON-LIDE70 [2] http://www.sane-project.org/man/sane-canon_lide70.5.html [3] https://gitlab.com/sane-project/backends/-/tree/master/ChangeLogs [4] https://gitlab.com/sane-project/backends/-/merge_requests/247 From skelband at gmail.com Tue Jul 21 16:05:57 2020 From: skelband at gmail.com (Ralph Little) Date: Tue, 21 Jul 2020 08:05:57 -0700 Subject: [sane-devel] [janitorial] Let's release 1.0.31 in August In-Reply-To: <871rl5xfaq.fsf@member.fsf.org> References: <871rl5xfaq.fsf@member.fsf.org> Message-ID: <12475cf9-1f68-dc54-f38c-86700a556343@gmail.com> Hi, On 2020-07-21 4:45 a.m., Olaf Meeuwissen wrote: > Hi all, > > I've been dragging my feet of late. Not just as far as the SANE Project > is concerned but in general. For one reason or another I just can't get > myself to do much after I get home from work ... :-/ I know just what you mean :( > Let's see if I can change that a bit by upping the pressure (on myself) > and announce intent to release sane-backend-1.0.31 sometime next month. > That would keep us on track for a roughly half-yearly release cycle, not > counting security bug fix releases like 1.0.30. > > In keeping with what's in our `doc/release.txt` (minus a day or two), I > would like to proceed along the following timeline > > 2020-07-21 Kick-off > 2020-08-02 Feature Freeze (-> cut release/1.0.31 branch) I will be away for a few days beginning the week of the 2nd. > 2020-08-16 Code Freeze > 2020-08-23 Release > > You can find a milestone for 1.0.31 at > > https://gitlab.com/sane-project/backends/-/milestones/4 > > I'll be adding issues fixed and merge requests to be included or already > included in the coming weeks and hope to finish that before the feature > freeze. Help with that chore is welcome by the way. I noticed the other day that some changes that I did in the hp5400 backend created a compile warning about an initialization bug. I don't know how I missed that but I will fix it in the next couple of days. Put me down for en_GB translations. I will check in with my daughter on the French translations but don't hold your breath. If someone else would like to take them on, then please feel free. Cheers, Ralph From paddy-hack at member.fsf.org Wed Jul 22 13:12:48 2020 From: paddy-hack at member.fsf.org (Olaf Meeuwissen) Date: Wed, 22 Jul 2020 21:12:48 +0900 Subject: [sane-devel] [janitorial] Let's release 1.0.31 in August In-Reply-To: References: <871rl5xfaq.fsf@member.fsf.org> Message-ID: <87sgdjiw8v.fsf@member.fsf.org> Hi Sedat, Sedat Dilek writes: > On Tue, Jul 21, 2020 at 1:45 PM Olaf Meeuwissen > wrote: >> >> Hi all, >> >> I've been dragging my feet of late. Not just as far as the SANE Project >> is concerned but in general. For one reason or another I just can't get >> myself to do much after I get home from work ... :-/ >> >> Let's see if I can change that a bit by upping the pressure (on myself) >> and announce intent to release sane-backend-1.0.31 sometime next month. >> That would keep us on track for a roughly half-yearly release cycle, not >> counting security bug fix releases like 1.0.30. >> >> In keeping with what's in our `doc/release.txt` (minus a day or two), I >> would like to proceed along the following timeline >> >> 2020-07-21 Kick-off >> 2020-08-02 Feature Freeze (-> cut release/1.0.31 branch) >> 2020-08-16 Code Freeze >> 2020-08-23 Release >> >> You can find a milestone for 1.0.31 at >> >> https://gitlab.com/sane-project/backends/-/milestones/4 >> >> I'll be adding issues fixed and merge requests to be included or already >> included in the coming weeks and hope to finish that before the feature >> freeze. Help with that chore is welcome by the way. >> >> # FTR, I'll be mostly off-line during the August 12-16 period. >> >> Hope this helps, > > I am not 100% following this mailing-list, so I can miss fundamental > informations. > > As I had a Canon LIDE 70 I wanted to ask what is the status of support for it? Support will be added in 1.0.31. It's already mentioned in the NEWS file https://gitlab.com/sane-project/backends/-/blob/master/NEWS > While searching for informations myself: > 1. Its man-page [2] points to nirvana. That's because the backend has not been included in a release yet and is something that we might want to fix. Please submit an issue. > 2. The ChangeLogs file [3] ends with release 1.0.28. Actually, that points to a ChangeLogs *directory*. We decided to stop updating the ChangeLog in the repository itself because `git log` will tell you anyway. Of course that assumes you have cloned the repository but if you haven't, you can check https://gitlab.com/sane-project/backends/-/commits/master Our source tarballs, both release and snapshots, include a generated ChangeLog file though. There's also an issue about this https://gitlab.com/sane-project/backends/-/issues/313 > Thanks for a feedback in advance. > > - Sedat - > > [1] http://www.sane-project.org/lists/sane-backends-cvs.html#S-CANON-LIDE70 > [2] http://www.sane-project.org/man/sane-canon_lide70.5.html > [3] https://gitlab.com/sane-project/backends/-/tree/master/ChangeLogs > [4] https://gitlab.com/sane-project/backends/-/merge_requests/247 As for that last merge request, you want to look at 315 instead (as mentioned at the bottom of the feedback on 247). Hope this helps, -- Olaf Meeuwissen, LPIC-2 FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Software https://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join From ola.andersson at ymail.com Wed Jul 22 15:10:20 2020 From: ola.andersson at ymail.com (Ola Andersson) Date: Wed, 22 Jul 2020 14:10:20 +0000 (UTC) Subject: [sane-devel] Any love for Mac OS 10.15 (Catalina) and a PIXMA-scanner (Canoscan 8800F)? References: <255574007.8327268.1595427020214.ref@mail.yahoo.com> Message-ID: <255574007.8327268.1595427020214@mail.yahoo.com> I would really like to get my old Canoscan 8800F to work with my MacMini Mac OS 10.15.6 Catalina (latest) and when I discovered SANE-Project I was initally very happy since my scanner was on the list of supported devices.? Several days later after trying a bunch of different things, the scanimage command, or XSANE GUI, it just doesn't work. Any help is appreciated! Below is a list of what I have tried, but I suspect this is some form of permission problem with Mac OS >10.13, that has a new security model. For instance developer need to place their software outside of protected folders that are usually available on other OS's. Also as a user you sometimes need to give apps access to folders, disk and other things in the Security control panel. Another thing could be something strange in the USB-communication, or that maybe the OS is marking the scanner as busy with for some reason ( I have no way of finding that out). But theese are just guesses. Things I did: - Installed sane-backends using Brew. Brew is a package manager for Mac OS that also installs any other library that is needed, and it is regularly updated. This particualar package has support for Mac OS 10.15, and installs sane 1.0.30, the very latest version. Source is available at Github and the link to Brew shows what other libraries are installed. libusb for instance. - Some commands work now:? - man sane - man sane-pixma (In the list of supported scanners are my scanner, Canoscan 8800F.) - sane-find-scanner (output pasted below) - sane-find-scanner -v -v (This gives very detailed output about all connected USB-devices, incl my Caonscan 8800F , with same manufacturer and model ID, but not serial number) as the next command. - scanimage -L (gives this output: "device `pixma:04A91901' is a CANON Canoscan 8800F multi-function peripheral - This command doesn't work:? - scanimage --format="jpeg" --progress --output-file="scan1.jpg" --resolution="600" --mode="color" --source="Flatbed" --button-controlled="no" "scanimage: sane_read: Error during device I/O"? - Same result with sudo ifront. Dunno why. - Installed XSANE?(also installed with?Brew).? - Tried scanning with this program, and I get this?error message: "Could not create file: Permission denied.? - I click Close, and get to the gui, click the button "Get preview" and get the error message:?"Error during reading: Error under unit I/O)".?The wording might differ, since my error messages are in swedish. - Also tried starting xsane in the terminal with sudo xsane, same difference. - Output pasted below. - Tried getting debug-info with theese commands - export SANE_DEBUG_PIXMA=21? - (This logs all USB-communication) - scanimage 2> canonscan8800F.log > test.pnm? - (This tries scanning and creates an error log, pasted below) - Also tried changing settings in the config-file, and also turned them off again located here:?/usr/local/Cellar/sane-backends/1.0.30/etc/sane.d/pixma.conf. Some lines that are now commented out again since they don't seem to matter.? - # Dunno what the correct name is for this param, but since my scanner is connected with USB, I don't think it is this:?bjnp-timeout=5000 - pixma-timeout=5000 - usb-timeout=5000 - timeout=5000 - # Turned off networking - networking=no - # This is a suggestion from man sane-pixma, can't see it makes any difference. - usb 0x04a9 0x1901 - I have also, per suggestion from man sane-pixma tried this command:? - export SANE_USB_WORKAROUND=1? - Wich doesn't seem to help, so I have run same with a zero in the end.? - Lastly I have also tried installing the installers from this page, they don't work either.? - Mattias Ellert's?binary installer packages?of sane-backends, the TWAIN SANE interface and related software.? - They are very old (over three years) and seems pretty useless, even with Gimp.? - Also several restarts, uninstalls and reinstalls. - Tried two usb-cables. So, any help or tips or tricks to try or things to check? Appreciate all help! /Ola Here are the outputs:? Output from sane-find-scanner > sane-find-scanner ? # sane-find-scanner will now attempt to detect your scanner. If the ? # result is different from what you expected, first make sure your ? # scanner is powered up and properly connected to your computer. ? # No SCSI scanners found. If you expected something different, make sure that ? # you have loaded a kernel SCSI driver for your SCSI adapter. found USB scanner (vendor=0x04a9 [Canon], product=0x1901 [CanoScan]) at libusb:020:010 could not fetch string descriptor: Pipe error could not fetch string descriptor: Pipe error ? # Your USB scanner was (probably) detected. It may or may not be supported by ? # SANE. Try scanimage -L and read the backend's manpage. ? # Not checking for parallel port scanners. ? # Most Scanners connected to the parallel port or other proprietary ports ? # can't be detected by this program. ? # You may want to run this program as root to find all devices. Once you ? # found the scanner devices, be sure to adjust access permissions as ? # necessary. I get the same result with sudo sane-find-scanner. canonscan8800F.log contents This is the content of the created log-file, from 5.2 above. Output format is not set, using pnm as a default.[15:42:34.787160] [sanei_debug] Setting debug level of pixma to 21.[15:42:34.788373] [pixma] pixma is compiled without pthread support.[15:42:34.788782] [pixma] pixma version 0.27.0[15:42:34.791163] [pixma] pixma_collect_devices() found Canoscan 8800F at libusb:020:010[15:42:34.791879] [pixma] WARNING:No serial number[15:42:34.792158] [pixma] pixma_find_scanners() found 1 devices[15:42:39.924269] [pixma] pixma_collect_devices() found Canoscan 8800F at libusb:020:010[15:42:39.925280] [pixma] WARNING:No serial number[15:42:39.925672] [pixma] pixma_open(): Canoscan 8800F[15:42:39.926504] [pixma] OUT? T=5.137 len=16[15:42:39.926541] [pixma]? 00000000:ef 20 00 00 00 00 00 00? 00 00 00 00 00 00 00 00?[15:42:39.926558] [pixma]?[15:42:39.943538] [pixma] IN? ?T=5.154 len=8[15:42:39.943584] [pixma]? 00000000:06 06 00 00 00 00 00 00??[15:42:39.943597] [pixma]?[15:42:39.944638] [pixma] Reader task id=11001 (forked)[15:42:39.945097] [pixma] Reader task started[15:42:39.945377] [pixma]?[15:42:39.945542] [pixma] pixma_scan(): start[15:42:39.945686] [pixma]? ?line_size=1914 image_size=1678578 channels=3 depth=8[15:42:39.945826] [pixma]? ?dpi=75x75 offset=(0,0) dimension=638x877[15:42:39.945965] [pixma]? ?gamma_table=0x7fb98000ee40 source=0[15:42:39.946103] [pixma]? ?threshold=127 threshold_curve=0[15:42:39.946242] [pixma]? ?adf-wait=0[15:42:39.946380] [pixma]? ?ADF page count: 0[15:42:39.946592] [pixma] WARNING:pixma_write(): count(0) != len(16)[15:42:39.946740] [pixma] OUT? T=5.157 len=-1[15:42:39.946880] [pixma]? 00000000:db 20 00 00 00 00 00 00? 00 00 00 00 00 00 00 00?[15:42:39.947020] [pixma]? ?ERROR: EIO[15:42:39.947175] [pixma]?[15:42:39.947321] [pixma] WARNING:pixma_write(): count(0) != len(16)[15:42:39.947466] [pixma] OUT? T=5.158 len=-1[15:42:39.947638] [pixma]? 00000000:ef 20 00 00 00 00 00 00? 00 00 00 00 00 00 00 00?[15:42:39.947813] [pixma]? ?ERROR: EIO[15:42:39.947989] [pixma]?[15:42:39.948163] [pixma] WARNING:abort_session() failed -1[15:42:39.948341] [pixma] pixma_scan() failed EIO[15:42:39.948528] [pixma] read_image():reader task closed the pipe:0 bytes received, 1678578 bytes expected[15:42:39.948519] [pixma] Reader task terminated: EIOscanimage: sane_read: Error during device I/O[15:42:39.949291] [pixma] pixma_close(): Canoscan 8800F Output in terminal from command xsane and also trying to get preview. > xsane [15:54:47.039943] [sanei_debug] Setting debug level of pixma to 21. [15:54:47.039992] [pixma] pixma is compiled without pthread support. [15:54:47.040162] [pixma] pixma version 0.27.0 [15:54:47.042920] [pixma] pixma_collect_devices() found Canoscan 8800F at libusb:020:010 [15:54:47.043776] [pixma] WARNING:No serial number [15:54:47.044083] [pixma] pixma_find_scanners() found 1 devices [15:54:51.347757] [pixma] pixma_collect_devices() found Canoscan 8800F at libusb:020:010 [15:54:51.348781] [pixma] WARNING:No serial number [15:54:51.349463] [pixma] pixma_open(): Canoscan 8800F [15:54:51.350895] [pixma] OUT? T=4.310 len=16 [15:54:51.350915] [pixma]? 00000000:ef 20 00 00 00 00 00 00? 00 00 00 00 00 00 00 00? [15:54:51.350923] [pixma]? [15:54:51.367958] [pixma] IN ? T=4.327 len=8 [15:54:51.367988] [pixma]? 00000000:06 06 00 00 00 00 00 00 ? [15:54:51.367996] [pixma]? [15:55:18.241453] [pixma] Reader task id=39449 (forked) [15:55:18.242043] [pixma] Reader task started [15:55:18.242643] [pixma]? [15:55:18.242898] [pixma] pixma_scan(): start [15:55:18.243131] [pixma] ? line_size=1914 image_size=1678578 channels=3 depth=8 [15:55:18.243361] [pixma] ? dpi=75x75 offset=(0,0) dimension=638x877 [15:55:18.243624] [pixma] ? gamma_table=0x7fdffd021a40 source=0 [15:55:18.243892] [pixma] ? threshold=127 threshold_curve=0 [15:55:18.244218] [pixma] ? adf-wait=0 [15:55:18.244508] [pixma] ? ADF page count: 0 [15:55:18.244884] [pixma] Setting non-blocking mode [15:55:18.244989] [pixma] WARNING:pixma_write(): count(0) != len(16) [15:55:18.245251] [pixma] OUT? T=31.205 len=-1 [15:55:18.245588] [pixma]? 00000000:db 20 00 00 00 00 00 00? 00 00 00 00 00 00 00 00? [15:55:18.245817] [pixma] ? ERROR: EIO [15:55:18.246026] [pixma]? [15:55:18.246278] [pixma] WARNING:pixma_write(): count(0) != len(16) [15:55:18.246493] [pixma] OUT? T=31.206 len=-1 [15:55:18.246749] [pixma]? 00000000:ef 20 00 00 00 00 00 00? 00 00 00 00 00 00 00 00? [15:55:18.246980] [pixma] ? ERROR: EIO [15:55:18.247209] [pixma]? [15:55:18.247461] [pixma] WARNING:abort_session() failed -1 [15:55:18.248018] [pixma] pixma_scan() failed EIO [15:55:18.248328] [pixma] Reader task terminated: EIO [15:55:18.344655] [pixma] read_image():reader task closed the pipe:0 bytes received, 1678578 bytes expected [15:59:25.269328] [pixma] pixma_close(): Canoscan 8800F -------------- next part -------------- An HTML attachment was scrubbed... URL: From kitno455 at gmail.com Fri Jul 24 01:53:02 2020 From: kitno455 at gmail.com (m. allan noah) Date: Thu, 23 Jul 2020 20:53:02 -0400 Subject: [sane-devel] Canon DR-C225 II - black scan In-Reply-To: <20200626203316.ik45i2g4n7zeknu2@nur.localdomain> References: <20200626203316.ik45i2g4n7zeknu2@nur.localdomain> Message-ID: Marek, I'm sorry it has taken me a month to reply, life is a little 'different' these days :) So I have gone back through every email thread I have had about the DR-C225, and do have a set of logs from the windows driver. I will attempt to determine which bit of magic we are missing. It will take me some time, as I am travelling now. If you do not hear from me soon, please feel free to reach out. Also, if you want to study up on rebuilding sane-backends from source in the meantime, we will need it. allan On Fri, Jun 26, 2020 at 4:33 PM Marek wrote: > > Dear developers, > I wonder if you could help me with resolving a problem with Canon > DR-C225 II scanner (canon_dr backend). The output scan is all black. In > 2015 there was a thread on the predecessor of this scanner: DR-C225 > (without 'II'), which suffered from similar problem. Unfortunately that > thread seems to be prematurely abandoned without solving the issue. > I'm attaching a scanimage log for a page scanned in a grayscale mode (for > the color mode the output scan is black as well). > Best regards, > Marek -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand" From threestags at gmail.com Fri Jul 24 07:13:20 2020 From: threestags at gmail.com (Graham) Date: Fri, 24 Jul 2020 16:13:20 +1000 Subject: [sane-devel] Xerox PE220 scanner not detected Message-ID: <6787f96a-5642-944d-e68e-e171319f1e0b@gmail.com> I have not been able to use my scanner with Linux for some years now (it works find with windows).? I am currently using Linux Mint 19. All connections are good, printer is powered and operates normally (except scan). sane-find-scanner found USB scanner (vendor=0x0924 [Xerox], product=0x420f [Xerox WorkCentre PE220 Series]) at libusb:001:004 scanimage -L No scanners were identified. edited file /etc/sane.d/xerox_mfp.conf added #Xerox MFP usb 0x0924 0x420f I suspect it may be a permissions issue but I am unable to resolve. Any ideas please. Cheers Graham From jffry at posteo.net Sun Jul 26 10:35:11 2020 From: jffry at posteo.net (Jeff) Date: Sun, 26 Jul 2020 11:35:11 +0200 Subject: [sane-devel] gscan2pdf v2.8.2 released Message-ID: <521d2138-efc3-bab4-c3ae-bc13f06f3bd5@posteo.net> gscan2pdf - A GUI to produce a multipage PDF or DjVu from a scan. http://gscan2pdf.sourceforge.net/ Five clicks are required to scan several pages and then save all or a selection as a PDF or DjVu file, including metadata if required. gscan2pdf can control regular or sheet-fed (ADF) scanners with SANE via libimage-sane-perl, scanimage or scanadf, and can scan multiple pages at once. It presents a thumbnail view of scanned pages, and permits simple operations such as cropping, rotating and deleting pages. OCR can be used to recognise text in the scans, and the output embedded in the PDF or DjVu. PDF conversion is done by PDF::API2. The resulting document may be saved as a PDF, DjVu, multipage TIFF file, or single page image file. Changelog for 2.8.2: * If previously used font no longer exists, automatically pick another one. * Delete temporary files that fall off the undo buffer. Closes #350 (When delete photos the files in /tmp are not deleted) * Fix reload-recursion-limit problems after device-not-found mini- wizard. Closes Debian bug #965153 ("fails to open device" for Epson NX100) * Update to German translation (thanks to Matthias Sprau) * Update to Ukrainian translation (thanks to Yuri Chornoivan) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From paddy-hack at member.fsf.org Sun Jul 26 13:04:08 2020 From: paddy-hack at member.fsf.org (Olaf Meeuwissen) Date: Sun, 26 Jul 2020 21:04:08 +0900 Subject: [sane-devel] Any love for Mac OS 10.15 (Catalina) and a PIXMA-scanner (Canoscan 8800F)? In-Reply-To: <255574007.8327268.1595427020214@mail.yahoo.com> References: <255574007.8327268.1595427020214.ref@mail.yahoo.com> <255574007.8327268.1595427020214@mail.yahoo.com> Message-ID: <87v9iascsn.fsf@member.fsf.org> Hi Ola, There aren't too many Mac users out here so don't hold your breath. Not a Mac user myself but I'll try to help anyway. TL;DR: Ask the folks who maintain the sane-backends brew packages. Apologies for re-organizing your post a bit. I just find it easier to reply when the significant bits of the logs are inlined. Ola Andersson via sane-devel writes: > I would really like to get my old Canoscan 8800F to work with my > MacMini Mac OS 10.15.6 Catalina (latest) and when I discovered > SANE-Project I was initally very happy since my scanner was on the > list of supported devices. > Several days later after trying a bunch of different things, the > scanimage command, or XSANE GUI, it just doesn't work. Any help is > appreciated! > Below is a list of what I have tried, but I suspect this is some form > of permission problem with Mac OS >10.13, that has a new security > model. For instance developer need to place their software outside of > protected folders that are usually available on other OS's. Also as a > user you sometimes need to give apps access to folders, disk and other > things in the Security control panel. Another thing could be something > strange in the USB-communication, or that maybe the OS is marking the > scanner as busy with for some reason ( I have no way of finding that > out). But theese are just guesses. > Things I did: > > - Installed sane-backends using Brew. Brew is a package manager for > Mac OS that also installs any other library that is needed, and it > is regularly updated. This particualar package has support for Mac > OS 10.15, and installs sane 1.0.30, the very latest version. Source > is available at Github and the link to Brew shows what other > libraries are installed. libusb for instance. If you really think it's an issue with changes to the Mac OS security model, I think you'd be better of talking to the folks that provide the brew packages for sane-backends. They are sure to be more knowledgeable in that area. Most of us hanging out here are using Linux ... > - Some commands work now: > > - man sane > - man sane-pixma (In the list of supported scanners are my scanner, > Canoscan 8800F.) > - sane-find-scanner (output pasted below) > - sane-find-scanner -v -v (This gives very detailed output about > all connected USB-devices, incl my Caonscan 8800F , with same > manufacturer and model ID, but not serial number) as the next > command. > - scanimage -L (gives this output: "device `pixma:04A91901' is a > CANON Canoscan 8800F multi-function peripheral OK, at least scanimage is able to find your device. That's good news. > - This command doesn't work: > > $ scanimage --format="jpeg" --progress --output-file="scan1.jpg" \ > --resolution="600" --mode="color" --source="Flatbed" \ > --button-controlled="no" > scanimage: sane_read: Error during device I/O > > - Same result with sudo ifront. Dunno why. If you get the same results with sudo preprended, it's unlikely to be a permissions issue but then again I don't know anything about how Mac OS handles read/write access to the device. However, there may be something with the set of options you pass. Have you tried scanning with the defaults? That is, have you tried SANE_DEBUG_PIXMA=127 scanimage -o out.pnm 2> out.log and does that produce a good image in out.pnm? If not, we're interested in the out.log file. Oh, you already included that below. Good! > - Installed XSANE(also installed withBrew). > > - Tried scanning with this program, and I get this error message: > "Could not create file: Permission denied. I *think* that's xsane not being able to create its "state" files below $HOME/.sane/xsane/ (or the $HOME/.sane/xsane directory itself). Does that directory exist? Does it have a xsane.rc and/or xsane.mdf and/or a *.drc file that matches your device? > - I click Close, and get to the gui, click the button "Get preview" > and get the error message:"Error during reading: Error under unit > I/O)".The wording might differ, since my error messages are in > swedish. That's probably the same issue you see when using scanimage. > - Tried getting debug-info with these commands > > $ export SANE_DEBUG_PIXMA=21 > $ scanimage > test.pnm > Output format is not set, using pnm as a default. > [15:42:34.787160] [sanei_debug] Setting debug level of pixma to 21. > [15:42:34.788373] [pixma] pixma is compiled without pthread support. > [15:42:34.788782] [pixma] pixma version 0.27.0 > [15:42:34.791163] [pixma] pixma_collect_devices() found Canoscan 8800F at libusb:020:010 > [15:42:34.791879] [pixma] WARNING:No serial number > [15:42:34.792158] [pixma] pixma_find_scanners() found 1 devices > [15:42:39.924269] [pixma] pixma_collect_devices() found Canoscan 8800F at libusb:020:010 > [15:42:39.925280] [pixma] WARNING:No serial number > [15:42:39.925672] [pixma] pixma_open(): Canoscan 8800F > [15:42:39.926504] [pixma] OUT T=5.137 len=16 > [15:42:39.926541] [pixma] 00000000:ef 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > [15:42:39.926558] [pixma] > [15:42:39.943538] [pixma] IN T=5.154 len=8 > [15:42:39.943584] [pixma] 00000000:06 06 00 00 00 00 00 00 > [15:42:39.943597] [pixma] > [15:42:39.944638] [pixma] Reader task id=11001 (forked) > [15:42:39.945097] [pixma] Reader task started > [15:42:39.945377] [pixma] > [15:42:39.945542] [pixma] pixma_scan(): start > [15:42:39.945686] [pixma] line_size=1914 image_size=1678578 channels=3 depth=8 > [15:42:39.945826] [pixma] dpi=75x75 offset=(0,0) dimension=638x877 > [15:42:39.945965] [pixma] gamma_table=0x7fb98000ee40 source=0 > [15:42:39.946103] [pixma] threshold=127 threshold_curve=0 > [15:42:39.946242] [pixma] adf-wait=0 > [15:42:39.946380] [pixma] ADF page count: 0 > [15:42:39.946592] [pixma] WARNING:pixma_write(): count(0) != len(16) This looks like the pixma backend doesn't have write permissions to the device file. I would have expected `sudo` to "fix" this but there may be other, Mac OS specific, access controls at play. Again, I guess the brew folks would be your best bet. They ought to know much more about this than this Linux-only user of two decades and counting ;-) > Output in terminal from command xsane and also trying to get preview. If scanimage doesn't work for some reason, xsane is almost certainly not to work for the same reason. > - Also tried changing settings in the config-file, and also turned > them off again located > here:/usr/local/Cellar/sane-backends/1.0.30/etc/sane.d/pixma.conf. Some > lines that are now commented out again since they don't seem to > matter. > > - # Dunno what the correct name is for this param, but since my > scanner is connected with USB, I don't think it is > this:bjnp-timeout=5000 > - pixma-timeout=5000 > - usb-timeout=5000 > - timeout=5000 > - # Turned off networking > - networking=no As long as you are using USB, the above changes have no effect, AFAIK. > - # This is a suggestion from man sane-pixma, can't see it makes > any difference. > - usb 0x04a9 0x1901 This should not be needed for 1.0.30. The Canoscan8800F has been supported since sane-backends-1.0.21. > - I have also, per suggestion from man sane-pixma tried this command: > > - export SANE_USB_WORKAROUND=1 > - Which doesn't seem to help, so I have run same with a zero in the > end. > > - Lastly I have also tried installing the installers from this > page, they don't work either. > > - Mattias Ellert's binary installer packages of sane-backends, the > TWAIN SANE interface and related software. > - They are very old (over three years) and seems pretty useless, > even with Gimp. Mattias is no longer updating these :-/ > - Also several restarts, uninstalls and reinstalls. > - Tried two usb-cables. Hope this helps, -- Olaf Meeuwissen, LPIC-2 FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Software https://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join From paddy-hack at member.fsf.org Sun Jul 26 13:11:13 2020 From: paddy-hack at member.fsf.org (Olaf Meeuwissen) Date: Sun, 26 Jul 2020 21:11:13 +0900 Subject: [sane-devel] [janitorial] Let's release 1.0.31 in August In-Reply-To: <12475cf9-1f68-dc54-f38c-86700a556343@gmail.com> References: <871rl5xfaq.fsf@member.fsf.org> <12475cf9-1f68-dc54-f38c-86700a556343@gmail.com> Message-ID: <87tuxuscgu.fsf@member.fsf.org> Hi Ralph, Ralph Little writes: > On 2020-07-21 4:45 a.m., Olaf Meeuwissen wrote: >> I'll be adding issues fixed and merge requests to be included or already >> included in the coming weeks and hope to finish that before the feature >> freeze. Help with that chore is welcome by the way. > I noticed the other day that some changes that I did in the hp5400 > backend created a compile warning about an initialization bug. > I don't know how I missed that but I will fix it in the next couple of days. Don't sweat it, master is still without warnings on Debian 10, which is all we really care about (at the moment). Our CI pipeline would have failed if it wasn't. > Put me down for en_GB translations. > I will check in with my daughter on the French translations but don't > hold your breath. > If someone else would like to take them on, then please feel free. Ordissimo submitted !493 which I merged already. But you should have gotten a notification about that as I /cc'd you on the MR. Hope this helps, -- Olaf Meeuwissen, LPIC-2 FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Software https://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join From Ulf.Zibis at gmx.de Mon Jul 27 18:21:30 2020 From: Ulf.Zibis at gmx.de (Ulf Zibis) Date: Mon, 27 Jul 2020 19:21:30 +0200 Subject: [sane-devel] Place for scanner firmware Message-ID: <9f6d999d-cf5a-dd13-5fc5-9ab6ad20c126@gmx.de> Hi all, is there any place on sane web site to share scanner firmware? E.g. for Mustek ScanExpress 1200 UB Plus I could share *SBfw.usb* (got from here: http://www.meier-geinitz.de/sane/gt68xx-backend/) -Ulf -- Von meinem Seibert gesendet -------------- next part -------------- An HTML attachment was scrubbed... URL: From sedat.dilek at gmail.com Mon Jul 27 19:33:47 2020 From: sedat.dilek at gmail.com (Sedat Dilek) Date: Mon, 27 Jul 2020 20:33:47 +0200 Subject: [sane-devel] [janitorial] Let's release 1.0.31 in August In-Reply-To: <87sgdjiw8v.fsf@member.fsf.org> References: <871rl5xfaq.fsf@member.fsf.org> <87sgdjiw8v.fsf@member.fsf.org> Message-ID: On Wed, Jul 22, 2020 at 2:12 PM Olaf Meeuwissen wrote: > > Hi Sedat, > > Sedat Dilek writes: > > > On Tue, Jul 21, 2020 at 1:45 PM Olaf Meeuwissen > > wrote: > >> > >> Hi all, > >> > >> I've been dragging my feet of late. Not just as far as the SANE Project > >> is concerned but in general. For one reason or another I just can't get > >> myself to do much after I get home from work ... :-/ > >> > >> Let's see if I can change that a bit by upping the pressure (on myself) > >> and announce intent to release sane-backend-1.0.31 sometime next month. > >> That would keep us on track for a roughly half-yearly release cycle, not > >> counting security bug fix releases like 1.0.30. > >> > >> In keeping with what's in our `doc/release.txt` (minus a day or two), I > >> would like to proceed along the following timeline > >> > >> 2020-07-21 Kick-off > >> 2020-08-02 Feature Freeze (-> cut release/1.0.31 branch) > >> 2020-08-16 Code Freeze > >> 2020-08-23 Release > >> > >> You can find a milestone for 1.0.31 at > >> > >> https://gitlab.com/sane-project/backends/-/milestones/4 > >> > >> I'll be adding issues fixed and merge requests to be included or already > >> included in the coming weeks and hope to finish that before the feature > >> freeze. Help with that chore is welcome by the way. > >> > >> # FTR, I'll be mostly off-line during the August 12-16 period. > >> > >> Hope this helps, > > > > I am not 100% following this mailing-list, so I can miss fundamental > > informations. > > > > As I had a Canon LIDE 70 I wanted to ask what is the status of support for it? > > Support will be added in 1.0.31. It's already mentioned in the NEWS > file > > https://gitlab.com/sane-project/backends/-/blob/master/NEWS > > > While searching for informations myself: > > 1. Its man-page [2] points to nirvana. > > That's because the backend has not been included in a release yet and is > something that we might want to fix. Please submit an issue. > > > 2. The ChangeLogs file [3] ends with release 1.0.28. > > Actually, that points to a ChangeLogs *directory*. We decided to stop > updating the ChangeLog in the repository itself because `git log` will > tell you anyway. Of course that assumes you have cloned the repository > but if you haven't, you can check > > https://gitlab.com/sane-project/backends/-/commits/master > > Our source tarballs, both release and snapshots, include a generated > ChangeLog file though. > > There's also an issue about this > > https://gitlab.com/sane-project/backends/-/issues/313 > > > Thanks for a feedback in advance. > > > > - Sedat - > > > > [1] http://www.sane-project.org/lists/sane-backends-cvs.html#S-CANON-LIDE70 > > [2] http://www.sane-project.org/man/sane-canon_lide70.5.html > > [3] https://gitlab.com/sane-project/backends/-/tree/master/ChangeLogs > > [4] https://gitlab.com/sane-project/backends/-/merge_requests/247 > > As for that last merge request, you want to look at 315 instead (as > mentioned at the bottom of the feedback on 247). > > Hope this helps, Hi Olaf, Thanks for commenting. Hope you can clarify in the next announcement and/or within SCM (I read ChangeLogs :-)). As said - currently - I have no scanner or a multi-function device w/ printer+scanner. So SANE has not a high priority for me. I should have kept the Canon LIDE 70 scanner - it was fu**ing cool device. Regards, - Sedat - From strredwolf at gmail.com Mon Jul 27 19:39:49 2020 From: strredwolf at gmail.com (Kelly Price) Date: Mon, 27 Jul 2020 14:39:49 -0400 Subject: [sane-devel] [janitorial] Let's release 1.0.31 in August In-Reply-To: References: <871rl5xfaq.fsf@member.fsf.org> <87sgdjiw8v.fsf@member.fsf.org> Message-ID: Can I agree that the Canon LiDE series have been f**king cool? I should get another for mobile work... On Mon, Jul 27, 2020 at 2:33 PM Sedat Dilek wrote: > > On Wed, Jul 22, 2020 at 2:12 PM Olaf Meeuwissen > wrote: > > > > Hi Sedat, > > > > Sedat Dilek writes: > > > > > On Tue, Jul 21, 2020 at 1:45 PM Olaf Meeuwissen > > > wrote: > > >> > > >> Hi all, > > >> > > >> I've been dragging my feet of late. Not just as far as the SANE Project > > >> is concerned but in general. For one reason or another I just can't get > > >> myself to do much after I get home from work ... :-/ > > >> > > >> Let's see if I can change that a bit by upping the pressure (on myself) > > >> and announce intent to release sane-backend-1.0.31 sometime next month. > > >> That would keep us on track for a roughly half-yearly release cycle, not > > >> counting security bug fix releases like 1.0.30. > > >> > > >> In keeping with what's in our `doc/release.txt` (minus a day or two), I > > >> would like to proceed along the following timeline > > >> > > >> 2020-07-21 Kick-off > > >> 2020-08-02 Feature Freeze (-> cut release/1.0.31 branch) > > >> 2020-08-16 Code Freeze > > >> 2020-08-23 Release > > >> > > >> You can find a milestone for 1.0.31 at > > >> > > >> https://gitlab.com/sane-project/backends/-/milestones/4 > > >> > > >> I'll be adding issues fixed and merge requests to be included or already > > >> included in the coming weeks and hope to finish that before the feature > > >> freeze. Help with that chore is welcome by the way. > > >> > > >> # FTR, I'll be mostly off-line during the August 12-16 period. > > >> > > >> Hope this helps, > > > > > > I am not 100% following this mailing-list, so I can miss fundamental > > > informations. > > > > > > As I had a Canon LIDE 70 I wanted to ask what is the status of support for it? > > > > Support will be added in 1.0.31. It's already mentioned in the NEWS > > file > > > > https://gitlab.com/sane-project/backends/-/blob/master/NEWS > > > > > While searching for informations myself: > > > 1. Its man-page [2] points to nirvana. > > > > That's because the backend has not been included in a release yet and is > > something that we might want to fix. Please submit an issue. > > > > > 2. The ChangeLogs file [3] ends with release 1.0.28. > > > > Actually, that points to a ChangeLogs *directory*. We decided to stop > > updating the ChangeLog in the repository itself because `git log` will > > tell you anyway. Of course that assumes you have cloned the repository > > but if you haven't, you can check > > > > https://gitlab.com/sane-project/backends/-/commits/master > > > > Our source tarballs, both release and snapshots, include a generated > > ChangeLog file though. > > > > There's also an issue about this > > > > https://gitlab.com/sane-project/backends/-/issues/313 > > > > > Thanks for a feedback in advance. > > > > > > - Sedat - > > > > > > [1] http://www.sane-project.org/lists/sane-backends-cvs.html#S-CANON-LIDE70 > > > [2] http://www.sane-project.org/man/sane-canon_lide70.5.html > > > [3] https://gitlab.com/sane-project/backends/-/tree/master/ChangeLogs > > > [4] https://gitlab.com/sane-project/backends/-/merge_requests/247 > > > > As for that last merge request, you want to look at 315 instead (as > > mentioned at the bottom of the feedback on 247). > > > > Hope this helps, > > Hi Olaf, > > Thanks for commenting. > Hope you can clarify in the next announcement and/or within SCM (I > read ChangeLogs :-)). > > As said - currently - I have no scanner or a multi-function device w/ > printer+scanner. > So SANE has not a high priority for me. > > I should have kept the Canon LIDE 70 scanner - it was fu**ing cool device. > > Regards, > - Sedat - > -- Kelly "STrRedWolf" Price http://redwolf.ws From paddy-hack at member.fsf.org Tue Jul 28 12:11:32 2020 From: paddy-hack at member.fsf.org (Olaf Meeuwissen) Date: Tue, 28 Jul 2020 20:11:32 +0900 Subject: [sane-devel] Place for scanner firmware In-Reply-To: <9f6d999d-cf5a-dd13-5fc5-9ab6ad20c126@gmx.de> References: <9f6d999d-cf5a-dd13-5fc5-9ab6ad20c126@gmx.de> Message-ID: <87d04frj17.fsf@member.fsf.org> Hi Ulf, Ulf Zibis writes: > is there any place on sane web site to share scanner firmware? > > E.g. for Mustek ScanExpress 1200 UB Plus I could share *SBfw.usb* (got > from here: http://www.meier-geinitz.de/sane/gt68xx-backend/) No. And for a good reason. Most firmware files are extracted from the vendor's Windows and/or Mac drivers. These drivers come with a license and unless that license explicitly allows redistribution of the firmware file (without the rest of the driver), redistributing it is bound to get you into legal trouble. In addition, the SANE Project's web site is published on servers maintained by GitLab.com so we have to abide by their rules as well. Naturally, GitLab.com doesn't want to get into legal trouble itself and requires that you have permission to publish whatever you publish. If you don't have that permission, you run a the risk of getting "kicked out". # I'm paraphrasing from memory. I had a quick look at the page you mentioned and could not find any mention of licenses for the various firmware files ... Definitely going out on a limb there. Hope this helps, -- Olaf Meeuwissen, LPIC-2 FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Software https://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join From Ulf.Zibis at gmx.de Wed Jul 29 11:28:23 2020 From: Ulf.Zibis at gmx.de (Ulf Zibis) Date: Wed, 29 Jul 2020 12:28:23 +0200 Subject: [sane-devel] Place for scanner firmware In-Reply-To: <87zh7id60e.fsf@member.fsf.org> References: <9f6d999d-cf5a-dd13-5fc5-9ab6ad20c126@gmx.de> <87d04frj17.fsf@member.fsf.org> <87zh7id60e.fsf@member.fsf.org> Message-ID: <5914ed28-2c59-d36e-4bb5-56212c51ca48@gmx.de> Hi Olaf, Am 29.07.20 um 11:28 schrieb Olaf Meeuwissen: > Hi Ulf, > > Ulf Zibis writes: > >> Hi Olaf, >> >> Am 28.07.20 um 13:11 schrieb Olaf Meeuwissen: >>> Hi Ulf, >>> >>> Ulf Zibis writes: >>> >>>> is there any place on sane web site to share scanner firmware? >>>> >>>> E.g. for Mustek ScanExpress 1200 UB Plus I could share *SBfw.usb* (got >>>> from here: http://www.meier-geinitz.de/sane/gt68xx-backend/) >>> No. And for a good reason. >>> >>> Most firmware files are extracted from the vendor's Windows and/or Mac >>> drivers. These drivers come with a license and unless that license >>> explicitly allows redistribution of the firmware file (without the rest >>> of the driver), redistributing it is bound to get you into legal >>> trouble. >>> >>> In addition, the SANE Project's web site is published on servers >>> maintained by GitLab.com so we have to abide by their rules as well. >>> Naturally, GitLab.com doesn't want to get into legal trouble itself and >>> requires that you have permission to publish whatever you publish. If >>> you don't have that permission, you run a the risk of getting "kicked >>> out". >>> >>> # I'm paraphrasing from memory. >>> >>> I had a quick look at the page you mentioned and could not find any >>> mention of licenses for the various firmware files ... >>> Definitely going out on a limb there. >>> >>> Hope this helps, >> Thanks for your explanation. >> >> Yes, it's a difficult subject with these licenses. >> >> I would say, if one owns the hardware, he is automatically legal owner >> of the firmware. > I'm afraid that's where you're wrong. At least in the general case. If > firmware files are needed by any SANE backend, it typically means that > it needs to be sent to the device before said device works. As soon as > you power the device off, whatever was sent to the device just sort of > "evaporates" and needs to be sent again. > > This is different from firmware that is preloaded on the device when you > buy it and a SANE backend works without any firmware file. > > If a firmware file came with a vendor provided driver, it is covered by > the license that came with the driver. You normally don't own anything > and just (barely) get the right to use it. > > Hope this helps, I know, that the firmware must be uploaded to the device on every usage. By "owning" I mean, that I have the vendor driver. If for what ever reason I'm missing this driver, I see no legal problem to use a copy of this driver, I get from elsewhere, because I have the license to use it by owning the hardware. The only problem from my point of view is, if "elsewhere" is allowed to share it to me, even if "elsewhere" has no license to use it, particularly if the vendor has no support for re-shipping the driver. -Ulf From kitno455 at gmail.com Thu Jul 30 21:57:16 2020 From: kitno455 at gmail.com (m. allan noah) Date: Thu, 30 Jul 2020 16:57:16 -0400 Subject: [sane-devel] Canon DR-C225 II - black scan In-Reply-To: References: <20200626203316.ik45i2g4n7zeknu2@nur.localdomain> Message-ID: Marek et al- I've spent a couple evenings looking at all the various logs that I have for the C225, and have discovered that it does a different type of fine calibration from other models. So, I've worked up the attached patch, against the current sane-backends sources. The idea is to re-use some of the existing calibration code instead of writing a new version just for this scanner. I expect this may not work, and if it does, it will only give us poor quality images. But, it should be enough to validate that the issue is caused by calibration. You will need to apply this patch to sane-backends source, and rebuild/reinstall. I don't have access to any Canon scanners at this time, so I have only verified that this compiles, unfortunately. Let me know what you find out, or if you need help. allan On Thu, Jul 23, 2020 at 8:53 PM m. allan noah wrote: > > Marek, I'm sorry it has taken me a month to reply, life is a little > 'different' these days :) > > So I have gone back through every email thread I have had about the > DR-C225, and do have a set of logs from the windows driver. I will > attempt to determine which bit of magic we are missing. It will take > me some time, as I am travelling now. If you do not hear from me soon, > please feel free to reach out. Also, if you want to study up on > rebuilding sane-backends from source in the meantime, we will need it. > > allan > > On Fri, Jun 26, 2020 at 4:33 PM Marek wrote: > > > > Dear developers, > > I wonder if you could help me with resolving a problem with Canon > > DR-C225 II scanner (canon_dr backend). The output scan is all black. In > > 2015 there was a thread on the predecessor of this scanner: DR-C225 > > (without 'II'), which suffered from similar problem. Unfortunately that > > thread seems to be prematurely abandoned without solving the issue. > > I'm attaching a scanimage log for a page scanned in a grayscale mode (for > > the color mode the output scan is black as well). > > Best regards, > > Marek > > > > -- > "well, I stand up next to a mountain- and I chop it down with the edge > of my hand" -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand" -------------- next part -------------- A non-text attachment was scrubbed... Name: c225-a.patch Type: text/x-patch Size: 17491 bytes Desc: not available URL: