https://bugzilla.novell.com/show_bug.cgi?id=469721 User dkukawka@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469721#c6 Danny Kukawka <dkukawka@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX | --- Comment #6 from Danny Kukawka <dkukawka@novell.com> 2009-01-28 08:10:30 MST --- (In reply to comment #1)
Simply ignore unwanted SusePlugger popups. As far as I know it does not use 70-hpmud.fdi. As far as I know it works on whatever else data. As far as I know the SusePlugger stuff is basically only a best-guess and cannot work correctly in any case.
That's not correct. If you take a look at the source (kdebase3-suse) suseplugger ask hal to find out what kind of device was added to the machine. In this case the information in 70-hpmud.fdi is used and it's clearly wrong, since the device is a printer and not a scanner. (In reply to comment #3)
info.capabilities is always set to 'scanner' because this is the only working value which is currently available for me (nothing would happen if I set info.capabilities to 'printer')
There is already a printer namespace in HAL (http://people.freedesktop.org/~dkukawka/hal-spec-git/hal-spec.html#device-pr...). The only problem was that there was no ACL/PolicyKit rule/policy. I've added the needed stuff to git (which grand access for active users to printer.device, which need to be set via a fdi file (e.g. copy it from the parent device)) and it will be in the next SLE11/openSUSE hal package/update. IMO the 70-hpmud.fdi is plain incorrect/buggy if there is no way to differ between pure scanner and printer devices (not sure atm what to do with combo devices, depends if there are different /dev/* devices for the scanner and the printer). -- 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.