Hi, Looks like moving the .so files is what did the trick. I have heard of other people having this problem. Ubuntu (and a few others I think) changed the location of their platform specific shared objects some years ago. Brother's installation package most likely pre-dates this so isn't setup to cope with this specific change.
So, I missed it when you said that it was now working. 😅 Good to get a result. Some answers below though: On Thu, May 15, 2025 at 2:55 AM David Brown <[email protected]> wrote: > Hi Ralph, > > I had a go att eh 3 queries you raised: > > So, a few things to try: > > 1) Try the ldd command with each of the 3 libbrother* files and make sure > it can resolve all the dependencies. > > >> My system did not recognise ldd command so I didn't push it further. > OK, I thought it was installed by default. My mistake. :( > > 2) SANE_DEBUG_DLL=5 scanimage -L > ...and look at the output. Make sure that the brother driver is mentioned > and that it says that it can find and load the .so files. > > >> This was all good as per attached pic. But did not mention the .so > files. > Looks from the attached picture that you used lowercase for SANE_DEBUG_DLL. It is case dependent, so must be uppercase. You should have seen a load of diag output. > > 3) The brother backend should be mentioned somewhere in > /etc/sane.d/dll.conf /etc/sane.d/dll.conf.d or somesuch IIRC. > Perhaps check that they are. > > >> My system has file: /etc/sane.d/dll.conf (not the other file > dll.conf.d) > This file contained mentions of brother and brother3 > Yeah, brother3 is what you are looking for, but you say it works now so I would expect that. 👍 > > Cheers > David > > On Thu, May 15, 2025 at 8:55 AM Ralph Little <[email protected]> wrote: > >> Hi, >> >> On Wed, May 14, 2025 at 3:47 PM David Brown <[email protected]> >> wrote: >> >>> Hi Ralph, >>> >>> Thanks for getting back to me. After I submitted my query I re-checked >>> my notes and tweaks from past 6 installs and found my scanner now works >>> after I re-copied files as follows: >>> sudo cp /usr/lib64/sane/libsane-brother* /usr/lib/x86_64-linux-gnu/sane >>> >> >> This is an Ubuntuism. They just path their platform-specific binaries in >> a different place. >> >> >>> >>> This command copied 3 new files across. There were 6 libsane-brother >>> files already but not the missing 3 which are listed below and scanner now >>> working (previous error message was "Missing Drivers"). >>> The three new files this copy command copied were: >>> libsane-brother1.so >>> libsane-brother1.so.1.0.7 >>> libsane-brother2.so.1.0.7 >>> >>> I don't what the difference is between these three files or which one or >>> combination worked. >>> I don't know why the missing 3 files were not previously copied??? I >>> had run this command before but may have had a syntax error - hard to say. >>> It's all a mystery to me. >>> >>> The above solution is but part of a sequence of tweaks I used on 24.04.1 >>> based on past years. >>> Basically - whenever I blow up my system and need a fresh install. It >>> happens lol. >>> >>> Other tweaks include: >>> >>> Edit 60-libsane1.rules cmd: sudo nano >>> //usr/lib/udev/rules.d/60-libsane1.rules # Brother scanner >>> ATTRS{Vendor}==”04f9”, ENV{libsane_matched}=”yes” >>> >>> sudo mkdir //usr/lib/sane >>> >>> sudo cp /usr/lib64/sane/libsane-brother* /usr/lib/sane >>> >>> In 2022 Brother suggested installing USB patch file (google Brother legacy >>> USB) >>> >>> dpkg-i brotherlegacyusb-1.1.0-0.all.deb >>> >>> >> Probably would be the same as the other tip I replied about related to >> libusb. >> >>> >>> On 17/3/25 I edited /usr/lib/udev/hwdb.d/20-sane.hwdb and added: >>> >>> usb:v04f9p0254* >>> >>> libsane-matched=yes >>> >>> >>> 13/4/25 I tried installing libusb but this was already the latest version. >>> >>> sudo apt-get install libusb-0.1-4 >>> >>> OK, gotcha. >> >> So, a few things to try: >> >> 1) Try the ldd command with each of the 3 libbrother* files and make sure >> it can resolve all the dependencies. >> >> 2) SANE_DEBUG_DLL=5 scanimage -L >> ...and look at the output. Make sure that the brother driver is mentioned >> and that it says that it can find and load the .so files. >> >> 3) The brother backend should be mentioned somewhere in >> /etc/sane.d/dll.conf /etc/sane.d/dll.conf.d or somesuch IIRC. >> Perhaps check that they are. >> >> Let us know what you discover. >> >> Cheers, >> Ralph >> >
