Bug 26071 - saned cannot be started, systemd unit file is borked
Summary: saned cannot be started, systemd unit file is borked
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: José Jorge
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-14 17:29 CET by Frank Griffin
Modified: 2020-01-16 00:48 CET (History)
1 user (show)

See Also:
Source RPM: sane-1.0.28-1.mga8.src.rpm
CVE:
Status comment:


Attachments

Description Frank Griffin 2020-01-14 17:29:49 CET
Our unit file doesn't work, as it is setting stdin to NULL and stdout to syslog.  A corrected one can be found at https://bugzilla.redhat.com/show_bug.cgi?id=1091566#c8 .
David Walser 2020-01-14 18:22:33 CET

Source RPM: saned => sane-1.0.28-1.mga8.src.rpm
Assignee: bugsquad => lists.jjorge

Comment 1 Martin Whitaker 2020-01-14 22:40:41 CET
Our unit file works fine on my system. And it matches the example given in the saned man page.

CC: (none) => mageia

Comment 2 Frank Griffin 2020-01-14 23:00:31 CET
Actually, the man page gives two versions of the saned@.service, one for the case where saned has been compiled with systemd support, which matches the one we ship, and one for the case where saned has been compiled without systemd support, which matches the sample given by the link I provided (almost - the salient point being that it sets StandardInput to "socket").

So the question is whether we compile saned with systemd support.
Comment 3 Martin Whitaker 2020-01-14 23:28:39 CET
(In reply to Frank Griffin from comment #2)
> So the question is whether we compile saned with systemd support.

We do:

http://svnweb.mageia.org/packages/cauldron/sane/current/SPECS/sane.spec?view=markup#l344
Comment 4 Frank Griffin 2020-01-15 02:20:07 CET
OK, then it comes down to whether we believe the reporter in the link I provided, and/or whether modifying our provided service file(s) to his specifications actually fixes the problems we're seeing here.
Comment 5 Martin Whitaker 2020-01-15 09:47:50 CET
(In reply to Frank Griffin from comment #4)
> OK, then it comes down to whether we believe the reporter in the link I
> provided

See the later comment in that report:
https://bugzilla.redhat.com/show_bug.cgi?id=1091566#c18

> and/or whether modifying our provided service file(s) to his
> specifications actually fixes the problems we're seeing here.

As I reported on qa-discuss, it works for me as it is.
Comment 6 Frank Griffin 2020-01-15 15:17:16 CET
OK, since I haven't experienced the problem myself, I'll close this as WORKSFORME.  But it still doesn't explain why both the OP in the link and the OP in qa-discuss have the problem, or possibly whether it's in MGA7 and not cauldron.

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME

Comment 7 Martin Whitaker 2020-01-16 00:48:48 CET
Sorry, got the link wrong. The comment I meant to refer to is
https://bugzilla.redhat.com/show_bug.cgi?id=1091566#c16
which explains why the OP in your link had the problem and why we don't.

Having followed my suggestions, the OP in qa-discuss (Herman) no longer has a problem.

drakscanner does need to be updated though, as it tries to enable saned.service, whereas it should now enable saned.socket.

Note You need to log in before you can comment on or make changes to this bug.