Description of problem: Saned provides a way to configure a network-listening scan server. That is, on the machine with the scanner attached, saned listens on the network for connections from other machines that can then use the remote scanner to scan documents. It's all documented in the manpage, quite well in fact. Except that the systemd instructions don't seem to quite work. Version-Release number of selected component (if applicable): 1.0.24-7.fc20 How reproducible: 100% Steps to Reproduce: 1. Follow instructions in the saned manpage 2. Create saned user/group (not documented above) 3. Enable and start the services in systemd 4. Configure sane client to use network scan server Actual results: Client should be able to scan Expected results: saned fails to get started Additional info: The real solution here is to provide a new package, called perhaps sane-network or sane-server or something that packages up all of the bits (user/group, systemd configuration, etc.) needed to _easily_ configure a network scan server with sane.
I hit similar issue when attempting to use a networked all-in-one printer HP Photosmart Estation. The printer is recognized but not the scanner which can only be access through web. It would be nice to get an unit for these networked scanners.
(In reply to Luya Tshimbalanga from comment #1) > I hit similar issue when attempting to use a networked all-in-one printer HP > Photosmart Estation. The printer is recognized but not the scanner which can > only be access through web. > It would be nice to get an unit for these networked scanners. This particular problem sounds more like a duplicate of bug 1065549. The network-listening scan server Brian mentions ('saned') is not related at all to real network scanners. I do have the same issue as Brian: I don't manage to configure saned on one computer so I can access the usb-attached scanner from another computer.
It looks to me bug 1091566 has a patch to implement this enhancement request. Perhaps this bug could be marked as a duplicate of bug 1091566 ?
*** This bug has been marked as a duplicate of bug 1091566 ***