$ rpm -qa sane-backends sane-backends-1.0.27-5.fc27.x86_64 Problem: the RPM post install scripts of sane-backends does not install systemd configuration files. What a pain in the neck to have to do it manually. Not everyone is a Linux litter system administrator (I am, but it is still a pain in the neck). (Samba, etc., etc., etc. all come with them.) Request for Enhancement: Please include these scripts Also, please make sure explicit systemd support is also included $ rpm -ql sane-backends | grep syst $ <nothing> Many thanks, -T From the man page: SYSTEMD CONFIGURATION for systemd we need to add 2 configuation files in /etc/systemd/system. The first file we need to add here is called saned.socket. It shall have the following contents: [Unit] Description=saned incoming socket [Socket] ListenStream=6566 Accept=yes MaxConnections=1 [Install] WantedBy=sockets.target The second file to be added is saned@.service with the following con‐ tents: [Unit] Description=Scanner Service Requires=saned.socket [Service] ExecStart=/usr/sbin/saned User=saned Group=saned StandardInput=null StandardOutput=syslog StandardError=syslog # Environment=SANE_CONFIG_DIR=/etc/sane.d SANE_DEBUG_DLL=255 Is you need to set an environment variable for saned like SANE_CON‐ FIG_DIR you will have to remove the # on the last line and set the variable appropriately. Multiple variables can be set by separating the assignments by spaces as shown in the example above. Unlike (x)inetd systemd allows debugging output from backends set using SANE_DEBUG_<backend_name> to be captured. With the service unit as described above, the debugging output is forwarded to the system log.
Also, it would be nice if the "man page" included # systemctl enable saned.socket (one time only) # systemctl -l start saned.socket So the user knew which syctemd script to enable and start
Hi, these files are already part of subpackage sane-backends-daemon in Fedora, because they aren't needed when you usually use scanner. Nowadays when you use scanner, scanning program communicate with scanner directly, not through daemon. The saned daemon is used usually for remote scanning (like remote client accesses server, where scanning device is connected), which is not usual. I can move saned man pages (with your suggestion about enabling and restarting socket) to subpackage daemon, so it wouldn't be confusing about not being saned installed. Is it acceptable?
Created attachment 1357524 [details] proposed patch Proposed patch for saned manpage
(In reply to Zdenek Dohnal from comment #2) > Hi, > > these files are already part of subpackage sane-backends-daemon in Fedora, > because they aren't needed when you usually use scanner. I did not have sane-backends-daemon installed, which explains a lot of things. Would you add something to the man page to the effect that it has to be installed for this to work? And at the bottom in the See Other Files section too. If you are using you computer as a workstation and are working with a lot of PDF's, Qoppa's PDF Studio is a necessity and is worth every dime they charge for it. Qoppa has an unlimited trial too (writes something across every other page when you save it). Qoppa uses this daemon method to scan into PDF Studio. So you can download it and try scanning for yourself. https://www.qoppa.com/pdfstudio/ > Nowadays when you > use scanner, scanning program communicate with scanner directly, not through > daemon. The saned daemon is used usually for remote scanning (like remote > client accesses server, where scanning device is connected), which is not > usual. That would be PDF Studio. > I can move saned man pages (with your suggestion about enabling and > restarting socket) to subpackage daemon, so it wouldn't be confusing about > not being saned installed. Is it acceptable? Yes, thank you! Also, is there any way you can port the new sane, backends and all, over to RHEL 7.x. They do not even have a sane-backends-daemons. This may be because their old, defunct version of sane (1.0.24) did not have the two broken out yet and sane-backends was compiled without daemon support.
(In reply to Todd from comment #4) > I did not have sane-backends-daemon installed, which explains a lot of > things. Would you add something to the man page to the effect that it has > to be installed for this to work? And at the bottom in the See Other Files > section too. I can add README.Fedora file into /usr/share/doc/sane-backends directory, in which I can explain that saned is located in sane-backends-daemon package. This file will be shipped with main package. I cannot change man page itself, because it is part of sane-backends project and this change is only for packaging sane-backends in Fedora - so patch would not be accepted by upstream and would stay as downstream patch. Downstream patches are last resort for us and IMHO man page change is not that critical to create downstream patch for it. (And creating README.Fedora file is even recommended by Fedora packaging guidelines in this case) > > I can move saned man pages (with your suggestion about enabling and > > restarting socket) to subpackage daemon, so it wouldn't be confusing about > > not being saned installed. Is it acceptable? > > Yes, thank you! Ok, I'll add it with README.Fedora file. > > Also, is there any way you can port the new sane, backends and all, over to > RHEL 7.x. They do not even have a sane-backends-daemons. This may be > because their old, defunct version of sane (1.0.24) did not have the two > broken out yet and sane-backends was compiled without daemon support. I'll explain it in RHEL bugzilla.
sane-backends-1.0.27-7.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-885866a718
sane-backends-1.0.27-7.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-885866a718
sane-backends-1.0.27-7.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.