Entonces, mi escáner de impresión Samsung SCX-4300 funciona bien a través de USB y, en su lugar, lo conecté con un "Servidor USB de red" como en el siguiente enlace:
A través del servidor, la impresión funciona bien pero el escáner no funciona y seguí las instrucciones del tutorial de Ubuntu:
https://help.ubuntu.com/community/SaneDaemonTutorial?action=show&redirect=sane.d+tutorial
1.Entonces escribí en la terminal sudo service saned restart:
Failed to restart saned.service: unit saned.service is masked
2.Más tarde, sudo service saned status:
● saned.service
Active: inactive (dead)
Loaded: masked (/dev/null; bad)
Luego busqué en internet y encontré esta web:systemctl, cómo desenmascarar
3. file /lib/systemd/system/saned.service:
/lib/systemd/system/saned.service: symbolic lik to /dev/null
4.Escribí para comprobar sudo nano /run/systemd/generator.late/saned.servicey encontré que estaba completamente vacío.
5. sudo rm /lib/systemd/system/saned.servicey luego, más tarde,sudo systemctl daemon-reload
7.y finalmente, systemctl status saned:
● saned.service - LSB: SANE network scanner server
Loaded: loaded (/etc/init.d/saned; generated)
Active: failed (Result: exit-code) since Sun 2019-06-16 13:19:23 -05; 9min ago
Docs: man:systemd-sysv-generator(8)
Process: 923 ExecStart=/etc/init.d/saned start (code=exited, status=1/FAILURE)
jun 16 13:19:22 MS-7529 saned[923]: * Starting SANE network scanner server saned
jun 16 13:19:23 MS-7529 saned[944]: saned (AF-indep+IPv6) from sane-backends 1.0.27 starting up
jun 16 13:19:23 MS-7529 saned[944]: do_bindings: [1] bind failed: Address already in use
jun 16 13:19:23 MS-7529 saned[944]: do_bindings: [0] bind failed: Address already in use
jun 16 13:19:23 MS-7529 saned[944]: do_bindings: couldn't bind an address. Exiting.
jun 16 13:19:23 MS-7529 saned[944]: FATAL ERROR; bailing out, waiting for children...
jun 16 13:19:23 MS-7529 saned[944]: bail_out: all children exited
jun 16 13:19:23 MS-7529 systemd[1]: saned.service: Control process exited, code=exited status=1
jun 16 13:19:23 MS-7529 systemd[1]: saned.service: Failed with result 'exit-code'.
jun 16 13:19:23 MS-7529 systemd[1]: Failed to start LSB: SANE network scanner server.
8:Así que fui a comprobarlo de nuevo sudo nano /run/systemd/generator.late/saned.service:
# Automatically generated by systemd-sysv-generator
[Unit]
Documentation=man:systemd-sysv-generator(8)
SourcePath=/etc/init.d/saned
Description=LSB: SANE network scanner server
Before=multi-user.target
Before=multi-user.target
Before=multi-user.target
Before=graphical.target
After=remote-fs.target
After=dbus.service
After=avahi-daemon.service
[Service]
Type=forking
Restart=no
TimeoutSec=5min
IgnoreSIGPIPE=no
KillMode=process
GuessMainPID=no
RemainAfterExit=yes
SuccessExitStatus=5 6
ExecStart=/etc/init.d/saned start
ExecStop=/etc/init.d/saned stop
9.Escribí de nuevo sudo service saned status:
● saned.service - LSB: SANE network scanner server
Loaded: loaded (/etc/init.d/saned; generated)
Active: failed (Result: exit-code) since Sun 2019-06-16 13:19:23 -05; 1h 20min ago
Docs: man:systemd-sysv-generator(8)
Process: 923 ExecStart=/etc/init.d/saned start (code=exited, status=1/FAILURE)
jun 16 13:19:22 MS-7529 saned[923]: * Starting SANE network scanner server saned
jun 16 13:19:23 MS-7529 saned[944]: saned (AF-indep+IPv6) from sane-backends 1.0.27 starting up
jun 16 13:19:23 MS-7529 saned[944]: do_bindings: [1] bind failed: Address already in use
jun 16 13:19:23 MS-7529 saned[944]: do_bindings: [0] bind failed: Address already in use
jun 16 13:19:23 MS-7529 saned[944]: do_bindings: couldn't bind an address. Exiting.
jun 16 13:19:23 MS-7529 saned[944]: FATAL ERROR; bailing out, waiting for children...
jun 16 13:19:23 MS-7529 saned[944]: bail_out: all children exited
jun 16 13:19:23 MS-7529 systemd[1]: saned.service: Control process exited, code=exited status=1
jun 16 13:19:23 MS-7529 systemd[1]: saned.service: Failed with result 'exit-code'.
jun 16 13:19:23 MS-7529 systemd[1]: Failed to start LSB: SANE network scanner server.
No pude encontrar cómo solucionarlo para conectar el escáner a través del servidor.
Entonces, ¿alguien sabe cómo solucionar este fallo?