On Mon, 12 Oct 2020 10:47:47 +0200 =?ISO-8859-1?Q?J=F6rg_Frings-F=FCrst? = <debian@jff.email> wrote: > tags 971584 + pending > thanks > The issue with the /var/lock/sane directory is fixed with > > commit 736573a8db4bd098da28a4831ce4c601f880aacd > Hello Jörg, I tested the change in the commit but it did not work for me : - with systemd, the /var/lock/sane directory does not survive a reboot because /var/lock is volatile (/var/lock is a link to /var/run, see /usr/lib/tmpfiles.d/legacy.conf). I solved this by creating a tmpd-file with: d /var/lock/sane 0775 root scanner - - in it - but it is not enough, I had to put myself in the scanner group, something I did not need with 1.0.27 version.
By the way, why giving /var/lock/sane rights to "saned" exclusively instead of "scanner" ? (It is just a question, I do not know myself the right thing to do). The saned group is created when installing sane-utils and by default sane-utils adds "saned" to the scanner group. Moreover, sane-utils is not always installed (not necessary for a local scanner accessed by a client like simple-scan). Best regards Pascal
