Description of problem: Whenever I launch xsane, the system log files show: systemd-udevd[PID]: Process '/usr/bin/setfacl -m g:saned:rw ' failed with exit code 2. Version-Release number of selected component (if applicable): sane-backends-daemon-1.0.27-18.fc29.x86_64 How reproducible: Always Steps to Reproduce: 1. Watch the log files: journalctl -f | grep systemd-udevd 2. Launch xsane Actual results: An error message shows up: systemd-udevd[PID]: Process '/usr/bin/setfacl -m g:saned:rw ' failed with exit code 2. Expected results: No error should show up. Additional info: Apparently, ENV{DEVNAME} can be empty for some devices, so changing /usr/lib/udev/rules.d/66-saned.rules from: ENV{libsane_matched}=="yes", RUN+="/usr/bin/setfacl -m g:saned:rw $env{DEVNAME}" to: ENV{libsane_matched}=="yes", ENV{DEVNAME}!="", RUN+="/usr/bin/setfacl -m g:saned:rw $env{DEVNAME}" does the trick.
Hi Philippe! thank you for reporting the issue and the patch! Would you mind testing the fixed package? Because I only have device, which has DEVNAME defined. Here are the rpms for testing https://koji.fedoraproject.org/koji/taskinfo?taskID=32412287
Zdenek, I've tested the 1.0.27-21.fc29 packages from the koji build and the error message is gone. Scanning also works properly :-) Phil.
sane-backends-1.0.27-22.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-708a2e3e14
sane-backends-1.0.27-22.fc29 has been pushed to the Fedora 29 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-2019-708a2e3e14
sane-backends-1.0.27-22.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.
Confirming that the released sane-backends-daemon-1.0.27-22.fc29 update fixes the issue.