| Summary: | hplip binary driver installation fails for certain printers | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Brett Ginsburg <zekeb> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | doktor5000, marcello.anni |
| Version: | 2 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| URL: | https://forums.mageia.org/en/viewtopic.php?f=24&t=3377&p=25888#p25888 | ||
| Whiteboard: | |||
| Source RPM: | hplip 3.12.4 | CVE: | |
| Status comment: | |||
| Attachments: | Printing debug output | ||
|
Description
Brett Ginsburg
2012-09-17 17:34:37 CEST
I posted this same information on Bug 5395 as it seems like mine is a duplicate. I can run hp-plugin as root and the plugin installs with no errors. If I run hp-setup, the printer is found and identified correctly, then hp-plugin runs, and I get a report of successful installation, but in debug mode I see this error: hp-setup[24262]: debug: Unable to open file /var/lib/hp/hplip.state for reading. hp-setup[24262]: debug: Plugin is not installed error: The printer you are trying to setup requires a binary driver plug-in and it failed to install. Please check your internet connection and try again. Visit http://hplipopensource.com for more infomation. /var/lib/hp does not exist. Solved by creating /var/lib/hp as root. i have /var/lib/hp but the problem you described remains (hp laserjet 1018). the installation as root seems to go well, but when i plug the printer a new pop-up appears saying me to install the plugin. i have this issue since a lot of years CC:
(none) =>
marcello.anni Marcello, have you tried to delete /var/lib/hp/hplip.state then rerun hp-setup? May be that hplip.setup is corrupt and needs to be rewritten. Created attachment 2817 [details]
Printing debug output
Nothing changed. i've used the debug option and i've attached the output. hope
it can be useful
@Marcello: Please don't cross-post between different report for the same issue, makes things even harder to track ... *** This bug has been marked as a duplicate of bug 5395 *** Status:
NEW =>
RESOLVED |