Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1444651 - Unable to print on HP Printers after upgrade from Fedora 25 to Fedora 26 Alpha
Summary: Unable to print on HP Printers after upgrade from Fedora 25 to Fedora 26 Alpha
Keywords:
Status: CLOSED DUPLICATE of bug 1440502
Alias: None
Product: Fedora
Classification: Fedora
Component: cups
Version: 26
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Zdenek Dohnal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: RejectedBlocker
Depends On:
Blocks: F26BetaBlocker
TreeView+ depends on / blocked
 
Reported: 2017-04-23 17:55 UTC by Sumit Bhardwaj
Modified: 2017-04-25 12:27 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-25 12:27:52 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
Journald log captured while giving print (93.07 KB, text/plain)
2017-04-23 17:55 UTC, Sumit Bhardwaj 		no flags Details
HPLIP Gui showing stopped print job (66.81 KB, image/png)
2017-04-23 17:56 UTC, Sumit Bhardwaj 		no flags Details
View All

Description Sumit Bhardwaj 2017-04-23 17:55:09 UTC 
Created attachment 1273463 [details]
Journald log captured while giving print

Description of problem:
Upgraded a fully updated Fedora 25 Workstation to Fedora 26 Alpha Workstation. Before upgrade, I was using a HP Deskjet 2520hc printer with hplip and cups to print in Fedora 25. But after upgrade, the printing does not happen.

On giving print from any application, I get messages Printing Started and Printing Stopped. HPLip  GUI shows print jobs as stopped.

Screenshot of the HPLIP GUI and journald log generated at the time are attached.

Version-Release number of selected component (if applicable):
Cups
===========
cups-pk-helper-0.2.6-2.fc26.x86_64
cups-libs-2.2.2-5.fc26.x86_64
cups-filters-libs-1.13.4-1.fc26.x86_64
cups-libs-2.2.2-5.fc26.i686
cups-filesystem-2.2.2-5.fc26.noarch
cups-client-2.2.2-5.fc26.x86_64
cups-2.2.2-5.fc26.x86_64
cups-filters-1.13.4-1.fc26.x86_64
python3-cups-1.9.72-11.fc26.x86_64

HPLip
========
hplip-3.16.11-7.fc26.x86_64
hplip-gui-3.16.11-7.fc26.x86_64
hplip-libs-3.16.11-7.fc26.x86_64
hplip-common-3.16.11-7.fc26.x86_64


How reproducible:
Try printing anything. 

Steps to Reproduce:
1. Connect the printer to machine.
2. Open a document or image and give print.
3. Select the correct printer in dialog and click print.

Actual results:
Printer should print the document. Document should successfully removed from the print queue.

Expected results:
Document is not printed and remains in print queue in Stopped state.

Additional info:
The log captured was taken while printing an image /home/sumitb/ACC_Poster/Poster.jpg using eog ("image viewer").
Comment 1 Sumit Bhardwaj 2017-04-23 17:56:02 UTC 
Created attachment 1273464 [details]
HPLIP Gui showing stopped print job
Comment 2 Zdenek Dohnal 2017-04-24 11:23:12 UTC 
Hi,

would you mind re-installing your printer with:

1) $ hp-setup -r
2) $ hp-setup
3) $ hp-plugin -i

if it helps? You can also try 'systemctl reload dbus' or 'setenforce 0' - if that dbus log from journald is really source of issue.
Comment 3 Sumit Bhardwaj 2017-04-24 16:59:56 UTC 
(In reply to Zdenek Dohnal from comment #2)
> Hi,
> 
> would you mind re-installing your printer with:
> 
> 1) $ hp-setup -r
> 2) $ hp-setup
> 3) $ hp-plugin -i
> 
> if it helps? You can also try 'systemctl reload dbus' or 'setenforce 0' - if
> that dbus log from journald is really source of issue.

Completed the mentioned steps. First steps asked for removal of Print queue, allowed. Second step ran GUI setup to create the queue again, done. Third step asked to download and reinstall the hp-plugin, done.

Reloaded dbus daemon and selinux is already on permissive mode on my system. Did setenforce 0 nevertheless. 

Still the issue remains same as before.
Comment 4 Geoffrey Marr 2017-04-24 19:10:54 UTC 
Discussed during the 2017-04-24 blocker review meeting: [1]

The decision to classify this bug as a "RejectedBlocker" was made as it currently does not violate any blocker criteria. If it can be successfully reproduced on several different setups, we will consider it as a Freeze Exception.

[1] https://meetbot.fedoraproject.org/fedora-blocker-review/2017-04-24/f26-blocker-review.2017-04-24-16.00.txt
Comment 5 Zdenek Dohnal 2017-04-25 12:27:52 UTC 
Closing as duplicate of #1440502.

*** This bug has been marked as a duplicate of bug 1440502 ***
Note You need to log in before you can comment on or make changes to this bug.