http://bugzilla.novell.com/show_bug.cgi?id=554664
User jsmeix@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=554664#c3
Johannes Meixner changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
Info Provider| |nice@titanic.nyme.hu
--- Comment #3 from Johannes Meixner 2009-11-12 02:12:54 MST ---
1)
At first glance it looks like a duplicate of bug #542473
("HAL does not set ACL for normal user access
for USB devices with "scanner" capability")
See there how to check if this one is really a duplicate.
The best workaround to get those kind of HAL issues
out of sight is to use the YaST scanner module and:
-----------------------------------------------------------
.. you could access
the scanner via the 'saned' as a workaround.
For this workaround choose 'scanning via network'
and select the 'local host configuration'.
----------------------------------------------------------
In particular on a workstation in a trusted network
environment (e.g. when the Suse firewall protects it
from acceess from the external network zone / Internet)
this workaround should cause no security problems.
Alternatively - and to get additionally even the device status
information via hp-toolbox working:
In particular on a workstation in a trusted network
environment (e.g. when the Suse firewall protects it
from acceess from the external network zone / Internet)
you may change as a workaround in /etc/udev/rules.d/55-hpmud.rules
in the line (which is only here shown wrapped):
ATTR{idVendor}=="03f0", ATTR{idProduct}=="??17", OWNER="root",
GROUP="lp", MODE="664", ENV{sane_hpaio}="yes"
the MODE="664" to MODE="666" to allow any user read/write access.
2)
But because of comment #2 "same error symptoms ... when run as root"
it could be something else here or additionally to the above
udev/HAL bug something else could prevent access even as root.
Perhaps you have whatever special add-on security stuff
set up and running which could even jail root-processes
like AppArmor or SELinux or whatever else?
If yes, disable it and test scanning as root.
3)
Finally: the "udev-configure-printer: failed to claim interface"
message may indicate that whatever udev printer setup magic
simply failed to set it up correctly - in particular because
HP all-in-one devices must be set up with HPLIP's CUPS backend "hp"
and not with the generic CUPS backend "usb" because the latter
does not support scanning which could be a reason why scanning
fails for you in any case.
Therefore you should delete any print queue which may have been
already set up by whatever udev printer setup magic
(e.g. use the YaST printer module to do it) and then
set up the printer unit either with the YaST printer module
or as root by running "hp-setup" (HPLIP's setup tool)
and finally you may need to set up the scanner unit
with the YaST scanner module (but usually the scanner
driver "hpaio" is automatically activated in
/etc/sane.d/dll.conf via /etc/udev/rules.d/55-hpmud.rules).
Please report about your results for the above cases 1) 2) and 3).
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.