Lawrence Woodman <lwood...@vlifesystems.com> writes: > On 08/02/14 02:13, Mark Buda wrote: >> Or, it *did* happen, but something else changed it. What version of the >> "hal" package do you have installed? > I'm using version: 0.5.14-8
Well now I am really confused. The ACLs on the USB device do not include "group:scanner:rw-" or "user:whoeveryouare:rw-", which means that either (a) both the call to setfacl and the internal "uaccess" builtin failed, or (b) something afterwards reset the ACL. But the only thing after that is the HAL notification. But according to the changelog, they dropped ACL support in HAL in 0.5.13-4. Squeeze had 0.5.14-3, so the only thing I can think of is that you originally installed a pre-squeeze release, upgraded, and during the course of the upgrade, the "hal-acl-tool" program (which is no longer included) didn't get deleted, nor did the configuration files that tell HAL to run it and (if I'm reading the code correctly) delete pre-existing ACLs. I'm pretty sure this is not a SANE bug, but I don't know whose it is. Did you originally install a pre-squeeze release on this system? Do the files "hal-acl-tool" or "20-acl-management.fdi" exist on your system? I'm not sure where they would live. Can you remove the scanner device, and reinsert it while running strace -o /tmp/udev-strace.out -f -p UDEVDPROCESSID where, of course, UDEVDPROCESSID is the pid of udevd, and send /tmp/udev-strace.out. I have three udevd's running on my system, though, and I'm not sure why or which one does what... I will set up a VM running an old-enough Debian release and see what happens regarding HAL's ACL treatment when I upgrade. -- Mark Buda <her...@acm.org> I get my monkeys for nothing and my chimps for free. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
