Bug 20457 - Recent printer not recognized due to too old hplip
Summary: Recent printer not recognized due to too old hplip
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: Backports (show other bugs)
Version: 5
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords: Backport
Depends on:
Blocks:
 
Reported: 2017-03-12 10:51 CET by Philippe Flat
Modified: 2018-07-12 15:49 CEST (History)
1 user (show)

See Also:
Source RPM: hplip
CVE:
Status comment:


Attachments

Description Philippe Flat 2017-03-12 10:51:45 CET
Description of problem:
I have bought an HP OfficeJet Pro 6960 and the driver is not present in Mageia 5: hplip 3.15.11.
It is recognize in Cauldron : hplip 3.166.11.
Can you back-port it?

Version-Release number of selected component (if applicable):
hplip 3.15.11

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.
Comment 1 Marja Van Waes 2017-03-13 06:49:34 CET
Assigning to all packagers collectively, since there is no registered maintainer for this package.

Keywords: (none) => Backport
CC: (none) => marja11
Component: RPM Packages => Backports
Assignee: bugsquad => pkg-bugs

Comment 2 Marja Van Waes 2018-07-12 15:49:38 CEST
Hi Philippe,

Thank you for having taken the needed time to report this issue!

We regret if this issue didn't get fixed in Mageia 5.

Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, but non-security bugs have no chance of still getting fixed.

Closing as OLD.

The hplip version in Mageia 6 shouldn't have this problem, but please reopen this report and change its "Version:" at the top left to "6", if I'm wrong and the same bug still exists in Mageia 6.

==> If you didn't reset your password after february 2018, then you'll need to reset it here https://identity.mageia.org/forgot_password to be able to log in and comment in this report. <==

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.