User talk:Billie

HPLIP Binary Upgrade
PROBLEM: The HPLIP ebuild itself does not upgrade the binary plugin(s) when the ebuild is upgraded. A symptom of this problem, you may get segfaults when starting XSane. (i.e. The HP LaserJet M1522nf requires a binary plugin for using the scanning feature.)

My Edit: -- SOLUTION: The following upgrade instructions should upgrade the Sane plugin file "/usr/lib64/sane/libsane-hpaio.so*". (hp-setup also upgrades the plugin?) --

Your Change: ++ SOLUTION: Following the upgrade instructions should take care of this as hp-setup tries to upgrade the plugin.

Within English Grammar, your statement lacks sense unless you are implying the upgrading of the binary (scanner/xsane) plugin is now upgraded while installing the package. (ie. Scripted now within the EBuild file?) If so, you should also say so for clarification. Albeit, I wasn't aware of this move, as I am already CC'ed on a few HPLIP bugs. Additionally, one of the reasons for specifying the "/usr/lib64/sane/libsane-hpaio.so*", is so that users know where the binary plugin file for xsane is installed for HPLIP and can manually check that their binary plugin for xsane has been updated, instead of depending explicitly upon the hplip utilities. (Funny though, I diff'ed the =net-print/hplip-3.13.9 and =net-print/hplip-3.14.1, and found those files to be different while still having the same 1.0 version, even noted within the library itself when searching using strings/hexedit!)

I already recognize I may not even have had this bug properly corrected and documented initially, as downgrading to =net-print/hplip-3.13.9, and merrily running xsane afterwards still results in a device not found, without manually deleting and adding the fax/scanning device again. And as such, the binary plugin maynot be upgraded upon the next upgrade. If I'm not mistaken, HP developers' official stance on this (per their bug pages and support) is to manually delete all print/fax quenes and manually recreate the print/fax quenes after each upgrade or downgrade. Sort of defeats the purpose of so-called "upgrades", reverting back to MS Windows' early style of difficult package management!

(Cross posting onto the HPLIP discussion page, and merrily documented to alert you of the problem with upgrading the binary plugin.)