https://jff.email/cgit/sane-
backends.git/tree/debian/libsane1.README.Debian (under "SETUP")
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/236956
Title:
sane devices should not be managed by console
https://jff.email/cgit/sane-
backends.git/tree/debian/libsane1.README.Debian (under "SETUP")
** Changed in: sane-backends (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
i have also a problem with scanner after precise pangolin 12.04
i have informed here:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1080787/comments/10
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1080787/comments/11
is it the same problem?
is it possible to correc
Brian, are you sure? I've ssh'd into a precise box today and cannot
access the attached scanner as an ordinary user. Scanning being broken
for so many years and differently in every release is really
frustrating!
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Appears to be no longer an issue in ubuntu 12.04
If I ssh to my box and try to access scanner from the shell (e.g.
scanimage -L) the device is not accessible; but once I add myself to
group 'scanner' and logout and back in again, it works fine.
There is clearly the correct ACL here.
$ ls -l /dev
I tried to work-around thusly:
sudo polkit-auth --user saned --grant org.freedesktop.hal.device-
access.scanner
But no joy. The machine is headless and gnomeless, and I'd like to keep
it that way. Any ideas?
--
sane devices should not be managed by consolekit
https://bugs.launchpad.net/bugs/
Could someone please describe and document the command-line version of
the explicit grant needed so that 'scanimage|scanadf' works always for
that user, even for an ssh into the machine or cron script?
Are the Ubuntu 8.04.1 /etc/udev/rules.d/45-libsane.rules a simple file-
copy to install under 8.
Indeed this could be fixed by reintroducing the udev rules, so that the
devices are accessible by *either* being on a local console, *or* being
in the 'scanner' group (as in gutsy and earlier).
** Changed in: consolekit (Ubuntu)
Status: New => Invalid
** Changed in: sane-backends (Ubuntu)
Hi,
To me it seems like this bug would be fixed if the policy for the scanner was
changed to allow saned to access it explicitly, so that both console users and
the sane service can use the device, is this correct?
Thanks,
James
--
sane devices should not be managed by consolekit
https://bugs.
Please do not consider this bug to be fixed. It is affecting server
edition, and polkit-gnome-authorization is not a convenient
configuration option on that platform.
--
sane devices should not be managed by consolekit
https://bugs.launchpad.net/bugs/236956
You received this bug notification beca
Please consider this bug to be (almost) fixed.
Following the instructions that I received on the hal mailing list, I
have used polkit-gnome-authorisation to change the system behaviour, so
that the ownership of the USB scanners is not anymore given to the
current console user, but to user "saned"
BTW, also note that if I have a machine with a scanner attached to it
and 10 users that might seat at the console, there is a chance that I do
not want to give all 10 the privilege to use the scanner. So, it is
just nice to have a scanner group, where I can put the users allowed to
use the scanner
12 matches
Mail list logo
