https://bugzilla.novell.com/show_bug.cgi?id=392837
User jsmeix@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=392837#c3
Johannes Meixner changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
Info Provider| |mmeeks@novell.com
--- Comment #3 from Johannes Meixner 2008-05-21 08:21:26 MST ---
See bug #340173 for some background information.
Could you explain what happened in comment #0 in more detail.
What you posted looks like a mix-up of YaST log messages
(which should go to y2log) and the actual stderr message of
/usr/lib/YaST2/bin/test_and_set_scanner_access_permissions
Was this all shown mixed up in the YaST popup with the
first line "Failed to set scanner access permissions..."?
Can you run as root
/usr/lib/YaST2/bin/test_and_set_scanner_access_permissions
and post its output (it is silent on my machines) and in
your case it should show only this stderr message
------------------------------------------------------------
The following models are currently not known to HAL:
USB-ID(hex)=04b8:082e
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 a SCSI scanner which was switched on during boot
is not listed in the 'lshal' output, the usual reason
is that the kernel module for the scanner's SCSI host
adapter does not notify HAL about the scanner device.
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'
------------------------------------------------------------
--
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.
