Bug 11360

Summary:	When trying to scan via network getting "Invalid arguments"
Product:	Mageia	Reporter:	Paulo Silva <paulo>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	dmorganec, fundawang, luis.daniel.lucio, mageia, paulo
Version:	3	Keywords:	Triaged
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	sane-1.0.23-7.mga3.src.rpm	CVE:
Status comment:

Description Paulo Silva 2013-10-02 15:32:53 CEST

Description of problem:

After configure saned to server a scanner via network and configure the client machine to access the server's scanner, get the error "invalid arguments" as response for scanimage -d net:server_ip:device_id.

The /var/log/messages log at server indicates the client has accessed the server, the access was granted, but /usr/sbin/saned quit shortly.

After some search and try, I realized that the user "saned" was not part of "scanner" group. After I added the group "scanner" to the user "saned", all worked just fine.

So I think that the package installation isn't setting correctly the groups attribuitons for the user saned.

Reproducible: 

Steps to Reproduce:

Paulo Silva 2013-10-02 15:34:49 CEST

CC: (none) => paulo

Comment 1 Manuel Hiebel 2013-10-02 22:03:12 CEST

is it indeed not the case http://svnweb.mageia.org/packages/updates/3/sane/current/SPECS/sane.spec?view=markup#l508

Keywords: (none) => Triaged
CC: (none) => dmorganec, fundawang, luis.daniel.lucio, mageia

Comment 2 Marja Van Waes 2015-03-31 16:02:34 CEST

Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

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