Right! I never tried issuing the start command without the files in /etc. At that point I assumed it should just start working when I put the files there. Removing the files in /etc and explicitly stopping/restarting the saned.socket service, it indeed still works.
But this means the system is back to how it was when I first reported the issue. I guess there must have been an update to some systemd related package making the saned.socket service start on boot. However, I cannot see anything that seems relevant in the changelogs. I haven't rebooted since upgrading to Xenial, so it is difficult to say when that might have happened. Without the start command, systemctl status saned.socket reports "Active: inactive (dead)" To sum up: It seems that, confusingly, the saned service is masked and impossible to unmask by design, and instead the saned.socket service needs to be running for networked scanning to work. Since this is a multi purpose server, I am reluctant to reboot it. Can you confirm that everything on your setup is back to the stock config and that it still works after a reboot? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577137 Title: sane service masked and cannot be unmasked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1577137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
