https://bugzilla.novell.com/show_bug.cgi?id=335674#c5
--- Comment #5 from Johannes Meixner 2007-10-26 08:46:51 MST ---
What I see from your YaST log:
It is detected as
"SCSI scanner ' Scanner 636A4 1.50' at /dev/sg5"
You selected the model "Microtek", "ScanMaker X6" with the driver "microtek2".
The "microtek2" line was activated in /etc/sane.d/dll.conf
The driver recognized the scanner and it is shown in YaST like
microtek2 | Microtek ScanMaker X6USB at microtek2:/dev/sg5
Finally this command is executed by YaST:
/usr/lib/YaST2/bin/test_and_set_scanner_access_permissions \
'microtek2:/dev/sg5;unknown;'
which should "do the right thing" - which is nothing in your case
because according to comment #1 and comment #3 you scanner
shows up as SCSI type "scanner" so that the default entry
for SCSI scanners in /etc/hal/fdi/policy/10osvendor/70-scanner.fdi
--------------------------------------------------------------------
<match key="info.category" string="scsi_generic">
<match key="@info.parent:scsi.type" string="scanner">
<append key="info.capabilities" type="strlist">scanner</append>
</match>
</match>
--------------------------------------------------------------------
should trigger the udev/HAL/hal-resmgr machinery which should
set an appropriate ACL on the scanner's device file.
Please check that you have such an entry.
If yes, the question is why the udev/HAL/hal-resmgr machinery
is not doing what it should do...
Please attach also a full "lshal" output.
Try if it helps to restart HAL with the scanner switched on.
If not, try if it helps to reboot with the scanner switched on.
--
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.