<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>
<pre class="western">I hope this is not to long of message or upsetting the list please do let me know if it is.
Hi Thierry, Thanks for your message.
I backed up file /etc/sane.d/escl.conf and added the following entries to the file.
[device]
model Brother MFC-J485DW
type http
ip 192.168.1.28:80
port 80
Above in ip 192.168.1.28:80 line (must remove :80) or 4 Available devices appear. I have now the following:
[device]
model Brother MFC-J485DW
type http
ip 192.168.1.28
port 80
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.world@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.world@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 I attempt to use Synaptic Package Manager to
>> attempt to (Force Version downgrade) of the "libsane-common" package
>> back to version 1.0.29-0ubuntu5.0 from 1.0.29-Oubuntu5.1 the (To be
>> removed) list includes the following packages:
>>
>> brscan-skey
>> colord
>> hplip
>> libsane
>> libsane1
>> sane
>> sane-utils
>> simple-scan
>> xsane
>>
>> 2. Is there any advice that I can proceed with here? Before
> attempting
>> to revert to a earlier backup of Mint 20 or even potentialy proceed
>> back to Mint 19.3 completely?
>>
>> 3. For instance looking at the above package updates list it appears
>> the "libsane1:amd64" package is going back and forth between *.5 and
>> *.5.1 throughout the day.
>>
>> 4. I'm quite confused and would appreciate your advice. Thank you
> for
>> any assistance.</pre>
</div></div></body></html>