Download Brother Scanner App
Tisa Timchak
I have looked for an appropriate scanner driver for solving this problem. So far I am using brscan4 which is available on pamac. But after research brsan5 should be the correct driver for this brother scanner. But brscan5 is not available on pamac neither via console on sudo pacman -S brscan.
No I have installed the correct scanner driver for this model brscan5 and also brscan-key but the scan (with simple-scan and also scanlite) always stops after the first 2 pages with duplex scan. There was a time when it worked with an older version of Manjaro.
Here is the way I managed to make the scanner work. In my case I needed DCP-J315W but I saw this solution worked for other Brother devices too.
Some suggest to delete the printer configuration if there is already one for the device you are attempting to install. I run the process on two machines with Fedora 36 installed and tried both leaving and deleting printer settings and worked well with both. I did however reinstall the drivers as per the following instructions.
I use a MFC-9440CN bronther printer as a scanner and after upgrading to Fedora 28 I got the classic "no device available" when using xsane. I reinstalled using the latest brother drivers etc (which I think was not required). I did the below:...
I am using XUbuntu 18.04 and I am struggling to install my scanner. I have tried everything i have been able to find on both Brother homepage and AskUbuntu.I have newest brsaneconfig4, brscan-skey and rules.
However, In my case, this folder was indeed present, but it was empty. The subsequent instructions were, essentially to copy the files libsane-brother* from the /usr/lib64/sane/ folder to /usr/lib/x86_64-linux-gnu/sane.
The only "catch" is: if you want to install it over WiFi, make sure your printer has a static IP assigned on your router, and use that IP during install (one of the options is to provide the installer with the IP of the machine).If the IP of the driver changes, there's a chance you will have to redo your brsaneconfig everytime that happens so it's better to assign static IP to the printer/scanner.
I have a brother DCP 7020 printer/scanner. I used to print and scan with it in my previous computer running arch linux without problems. Now I have a new laptop, and I tried to set it up again. I installed 'foomatic-db' and got the printer to work with cups. However I'm having problems getting the scanner to work. In particular, when I run xsane, I get a pop-up saying
PS. I rebooted both laptop and scanner after installing the packages and added my user to the scanner group. Also, the only difference between this and the previous laptop where the scanner worked, is that the new is 64bit and the old was 32bit.
PS2. This does not seem to be a permission problem either; I checked that there is a line for my printer in the udev rules file.
A backend configuration file /etc/sane.d/brotherN.conf isn't provided by upstream and seems by no means obligatory as it doesn't exist on the system the said Brother MFC-215C is connected to either.
Same applies to the apparent inconsistency between usb device numbering as stated by lsusb and 'scanimage -L' respectively. Same here, but scanner does work.
Membership in group scanner isn't needed any longer.
Several copies of line 'brother2' in /etc/sane.d/dll.conf are probably due to the predecessor package brscan2 not removing these upon uninstall. This shouldn't happen any longer using the current package.
Since my scanner works now, I'm happy and I think I won't tinker with it any longer. If however you think that tracking this down further could contribute to improve the package, I'll do, just let me know.
I played around a little more and I think I figured it out. You were right, the extra file in /lib/udev/rules.d is irrelevant, I removed it. What made a difference was plugging the scanner in a different usb port and rebooting. Of course I had used all the different ports in the beginning, but I hadn't rebooted after changing the port.
The funny thing is that after using the 'correct' port and rebooting, then after boot up I can change the usb port to the 'bad' ones and the scanner still works. Or I'm missing something and it's just a coincidence.
In any case, now everything works with just brscan2 with no extra rules and no tinkering whatsoever. I'm not sure why it didn't work in some ports but it does now, so the package is obviously fine and my scanner works fine.
Thank you for the suggestion. Unfortunately, for me, it did not work switching to allow applications from anywhere. With Mac OS 11 it still gives that same error message. My only solution seems to be to use the iPrint/Scan app and it doesn't open from the printer/scanner driver.
To deal with the scanner driver on an ongoing basis, follow the suggested instructions, then drag the desired driver app file into the dock (I put it right next to "Preview" which is what I usually use to initiate a scan). Then you just click on "Brother Scanner" (or whatever brand you've got) in the dock and then launch your scanning app (for me, Preview).
I don't have a Brother scanner to try it. Apple supports a lot of printer/scanner vendors directly (Cannon, Epson, FujiXerox, Gestetner, HP, Infoprint, Infotec, Lanier, Lexmark, NRG, Ricoh, Samsung and Savin), although I'm sure with vendor help. Notice Brother is missing from the list.
I have a Brother MFC-2740DW that I have been using for many years. For over a year I have had it connected to the local network via wifi. It has a scanner function, which I normally use via the Printer application on my Mac. Today the scanner function is no longer present.
I found some advice online to reset the print system, which involves deleting the printers in the Printers and Scanners preferences app, then re-adding them back. I tried that, and still there is no scanner function.
I temporarily accepted an answer because the scan function appeared to have been restored. The scanner apps looks just like it used to. However, when I tried a scan, I get "Scanner reported an error" and "an error occurred while communicating with the scanner." So I am not out of the woods yet!
I don't scan very often. But over the last couple of years, every time I try to use the scanner function, the scanner icon is dimmed out. Rebooting printer and computer sometimes helps, but usually I have to reinstall the scanner driver, as described in my answer below.
After installing SSP.
I have found out how I can allow the device.
When the scanner is connected a window pops up from "Device guard(?)" saying that the scanner has connected, and it has been allowed.
Still when I press "Scan to Computer" which is how I have usually used it the device says it cannot connect to the PC.
When I try to use Brothers scan tool it finds the scanner, it can read the serial etc, but it cannot scan.
When I try to use the built in "Windows scan" it actually runs the paper through the scanner but hten says something went
wrong and no picture appears.
I have tried uninstalling the drivers and software, and reinstalling them without any difference.
Could this be a problem based on the scanner can be seen as a scanner and as usb storage?
Anything I can try? (not involving reinstalling Windows 11)
Let me add that scanner from Brother Brother HL-2280DW CUPS seems to work well - and when I tried various combinations for Brother MFC-L2750DW series-AirPrint some importing caused Affinity Photo to actually crash. I believe these bugs are latent for many versions of Affinity Photo.
To scan via Image Capture directly into Photo, you can create a totally simple Automator plugin, which will pass the scanner input (that is being temporarily saved in a hidden system folder) to open with Photo:
@loukash, thank you for the idea, I will look into it. I was hoping that by indicating it didn't work for one brother scanner, but yet another it did work, that info might help Affinity. The fact that it works for Pixelmator pro, and perhaps other photo editing apps, should be a stimulus to accelerate a fix. In terms of the "same process", well it might not be the same "environment" - timing, memory management, race conditions, whatever, recursive code if they implement that way. This is an annoying situation, similar to have to work around using nik collection on an apple silicon. Affinity needs to strive for perfection.
It will be a new image file, not "Untitled" as from Acquire Image.
The major difference is that you can select the format you're scanning to and define the file name before scanning. If you're scanning to TIFF (or PNG, unless your scanner support features that PNG can't do), the scan will be just as lossless as with Acquire Image.
Well, I view it more as a timing bug in and around the api call, because if I wait a few seconds, click again, or switch to another scanner and then back, it works. That is why I said earlier that the environment in and around calling the api is different. Anyway, your second suggestion, simply outputting image capture to AP2 is fine. Doing it twice creates a 2nd tab which is ok, so the image can be modified, then copy/pasted to the first tab. This is a good enough solution for me and it is out of the box, w/o having to create custom code (automator) that perhaps can break in a future OS upgrade.
df19127ead