Your request / output of lshal and getfacl /dev/sg2
kay.sievers at vrfy.org
Mon Jan 5 16:29:13 PST 2009
On Mon, Jan 5, 2009 at 17:41, Dieter Jurzitza
<dieter.jurzitza at t-online.de> wrote:
> ok, that far I've been, too. I readily knew that the device had had been
> identified as scanner by hal - this happens for all three scsci-scanners I've
> been testing so far (luck me, I've three of them at hand - poor me, none of
> them worked from the very begin :-) )
> Is this an issue of hal itself or is this an issue of another program that
> should be triggered by hal? In the latter case, what program is being
> triggered (or should be triggered?)
Yes, "hal-acl-tool" should be called. Seems, this call is not merged
to the device.
> Would it make sense / would it be possibel to downgrade to hal from opeSUSE
> 10.3 (or 11.0) in order to make things work again?
I don't think that will work properly.
> How can I debug further?
Maybe Danny's patch later in this thread already solves the problem.
More information about the hal