saned does not have permission to access the scanner
Bug #229343 reported by
Paul Worrall
This bug report is a duplicate of:
Bug #236956: sane devices should not be managed by consolekit.
Edit
Remove
This bug affects 13 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
sane-backends (Ubuntu) |
Triaged
|
Medium
|
Unassigned | ||
Hardy |
Won't Fix
|
High
|
Unassigned |
Bug Description
Starting with Hardy, my scanner device is no longer owned by the group "scanner", instead (AIUI) the PolicyKit / ConsoleKit /HAL scheme uses ACLs to allow the user with the active session access to the scanner. However this scheme does not permit the SANE Network Demon "saned" to access the scanner and hence other machines on the network can no longer access the scanner.
Changed in sane-backends (Ubuntu Hardy): | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in sane-backends (Ubuntu Hardy): | |
status: | Triaged → Won't Fix |
Changed in sane-backends (Ubuntu): | |
importance: | Undecided → Medium |
assignee: | Martin Pitt (pitti) → nobody |
summary: |
- saned cannot access the scanner in Hardy + saned does not have permission to access the scanner |
To post a comment you must log in.
saned is started by inetd with user name "saned" so, hacking the file "/usr/share/ hal/fdi/ policy/ 10osvendor/ 20-acl- management. fdi" I created the attached file in "/etc/hal/ fdi/policy/ 20-acl- management. fdi" which ensures that user "saned" always has access to the scanner. This seems to resolve the problem.