Bug 309815

Created attachment 163516 [details]
screnshoot 1 (after reboot)

This screnshoot shows window error and the output of lsusb and hwinfo --scan when problem occurs.

Created attachment 163518 [details]
screnshoot 1 (after powering off/on scanner)

In this other screenshot nothing has changed, except I've powered off, then powered on my scanner.

Created attachment 163519 [details]
My /var/log/messages

Because it "disappears when I reset (power off, then power on)
the scanner" it is
either
a problem in the scanner e.g. that it may fall into a (comatose)
sleep mode where only a power-off/on awakes it
or
it is a problem in the udev/HAL/resmgr machinery.

Did you use openSUSE 10.2 or Suse Linux 10.1 before and
there it doesn't happen?
If yes, it is no problem in the scanner.

Does the problem happen only for a normal user
but as root it works always?
If yes it is a problem with the permission setting for normal usres
which is done via the udev/HAL/resmgr machinery.
Do "scanimage -L" as normal user and as root to find out
if the scanner is accessible.

Regarding "no device available":
This messge may be misleading because when "lsusb" lists it,
it doesn't mean that the actual device file /dev/bus/usb/*/*
which is used for I/O by the SANE software is correctly created.

Therefore provide the output of the three commands (as root)
when the problem happens:

lsusb

ls -l /dev/bus/usb/*/*

getfacl /dev/bus/usb/*/*

(Preferably as text/plain attachment and not as a screenhot image.)

This scanner works actually without problems in openSUSE 10.2 / Ubuntu 7.10

I will try to reproduce the problem after/before syncing with today's Factory changes and provide you with requested information if it persists.

Please provide the output of the commands in comment #0
when the problem is present and after you did a power-off/on.
Alternatively a USB cable unplug/replug should also help
because this also triggers the udev->HAL->resmgr machinery.

You're right, this is an udev->HAL->resmgr permissions problem, and unpluging/replugin USB cable helps too.

Created attachment 163789 [details]
lsusb

Created attachment 163790 [details]
ls -l /dev/bus/usb/*/*

Created attachment 163792 [details]
getfacl /dev/bus/usb/*/*

Attachment #163790 [details] shows that the udev rules
in /etc/udev/rules.d/55-libsane.rules have been applied
because the group is set to "lp".

Attachment #163792 [details] shows that the HAL/resmgr stuff was not done
because no ACL was set.

Because it works after re-plug, it shows that the HAL policy
files are correctly set up.
In particular your /etc/hal/fdi/policy/10osvendor/70-scanner.fdi
should contain this entry for your model:
-------------------------------------------------------------------
<match key="info.bus" string="usb_device">
 <match key="usb_device.vendor_id" int="0x04b8">
  <match key="usb_device.product_id" int="0x011b">
   <append key="info.capabilities" type="strlist">scanner</append>
  </match>
 </match>
</match>
-------------------------------------------------------------------

If the HAL/resmgr stuff works, getfacl would show something like
-------------------------------------------------------------------
# file: dev/bus/usb/003/003
# owner: root
# group: lp
user::rw-
user:<normal-user>:rw-
group::rw-
mask::rw-
other::r--
-------------------------------------------------------------------
to allow the <normal-user> read/write access.

As a workaround add the normal users which should be allowed
to access the scanner to the "lp" group.

I am no HAL/resmgr expert so that I cannot debug it further
and therefore I reassign it to the HAL maintainer.

Could you please attach the complete output of lshal?

sounds like a duplicate of bug 309171
Is autologin enabled?

Created attachment 163820 [details]
lshal

Yes, autologin was enabled.

Disabling it solves the problem and is as an acceptable workaround for me.

*** This bug has been marked as a duplicate of bug 309171 ***