Bug#950646: sane-utils: saned does not work if starteed via systemd

2020-09-30 Thread Jörg Frings-Fürst
fixed 950646 sane-backends/1.0.31-2 thanks Hello, this bug ist fixed in version 1.0.31-2. The requested rule is now installed. So I close this bug. CUJörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAc

Bug#950646: sane-utils: saned does not work if starteed via systemd

2020-09-01 Thread Bernhard Übelacker
Hello, searched the upstream issue tracker and found following, that seems to match your situation. https://gitlab.com/sane-project/backends/-/issues/275 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958074 Kind regards, Bernhard

Bug#950646: sane-utils: saned does not work if starteed via systemd

2020-09-01 Thread Bernhard Übelacker
Hello Patrick, I found another environment to increase verbosity another little bit, please see below. Your output points also into the direction of an permission problem like what Stefan described in the first message. The unit file starts the saned server with user and group saned. On the ot

Bug#950646: sane-utils: saned does not work if starteed via systemd

2020-08-27 Thread Patrick Holthuizen
Thank you for the additional information. This gives me an additional error: aug 27 14:09:01 eaze saned[6203]: [plustek] sanei_usb_open failed: Permission denied (13) aug 27 14:09:01 eaze saned[6203]: [plustek] open failed: -1 See also the attached log file. aug 27 14:09:01 eaze saned[6203]: [san

Bug#950646: sane-utils: saned does not work if starteed via systemd

2020-08-26 Thread Bernhard Übelacker
Hello Patrick, you might add in the sane unit file a backend specific logging environment too. That should give much more details for the plustek module. Kind regards, Bernhard /lib/systemd/system/saned@.service: Environment=SANE_CONFIG_DIR=/etc/sane.d SANE_DEBUG_DLL=255 SANE_DEBUG_PLUSTEK=12

Bug#950646: sane-utils: saned does not work if starteed via systemd

2020-08-21 Thread Patrick Holthuizen
Reproduced the steps as indicated by Bernhard. I got the same results as Bernhard with the backend "test". For the actual scanner I use the backend plustek. scanimage -L lists the correct scanner. Executing the actual scan gives an error: scanimage: open of device net:localhost:plustek:0 failed:

Bug#950646: sane-utils: saned does not work if starteed via systemd

2020-08-18 Thread Bernhard Übelacker
Hello Stefan, hello Patrick, I am not specifically involved in packaging sane but tried to reproduce your issue. These were the steps I tested: - systemctl enable saned.socket - systemctl start saned.socket - activated the backend "test" in /etc/sane.d/dll.conf - added the "remote" server localho

Bug#950646: sane-utils: saned does not work if starteed via systemd

2020-02-04 Thread stefan
Package: sane-utils Version: 1.0.27-3.2 Severity: important Manual starting of saned (as user saned) works. I can access the scanners remotley. But if saned is started via systemd, it does not work. scanimage -L on a client does not find anything. `systemctl status saned.socket` prints: > ● s