https://bugzilla.novell.com/show_bug.cgi?id=438867
User jsmeix@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=438867#c3
Johannes Meixner changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jsmeix@novell.com
AssignedTo|jsmeix@novell.com |bnc-team-screening@forge.provo.novell.com
--- Comment #3 from Johannes Meixner 2008-10-31 02:20:59 MDT ---
I do not find anything in attachment #248160
about the YaST scanner module
so that it cannot be a bug there.
Perhaps your scanner was set up full automated
as described in bug #347943 so that in your case
you might got the problem described in
https://bugzilla.novell.com/show_bug.cgi?id=340173#c5
But this cannot be true either because
according to /etc/udev/rules.d/55-libsane.rules
the Epson GT-9300(UF) has the USB IDs 0x04b8:0x011b
and this are also listed in
/etc/udev/rules.d/56-sane-backends-autoconfig.rules
but here with "sane_backend_epkowa"
(i.e. using the "epkowa" driver) which does not match
to "epson:libusb:001:002" in comment #0
(i.e. using the "epson" driver).
It would have been nice if you described how you did
set up your scanner and not let us do blind guessing via
inspecting whatever files what there might have happened
on your particular system.
Background information:
Since a longer time normal-user access for scanners is granted
via the udev/HAL/hal-resmgr machinery which sets an ACL
for the scanner's device file.
Run lsusb to determine the current USB bus and device number
and the run e.g.
getfacl /dev/bus/usb/001/002
(replace bus and device number 001/002 by what is currently
shown by the lsusb command for your scanner)
to see if an ACL is set and if yes, which one and for which user.
By default only users which are logged in directly at the computer
(i.e. via console "login" or via KDM/XDM but not via remote login)
get access granted via the udev/HAL/hal-resmgr machinery.
It is a well known problem since this machinery is used
that it does not work reliably. I am neither a USB expert
nor an expert regarding udev and/or HAL and/or hal-resmgr
but as far as I see, the whole machinery seems to be
somewhat overcomplicated: hal-resmgr depends on HAL (and PAM)
and HAL depends on udev which depends on the USB system.
Therefore any issue somewhere in this stack can result
whatever failure for normal users (e.g. compare bug #434540).
The only thing in the YaST scanner module which makes
settings for HAL is
/usr/lib/YaST2/bin/test_and_set_scanner_access_permissions
It writes
/etc/hal/fdi/policy/10osvendor/80-scanner.fdi
if the device is not already listed in
/etc/hal/fdi/policy/10osvendor/70-scanner.fdi
(the latter belongs to the sane-backends RPM).
The YaST scanner module runs it when it set up a
scanner and also via the "Other"->"Test" functionality.
It does also a test whether or not it looks o.k.
that the udev/HAL/hal-resmgr magic works so that
normal users would get access permissions, see bug #340173.
You can have a look at
/usr/lib/YaST2/bin/test_and_set_scanner_access_permissions
---------------------------------------------------------------------
To access the scanner as normal user,
udev, HAL, and hal-resmgr are needed to grant
appropriate access permissions automatically.
Therefore the scanner model must be known to HAL.
If the scanner is not known to HAL, a re-plug
of a USB scanner should help.
Otherwise a reboot should be done to restart
the whole udev/HAL/hal-resmgr machinery.
Check if the scanner is listed in the 'lshal' output.
.
If even a reboot does not help, you could access
the scanner via the 'saned' as a workaround.
For this workaround choose 'scanning via network'
and select the 'local host configuration'.
---------------------------------------------------------------------
Usually this workaround is the only feasible solution for
non-experts to get access permissions for normal users
if there is an issue in the udev/HAL/hal-resmgr magic.
Additionally see
http://en.opensuse.org/SDB:Configuring_Scanners_from_SUSE_LINUX_9.2
---------------------------------------------------------------------
libusb + resmgr + PAM
Note that the details change from version to version.
Additionally there will be further enhancements
(e.g. "udev", "HAL", "hal-resmgr",...).
An article regarding scanner setup cannot describe
all the details about USB, hotplug, udev, HAL, resmgr/hal-resmgr,
PAM, and so on. Refer to the appropriate specific documentation
if there are problems in one of these areas.
---------------------------------------------------------------------
By the way:
According to /etc/udev/rules.d/55-libsane.rules
the scanner device node/dev/bus/usb/xxx/yyy
should be in the "lp" group so that it should work
to add the normal users which should use the scanner
to the group "lp".
An "automated add of normal users to the lp group"
cannot be done, see bug #349084 in particular see
https://bugzilla.novell.com/show_bug.cgi?id=349084#c9
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.