Bug 1012153

Summary:	cups-pdf should report failures when generating/storing PDFs in e-mail to the user
Product:	[Fedora] Fedora	Reporter:	Dale R. Worley <worley>
Component:	cups-pdf	Assignee:	Remi Collet <fedora>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	19	CC:	fedora
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-26 04:28:34 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:

Description Dale R. Worley 2013-09-25 20:30:08 UTC

(related to https://bugzilla.redhat.com/show_bug.cgi?id=1010434)

Description of problem:

Various problems can cause cups-pdf to be unable to generate or store the PDF.  Currently failures are reported only in /var/log/cups/cupsd-pdf_log, which is not readable by ordinary users.  (Failures will be reported after https://bugzilla.redhat.com/show_bug.cgi?id=1010434 is fixed.)

It would be much easier for users if cups-pdf would report errors to the user via e-mail, similar to how cron reports output from cron jobs.  I believe that this would not be difficult for cups-pdf to do.

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

cups-pdf-2.6.1-4.fc19.x86_64

How reproducible:

reproducible

Steps to Reproduce:
1. Set the selinux label of ~/Desktop to unconfined_u:object_r:default_t:s0
2. Print to CUPS-PDF (e.g., using Firefox or Libreoffice)
3. Remember to restore the selinux label of ~/Desktop to unconfined_u:object_r:user_home_t:s0 afterward!

Actual results:

No user-visible indication of failure, other than that the PDF file is not inserted into ~/Desktop.

Expected results:

Desired results are positive notification of the user that PDF generation failed.

Additional info:

Comment 1 Remi Collet 2013-09-26 04:28:34 UTC

Thanks for this report, but such a request for change have to be proposed to cups-pdf upstream. It's a big change which cannot be simply implement by a trivial patch.

This this is not a bug (as not a feature of current cups-pdf version), but a RFC.

So closing this one.

Comment 2 Dale R. Worley 2013-09-26 14:58:11 UTC

(In reply to Remi Collet from comment #1)
> Thanks for this report, but such a request for change have to be proposed to
> cups-pdf upstream.

OK, that's cool...  But could you give me *some hint* as to where or how to do that rather than just giving me the brushoff?  This is, after all, the issue tracker for Fedora, isn't it?

Comment 3 Remi Collet 2013-09-26 15:31:03 UTC

(In reply to Dale R. Worley from comment #2)
> (In reply to Remi Collet from comment #1)
> > Thanks for this report, but such a request for change have to be proposed to
> > cups-pdf upstream.
> 
> OK, that's cool...  But could you give me *some hint* as to where or how to
> do that rather than just giving me the brushoff? 

$ yum info cups-pdf
URL         : http://www.cups-pdf.de/

>  This is, after all, the issue tracker for Fedora, isn't it?

Yes "issue" tracker. And as explained above, this is not an issue.

Comment 4 Dale R. Worley 2013-10-04 19:50:02 UTC

(In reply to Remi Collet from comment #3)
> $ yum info cups-pdf
> URL         : http://www.cups-pdf.de/

Ah, thanks, I didn't know that yum provided that information.

> >  This is, after all, the issue tracker for Fedora, isn't it?
> 
> Yes "issue" tracker. And as explained above, this is not an issue.

In every software operation I've ever been involved with, the term "issue" explicitly included both bug reports and enhancement requests.  I eventually figured out that it was because it could take quite a bit of investigation to determine whether an item was a bug or feature request.

Comment 5 Dale R. Worley 2013-10-04 19:55:47 UTC

Reported to Volker Christian Behr, who appears to be the maintainer of cups-pdf.