<p dir="ltr">Thanks Daniel, </p>
<p dir="ltr">maybe that was the only thing I had to do, I don't know yet anymore. <br>
I tried first enabling the service with systemctl enable saned.service<br>
assuming that it is a service ( in the background ) but with no luck just getting the message that saned is masked.<br>
I must stated it doesn't come in mind that I had to enable saned.socket instead.</p>
<p dir="ltr">Well it's running now again, but it is truly a bad experience to get thrown in cold water through the update from 14.04 -> 16.04 LTS and have to handle a completely new init system. :/<br>
Took a lot of time and emptied my coffee box.</p>
<p dir="ltr">Kind regards,</p>
<p dir="ltr">Ingo Weigert</p>
<div class="gmail_quote">Am 02.05.2016 13:35 schrieb "Daniel Curran-Dickinson" <<a href="mailto:daniel@daniel.thecshore.com">daniel@daniel.thecshore.com</a>>:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 16-05-01 02:57 PM, Jörn-Ingo Weigert wrote:<br>
> Well, my impression is that this is to 99% a result of the guys at<br>
> Ubuntu cause they ignored the fact of an enabled running saned service,<br>
> indicated through RUN=yes option and a<br>
> Tending misleading configuration hint in the saned(8) man page, there<br>
> the near distance of a SysV Init and a systemd supported saned-config<br>
> option.<br>
><br>
> though it should be clear that the saned should be started through<br>
> systemctl command but this info is missing in the man page and I suggest<br>
> that that info should be noted in the saned(8) man page within the<br>
> systemd section.<br>
><br>
> There was a related bug report on Debian bug tracker which lead me to<br>
> the right solution at the end..<br>
<br>
If it told you edit files, then the person contributing that answer was<br>
in fact incorrect. As stated in my last email all that is required is:<br>
<br>
systemctl enable saned.socket<br>
<br>
(as root)<br>
<br>
Regards,<br>
<br>
Daniel<br>
><br>
> Kind regards<br>
><br>
> Ingo Weigert<br>
><br>
> Am 01.05.2016 19:45 schrieb "m. allan noah" <<a href="mailto:kitno455@gmail.com">kitno455@gmail.com</a><br>
> <mailto:<a href="mailto:kitno455@gmail.com">kitno455@gmail.com</a>>>:<br>
><br>
> Thanks for the info. I'm not sure how much of this configuration comes<br>
> with sane-backends, and how much is provided by the distro. Perhaps<br>
> you could also ask the distro about it?<br>
><br>
> allan<br>
><br>
> On Sun, May 1, 2016 at 12:59 PM, Jörn-Ingo Weigert<br>
> <<a href="mailto:jiweigert@gmail.com">jiweigert@gmail.com</a> <mailto:<a href="mailto:jiweigert@gmail.com">jiweigert@gmail.com</a>>> wrote:<br>
> > Info for all who are affected that saned stopped working after<br>
> upgrade to<br>
> > Ubuntu 16.04 with using systemd (which is default in Ubuntu 16.04)<br>
> ><br>
> > The problem is that saned stopped working after upgrade, cause the<br>
> > saned.service is indicated as "marked" when you try to start it via:<br>
> ><br>
> > `sudo service saned start´ or `systemctl start saned.service´.<br>
> ><br>
> > The solution was to modify the related systemd files as the<br>
> > delivered/generated files in the sane-utils package did not the<br>
> job right.<br>
> ><br>
> > 1. Check that the RUN option in file /etc/default/saned is set to<br>
> RUN=no (As<br>
> > we dont use systemd AND NOT SysV Init!!)<br>
> ><br>
> > 2. I deleted the file /lib/systemd/system/saned.service as it was<br>
> linked to<br>
> > /dev/null (why?)<br>
> ><br>
> > 3. The file /lib/systemd/system/saned.socket should have this<br>
> (unmodified)<br>
> > content:<br>
> ><br>
> > [Unit]<br>
> > Description=saned incoming socket<br>
> ><br>
> > [Socket]<br>
> > ListenStream=6566<br>
> > Accept=yes<br>
> > MaxConnections=1<br>
> ><br>
> > [Install]<br>
> > WantedBy=sockets.target<br>
> ><br>
> > 4. The content of the file /lib/systemd/system/saned@.service<br>
> should be<br>
> > changed to:<br>
> ><br>
> > [Unit]<br>
> > Description=Scanner Service<br>
> > Requires=saned.socket<br>
> ><br>
> > [Service]<br>
> > ExecStart=/usr/sbin/saned<br>
> > User=saned<br>
> > Group=saned<br>
> > StandardInput=null<br>
> > StandardOutput=syslog<br>
> > StandardError=syslog<br>
> > Environment=SANE_CONFIG_DIR=/etc/sane.d<br>
> > # Environment=SANE_CONFIG_DIR=/etc/sane.d SANE_DEBUG_DLL=255<br>
> ><br>
> > [Install]<br>
> > Also=saned.socket<br>
> ><br>
> > Where "StandardInput" should be set to "StandardInput=null"<br>
> ><br>
> > 5. To start saned on bootup use the command:<br>
> ><br>
> > `systemctl enable saned@.service´<br>
> ><br>
> > 6. Check in /etc/sane.d/net.conf if "connect_timeout=60" is not<br>
> commented<br>
> > out and localhost / your servers ipadress is listed to check via<br>
> > [simple-scan | xsane | scanimage -L] on the server, that the<br>
> scanner is<br>
> > available after a REBOOT.<br>
> ><br>
> > 7. Check if your client-ipadresses / -FQDN are listed in<br>
> > /etc/sane.d/saned.conf otherwise they are not allowed to connect!<br>
> ><br>
> > 8. Check if the appropriate backend is enabled in<br>
> /etc/sane.d/dll.conf for<br>
> > your scanner-model<br>
> ><br>
> > 9. Follow the hints about the permissions you may have to set to the<br>
> > usb-device / inside the udev-file:<br>
> /lib/udev/rules.d/40-libsane.rules .<br>
> ><br>
> > 10. If you can scan successfully local on your server / pc with<br>
> one of the<br>
> > scanner frontends then press your thumbs and reboot your server / pc<br>
> ><br>
> > 11. After reboot, `scanimage -L´ should list the USB-device<br>
> > (usb:usbport:xxx) and the provided network device<br>
> > (net:<ip>:<device_serial_number>) for your scanner<br>
> ><br>
> > Check with `systemctl status saned.socket´ and `systemctl status<br>
> > saned@.service´ if both are active/ready.<br>
> ><br>
> ><br>
> > Now you should be able to scan remotly again<br>
> ><br>
> > Hope this little advises help someone.<br>
> ><br>
> > Ingo Weigert<br>
> ><br>
> > --<br>
> > sane-devel mailing list: <a href="mailto:sane-devel@lists.alioth.debian.org">sane-devel@lists.alioth.debian.org</a><br>
> <mailto:<a href="mailto:sane-devel@lists.alioth.debian.org">sane-devel@lists.alioth.debian.org</a>><br>
> > <a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel" rel="noreferrer" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel</a><br>
> > Unsubscribe: Send mail with subject "unsubscribe your_password"<br>
> > to <a href="mailto:sane-devel-request@lists.alioth.debian.org">sane-devel-request@lists.alioth.debian.org</a><br>
> <mailto:<a href="mailto:sane-devel-request@lists.alioth.debian.org">sane-devel-request@lists.alioth.debian.org</a>><br>
><br>
><br>
><br>
> --<br>
> "well, I stand up next to a mountain- and I chop it down with the edge<br>
> of my hand"<br>
><br>
><br>
><br>
<br>
--<br>
sane-devel mailing list: <a href="mailto:sane-devel@lists.alioth.debian.org">sane-devel@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel" rel="noreferrer" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel</a><br>
Unsubscribe: Send mail with subject "unsubscribe your_password"<br>
to <a href="mailto:sane-devel-request@lists.alioth.debian.org">sane-devel-request@lists.alioth.debian.org</a><br>
</blockquote></div>