Bug 1207154 - Should ignore 'cups-waiting-for-job-completed' job state reason
Summary: Should ignore 'cups-waiting-for-job-completed' job state reason
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-settings-daemon
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Marek Kašík
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-30 10:44 UTC by Tim Waugh
Modified: 2016-07-19 13:17 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 13:17:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Tim Waugh 2015-03-30 10:44:10 UTC
Description of problem:
When printing to a network printer use any of the ipp, lpd, socket, or dnssd backends, the cups-waiting-for-job-completed job state reason is normal and should not cause a desktop notification.

Version-Release number of selected component (if applicable):
gnome-settings-daemon-3.16.0-1.fc22.x86_64
cups-2.0.2-5.fc22.x86_64

Comment 1 Marek Kašík 2015-05-20 13:16:35 UTC
Hi,

I've pushed a patch fixing this to upstream's gnome-3-16 and master branches. It will get into Fedora with gnome-settings-daemon-3.16.2 release once it is released (although, I'm not sure when it will happen).

Regards and thank you for the notification

Marek

Comment 2 Fedora End Of Life 2016-07-19 13:17:05 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.


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