[sane-devel] brother-MFC-J485DW fails after update.
Hi Thierry, Thanks for your message. I backed up file /etc/sane.d/esl.conf and added the following entries to the file. [device] model Brother MFC-J485DW type http ip 192.168.1.28:80 port 80 Using the brother driver I noticed that I can scan at 1200 dpi instead of 600 dpi maximum with eSCL sane-airscan. CUPS Off-Topic perhaps: I currently have setting (Device URI) > ipp://BRWA8A7953594FC.local:631/ipp/print?encryption=required CUPS Off-Topic perhaps: Could you recommend some link for airprint cups driver setup at all? I found this > https://wiki.debian.org/CUPSAirPrint I read that> There are two technologies central to the AirPrint facility on a printer: 1a. The printer must be advertised with Bonjour broadcasting. The printer must communicate with the client using IPP. "lpinfo --include-schemes dnssd -v" network dnssd://Brother%20MFC-J485DW._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-a8a7953594fc network dnssd://Brother%20MFC-J485DW._printer._tcp.local/?uuid=e3248000-80ce-11db-8000-a8a7953594fc 2a. For a view of printers only there is. "avahi-browse -rt _ipp._tcp > discovered" no output shown Also I have reviewed the CUPS help page. Is there a good place I can ask some CUPS questions you recommend? Thanks alot for your help. Hi, For escl to be constant, I suggest you add the following entries (I would look at why it disappears (I have already noticed it) [device] model Brother MFC-J485DW type http ip 192.168.1.28:80 port 80 in the file: /etc/sane.d/escl.conf Brother and owner, I have a preference for free drivers, if you choose this solution, the entries "brother2", "brother3" and "brother4" can be erased. For airscan, the maintainer has read your message and will probably ask you for the log files. Another thing, for your printer using the airprint cups driver it is much better than the driver provided by Brother. Translated with www.DeepL.com/Translator (free version) Thierry Le 2020-08-25 21:23, pj.wo...@gmx.com a écrit : - > Hello and thank you for your response. I am uncertain what the best > format in which to respond to the mailing list is so I am including my > original message at the bottom. Then Thierry's response and this > message on top. > > 1. I determined that the MFC-J485DW was not communicating when I > attempted to ping it's designated ip address. It made some sense > because devices had been occasionally dropping off the network > suddenly this past week. > > 2. I replaced modem-router combo with a different unit on hand. I was > then able to ping the MFC-J485DW. > > 3. SANE worked again. > > 4. I added the ppa by: > > sudo add-apt-repository ppa:rolfbensch/sane-git > sudo apt-get update > sudo apt install libsane libsane-common sane-utils > > 5. I added backend entries "brother2" "brother3" "brother4" to > /etc/sane.d/dll.conf > > 6. I updated entire system "sudo apt-get update && sudo apt-get > upgrade" and then rebooted. > > 7. My question is as follows: xsane 0.999 shows when opening. (In the > "Available devices" menu). After fresh system boot Initially 3 device > options are shown. Then once xsane is closed and executed later during > same system boot only 2 device options are shown as follows: > > Initially these options are available: Brother MFC-J485DW MFC-J485DW > [brother:net1;dev0] > > Brother > MFC-J485DW flatbed scanner [escl:http://192.168.1.28:80] > > eSCL Brother > MFC-J485 eSCL network scanne [airscan:e0:Brother MFC-J485DW > > After initial xsane use only 2 options are available: Brother > MFC-J485DW MFC-J485DW [brother:net1;dev0] > > > eSCL Brother MFC-J485 eSCL network scanne > [airscan:e0:Brother MFC-J485DW > > Which option is prefered it seems now with updates applied today > through the PPA all are functional. Whereis prior sane-airscan did not > scan correctly with the MFC-J485DW. sane-airscan worked fine on my > HP-Officejet 4630 though. > > 8. Thank you for your thoughts and assistance if able. > Paul > > Hi, > the Brother driver is not free. > report the bug to: https://support.brother.comotre scanner is > supported > by the free escl and sanr-airscan driver. > I suggest you update your sane version: > sudo add-apt-repository ppa:rolfbensch/sane-git > sudo apt-get update > sudo apt install libsane libsane-common sane-utils > Thierry > Le 2020-08-25 02:51, pj.wo...@gmx.com a écrit : > >> Hello, I am running LinuxMint 20 upgraded from LinuxMint 19.3 > earlier >> this month. The (brother MFC-J485DW all-in-one) is connected >> wirelessly to the network and was functioning fine after the update > to >> Mint20 when then reinstallation of the (brother
[sane-devel] Alexander Pevzner-sane-airscan-version
Hello, Alexander Pevzner. I have sane-airscan version (0.99.9+67.1 amd64) currently installed. Now I am seeing on https://github.com/alexpevzner/sane-airscan that version https://download.opensuse.org/repositories/home:/pzz/xUbuntu_20.04/amd64/sane-airscan_0.99.15+74.1_amd64.deb Is available for Mint 20. 1. I am seeing in my prior post I wrote (Whereis prior sane-airscan did not scan correctly with the MFC-J485DW). It was obviously a different package affecting the scan output then sane-airscan package. I recall that I could scan using sane-airscan but output was all grey or something completely NON legible. 1. I suppose I should probably update the installed version of sane-airscan to (0.99.15+74.1_amd64.deb) correct? 2. With sane-airscan version (0.99.9+67.1 amd64) currently installed. The brother MFC-J485DW works with xsane 0.999 to scan using sane-airscan eSCL option. I think it can be added to the compatible list maybe. 3. I notice with sane-airscan version (0.99.9+67.1 amd64) that 600 dpi is maximum. When I use the Brother device driver I can select 1200 dpi. Thankyou -- Hi Paul, On 8/25/20 10:23 PM, pj.wo...@gmx.com wrote: > Which option is prefered it seems now with updates applied today through > the PPA all are functional. Whereis prior sane-airscan did not scan > correctly with the MFC-J485DW. sane-airscan worked fine on my > HP-Officejet 4630 though. Regarding sane-airscan, what version do you use? -- Wishes, Alexander Pevzner (p...@apevzner.com)
Re: [sane-devel] brother-MFC-J485DW fails after update. [partially solved]
Hi Paul, On 8/25/20 10:23 PM, pj.wo...@gmx.com wrote: Which option is prefered it seems now with updates applied today through the PPA all are functional. Whereis prior sane-airscan did not scan correctly with the MFC-J485DW. sane-airscan worked fine on my HP-Officejet 4630 though. Regarding sane-airscan, what version do you use? -- Wishes, Alexander Pevzner (p...@apevzner.com)
Re: [sane-devel] brother-MFC-J485DW fails after update. [partially solved]
Sorry, this entries is correct : [device] model Brother MFC-J485DW type http ip 192.168.1.28:80 port 80 Le 25 août 2020 21:53:09 GMT+02:00, Thierry HUCHARD a écrit : >Hi, > >For escl to be constant, I suggest you add the following entries (I >would look at why it disappears (I have already noticed it) > > >[device] >model Brother MFC-J485DW >http type >ip 192.168.1.28:80 >port 80 > > in the file: /etc/sane.d/escl.conf > >Brother and owner, I have a preference for free drivers, if you choose >this solution, the entries "brother2", "brother3" and "brother4" can be >erased. > >For airscan, the maintainer has read your message and will probably ask >you for the log files. > >Another thing, for your printer using the airprint cups driver it is >much better than the driver provided by Brother. > >Translated with www.DeepL.com/Translator (free version) > >Thierry > >Le 2020-08-25 21:23, pj.wo...@gmx.com a écrit : >> Hello and thank you for your response. I am uncertain what the best >> format in which to respond to the mailing list is so I am including my >> origional message at the bottom. Then Thierry's response and this >> message on top. >> >> 1. I determined that the MFC-J485DW was not communicating when I >> attempted to ping it's designated ip address. It made some sense >> because devices had been occasionally dropping off the network >> suddenly this past week. >> >> 2. I replaced modem-router combo with a different unit on hand. I was >> then able to ping the MFC-J485DW. >> >> 3. SANE worked again. >> >> 4. I added the ppa by: >> >> sudo add-apt-repository ppa:rolfbensch/sane-git >> sudo apt-get update >> sudo apt install libsane libsane-common sane-utils >> >> 5. I added backend entries "brother2" "brother3" "brother4" to >> /etc/sane.d/dll.conf >> >> 6. I updated entire system "sudo apt-get update && sudo apt-get >> upgrade" and then rebooted. >> >> 7. My question is as follows: xsane 0.999 shows when opening. (In the >> "Available devices" menu). After fresh system boot Initially 3 device >> options are shown. Then once xsane is closed and executed later during >> same system boot only 2 device options are shown as follows: >> >> Initially these options are available: Brother MFC-J485DW MFC-J485DW >> [brother:net1;dev0] >> >> Brother >> MFC-J485DW flatbed scanner [escl:http://192.168.1.28:80] >> >> eSCL Brother >> MFC-J485 eSCL network scanne [airscan:e0:Brother MFC-J485DW >> >> After initial xsane use only 2 options are available: Brother >> MFC-J485DW MFC-J485DW [brother:net1;dev0] >> >> >> eSCL Brother MFC-J485 eSCL network scanne >> [airscan:e0:Brother MFC-J485DW >> >> Which option is prefered it seems now with updates applied today >> through the PPA all are functional. Whereis prior sane-airscan did not >> scan correctly with the MFC-J485DW. sane-airscan worked fine on my >> HP-Officejet 4630 though. >> >> 8. Thank you for your thoughts and assistance if able. >> Paul >> >> Hi, >> the Brother driver is not free. >> report the bug to: https://support.brother.comotre scanner is >> supported >> by the free escl and sanr-airscan driver. >> I suggest you update your sane version: >> sudo add-apt-repository ppa:rolfbensch/sane-git >> sudo apt-get update >> sudo apt install libsane libsane-common sane-utils >> Thierry >> Le 2020-08-25 02:51, pj.wo...@gmx.com a écrit : >> >>> Hello, I am running LinuxMint 20 upgraded from LinuxMint 19.3 >> earlier >>> this month. The (brother MFC-J485DW all-in-one) is connected >>> wirelessly to the network and was functioning fine after the update >> to >>> Mint20 when then reinstallation of the (brother Driver Install Tool >>> was applied). xsane .999 is the currently installed version. The >>> printer and scanner were working fine before I updated the system >>> earlier today which is 2020-8-24. >>> >>> Below is a list of all updates upgraded and installed on 2020-8-24 >> one >>> or more of which apparently broke the functionality of xsane and >>> printing features on the MFC-J485DW today. >>> >>> Command > "GREP UPGRADE /VAR/LOG/DPKG.LOG" outputs: >>> >>> 2020-08-24 09:30:13 UPGRADE libsane:i386 1.0.29-0ubuntu5 >>> 1.0.29-0ubuntu5.1 >>> 2020-08-24 09:30:15 UPGRADE libsane:amd64 1.0.29-0ubuntu5 >>> 1.0.29-0ubuntu5.1 >>> 2020-08-24 09:30:16 UPGRADE libsane1:amd64 1.0.29-0ubuntu5 >>> 1.0.29-0ubuntu5.1 >>> 2020-08-24 09:30:17 UPGRADE libsane-common:all 1.0.29-0ubuntu5 >>> 1.0.29-0ubuntu5.1 >>> 2020-08-24 09:30:19 UPGRADE sane-utils:amd64 1.0.29-0ubuntu5 >>> 1.0.29-0ubuntu5.1 >>> 2020-08-24 09:30:20 UPGRADE ghostscript-x:amd64 9.50~dfsg-5ubuntu4.1 >>> 9.50~dfsg-5ubuntu4.2 >>> 2020-08-24 09:30:21 UPGRADE ghostscript:amd64 9.50~dfsg-5ubuntu4.1 >>> 9.50~dfsg-5ubuntu4.2 >>> 2020-08-24 09:30:22 UPGRADE libgs9:amd64 9.50~dfsg-5ubuntu4.1 >>> 9.50~dfsg-5ubuntu4.2 >>> 2020-08-24 09:30:24 UPGRADE libgs9-common:all
Re: [sane-devel] brother-MFC-J485DW fails after update. [partially solved]
Hi, For escl to be constant, I suggest you add the following entries (I would look at why it disappears (I have already noticed it) [device] model Brother MFC-J485DW http type ip 192.168.1.28:80 port 80 in the file: /etc/sane.d/escl.conf Brother and owner, I have a preference for free drivers, if you choose this solution, the entries "brother2", "brother3" and "brother4" can be erased. For airscan, the maintainer has read your message and will probably ask you for the log files. Another thing, for your printer using the airprint cups driver it is much better than the driver provided by Brother. Translated with www.DeepL.com/Translator (free version) Thierry Le 2020-08-25 21:23, pj.wo...@gmx.com a écrit : Hello and thank you for your response. I am uncertain what the best format in which to respond to the mailing list is so I am including my origional message at the bottom. Then Thierry's response and this message on top. 1. I determined that the MFC-J485DW was not communicating when I attempted to ping it's designated ip address. It made some sense because devices had been occasionally dropping off the network suddenly this past week. 2. I replaced modem-router combo with a different unit on hand. I was then able to ping the MFC-J485DW. 3. SANE worked again. 4. I added the ppa by: sudo add-apt-repository ppa:rolfbensch/sane-git sudo apt-get update sudo apt install libsane libsane-common sane-utils 5. I added backend entries "brother2" "brother3" "brother4" to /etc/sane.d/dll.conf 6. I updated entire system "sudo apt-get update && sudo apt-get upgrade" and then rebooted. 7. My question is as follows: xsane 0.999 shows when opening. (In the "Available devices" menu). After fresh system boot Initially 3 device options are shown. Then once xsane is closed and executed later during same system boot only 2 device options are shown as follows: Initially these options are available: Brother MFC-J485DW MFC-J485DW [brother:net1;dev0] Brother MFC-J485DW flatbed scanner [escl:http://192.168.1.28:80] eSCL Brother MFC-J485 eSCL network scanne [airscan:e0:Brother MFC-J485DW After initial xsane use only 2 options are available: Brother MFC-J485DW MFC-J485DW [brother:net1;dev0] eSCL Brother MFC-J485 eSCL network scanne [airscan:e0:Brother MFC-J485DW Which option is prefered it seems now with updates applied today through the PPA all are functional. Whereis prior sane-airscan did not scan correctly with the MFC-J485DW. sane-airscan worked fine on my HP-Officejet 4630 though. 8. Thank you for your thoughts and assistance if able. Paul Hi, the Brother driver is not free. report the bug to: https://support.brother.comotre scanner is supported by the free escl and sanr-airscan driver. I suggest you update your sane version: sudo add-apt-repository ppa:rolfbensch/sane-git sudo apt-get update sudo apt install libsane libsane-common sane-utils Thierry Le 2020-08-25 02:51, pj.wo...@gmx.com a écrit : Hello, I am running LinuxMint 20 upgraded from LinuxMint 19.3 earlier this month. The (brother MFC-J485DW all-in-one) is connected wirelessly to the network and was functioning fine after the update to Mint20 when then reinstallation of the (brother Driver Install Tool was applied). xsane .999 is the currently installed version. The printer and scanner were working fine before I updated the system earlier today which is 2020-8-24. Below is a list of all updates upgraded and installed on 2020-8-24 one or more of which apparently broke the functionality of xsane and printing features on the MFC-J485DW today. Command > "GREP UPGRADE /VAR/LOG/DPKG.LOG" outputs: 2020-08-24 09:30:13 UPGRADE libsane:i386 1.0.29-0ubuntu5 1.0.29-0ubuntu5.1 2020-08-24 09:30:15 UPGRADE libsane:amd64 1.0.29-0ubuntu5 1.0.29-0ubuntu5.1 2020-08-24 09:30:16 UPGRADE libsane1:amd64 1.0.29-0ubuntu5 1.0.29-0ubuntu5.1 2020-08-24 09:30:17 UPGRADE libsane-common:all 1.0.29-0ubuntu5 1.0.29-0ubuntu5.1 2020-08-24 09:30:19 UPGRADE sane-utils:amd64 1.0.29-0ubuntu5 1.0.29-0ubuntu5.1 2020-08-24 09:30:20 UPGRADE ghostscript-x:amd64 9.50~dfsg-5ubuntu4.1 9.50~dfsg-5ubuntu4.2 2020-08-24 09:30:21 UPGRADE ghostscript:amd64 9.50~dfsg-5ubuntu4.1 9.50~dfsg-5ubuntu4.2 2020-08-24 09:30:22 UPGRADE libgs9:amd64 9.50~dfsg-5ubuntu4.1 9.50~dfsg-5ubuntu4.2 2020-08-24 09:30:24 UPGRADE libgs9-common:all 9.50~dfsg-5ubuntu4.1 9.50~dfsg-5ubuntu4.2 2020-08-24 15:49:12 UPGRADE libsnmp-base:all 5.8+dfsg-2ubuntu2.2 5.8+dfsg-2ubuntu2.3 2020-08-24 15:49:13 UPGRADE libsnmp35:i386 5.8+dfsg-2ubuntu2.2 5.8+dfsg-2ubuntu2.3 2020-08-24 15:49:15 UPGRADE libsnmp35:amd64 5.8+dfsg-2ubuntu2.2 5.8+dfsg-2ubuntu2.3 2020-08-24 16:10:34 UPGRADE mfcj485dwlpr:i386 1.0.0-0 1.0.0-0 2020-08-24 16:11:53 UPGRADE brscan4:amd64 0.4.9-1 0.4.9-1 2020-08-24 16:11:58 UPGRADE brscan-skey:amd64 0.3.1-1 0.3.1-1 2020-08-24 17:09:17 UPGRADE libsane1:amd64
[sane-devel] brother-MFC-J485DW fails after update. [partially solved]
Hello and thank you for your response. I am uncertain what the best format in which to respond to the mailing list is so I am including my origional message at the bottom. Then Thierry's response and this message on top. 1. I determined that the MFC-J485DW was not communicating when I attempted to ping it's designated ip address. It made some sense because devices had been occasionally dropping off the network suddenly this past week. 2. I replaced modem-router combo with a different unit on hand. I was then able to ping the MFC-J485DW. 3. SANE worked again. 4. I added the ppa by: sudo add-apt-repository ppa:rolfbensch/sane-git sudo apt-get update sudo apt install libsane libsane-common sane-utils 5. I added backend entries "brother2" "brother3" "brother4" to /etc/sane.d/dll.conf 6. I updated entire system "sudo apt-get update && sudo apt-get upgrade" and then rebooted. 7. My question is as follows: xsane 0.999 shows when opening. (In the "Available devices" menu). After fresh system boot Initially 3 device options are shown. Then once xsane is closed and executed later during same system boot only 2 device options are shown as follows: Initially these options are available: Brother MFC-J485DW MFC-J485DW [brother:net1;dev0] Brother MFC-J485DW flatbed scanner [escl:http://192.168.1.28:80] eSCL Brother MFC-J485 eSCL network scanne [airscan:e0:Brother MFC-J485DW After initial xsane use only 2 options are available: Brother MFC-J485DW MFC-J485DW [brother:net1;dev0] eSCL Brother MFC-J485 eSCL network scanne [airscan:e0:Brother MFC-J485DW Which option is prefered it seems now with updates applied today through the PPA all are functional. Whereis prior sane-airscan did not scan correctly with the MFC-J485DW. sane-airscan worked fine on my HP-Officejet 4630 though. 8. Thank you for your thoughts and assistance if able. Paul Hi, the Brother driver is not free. report the bug to: https://support.brother.comotre scanner is supported by the free escl and sanr-airscan driver. I suggest you update your sane version: sudo add-apt-repository ppa:rolfbensch/sane-git sudo apt-get update sudo apt install libsane libsane-common sane-utils Thierry Le 2020-08-25 02:51, pj.wo...@gmx.com a écrit : > Hello, I am running LinuxMint 20 upgraded from LinuxMint 19.3 earlier > this month. The (brother MFC-J485DW all-in-one) is connected > wirelessly to the network and was functioning fine after the update to > Mint20 when then reinstallation of the (brother Driver Install Tool > was applied). xsane .999 is the currently installed version. The > printer and scanner were working fine before I updated the system > earlier today which is 2020-8-24. > > Below is a list of all updates upgraded and installed on 2020-8-24 one > or more of which apparently broke the functionality of xsane and > printing features on the MFC-J485DW today. > > Command > "GREP UPGRADE /VAR/LOG/DPKG.LOG" outputs: > > 2020-08-24 09:30:13 UPGRADE libsane:i386 1.0.29-0ubuntu5 > 1.0.29-0ubuntu5.1 > 2020-08-24 09:30:15 UPGRADE libsane:amd64 1.0.29-0ubuntu5 > 1.0.29-0ubuntu5.1 > 2020-08-24 09:30:16 UPGRADE libsane1:amd64 1.0.29-0ubuntu5 > 1.0.29-0ubuntu5.1 > 2020-08-24 09:30:17 UPGRADE libsane-common:all 1.0.29-0ubuntu5 > 1.0.29-0ubuntu5.1 > 2020-08-24 09:30:19 UPGRADE sane-utils:amd64 1.0.29-0ubuntu5 > 1.0.29-0ubuntu5.1 > 2020-08-24 09:30:20 UPGRADE ghostscript-x:amd64 9.50~dfsg-5ubuntu4.1 > 9.50~dfsg-5ubuntu4.2 > 2020-08-24 09:30:21 UPGRADE ghostscript:amd64 9.50~dfsg-5ubuntu4.1 > 9.50~dfsg-5ubuntu4.2 > 2020-08-24 09:30:22 UPGRADE libgs9:amd64 9.50~dfsg-5ubuntu4.1 > 9.50~dfsg-5ubuntu4.2 > 2020-08-24 09:30:24 UPGRADE libgs9-common:all 9.50~dfsg-5ubuntu4.1 > 9.50~dfsg-5ubuntu4.2 > 2020-08-24 15:49:12 UPGRADE libsnmp-base:all 5.8+dfsg-2ubuntu2.2 > 5.8+dfsg-2ubuntu2.3 > 2020-08-24 15:49:13 UPGRADE libsnmp35:i386 5.8+dfsg-2ubuntu2.2 > 5.8+dfsg-2ubuntu2.3 > 2020-08-24 15:49:15 UPGRADE libsnmp35:amd64 5.8+dfsg-2ubuntu2.2 > 5.8+dfsg-2ubuntu2.3 > 2020-08-24 16:10:34 UPGRADE mfcj485dwlpr:i386 1.0.0-0 1.0.0-0 > 2020-08-24 16:11:53 UPGRADE brscan4:amd64 0.4.9-1 0.4.9-1 > 2020-08-24 16:11:58 UPGRADE brscan-skey:amd64 0.3.1-1 0.3.1-1 > 2020-08-24 17:09:17 UPGRADE libsane1:amd64 1.0.29-0ubuntu5.1 > 1.0.29-0ubuntu5 > 2020-08-24 17:15:58 UPGRADE libsane1:amd64 1.0.29-0ubuntu5 > 1.0.29-0ubuntu5.1 > > Here are additional command outputs: > > Command > "BRSANECONFIG4 -Q | GREP MFC-J485DW" outputs: > * *MFC-J485DW [ 192.168.1.23] MFC-J485DW > > Command > "BRSCAN-SKEY -L" outputs: > MFC-J485DW : brother4:net1;dev0 : 192.168.1.23 Not > responded > > 1. For instance when
Re: [sane-devel] Question SANE and Canon Scanner
Hi Frank, Lide 300 supports IPP over USB, and eSCL on a top of it. The presence of the IPP-over-USB support causes ippusbxd daemon to start, which effectively blocks sane-pixma driver and should, in theory, enable sane-escl driver, which seems doesn't want to work. You have two possibilities here: 1. Remove ippusbxd in a hope to unblock sane-pixma: sudo apt-get remove ippusbxd 2. Replace eSCL/IPP-over-USB stack with the modern alternative. First step as above (remove ippusbxd), then download and install ipp-usb and sane-airscan packages from the following location: https://download.opensuse.org/repositories/home:/pzz/xUbuntu_20.04/ Note, both of these packages will be officially included into the subsequent release of Ubuntu, so you will not be locked with some strange 3rd party packages. -- Wishes, Alexander Pevzner (p...@apevzner.com)
Re: [sane-devel] Question SANE and Canon Scanner
Have you tried Rolf's PPA?
sudo add-apt-repository ppa:rolfbensch/sane-release
sudo apt-get update
sudo apt-get upgrade
The -dev packages usually install headers and such that allow folks to
program against libsane.
At worst, uninstall the Mint versions and use the PPA.
On Tue, Aug 25, 2020 at 8:02 AM m. allan noah wrote:
>
> "Unable to open device: Device busy"
>
> do you have something else installed that is talking to the scanner?
> like canon's scangear software, or a VM running another OS?
>
> allan
>
> On Tue, Aug 25, 2020 at 5:28 AM <2bfr...@posteo.de> wrote:
> >
> > Dear SANE team,
> >
> > thanks for a great FOSS project ! Can I bother you with a question, you
> > are my last resort, I tried various forums;
> > regarding the Cannon LiDE 300 Scanner. I bought it because it is listed
> > as "completely supported" in the SANE list
> > (http://www.sane-project.org/sane-mfgs.html#Z-CANON),
> > but I can't get it to work. Here's what I tried:
> >
> > I am on Linux Mint 20 (Ubuntu 20.04 base), and the scanner is
> > recognised:
> >
> > lsusb
> > Bus 003 Device 004: ID 04a9:1913 Canon, Inc. LiDE 300
> >
> > scanimage -L
> > device `pixma:04A91913' is a CANON CanoScan LiDE 300 multi-function
> > peripheral
> >
> > sane-find-scanner
> > found USB scanner (vendor=0x04a9 [Canon], product=0x1913 [LiDE 300]) at
> > libusb:001:004
> >
> > I found out that it works with sane-pixma, provided by
> > libsane-common_1.0.22-7ubuntu1_amd64 bug
> > I have 1.0.29 installed, so it should be OK too? According to
> > https://packages.debian.org/buster/amd64/libsane-dev/filelist
> > it is provided by the libsane-dev package, so I tried
> >
> > sudo apt install libsane-dev
> > still no result...
> >
> > simple scan output:
> >
> > simple-scan -d (debug mode)
> > +9,45s] DEBUG: scanner.vala:341: sane_get_devices () -> SANE_STATUS_GOOD
> > [+9,45s] DEBUG: scanner.vala:353: Device: name="pixma:04A91913"
> > vendor="CANON" model="CanoScan LiDE 300" type="multi-function
> > peripheral"
> > [+9,45s] DEBUG: scanner.vala:353: Device:
> > name="escl:http://127.0.0.1:6; vendor="ESCL" model="LiDE 300 HTTP"
> > type="flatbed scanner"
> > [+13,68s] DEBUG: simple-scan.vala:455: Requesting scan at 300 dpi from
> > device 'pixma:04A91913'
> > [+13,68s] DEBUG: scanner.vala:1676: Scanner.scan ("pixma:04A91913",
> > dpi=300, scan_mode=ScanMode.COLOR, depth=8, type=single, paper_width=0,
> > paper_height=0, brightness=0, contrast=0, delay=3000ms)
> > [+13,68s] DEBUG: scanner.vala:828: Processing request
> > [+14,20s] DEBUG: scanner.vala:889: sane_open ("pixma:04A91913") ->
> > SANE_STATUS_DEVICE_BUSY
> > [+14,20s] WARNING: scanner.vala:893: Unable to open device: Device busy
> >
> > XSane says the same thing. Unable to open device: Device busy
> >
> > here's what dmesg said:
> >
> > dmesg
> > 41353.742838] usb 1-3: new high-speed USB device number 5 using xhci_hcd
> > [41353.804289] usb 1-3: New USB device found, idVendor=04a9,
> > idProduct=1913, bcdDevice= 1.00
> > [41353.804292] usb 1-3: New USB device strings: Mfr=1, Product=2,
> > SerialNumber=3
> > [41353.804295] usb 1-3: Product: LiDE 300
> > [41353.804297] usb 1-3: Manufacturer: Canon
> > [41353.804298] usb 1-3: SerialNumber: 486D04
> > [41353.864304] usb 1-3: usbfs: process 20985 (ippusbxd) did not claim
> > interface 0 before use
> > [41353.906525] audit: type=1400 audit(1598002277.392:90):
> > apparmor="DENIED" operation="open" profile="ippusbxd"
> > name="/etc/nsswitch.conf" pid=21004 comm="ippusbxd" requested_mask="r"
> > denied_mask="r" fsuid=0 ouid=0
> >
> > I found in a forum that ippusbxd might be the problem, removed the
> > package, but no result.
> >
> > I also manually added line in file /etc/sane.d/genesys.conf and
> > /etc/sane.d/canon.conf
> > # Canon LIDE 300
> > usb 0x04a9 0x1913
> >
> > as well as in
> > /lib/udev/rules.d/60-libsane.rules
> > # Canon LIDE
> > ATTRS{type}=="3", ATTRS{vendor}=="04a9", ATTRS{model}=="1913",
> > ENV{libsane_matched}="yes"
> >
> > -
> > I'm really sorry to use you as a hotline, but if there are any ideas, I
> > would be grateful;
> > All the Best
> > Frank
> >
>
>
> --
> "well, I stand up next to a mountain- and I chop it down with the edge
> of my hand"
>
--
Kelly "STrRedWolf" Price
http://redwolf.ws
Re: [sane-devel] Question SANE and Canon Scanner
"Unable to open device: Device busy"
do you have something else installed that is talking to the scanner?
like canon's scangear software, or a VM running another OS?
allan
On Tue, Aug 25, 2020 at 5:28 AM <2bfr...@posteo.de> wrote:
>
> Dear SANE team,
>
> thanks for a great FOSS project ! Can I bother you with a question, you
> are my last resort, I tried various forums;
> regarding the Cannon LiDE 300 Scanner. I bought it because it is listed
> as "completely supported" in the SANE list
> (http://www.sane-project.org/sane-mfgs.html#Z-CANON),
> but I can't get it to work. Here's what I tried:
>
> I am on Linux Mint 20 (Ubuntu 20.04 base), and the scanner is
> recognised:
>
> lsusb
> Bus 003 Device 004: ID 04a9:1913 Canon, Inc. LiDE 300
>
> scanimage -L
> device `pixma:04A91913' is a CANON CanoScan LiDE 300 multi-function
> peripheral
>
> sane-find-scanner
> found USB scanner (vendor=0x04a9 [Canon], product=0x1913 [LiDE 300]) at
> libusb:001:004
>
> I found out that it works with sane-pixma, provided by
> libsane-common_1.0.22-7ubuntu1_amd64 bug
> I have 1.0.29 installed, so it should be OK too? According to
> https://packages.debian.org/buster/amd64/libsane-dev/filelist
> it is provided by the libsane-dev package, so I tried
>
> sudo apt install libsane-dev
> still no result...
>
> simple scan output:
>
> simple-scan -d (debug mode)
> +9,45s] DEBUG: scanner.vala:341: sane_get_devices () -> SANE_STATUS_GOOD
> [+9,45s] DEBUG: scanner.vala:353: Device: name="pixma:04A91913"
> vendor="CANON" model="CanoScan LiDE 300" type="multi-function
> peripheral"
> [+9,45s] DEBUG: scanner.vala:353: Device:
> name="escl:http://127.0.0.1:6; vendor="ESCL" model="LiDE 300 HTTP"
> type="flatbed scanner"
> [+13,68s] DEBUG: simple-scan.vala:455: Requesting scan at 300 dpi from
> device 'pixma:04A91913'
> [+13,68s] DEBUG: scanner.vala:1676: Scanner.scan ("pixma:04A91913",
> dpi=300, scan_mode=ScanMode.COLOR, depth=8, type=single, paper_width=0,
> paper_height=0, brightness=0, contrast=0, delay=3000ms)
> [+13,68s] DEBUG: scanner.vala:828: Processing request
> [+14,20s] DEBUG: scanner.vala:889: sane_open ("pixma:04A91913") ->
> SANE_STATUS_DEVICE_BUSY
> [+14,20s] WARNING: scanner.vala:893: Unable to open device: Device busy
>
> XSane says the same thing. Unable to open device: Device busy
>
> here's what dmesg said:
>
> dmesg
> 41353.742838] usb 1-3: new high-speed USB device number 5 using xhci_hcd
> [41353.804289] usb 1-3: New USB device found, idVendor=04a9,
> idProduct=1913, bcdDevice= 1.00
> [41353.804292] usb 1-3: New USB device strings: Mfr=1, Product=2,
> SerialNumber=3
> [41353.804295] usb 1-3: Product: LiDE 300
> [41353.804297] usb 1-3: Manufacturer: Canon
> [41353.804298] usb 1-3: SerialNumber: 486D04
> [41353.864304] usb 1-3: usbfs: process 20985 (ippusbxd) did not claim
> interface 0 before use
> [41353.906525] audit: type=1400 audit(1598002277.392:90):
> apparmor="DENIED" operation="open" profile="ippusbxd"
> name="/etc/nsswitch.conf" pid=21004 comm="ippusbxd" requested_mask="r"
> denied_mask="r" fsuid=0 ouid=0
>
> I found in a forum that ippusbxd might be the problem, removed the
> package, but no result.
>
> I also manually added line in file /etc/sane.d/genesys.conf and
> /etc/sane.d/canon.conf
> # Canon LIDE 300
> usb 0x04a9 0x1913
>
> as well as in
> /lib/udev/rules.d/60-libsane.rules
> # Canon LIDE
> ATTRS{type}=="3", ATTRS{vendor}=="04a9", ATTRS{model}=="1913",
> ENV{libsane_matched}="yes"
>
> -
> I'm really sorry to use you as a hotline, but if there are any ideas, I
> would be grateful;
> All the Best
> Frank
>
--
"well, I stand up next to a mountain- and I chop it down with the edge
of my hand"
[sane-devel] Question SANE and Canon Scanner
Dear SANE team,
thanks for a great FOSS project ! Can I bother you with a question, you
are my last resort, I tried various forums;
regarding the Cannon LiDE 300 Scanner. I bought it because it is listed
as "completely supported" in the SANE list
(http://www.sane-project.org/sane-mfgs.html#Z-CANON),
but I can't get it to work. Here's what I tried:
I am on Linux Mint 20 (Ubuntu 20.04 base), and the scanner is
recognised:
lsusb
Bus 003 Device 004: ID 04a9:1913 Canon, Inc. LiDE 300
scanimage -L
device `pixma:04A91913' is a CANON CanoScan LiDE 300 multi-function
peripheral
sane-find-scanner
found USB scanner (vendor=0x04a9 [Canon], product=0x1913 [LiDE 300]) at
libusb:001:004
I found out that it works with sane-pixma, provided by
libsane-common_1.0.22-7ubuntu1_amd64 bug
I have 1.0.29 installed, so it should be OK too? According to
https://packages.debian.org/buster/amd64/libsane-dev/filelist
it is provided by the libsane-dev package, so I tried
sudo apt install libsane-dev
still no result...
simple scan output:
simple-scan -d (debug mode)
+9,45s] DEBUG: scanner.vala:341: sane_get_devices () -> SANE_STATUS_GOOD
[+9,45s] DEBUG: scanner.vala:353: Device: name="pixma:04A91913"
vendor="CANON" model="CanoScan LiDE 300" type="multi-function
peripheral"
[+9,45s] DEBUG: scanner.vala:353: Device:
name="escl:http://127.0.0.1:6; vendor="ESCL" model="LiDE 300 HTTP"
type="flatbed scanner"
[+13,68s] DEBUG: simple-scan.vala:455: Requesting scan at 300 dpi from
device 'pixma:04A91913'
[+13,68s] DEBUG: scanner.vala:1676: Scanner.scan ("pixma:04A91913",
dpi=300, scan_mode=ScanMode.COLOR, depth=8, type=single, paper_width=0,
paper_height=0, brightness=0, contrast=0, delay=3000ms)
[+13,68s] DEBUG: scanner.vala:828: Processing request
[+14,20s] DEBUG: scanner.vala:889: sane_open ("pixma:04A91913") ->
SANE_STATUS_DEVICE_BUSY
[+14,20s] WARNING: scanner.vala:893: Unable to open device: Device busy
XSane says the same thing. Unable to open device: Device busy
here's what dmesg said:
dmesg
41353.742838] usb 1-3: new high-speed USB device number 5 using xhci_hcd
[41353.804289] usb 1-3: New USB device found, idVendor=04a9,
idProduct=1913, bcdDevice= 1.00
[41353.804292] usb 1-3: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[41353.804295] usb 1-3: Product: LiDE 300
[41353.804297] usb 1-3: Manufacturer: Canon
[41353.804298] usb 1-3: SerialNumber: 486D04
[41353.864304] usb 1-3: usbfs: process 20985 (ippusbxd) did not claim
interface 0 before use
[41353.906525] audit: type=1400 audit(1598002277.392:90):
apparmor="DENIED" operation="open" profile="ippusbxd"
name="/etc/nsswitch.conf" pid=21004 comm="ippusbxd" requested_mask="r"
denied_mask="r" fsuid=0 ouid=0
I found in a forum that ippusbxd might be the problem, removed the
package, but no result.
I also manually added line in file /etc/sane.d/genesys.conf and
/etc/sane.d/canon.conf
# Canon LIDE 300
usb 0x04a9 0x1913
as well as in
/lib/udev/rules.d/60-libsane.rules
# Canon LIDE
ATTRS{type}=="3", ATTRS{vendor}=="04a9", ATTRS{model}=="1913",
ENV{libsane_matched}="yes"
-
I'm really sorry to use you as a hotline, but if there are any ideas, I
would be grateful;
All the Best
Frank
[sane-devel] how to switch off the scan lamp?
hello there, i'm honestly a bit unsure whether or not my question is too dumb.. for a project, i would love to be able to switch off the lamp of my scanner. i currently use a "canon lide 210", but i would switch to any other device that would me allow to disable the lamp (preferably canon devices). i'm very grateful for any advice, even if it just leads to what to google :) not sure if that's of importance: my workhorse is a macbook (mid 2012), running on catalina (10.15.5) many thanks in advance! best wishes, marten
