[opensuse] HP Device Manager
I want to use HP Device Manager to set up my HP M277dw device that requires an HP driver but openSUSE has disabled the ability to install the driver from HP. This prevents me from setting up the printer with all of it's features and difficult to setup and use the scanner function. Does anyone have a work-around for installing the proper driver for this printer? Or how-to to undo a "feature" that paranoid people thinks is "unsafe in the HPlip package. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/03/2020 16.17, Ken Schneider - openSUSE wrote:
I want to use HP Device Manager to set up my HP M277dw device that requires an HP driver but openSUSE has disabled the ability to install the driver from HP. This prevents me from setting up the printer with all of it's features and difficult to setup and use the scanner function. Does anyone have a work-around for installing the proper driver for this printer? Or how-to to undo a "feature" that paranoid people thinks is "unsafe in the HPlip package.
The only disabled feature, AFAIK, is automatic update by the driver. Instead, you download and install the driver and its updates using the same system as any other package in the distribution: YaST/zypper/packagekit. Every other feature should be there. If it is new and you are using Leap, just install from the Printer repository. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.0 x86_64 (Minas Tirith))
On Sun, 2020-03-01 at 10:17 -0500, Ken Schneider - openSUSE wrote:
I want to use HP Device Manager to set up my HP M277dw device that requires an HP driver but openSUSE has disabled the ability to install the driver from HP. This prevents me from setting up the printer with all of it's features and difficult to setup and use the scanner function. Does anyone have a work-around for installing the proper driver for this printer? Or how-to to undo a "feature" that paranoid people thinks is "unsafe in the HPlip package.
-- Ken Schneider SuSe since Version 5.2, June 1998
You don't state what version of openSUSE you are using but according to the hp-linux-imaging website: https://developers.hp.com/hp-linux-imaging-and-printing/supported_devices/in... it's been supported since hplip version 3.15.4 . Leap 15.1 has version 3.18.6 . A driver plugin is required. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 3/1/20 1:36 PM, Mark Petersen wrote:
On Sun, 2020-03-01 at 10:17 -0500, Ken Schneider - openSUSE wrote:
I want to use HP Device Manager to set up my HP M277dw device that requires an HP driver but openSUSE has disabled the ability to install the driver from HP. This prevents me from setting up the printer with all of it's features and difficult to setup and use the scanner function. Does anyone have a work-around for installing the proper driver for this printer? Or how-to to undo a "feature" that paranoid people thinks is "unsafe in the HPlip package.
-- Ken Schneider SuSe since Version 5.2, June 1998
You don't state what version of openSUSE you are using but according to the hp-linux-imaging website:
https://developers.hp.com/hp-linux-imaging-and-printing/supported_devices/in...
it's been supported since hplip version 3.15.4 . Leap 15.1 has version 3.18.6 . A driver plugin is required.
And that is the problem, installing the plugin is being blocked. Somebody decided it was a security risk and don't think admins are smart enough to install plugins from HP. :-(( Currently hplip 3.19.12 is installed. And no Carlos, the plugin cannot be installed using zypper. Packagekit is taboo on my TW install. And by the way, trying to install the plugin mannualy goes into a loop thinking the plugin has not been installed when it has making HP Device Manager useless if a plugin is required. Can you sense my frustration!! -- Ken Schneider -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/03/2020 16.15, Ken Schneider - Factory wrote:
On 3/1/20 1:36 PM, Mark Petersen wrote:
And that is the problem, installing the plugin is being blocked. Somebody decided it was a security risk and don't think admins are smart enough to install plugins from HP. :-((
it IS a security risk, if you think it carefully and calmly. :-)
Currently hplip 3.19.12 is installed. And no Carlos, the plugin cannot be installed using zypper. Packagekit is taboo on my TW install.
Then YaST or zypper or plain rpm. I mentioned the three programs.
And by the way, trying to install the plugin mannualy goes into a loop thinking the plugin has not been installed when it has making HP Device Manager useless if a plugin is required.
Can you sense my frustration!!
What you need are the exact instructions for installing that printer on openSUSE. I think the plugin should already be in the hplip package. So, declare a bugzilla. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.0 x86_64 (Minas Tirith))
On 3/2/20 12:37 PM, Carlos E. R. wrote:
On 02/03/2020 16.15, Ken Schneider - Factory wrote:
On 3/1/20 1:36 PM, Mark Petersen wrote:
And that is the problem, installing the plugin is being blocked. Somebody decided it was a security risk and don't think admins are smart enough to install plugins from HP. :-((
it IS a security risk, if you think it carefully and calmly. :-)
It MAY be a security risk. Who made the decision?!!!! What ever happened to letting the admins shoot themselves in the foot? Instead we are only offered crippled software.
Currently hplip 3.19.12 is installed. And no Carlos, the plugin cannot be installed using zypper. Packagekit is taboo on my TW install.
Then YaST or zypper or plain rpm. I mentioned the three programs.
The plugin is a run file so YaST, zypper or rpm will not work. But thanks anyway. I have downloaded the run file for the plugin and choose to run the installed file but then the loop starts. printer needs plugin download plugin from HP site install plugin from downloaded file (in HP Device Manager) when plugin install is finished a pop-up window informs me that the printer requires a plugin... So not only can I NOT install the plugin but cannot install the plugin in any way shape or form. HP Device Manager has been crippled for anyone needing an HP plugin!
And by the way, trying to install the plugin mannualy goes into a loop thinking the plugin has not been installed when it has making HP Device Manager useless if a plugin is required.
Can you sense my frustration!!
What you need are the exact instructions for installing that printer on openSUSE. I think the plugin should already be in the hplip package. So, declare a bugzilla.
Will do so soon. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/03/2020 18.09, Ken Schneider - openSUSE wrote:
On 3/2/20 12:37 PM, Carlos E. R. wrote:
On 02/03/2020 16.15, Ken Schneider - Factory wrote:
On 3/1/20 1:36 PM, Mark Petersen wrote:
And that is the problem, installing the plugin is being blocked. Somebody decided it was a security risk and don't think admins are smart enough to install plugins from HP. :-((
it IS a security risk, if you think it carefully and calmly. :-)
It MAY be a security risk. Who made the decision?!!!! What ever happened to letting the admins shoot themselves in the foot? Instead we are only offered crippled software.
You are not looking at it calmly. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.0 x86_64 (Minas Tirith))
On Mon, 2020-03-02 at 10:15 -0500, Ken Schneider - Factory wrote:
On 3/1/20 1:36 PM, Mark Petersen wrote:
On Sun, 2020-03-01 at 10:17 -0500, Ken Schneider - openSUSE wrote:
I want to use HP Device Manager to set up my HP M277dw device that requires an HP driver but openSUSE has disabled the ability to install the driver from HP. This prevents me from setting up the printer with all of it's features and difficult to setup and use the scanner function. Does anyone have a work-around for installing the proper driver for this printer? Or how-to to undo a "feature" that paranoid people thinks is "unsafe in the HPlip package.
-- Ken Schneider SuSe since Version 5.2, June 1998
You don't state what version of openSUSE you are using but according to the hp-linux-imaging website:
https://developers.hp.com/hp-linux-imaging-and-printing/supported_devices/in...
it's been supported since hplip version 3.15.4 . Leap 15.1 has version 3.18.6 . A driver plugin is required.
And that is the problem, installing the plugin is being blocked. Somebody decided it was a security risk and don't think admins are smart enough to install plugins from HP. :-(( Currently hplip 3.19.12 is installed. And no Carlos, the plugin cannot be installed using zypper. Packagekit is taboo on my TW install. And by the way, trying to install the plugin mannualy goes into a loop thinking the plugin has not been installed when it has making HP Device Manager useless if a plugin is required.
Can you sense my frustration!!
-- Ken Schneider
Yes, I can :-) I have an HP CM2320 that requires the plugin, and during the printer setup (using hp-setup) the installation stalls with high CPU usage. It's been a while, but my memory of getting the plugin to install was to kill whatever process was using up the CPU (I think it was a python process) and then lo and behold a permission box would show and then the process would install the plugin. I meant to file a bug report the last time it happened but forgot. Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 02.03.20 um 16:15 schrieb Ken Schneider - Factory:
And that is the problem, installing the plugin is being blocked. Somebody decided it was a security risk and don't think admins are smart enough to install plugins from HP. :-((
Dear Ken! The reason for the decision to remove the library from the driver is not a security reason but a legal issue. HP provides this "driver" as an pre-compiled, proprietary library. We can also not assure, that the library works with our software-stack. Therefore openSUSE and many other distributions had to remove it from the package, which was quite some work. This library can simply not be distributed with openSUSE. The best you could do is to ask HP to publish the software under a free licence or use another printer which does not require this software. Best regards -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/09/2020 10:51 AM, Johannes Weberhofer wrote:
Am 02.03.20 um 16:15 schrieb Ken Schneider - Factory:
And that is the problem, installing the plugin is being blocked. Somebody decided it was a security risk and don't think admins are smart enough to install plugins from HP. :-((
Dear Ken!
The reason for the decision to remove the library from the driver is not a security reason but a legal issue. HP provides this "driver" as an pre-compiled, proprietary library. We can also not assure, that the library works with our software-stack.
Therefore openSUSE and many other distributions had to remove it from the package, which was quite some work. This library can simply not be distributed with openSUSE.
The best you could do is to ask HP to publish the software under a free licence or use another printer which does not require this software.
Best regards
This I do not understand at all. NVidia is proprietary and arrangements were made to ensure the driver is available. The same for a number of other packages. If it did take effort to remove the binary, then why not let somebody make it available on packman or at least provide the no-src rpm so a user can build it locally and actually have that functionality. To tell the user to go ask HP for a solution is a non-answer. If anybody is in a position to get HP's ear vis-sa-vis SuSE or Ken, it ain't Ken that is going to gets the attention of HP. Was an ask of HP ever made to release it as freeware during the removal process? If the ask was made and the answer was No, then that information would help in understanding why it is up to the user here. Surely there is some accommodation that can make the HP Device Manager available on openSuSE without it becoming a "It only works on windows" thing. (far too many of those as is) Just seems like another way Linux has found to shoot itself in the foot. Surely there are designated contacts for working with HP, just like there are with NVidia or AMD, etc.. Here is to hoping at least... -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 10.03.20 um 08:57 schrieb David C. Rankin:
This I do not understand at all. NVidia is proprietary and arrangements were made to ensure the driver is available. The same for a number of other packages.
Dear David, AFAIK theNVidia drivers are available as source-code and can be built for the distribution, only it's license is problematic. HP supports a black-box driver library which has dependencies to system components we can not provide.
If it did take effort to remove the binary, then why not let somebody make it available on packman or at least provide the no-src rpm so a user can build it locally and actually have that functionality.
Everyone is invited to do so.
To tell the user to go ask HP for a solution is a non-answer. If anybody is in a position to get HP's ear vis-sa-vis SuSE or Ken, it ain't Ken that is going to gets the attention of HP. Was an ask of HP ever made to release it as freeware during the removal process? If the ask was made and the answer was No, then that information would help in understanding why it is up to the user here.
All other open source projects had to remove this lib (RHEL, Fedora, Debian,...). I'm sure there was an request by one of the distributions; it has been some years ago and I can't remember: You may search for "libImageProcessor" to find required information.
Surely there is some accommodation that can make the HP Device Manager available on openSuSE without it becoming a "It only works on windows" thing. (far too many of those as is) Just seems like another way Linux has found to shoot itself in the foot. Surely there are designated contacts for working with HP, just like there are with NVidia or AMD, etc.. Here is to hoping at least...
I know that this is frustrating, but I'm sorry I can't help. Best regards, -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/03/2020 10.04, Johannes Weberhofer wrote:
Am 10.03.20 um 08:57 schrieb David C. Rankin:
This I do not understand at all. NVidia is proprietary and arrangements were made to ensure the driver is available. The same for a number of other packages.
Dear David,
AFAIK theNVidia drivers are available as source-code and can be built for the distribution, only it's license is problematic. HP supports a black-box driver library which has dependencies to system components we can not provide.
If it did take effort to remove the binary, then why not let somebody make it available on packman or at least provide the no-src rpm so a user can build it locally and actually have that functionality.
Everyone is invited to do so.
To tell the user to go ask HP for a solution is a non-answer. If anybody is in a position to get HP's ear vis-sa-vis SuSE or Ken, it ain't Ken that is going to gets the attention of HP. Was an ask of HP ever made to release it as freeware during the removal process? If the ask was made and the answer was No, then that information would help in understanding why it is up to the user here.
All other open source projects had to remove this lib (RHEL, Fedora, Debian,...). I'm sure there was an request by one of the distributions; it has been some years ago and I can't remember: You may search for "libImageProcessor" to find required information.
Surely there is some accommodation that can make the HP Device Manager available on openSuSE without it becoming a "It only works on windows" thing. (far too many of those as is) Just seems like another way Linux has found to shoot itself in the foot. Surely there are designated contacts for working with HP, just like there are with NVidia or AMD, etc.. Here is to hoping at least...
I know that this is frustrating, but I'm sorry I can't help.
Perhaps install the hplip packcage from the hp sources instead. The binary blob is out there, the problem is the distribution package blocking its installation by the user. So, you remove it, and block the user from installing it... this is absurd. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.0 x86_64 (Minas Tirith))
Am 10.03.20 um 11:13 schrieb Carlos E. R.:
Perhaps install the hplip packcage from the hp sources instead. The binary blob is out there, the problem is the distribution package blocking its installation by the user. So, you remove it, and block the user from installing it... this is absurd.
The source code had to be patched, so the RPM package can be created - openSUSE does not contain the libraries required. We do not allow downloading the driver file. But what we do block is the automatic update of the hplip, because it requires a full rebuild of the shources. That would lead to a inconsistent state between installed libraries and the locally built libraries. Of course you can remove our hplip RPMs and built hplip from source and get those running. If you find a way to simplify that for users, please share it. -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
if it makes you feel better arch is having problems too On 3/10/20 9:53 AM, Johannes Weberhofer wrote:
Am 10.03.20 um 11:13 schrieb Carlos E. R.:
Perhaps install the hplip packcage from the hp sources instead. The binary blob is out there, the problem is the distribution package blocking its installation by the user. So, you remove it, and block the user from installing it... this is absurd.
The source code had to be patched, so the RPM package can be created - openSUSE does not contain the libraries required. We do not allow downloading the driver file.
But what we do block is the automatic update of the hplip, because it requires a full rebuild of the shources. That would lead to a inconsistent state between installed libraries and the locally built libraries. Of course you can remove our hplip RPMs and built hplip from source and get those running.
If you find a way to simplify that for users, please share it.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (7)
-
Carlos E. R. -
David C. Rankin -
Hans Krueger -
Johannes Weberhofer -
Ken Schneider - Factory -
Ken Schneider - openSUSE
-
Mark Petersen