Bug 21381 - my printer HP Officet Pro 8000 a809 is not recognized by mageia6
Summary: my printer HP Officet Pro 8000 a809 is not recognized by mageia6
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: x86_64 Linux
Priority: High major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
: 21421 21459 21464 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-07-28 13:57 CEST by peter lawford
Modified: 2018-11-18 18:10 CET (History)
8 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
return of the command hp-check as root (16.65 KB, text/plain)
2017-07-28 17:05 CEST, peter lawford
Details
error-message when attempting to print a test-page (11.51 KB, image/png)
2017-07-30 20:03 CEST, peter lawford
Details

Description peter lawford 2017-07-28 13:57:38 CEST
Description of problem:
when attempting to print with my printer HP Officet Pro 8000 a809, I get an error message: device communication error: mp1q8yu2j5; I tried to remove it in the mageia mcc (stuff>printers) and reinstall it several times, but nothing changed.
this printer actually works fine with mageia5 64bits


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


How reproducible:
every time I try to print with it

Steps to Reproduce:
1.
2.
3.
Comment 1 peter lawford 2017-07-28 16:08:15 CEST
the same for my older all-in-one HP Officejet 7310; only the printer part don't work, but the scanner part is OK with xsane; here too, this printer works fine with mageia5
IMPORTANT: I didn't install mageia6 from the image.iso, but I have migrated from mageia5
Comment 2 peter lawford 2017-07-28 16:33:50 CEST
here is the return of the command system-config-printer
[root@magaux toto]# system-config-printer
Error creating proxy: La connexion est fermée (g-io-error-quark, 18)
Error creating proxy: La connexion est fermée (g-io-error-quark, 18)
Error creating proxy: La connexion est fermée (g-io-error-quark, 18)
Error creating proxy: La connexion est fermée (g-io-error-quark, 18)
task-printing-server-2011-10.mga6
task-printing-hp-2011-10.mga6
Comment 3 peter lawford 2017-07-28 17:05:42 CEST
Created attachment 9523 [details]
return of the command hp-check as root
Comment 4 Marja Van Waes 2017-07-28 23:19:50 CEST
(In reply to peter lawford from comment #3)
> Created attachment 9523 [details]
> return of the command hp-check as root

CC'ing some people who'll understand the output better than I do.

CC: sysadmin-bugs => doktor5000, kernel, makowski.mageia, marja11, pkg-bugs
Component: Release (media or process) => RPM Packages

Comment 5 peter lawford 2017-07-30 19:37:10 CEST
(In reply to Marja van Waes from comment #4)
> (In reply to peter lawford from comment #3)
> > Created attachment 9523 [details]
> > return of the command hp-check as root
> 
> CC'ing some people who'll understand the output better than I do.

I have removed mga6, reinstalled mga5 from my archives and migrated again to mga6 using command line in runlevel3, as advised in your migration guide.
I immediately tested the printers: the same occurs; a system with which printing is impossible is absolutely useless. I am afraid that mageia5 is the last version of mageia

Priority: Normal => High

Comment 6 peter lawford 2017-07-30 20:03:48 CEST
Created attachment 9538 [details]
error-message when attempting to print a test-page
Comment 7 Rémi Verschelde 2017-07-31 14:30:13 CEST
*** Bug 21421 has been marked as a duplicate of this bug. ***
Comment 8 Philippe Makowski 2017-07-31 19:03:11 CEST
I see this on your hp-check report :
error: 'sane-backends' package is missing/incompatible 
error: 'libnet-snmp-devel' package is missing/incompatible 
error: 'libcups2' package is missing/incompatible 
error: 'cups' package is missing or 'cups' service is not running.
error: 'cups-common' package is missing/incompatible 

do you have cups ?

what is the result of :
systemctl status cups.socket ?
rpm -qa cups ?
Comment 9 peter lawford 2017-07-31 22:51:19 CEST
(In reply to Philippe Makowski from comment #8)
> I see this on your hp-check report :
> error: 'sane-backends' package is missing/incompatible 
> error: 'libnet-snmp-devel' package is missing/incompatible 
> error: 'libcups2' package is missing/incompatible 
> error: 'cups' package is missing or 'cups' service is not running.
> error: 'cups-common' package is missing/incompatible 
> 
> do you have cups ?
> 
> what is the result of :
> systemctl status cups.socket ?
> rpm -qa cups ?

of course I have cups; cups was already installed before the migration to mageia6, and my printers worked very well when my system was only mageia5
as a reply to your questions:

[toto@magaux ~]$ rpm -qa | grep cups
cups-filters-1.13.4-2.mga6
cups-2.2.3-2.mga6
gutenprint-cups-5.2.11-2.mga6
cups-pk-helper-0.2.6-1.mga6
cups-filesystem-2.2.3-2.mga6
python3-cups-1.9.73-2.mga6
cups-drivers-foo2zjs-0.0-1.20121012.8.mga6
lib64cups2-2.2.3-2.mga6
lib64cups-filters1-1.13.4-2.mga6
cups-common-2.2.3-2.mga6
libcups2-2.2.3-2.mga6

[toto@magaux ~]$ systemctl status cups.socket
● cups.socket - CUPS Scheduler
   Loaded: loaded (/usr/lib/systemd/system/cups.socket; enabled; vendor preset: enabled)
   Active: active (running) since lun. 2017-07-31 13:23:46 CEST; 9h ago
   Listen: /var/run/cups/cups.sock (Stream)

at this precise moment, my printers are not yet recognized
Comment 10 Kristoffer Grundström 2017-07-31 23:19:17 CEST
Isn't the hplip package needed as well?

CC: (none) => hamnisdude

Comment 11 peter lawford 2017-07-31 23:45:19 CEST
(In reply to Kristoffer Grundström from comment #10)
> Isn't the hplip package needed as well?

[toto@magaux ~]$ rpm -qa | grep hplip
hplip-gui-3.17.4-1.mga6
hplip-model-data-3.17.4-1.mga6
hplip-hpijs-3.17.4-1.mga6
hplip-hpijs-ppds-3.17.4-1.mga6
hplip-3.17.4-1.mga6
Comment 12 peter lawford 2017-07-31 23:50:05 CEST
(In reply to peter lawford from comment #11)
> (In reply to Kristoffer Grundström from comment #10)
> > Isn't the hplip package needed as well?
> 
> [toto@magaux ~]$ rpm -qa | grep hplip
> hplip-gui-3.17.4-1.mga6
> hplip-model-data-3.17.4-1.mga6
> hplip-hpijs-3.17.4-1.mga6
> hplip-hpijs-ppds-3.17.4-1.mga6
> hplip-3.17.4-1.mga6

furthermore, without hplip-gui-3.17.4-1.mga6, I couldn't run the command hp-check, since /usr/bin/hp-check is part of hplip-gui-3.17.4-1.mga6
Comment 13 peter lawford 2017-08-01 17:21:43 CEST
FOUND THE FAILURE!!
 see attentively the returns of the commands:

[toto@magaux ~]$ type lpr
bash: type: lpr : non trouvé   (trad.eng.  not found)

but

[toto@magaux ~]$ ls -al /usr/bin/ | grep lpr
lrwxrwxrwx   1 root   root           21 août   1 15:07 lpr -> /etc/alternatives/lpr
-rwxr-xr-x   1 root   root        15232 mai   26 16:00 lpr.cups*
lrwxrwxrwx   1 root   root           17 sept.  8  2016 lpr-foomatic -> foomatic-printjob*
lrwxrwxrwx   1 root   root           22 août   1 15:07 lprm -> /etc/alternatives/lprm
-rwxr-xr-x   1 root   root        11128 mai   26 16:00 lprm.cups*
lrwxrwxrwx   1 root   root           17 sept.  8  2016 lprm-foomatic -> foomatic-printjob*
-rwxr-xr-x   1 root   root         5470 avril 29 20:24 lprsetup.sh*
-rwxr-xr-x   1 root   root         4165 avril 29 20:24 unix-lpr.sh*

which proves that /usr/bin/lpr exists; furthermore:

[toto@magaux ~]$ ls -al /etc/alternatives/ | grep lpr
lrwxrwxrwx   1 root root    17 août   1 15:07 lpr -> /usr/bin/lpr-cups
lrwxrwxrwx   1 root root    33 août   1 15:07 lpr.1.xz -> /usr/share/man/man1/lpr-cups.1.xz
lrwxrwxrwx   1 root root    18 août   1 15:07 lprm -> /usr/bin/lprm-cups
lrwxrwxrwx   1 root root    34 août   1 15:07 lprm.1.xz -> /usr/share/man/man1/lprm-cups.1.xz
lrwxrwxrwx   1 root root    17 juil. 30 16:49 print -> /usr/bin/lpr.cups*
lrwxrwxrwx   1 root root    18 juil. 30 16:49 print-lprm -> /usr/bin/lprm.cups*
lrwxrwxrwx   1 root root    33 juil. 30 16:49 print-lprman -> /usr/share/man/man1/lpr-cups.1.xz
lrwxrwxrwx   1 root root    34 juil. 30 16:49 print-lprmman -> /usr/share/man/man1/lprm-cups.1.xz

unfortunately, /usr/bin/lpr-cups DOESN'T EXIST:

[TOTO@magaux ~]$ ls /usr/bin/ | grep lpr
lpr@
lpr.cups*
lpr-foomatic@
lprm@
lprm.cups*
lprm-foomatic@
lprsetup.sh*
unix-lpr.sh*

but /usr/bin/lpr.cups exists and it's not the same file

but there is one another problem: I have already changed lpq.cups into lpq-cups
here is the result

[toto@magaux ~]$ lpq
lpq: Error - no default destination available.

but under root:

[toto@magaux alain4]# lpq
Officejet_Pro_8000_A809 is ready
no entries

which means that lpq-cups doesn't work, as it should do, for users, although the execution rights is given for all:

[toto@magaux ~]$ ls -al /usr/bin/ | grep lpq
lrwxrwxrwx   1 root   root           21 août   1 16:28 lpq -> /etc/alternatives/lpq*
-rwxr-xr-x   1 root   root        19480 mai   26 16:00 lpq-cups*
lrwxrwxrwx   1 root   root           17 sept.  8  2016 lpq-foomatic -> foomatic-printjob*

the same hold for lp, lpr, lprm lpstat

changing lp*.cups into lp*-cups is very easy, but I am not able to modify these
files in order they work for users
Comment 14 peter lawford 2017-08-01 23:10:17 CEST
I've switched as root /usr/bin/*.cups into /usr/bin/*-cups where *=lp, lpq, lpr lprm, lpstat, but unfortunately nothing has changed, printers don't work with the same error messages.
Comment 15 Philippe Makowski 2017-08-02 09:51:37 CEST
I don't think you need to rename lpr.cups to lpr-cups
alternatives seems correctly set with lpr pointing to lpr.cups

may be you just have a rights problem to access to the device
Comment 16 peter lawford 2017-08-02 11:56:53 CEST
(In reply to Philippe Makowski from comment #15)
> I don't think you need to rename lpr.cups to lpr-cups
> alternatives seems correctly set with lpr pointing to lpr.cups
> 
> may be you just have a rights problem to access to the device

I think you're wrong: for examples:

with lpq.cups:
[toto@magaux ~]$ type lpq
bash: type: lpq : non trouvé

with lpq-cups:
[toto@magaux ~]$ type lpq
lpq est /bin/lpq

which shows that lpq-cups is recognized, but not lpq.cups (the same for the others commands)

about the rights:

[toto@magaux ~]$ ls -al /usr/bin | grep cups
-rwxr-xr-x   1 root   root        15224 mai   26 16:00 cancel.cups*
-rwxr-xr-x   1 root   root        23912 mai   21  2016 cups-calibrate*
-rwxr-xr-x   1 root   root        15248 mai   26 16:00 cupstestdsc*
-rwxr-xr-x   1 root   root        56472 mai   26 16:00 cupstestppd*
lrwxrwxrwx   1 root   root           36 mai   26 16:02 driverless -> ../../usr/lib/cups/driver/driverless*
lrwxrwxrwx   1 root   root           38 mai   26 16:02 foomatic-rip -> ../../usr/lib/cups/filter/foomatic-rip*
-rwxr-xr-x   1 root   root         3237 oct.  14  2011 hpcups-update-ppds*
-rwxr-xr-x   1 root   root        19368 mai   26 16:00 lp-cups*
-rwxr-xr-x   1 root   root        19480 mai   26 16:00 lpq-cups*
-rwxr-xr-x   1 root   root        15232 mai   26 16:00 lpr-cups*
-rwxr-xr-x   1 root   root        11128 mai   26 16:00 lprm-cups*
-rwxr-xr-x   1 root   root        32048 mai   26 16:00 lpstat-cups*
-rwxr-xr-x   1 root   root          177 mai   25 17:38 print-cups.sh*

you can see that all printers commands have the right a+x

it's really a serious problem I think it's necessary to update cups, cups-common,... as quickly as possible
Comment 17 peter lawford 2017-08-02 17:12:31 CEST
the situation is not desperate; using hp-toobox gui, I could clean the heads of my HP officejet pro 8000, and print the result, but printing documents (pdf, doc,...) is always impossible
Comment 18 Philippe Makowski 2017-08-02 17:57:09 CEST
I don't understand what is wrong in your box, here I have :
type lpq
lpq is /usr/bin/lpq
ls -la /usr/bin/lpq
lrwxrwxrwx. 1 root root 27 11 juil. 16:31 /usr/bin/lpq -> /etc/alternatives/print-lpq
ls -la /etc/alternatives/print-lpq
lrwxrwxrwx. 1 root root 17 11 juil. 16:31 /etc/alternatives/print-lpq -> /usr/bin/lpq.cups
ls -la /usr/bin/lpq.cups 
-rwxr-xr-x. 1 root root 19392  9 mai   12:47 /usr/bin/lpq.cups

And I have cups-2.2.3-2.mga6 (before this box was under mga5)
Comment 19 peter lawford 2017-08-02 22:58:05 CEST
(In reply to Philippe Makowski from comment #18)
> I don't understand what is wrong in your box, here I have :
> type lpq
> lpq is /usr/bin/lpq
> ls -la /usr/bin/lpq
> lrwxrwxrwx. 1 root root 27 11 juil. 16:31 /usr/bin/lpq ->
> /etc/alternatives/print-lpq
> ls -la /etc/alternatives/print-lpq
> lrwxrwxrwx. 1 root root 17 11 juil. 16:31 /etc/alternatives/print-lpq ->
> /usr/bin/lpq.cups
> ls -la /usr/bin/lpq.cups 
> -rwxr-xr-x. 1 root root 19392  9 mai   12:47 /usr/bin/lpq.cups
> 
> And I have cups-2.2.3-2.mga6 (before this box was under mga5)

today, I have uninstalled and reinstalled cups, cups-common and their dependances
I have actually the same returns as you for the different ls -la ...; but these returns were completely different before I uninstalled and reinstalled the cups packages, and now the printing system seems to work well; I think that during the migration mag5 to mag6, these packages were corrupted.
tomorrow, I'll perform others trials with my printers to confirm (or infirm) that the problem in now fixed
I will keep you informed of the course of events
thank you for your interest to this problem
best regards
Comment 20 Philippe Makowski 2017-08-03 18:47:08 CEST
resolved

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

Comment 21 peter lawford 2017-08-03 19:56:40 CEST
concerning my second printer HP officejet 7310, I had to uninstall it, and after reinstall it so that it would be recognized; problem: it was a long time I didn't use it, and it no longer correctly works (output white paper); perhaps tanks are empty or more likely printheads are out of use; so, I can't test it under mageaia6
it's not impossible I would have led to reopen this bug
I am really sorry
Comment 22 Rémi Verschelde 2017-08-04 10:05:08 CEST
I'm glad you found how to fix it :) Good job investigating and trying to debug the issues at any rate.
Comment 23 peter lawford 2017-08-05 15:58:17 CEST
after changing the tanks-heads, HP officejet 7310 fine works
I consider this bug as fixed
Comment 24 Rémi Verschelde 2017-08-07 13:50:31 CEST
*** Bug 21464 has been marked as a duplicate of this bug. ***
Comment 25 Rémi Verschelde 2017-08-07 13:51:25 CEST
Reopening as requested in bug 21464.

Please stop opening duplicates, just add a comment here if you want the bug reopened or if you want to provide new info. One issue = one bug report.

Status: RESOLVED => REOPENED
Resolution: INVALID => (none)

Comment 26 Nicolas Lécureuil 2017-08-07 15:51:46 CEST
*** Bug 21467 has been marked as a duplicate of this bug. ***

CC: (none) => joselp

Comment 27 Marja Van Waes 2017-08-07 17:53:08 CEST
*** Bug 21459 has been marked as a duplicate of this bug. ***
Comment 28 Frédéric "LpSolit" Buclin 2017-08-08 11:51:17 CEST
*** Bug 21467 has been marked as a duplicate of this bug. ***
Comment 29 Frédéric "LpSolit" Buclin 2017-08-08 12:08:09 CEST
With the recent update for cups-filters, can this bug be closed?
Comment 30 peter lawford 2017-08-08 12:17:55 CEST
NO! today I'm not at home and have no time to test; keep you aware of the course of events
thank you
Comment 31 Florian Hubold 2017-08-08 23:22:23 CEST
(In reply to Nicolas Lécureuil from comment #26)
> *** Bug 21467 has been marked as a duplicate of this bug. ***
(In reply to Frédéric Buclin from comment #28)
> *** Bug 21467 has been marked as a duplicate of this bug. ***

Those are actually duplicates to bug 21444 but not to this one ?
Comment 32 Florian Hubold 2017-08-08 23:34:19 CEST
(In reply to Philippe Makowski from comment #8)
> what is the result of :
> systemctl status cups.socket ?

The question that is more important is what's the result of

systemctl status cups.service

Because the socket is one thing, but if cupsd itself isn't running for whatever reason then the socket is useless.
Comment 33 Marja Van Waes 2017-08-08 23:49:01 CEST
(In reply to Florian Hubold from comment #32)
> (In reply to Philippe Makowski from comment #8)
> > what is the result of :
> > systemctl status cups.socket ?
> 
> The question that is more important is what's the result of
> 
> systemctl status cups.service
> 
> Because the socket is one thing, but if cupsd itself isn't running for
> whatever reason then the socket is useless.

Thanks, Florian and Philip, I added those questions to the "all other issues" part of https://wiki.mageia.org/en/Triage_guide#Printer_problems

Feel free to improve the Printer_problems section (or any other section of the triage guide).
Comment 34 Florian Hubold 2017-12-02 16:24:04 CET
With all the duplicates and this bug being reopened despite comment 23, what is the current status Peter?
Comment 35 peter lawford 2017-12-02 16:38:41 CET
old printer HP officejet 7300 works very well, but it's not the case of the other newer printer HP officejet 8000, but for the latter one I'm sure it's due to the printer itself and not to the system; production quality are deteriorating at HP, but only for HP I am afraid.
Comment 36 peter lawford 2017-12-02 16:39:19 CET
(In reply to Florian Hubold from comment #34)
> With all the duplicates and this bug being reopened despite comment 23, what
> is the current status Peter?

old printer HP officejet 7300 works very well, but it's not the case of the other newer printer HP officejet 8000, but for the latter one I'm sure it's due to the printer itself and not to the system; production quality are deteriorating at HP, but only for HP I am afraid.
Comment 37 Florian Hubold 2017-12-05 14:36:24 CET
So I'm gonna close this one, there's nothing we can do for a printer that isn't know to be working in the first place.

Status: REOPENED => RESOLVED
Resolution: (none) => INVALID

Comment 38 Tech Support 2018-11-18 09:15:28 CET
If the problem is black ink in yellow printed areas, these steps will not solve the issue. The Black/Yellow printhead needs replacing. Contact HP, and please be prepared to tell the agent how often the problem occurs, and what steps, if any, you have taken to solve the problem. To know more visit - https://macsupportnumber.com/blog/how-to-connect-ps4-controller-to-mac/

CC: (none) => seansopherfield

Comment 39 peter lawford 2018-11-18 18:10:00 CET
(In reply to Tech Support from comment #38)
> If the problem is black ink in yellow printed areas, these steps will not
> solve the issue. The Black/Yellow printhead needs replacing. Contact HP, and
> please be prepared to tell the agent how often the problem occurs, and what
> steps, if any, you have taken to solve the problem. To know more visit -
> https://macsupportnumber.com/blog/how-to-connect-ps4-controller-to-mac/

6 months I have no problem with the old printer HP 7310: about HP Officejet Pro 8000 a809, I trashed it months ago, which means that HP's quality manufacturing is worst and worst with time (and not only for HP); for HP7310, I no longer use original HP cartridges, but compatibles ones: it's much cheaper and better work

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