Bug 785403 - RFE: Clarify evince's messages about malformed PDFs
Summary: RFE: Clarify evince's messages about malformed PDFs
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: evince
Version: 16
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: 2012-01-28 18:00 UTC by Phill Wolf
Modified: 2013-02-13 19:05 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 19:04:51 UTC
Type: ---


Attachments (Terms of Use)

Description Phill Wolf 2012-01-28 18:00:13 UTC
Description of problem:

Evince (and only evince) won't display my electric bills.  BZ726991 established that the PDFs are malformed and evince is rejecting them by design.  

Enhancement is requested to make evince state clearly that there is something wrong with the PDF, as opposed to evince itself; and furthermore, to couch the messages in sentences complete and unambiguous enough to penetrate layers of "customer service".


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

evince-3.2.1-2.fc16.x86_64
poppler-0.18.0-2.fc16.x86_64.


Steps to Reproduce:

Open an electric-bill PDF with evince.  Big chunks missing.  Messages on standard error.  See BZ726991.
  
Actual results:

Evince's messages look like this:

Error (15359): Too few (2) args to 'Tm' operator
Error (15359): Too few (2) args to 'Tm' operator
Error (41897): Too few (2) args to 'Tm' operator

Expected results:

It would be nice to make these additional points explicitly, if they are true:

(1) The message pertains to a problem with the PDF file.  

(2) The PDF file is malformed with respect to PDF specification, version xyz, stated at http://foo.  

(3) The problem is at or near location nnn inside the PDF file.  

(4) Because of the above problem, there is no way to be certain how this document was intended to look.

(5) Please send the above to whoever gave you this PDF.

Furthermore, if there is a brief security-related justification for rejecting malformed PDFs, it would be helpful to state it or refer to it.

Comment 1 Fedora End Of Life 2013-01-16 15:54:27 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 WONTFIX if it remains open with a Fedora 
'version' of '16'.

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 prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Fedora End Of Life 2013-02-13 19:05:02 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.

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.