https://bugzilla.novell.com/show_bug.cgi?id=469721 User dkukawka@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=469721#c8 --- Comment #8 from Danny Kukawka <dkukawka@novell.com> 2009-01-28 09:44:40 MST --- IMO there should be a way to fix at least those devices which are reported to be a pure printer (and not a scanner) since the information the fdi file provides has been proven to be invalid/wrong. I guess atm there will be no superset for those combo devices. It makes IMO no sense to simply replace all scanner devices in this file with some kind of superset which mark them as desktop-peripheral while we can know that they are pure scanner or printer. You can add the scanner _and_ printer capabilities (and also the related namespace information) to the hal device for a combo device. If they have different USB devices for the scanner and the printer (and e.g. different /dev/* devices) in HAL there should be absolutely no problem. The only little problem is may info.category and the ACL rules (ACL shouldn't be a problem since they have both the same default settings), but we can find a solution for this. IMO the fax or cardreader stuff shouldn't be a problem, I guess they get exposed as extra devices which can get identified as cardreader and modem. If I check the libsane hpaio backend info (sane-backends-1.0.19/doc/descriptions-external/hpaio.desc), I can guess all these devices are at least scanner or combo devices which have a scanner (since sane is for scanner). This mean there is a big chance that all other devices in 70-hpmud.fdi are plain printer, or is this assumption wrong? There should be a way to diff them and mark them as printer. Btw. There should be a way to get in contact with HP (or to search the web) to find out which devices are pure printer, 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.