Bug 1329806

Summary: system-config-printer-udev causes HP LaserJet 1020 to malfunction
Product: [Fedora] Fedora Reporter: Jonas Jonsson <jonas>
Component: system-config-printerAssignee: Zdenek Dohnal <zdohnal>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 26CC: jpopelka, twaugh
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-29 11:54:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Log when udev-configure-printer fails to read device id none

Description Jonas Jonsson 2016-04-23 11:31:36 UTC
Created attachment 1149972 [details]
Log when udev-configure-printer fails to read device id

Description of problem:
When I plug in a HP LaserJet 1020 into my computer, it's detected, asks if hplip or foo2zjs should be installed but I can't printer after hplip has been installed.

I can hear that the firmware is loaded into the printer. The printer makes some noise when powered on, goes silent for a moment and then starts to make noise again when the firmeware is loaded.

I've debugged this issue for some time and it seems that system-config-printer-udev is to quick to query the printer (or whatever it does) before the firmware has been loaded into the printer.

By adding 
 ExecStartPre=/usr/bin/sleep 15
to configure-printer@.service the printer works as expected.

This is also very visible in the logs as well. I've attached log when this fails. The udev-configure-printer fails to fetch the device id. This happens while printer makes its "loading firmware noise". The sleep workaround above ensures that the firmware is finished loading.


Version-Release number of selected component (if applicable):
system-config-printer-udev-1.5.7-5.fc23.x86_64
hplip-3.16.2-1.fc23.x86_64

How reproducible:
Always.


Steps to Reproduce:
1. Plug in printer
2. Try to print a test page using cups web interface

Actual results:
Nothing printed.

Expected results:
Test page printed.

Comment 1 Fedora Admin XMLRPC Client 2016-06-24 10:41:46 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 2 Fedora End Of Life 2016-11-25 07:27:09 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2016-12-20 20:06:39 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 4 Jonas Jonsson 2017-08-21 10:08:30 UTC
This still happens on Fedora 26

system-config-printer-udev-1.5.9-4.fc26.x86_64

Workaround in original report still works.

Comment 5 Fedora End Of Life 2018-05-03 08:41:57 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2018-05-29 11:54:03 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.