https://bugzilla.suse.com/show_bug.cgi?id=1205860 https://bugzilla.suse.com/show_bug.cgi?id=1205860#c8 --- Comment #8 from Johannes Meixner <jsmeix@suse.com> --- Some general information: In general see the section "Third-Party Scanner Drivers" in https://en.opensuse.org/SDB:Configuring_Scanners Regarding HPLIP and its proprietary plugin see the section "Some devices require a proprietary HPLIP plugin" and its sub-sections in https://en.opensuse.org/SDB:How_to_set-up_a_HP_printer In particular regarding the screenshot in comment #3 https://bugzilla.suse.com/attachment.cgi?id=863780 that shows the same device twice as available via "hpaio" and as "not configured" in the Yast2 scanner module: The Yast2 scanner module calls /usr/lib/YaST2/bin/autodetect_scanners to autodetect devices which seem to be scanners which calls sane-find-scanner for SANE scanners and additionally hp-probe for HPLIP scanners. The Yast2 scanner module calls /usr/lib/YaST2/bin/determine_active_scanners to determine scanners that are available via a SANE driver which calls scanimage -f '%d,%v,%m;' that outpouts basically same as scanimage -L Then some "reasonable effort attempt" is done in the Yast2 scanner module to find out which autodetected device is available via a SANE driver. When that "reasonable effort attempt" cannot match an autodetected device to what is reported by scanimage -f '%d,%v,%m;' (e.g. the model name may not match), then one same device is reported twice as already available via a SANE driver and as not configured autodetected device. -- You are receiving this mail because: You are on the CC list for the bug.