- #Sane linux network scanner how to
- #Sane linux network scanner install
- #Sane linux network scanner drivers
Installation script `/opt/brother/scanner/brscan4/udev_config.sh`.Īlso check that the file `/etc/sane.d/dll.conf` contains `brscan4` line, if notĪdd it or fix their script `/opt/brother/scanner/brscan4/setupSaneScan4`: `/etc/udev/rules.d/les` and if not fix the `brother-udev-rule-type1-1.0.` but you won't need it as it wasīrother RPM packages are known to have lame scripting, their scripts usuallyĭon't work in different environments.
#Sane linux network scanner install
Tutorials also guides you to install package named For scanning you only need brscan4 actually, but I installed both. Then download brscan4 and brscan-skey RPM packages from [Brotherīoth. Package which somehow is not correctly listed in Fedora 28, so install these
#Sane linux network scanner how to
Here is how to fix this:įirst, I am going to use simple scan utility, it also needs a dependency If that's not possible, other solution (kind of temporary, but better for users than manually installing it) is requiring libnsl in spec file.įor googlers - there is another problem in their scriplets. The best course of action for Brother support is to port driver to use libnsl2 and requiring it in spec file. Not mentioning that libnsl can be removed from Fedora, because it is old, and only libnsl2 will be available, then even requiring libnsl will not help and driver will need to be ported to libnsl2. the fact that libnsl needs to be installed for running driver needs to be mentioned in spec file of rpm, which Brother ships.
#Sane linux network scanner drivers
I'm sorry, but IMHO this isn't permanent solution - if you consider other users of Brother scanners, then they have to install libnsl manually (and they need to know that they need to do it) when they install Brother 3rd party drivers to get scanner working. > could be considered a permanent solution or just a temporary fix. > I installed libnsl and the scanner now works as expected. Not sure which component to put my finger on, I choose xsane but it might be something else. This is not an upgrade issue, since I found similar results in my Lenovo laptop running F28 installed from scratch. I ran command "brsaneconfig3 -a name=SCANNER model=MFC-8890DW ip=192.168.1.106" as usual, and then command "brsaneconfig3 -q | grep SCANNER", which showed the scanner was duly detected: "0 SCANNER "MFC-8890DW" I:192.168.1.106". I verified specific brother drivers and they were installed, as well as sane-backends, sane-backends-drivers-cameras, sane-backends-drivers-scanners, sane-backends-libs and sane-frontends. I can print with it and access it via the web browser. I verified connections and everything seems OK. I upgraded my desktop from F27 to F28 beta and found this issue. The scanner is a Brother MFC-8890DW, used via network. Scanner detected in the same way as Fedora 27 and predecessors did. Version-Release number of selected component (if applicable):Įvery time I try to scan with either app.Ģ.Ask the app to detect networking scanner.ģ.The app reports no scanner found or crash altogether. Before upgrading to F28 everything worked just fine. Xsane, Simple-scan, Skanlite and gscan2pdf fail detecting network scanner.
0 kommentar(er)
