After doing some research I believe this is not a bug, but a
misunderstanding. With systemd in use in 16.04 saned is started only "on
demand", when a program calls for it.
The solution from the manpage I described above is actually realised
with the sane-utils package, the files are part of that
I checked the whole procedure on a fresh 16.04 install.
To start saned.socket first I needed to run
`sudo systemctl start saned.socket`
However, in /usr/share/doc/sane-utils/README.Debian I found the
solution: To use socket.saned from startup, you have to run
`sudo systemctl enable
I don't need the files in /etc/systemd/system, the default ones work
after I removed the "new" ones:
Loaded: loaded (/lib/systemd/system/saned.socket; enabled; vendor preset:
enabled)
.
Loaded: loaded (/lib/systemd/system/saned@.service; indirect; vendor preset:
enabled)
I don't recall using
There actually was an update for systemd (as jurgen already posted), so
probably there was a "fix" includes, who knows...
I can confirm that my setup is back to stock config, since I even reinstalled
sane-utils to make sure. I don't have to explicitly start saned.socket, it
works after every
With systemd used in 16.04 (xenial is 16.04, not 16.10, that will be
released in october...) saned is not meant to be started manually.
saned.socket is listening for incoming requests. saned is started when a
program like XSane or scanimage are started and request a start of
saned, too. There are
I don't know if kubuntu ships systemd. The command is `systemctl status
saned.socket`, sorry about that typo in the post above...
If you just used the scanner plugged into an usb socket of your machine,
and not the net-backend, there was no need to configure sane manually...
We are talking about
** Summary changed:
- sane service masked and cannot be unmasked
+ saned.service masked and cannot be unmasked
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1577137
Title:
I have the same problem, but at least found a workaround.
The man-page for saned
(http://manpages.ubuntu.com/manpages/xenial/man8/saned.8.html) shows a
solution using systemd. Two config-files are needed in
/etc/systemd/system, saned.socket and saned@.service.
With those files saned seem to
** Attachment added: "saned.socket"
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1577137/+attachment/4666733/+files/saned.socket
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
@ jurgen:
Perhaps you should have a look at https://wiki.ubuntuusers.de/SANE-
Scanserver_im_Netzwerk/, judging from your email address you might be
able to read german. Much about saned is documented there, I added my
solution just the other day.
--
You received this bug notification because
Another Workaround: Don't use systemd for saned. I removed
/lib/systemd/system/saned.service
/lib/systemd/system/saned.socket
/lib/systemd/system/saned@.service,
as well as the "new" files I added in
/etc/systemd/system/saned.socket
/etc/systemd/system/saned@.service,
configured saned as
Hi!
I guess that is a Simple Scan problem - afaik Simple Scan is not able to
use network scanners; at least I can't use network scanners with it, and
can't recall that it was possible with earlier versions. Have you tried
xsane? If scanimage -L finds the network scanner, xsane should work too.
Hi!
I tried to start simple scan with
#SANE_NET_HOSTS=XXX.XXX.XXX.XX simple-scan
and after some time it actually started, using the network scanner on
XXX.XXX.XXX.XX, using a saned process.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
13 matches
Mail list logo
