https://bugzilla.novell.com/show_bug.cgi?id=340173 Summary: add a test to yast2-scanner if HAL knows about a configured scanner Product: openSUSE 11.0 Version: unspecified Platform: All OS/Version: openSUSE 11.0 Status: ASSIGNED Severity: Enhancement Priority: P5 - None Component: Other AssignedTo: jsmeix@novell.com ReportedBy: jsmeix@novell.com QAContact: qa@suse.de Found By: Development The general problem "can access as root but cannot as normal user" is one of the most often reported problems regarding scanning. Therefore I think about an automated step in the YaST setup which tests if there is access as non-root and if the test fails YaST could show an appropriate information to the user which could suggest re-plug for USB scanners and if this doesn't help it could suggest a reboot of the computer, see https://bugzilla.novell.com/show_bug.cgi?id=218393#c24 and if even a reboot doesn't help it could suggest the saned+net workaround. The first idea to run "scanimage -L" as an unprivilleged user (e.g. via something like "su nobody") cannot work because arbitrary unprivilleged users don't have access via the udev/HAL/hal-resmgr magic. Only "console users" get access via the udev/HAL/hal-resmgr magic. A "console user" is a user who is currently actually logged in via console or XDM/KDM (or whatever the current resmgr setup is). Ludwig told me the right way to implement such a test: Run "scanimage -L" as root and for each SANE device check if there is a matching HAL entry with the "scanner" capability (e.g. run "hal-find-by-capability --capability scanner"). If yes, we can assume that the dev/HAL/hal-resmgr magic works to grant access for "console users" for this scanner. -- 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.