http://bugzilla.novell.com/show_bug.cgi?id=547962 User jsmeix@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=547962#c2 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Component|Printing |Other Platform|x86-64 |All Resolution| |DUPLICATE AssignedTo|jsmeix@novell.com |bnc-team-screening@forge.pr | |ovo.novell.com QAContact|jsmeix@novell.com |qa@suse.de --- Comment #2 from Johannes Meixner 2009-10-20 03:25:34 MDT --- Looks like a duplicate of the current bug #542473: "HAL does not set ACL for normal user access for devices with 'scanner' capability" See there how to check if this one is really a duplicate. By the way: This kind of HAL issue usually re-appears again for each Suse Linux / openSUSE version and must be fixed again and again, compare bug #438867. The best workaround to get those kind of HAL issues out of sight is to use the YaST scanner module and: ----------------------------------------------------------- .. you could access the scanner via the 'saned' as a workaround. For this workaround choose 'scanning via network' and select the 'local host configuration'. ---------------------------------------------------------- In particular on a workstation in a trusted network environment (e.g. when the Suse firewall protects it from acceess from the external network zone / Internet) this workaround should cause no security problems. Compare https://bugzilla.novell.com/show_bug.cgi?id=438867#c66 *** This bug has been marked as a duplicate of bug 542473 *** http://bugzilla.novell.com/show_bug.cgi?id=542473 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.