We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
does this ever occur in trusty or later?
** Changed in: sane-backends (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: sane-backends (Ubuntu)
Assignee: (unassigned) => Rolf Leggewie (r0lf)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I am running 12.04 (Precise). On my machine, the problem turned out to
be that the saned user was not part of the scanner group. So the simple
solution for me was to add the saned user to the scanner group with the
command:
sudo adduser saned scanner
Diagnosing the problem was made difficult by
This is still an issue in 12.04.
In order to have scanbuttond (and saned, should I need it in the future)
run as user saned, I had to add udev rule:
99-libsane.rules
ENV{libsane_matched}=="yes", OWNER="saned", GROUP="scanner"
Before the rule:
# file: dev/bus/usb/001/005
# owner: root
# group: ro
i've tried reconfiguring and reinstalling libsane and sane-utils packages.
scanner group was not created
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/773617
Title:
Saned group is missing permissio
Psy, on my oneiric machine, I have a scanner group, I also have a saned
group. I believe the problem is between these two groups. I've emailed
the maintainers to ask for advice.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
OK sounds like we've found the problem with the package. We need to
still create the scanner group in the libsane package. We should get
this information to the debian/ubuntu package maintainer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
OK, tested setfacl rule...
it does not work because there is no scanner group.
But it does work with existing groups.
also 40-libsane.rules is THE ONLY udev rule that contains setfacl
command. Everything else in the system assigns groups with GROUP=
Anyway, libsane package should create a group t
So does setfacl work, have you tried to run the command and see what
happens and why it fails?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/773617
Title:
Saned group is missing permissions to acces
Hm...
If I place GROUP= definition in libsane rules (instead or alongside setfacl
rule), it works.
Other devices in ubuntu, such as disk, cdrom, audio, video are handled
by both standard GROUP= rules and udev-acl.
$ getfacl /dev/sda1
getfacl: Removing leading '/' from absolute path names
# file
problem is in /lib/udev/rules.d/40-libsane.rules which resides in
libsane package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/773617
Title:
Saned group is missing permissions to access scanners v
There is the line in libsane rules:
ENV{libsane_matched}=="yes", RUN+="/bin/setfacl -m g:scanner:rw $env{DEVNAME}"
But it does not work
I've placed a test line nearby
ENV{libsane_matched}=="yes", RUN+="/usr/bin/touch /tmp/udev-scanner-test"
it works.
acl package is installed, /bin/setfacl exist,
Today udev package was upgraded in Archlinux. Change notification states that
it now uses upstream udev-acl rules for managing devices.
Funny thing: both standard group assignment AND udev-acl mechanisms work
simultaneously. I've just tested.
$ getfacl /dev/bus/usb/008/002
getfacl: Removing lead
The correct fix is to change udev-acl to accept a group param to make
sure it goes into the right group, or give the saned user special
privileges.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/773617
As files in /lib/udev/rules.d will be updated by package upgrades, the
correct workaround is to put corrected 70-udev-acl.rules to
/etc/udev/rules.d/ (file of the same name will override the rule in
/lib...)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
If I understand correctly, current behavior is to dynamically grant scanner
access to currently active user via consolekit.
1. this is overengineering
2. this is useless overengineering. What the point in doing that? Just to use
consolekit for something?
Why not just put new regular users to sca
_replacing_
ENV{libsane_matched}=="yes", TAG+="udev-acl"
with
ENV{libsane_matched}=="yes", GROUP="saned"
works
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/773617
Title:
Saned group is missing per
Is there any sense in using a super-stupid program, that practically
does nothing, instead of convenient unix-groups that can do whatever you
ask?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/773617
It's encoded in a C program the acl problem called from that rules file.
I think it's changing the owner back to root. There's a program to list
the extended permissions on a file. the program is super stupid about
being able to expand what groups and users can access a file.
--
You received this
i've inserted it right after that line.
OK, let's change the approach. Where are acl parameters? Maybe there is
a way to add acl item with 'scanner' group using new method?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
You need to add the rule to the middle of the file, where it does the
acl flag.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/773617
Title:
Saned group is missing permissions to access scanners via
adding group rule to 70-acl.rules does not work also
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/773617
Title:
Saned group is missing permissions to access scanners via udev-acl
To manage notific
it is weird how group management is being cut out from the system.
maybe ACL's and consolekit are good tools, but why dismantle unix groups? They
work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/77
Psy, In maverick I added:
ENV{libsane_matched}=="yes", GROUP="saned"
to /lib/udev/rules.d/70-acl.rules
But I also think that saned should be fixed to use the acl instead of
looking for the saned group, it's weird how any users are allowed to
access it but saned is not.
--
You received this bug
Tried to restore by adding
/etc/udev/rules.d/90-sane-group-fix.rules
with following content:
ENV{libsane_matched}=="yes", GROUP="saned"
but device still gets in root group
is there a way to add group support without breaking something?
--
You received this bug notification because you are a m
Stumbled on this, and I'm SHOCKED.
Why, in a name of what the group mechanism was removed?
It was simple, stable, efficient, KISS, unix-way of accessing scanners!
Please restore the group mechanism! You broke something that worked like
fine-tuned clockwork. It is the recommended way in SANE manua
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: sane-backends (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/773617
Title:
27 matches
Mail list logo
