Bug 7987

Summary:	3alpha3 - systemd-udevd: specified group 'scanner' unknown
Product:	Mageia	Reporter:	claire robinson <eeeemail>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	davidwhodgins, dmorganec, fundawang, george, mageia
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
See Also:	https://bugs.mageia.org/show_bug.cgi?id=7295
Whiteboard:	3beta2
Source RPM:	sane	CVE:
Status comment:

Description claire robinson 2012-11-05 18:26:00 CET

Noticed pre-3alpha3 classic installer dvd with both kde & gnome installs, possibly also lxde etc too.

seems to stem from the last few lines on /lib/udev/rules.d/60-libsane.rules


No group 'scanner' exists

claire robinson 2012-11-05 18:26:17 CET

Whiteboard: (none) => 3alpha3

Comment 1 claire robinson 2012-11-05 18:26:56 CET

above rule is part of sane-backends rpm

Manuel Hiebel 2012-11-15 18:25:52 CET

CC: (none) => dmorganec, fundawang, mageia
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=7295

Comment 2 Colin Guthrie 2012-11-15 18:44:21 CET

Seems fedora patch away the group.

http://pkgs.fedoraproject.org/cgit/sane-backends.git/tree/sane-backends-1.0.23-udev.patch?id=ad47c78c61c0836bf62db568729bd05c061732a3


I guess they rely on ACLs for this which makes sense to me.

Comment 3 Colin Guthrie 2012-11-15 18:49:43 CET

Note, that we may also want to run sane-desc manually in the spec to ensure we get ACL style rules generated as fedora do:

http://pkgs.fedoraproject.org/cgit/sane-backends.git/tree/sane-backends.spec?id=ad47c78c61c0836bf62db568729bd05c061732a3#n135

Comment 4 Dave Hodgins 2013-01-22 21:07:12 CET

Still present is Mageia 3 beta 2.

CC: (none) => davidwhodgins
Whiteboard: 3alpha3 => 3beta2

Comment 5 George Mitchell 2013-03-28 05:24:40 CET

This problem is still present in current Beta 3 and current Cauldren.

CC: (none) => george

Comment 6 George Mitchell 2013-04-26 03:51:13 CEST

Still present in RC.  Very low priority, of course, because it has no effect on anything other than the system logs.  But it is an irritation as are a number of low level idiocies that plague system logs release after release.  The problem, of course, likely lies upstream, in this case with the sane organization.  If their software EXPECTS a group "scanner", then they should be INCLUDING the software to CREATE the group "scanner", ACLs or no ACLs.

Comment 7 Colin Guthrie 2013-04-26 10:44:49 CEST

Well I only commented on it above technically. I was hoping the maintainer would have addressed it.

For the short term, I've simply added the group. I think longer term, we should ditch it but I don't want to rock the boat this near release.

Fixed in svn and push requested.

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

Comment 8 George Mitchell 2013-04-27 05:04:59 CEST

Colin, Thanks for addressing this in the short term.  It seems like these group problems are stemming from an archaic permissions approach used by Ubuntu.  The Red Hat people rightly want to move everything toward ACLs and Policy Kit.  The problem on the user side is that at this point we are stuck in the middle and have to put up with the bogus messages flowing out on the journal.  Since SOMETHING is trying to reference the group, I think it is appropriate at this point to simply create the group as you are doing and then work on a long term plan to remove all referrences to the group globally in one synchronized operation.  I think Red Hat IS working on that, and if they are upstream to Mageia in this case, hopefully the fix will just eventually flow through.  But you ARE correct, the whole thing is misguided, unneeded, and needs to be trashed.  I am currently noting the same problem with group "plugdev".  Thanks again for dealing with it for us.  - George